You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/dev/dev_setup.md
+4-7Lines changed: 4 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ or execute the various commands available in the toolbox.
7
7
8
8
1. If you don't already have it, install Python:
9
9
10
-
- Windows: [Python website][python_website] or from the [Windows store][python_39]
10
+
- Windows: [Python website][python_website] or from the [Windows store][python_312]
11
11
- Ubuntu/Debian `sudo apt-get install python3`
12
12
- RHEL/CentOS `sudo yum install python3`
13
13
@@ -46,17 +46,14 @@ or execute the various commands available in the toolbox.
46
46
The recommended place to store your .env file is one directory higher than the `azure-sdk-for-python` location.
47
47
This ensures the secrets will be loaded by the interpreter and most importantly not be committed to Git history.
48
48
49
-
## Set up the SDK's test-running tool
49
+
## Follow test-running guidance
50
50
51
-
SDK tests use an in-house tool called the test proxy, which runs in a container and enables recording and playing back HTTP interactions.
52
-
53
-
Follow the instructions in the [Perform one-time test proxy setup][proxy_setup] section of [tests.md][tests] to set up the test proxy on your machine.
51
+
After following the steps above, you'll be able to run recorded SDK tests with `pytest`. For more information about tests -- how to run live tests, write new tests, etc. -- refer to the documentation in [tests.md][tests].
0 commit comments