-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove hard-coded Fiddler code in tests #205
Milestone
Comments
Moving code to public fork. |
Verified |
g2vinay
pushed a commit
to g2vinay/azure-sdk-for-java
that referenced
this issue
Mar 4, 2019
5.5.0 Release
sima-zhu
pushed a commit
to sima-zhu/azure-sdk-for-java
that referenced
this issue
Mar 21, 2019
Using Heap based buffer explicitly for response contents
g2vinay
pushed a commit
to g2vinay/azure-sdk-for-java
that referenced
this issue
Jul 9, 2019
* Remove CosmosResource * Naming and JavaDocs updates * Move Scripts to CosmosScripts object * Add header * Fix JavaDoc build error * Fix up CosmosScripts + tests
navalev
pushed a commit
to navalev/azure-sdk-for-java
that referenced
this issue
Dec 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Dev estimate: 0
Test estimate: 0.5
In the following test files have hard-coded references to Fiddler
(Note that the code is not commented by default.)
Fiddler is not available cross-platform, and is not installed or running by default, which can lead to spurious, hard-to-debug test failures.
Testers can enable Fiddler via VM settings instead, to leave the code clean. For example, in my using their VM setup instead. For example, I set the following VM arguments to enable Fiddler when running the tests on my machine:
The text was updated successfully, but these errors were encountered: