[Test-Proxy] Point users to language repository test documentation #6368
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mccoyp
added
Docs
Test-Proxy
mccoyp
requested review from
benbp,
timovv,
kinelski,
jhendrixMSFT,
HarshaNalluru,
samvaity,
scbedd and
gearama
Merged
6 tasks
HarshaNalluru
approved these changes
Jun 26, 2023
scbedd
reviewed
Jun 27, 2023
| **To users writing SDK tests:** This document is not intended to be a test preperation reference. You should instead refer | ||
| to documentation in your specific language repository in order to configure recorded tests. | ||
|
|
||
| #### Test documentation by language: |
There was a problem hiding this comment.
We should add this to the asset-sync / test-proxy readme in sdk tools repo shouldn't we.
scbedd
approved these changes
Jun 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We recently had an instance where a partner team intended to set up the test proxy tool for testing their already-migrated Python library. Instead of referring to our language-specific test docs, though, they found this
azure-sdk-toolsdocumentation; this made them think that they had to set up the test proxy tool manually with .NET/Docker, but Python's tooling actually handles tool installation and startup for them.To avoid this issue, I think it would be good to have a disclaimer at the start of this document to let people know that this isn't meant for test writers' reference. I added links to what seem to be the test-writing guides for each language, but it would be great if each language's test proxy owner could double-check them 🙂