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
- Removed referenced to -UserAuth since that flag no longer exists
- Removed VisualStudioCodeCredential as a test credential option. This
credential has long been broken and is being deprecated soon.
Signed-off-by: Paul Van Eck <[email protected]>
Copy file name to clipboardExpand all lines: doc/dev/tests.md
+3-8Lines changed: 3 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -174,15 +174,12 @@ Live Azure resources will be necessary in order to run live tests and produce re
174
174
resource management commands, documented in [/eng/common/TestResources][test_resources], that streamline this process.
175
175
Both pure ARM templates (`test-resources.json`) and BICEP files (`test-resources.bicep`) are supported.
176
176
177
-
User-based authentication is preferred when using test resources. To enable this:
178
-
- Use the [`-UserAuth` command flag][user_auth_flag] when running the `New-TestResources` script.
177
+
User-based authentication is preferred when using test resources. The `New-TestResources` script defaults to user-based authentication. To use it:
179
178
- Choose a development tool to authenticate with by setting an `AZURE_TEST_USE_*_AUTH` environment variable to "true" (tests will authenticate as the tool's logged-in user). The following tools are supported, listed in the order that authentication will be attempted in if requested:
180
179
1. Azure PowerShell: set `AZURE_TEST_USE_PWSH_AUTH`.
181
180
2. Azure CLI (`az`): set `AZURE_TEST_USE_CLI_AUTH`.
182
-
3. Visual Studio Code: set `AZURE_TEST_USE_VSCODE_AUTH`.
183
181
4. Azure Developer CLI (`azd`): set `AZURE_TEST_USE_AZD_AUTH`.
184
-
- Ensure you're logged into the tool you choose -- if
185
-
you used `New-TestResources.ps1` to deploy resources, you'll already have logged in with Azure PowerShell.
182
+
- Ensure you're logged into the tool you choose -- if you used `New-TestResources` to deploy resources, you'll already have logged in with Azure PowerShell.
186
183
187
184
**Important:** these environment variables will only be successfully used if test credentials are fetched with the
188
185
[`AzureRecordedTestCase.get_credential`][get_credential] method. See [Write your tests](#write-your-tests) for details.
@@ -215,11 +212,10 @@ environment variables necessary to run live tests for the service. After storing
215
212
-- formatted as `VARIABLE=value` on separate lines -- your credentials and test configuration variables will be set in
216
213
our environment when running tests.
217
214
218
-
If you used the [`-UserAuth` command flag][user_auth_flag]to deploy test resources, choose a development tool to
215
+
Since `New-TestResources` defaults to user-based authentication, choose a development tool to
219
216
authenticate with by setting an `AZURE_TEST_USE_*_AUTH` environment variable to "true". The following tools are supported, listed in the order that authentication will be attempted in if requested:
220
217
1. Azure PowerShell: set `AZURE_TEST_USE_PWSH_AUTH`.
221
218
2. Azure CLI (`az`): set `AZURE_TEST_USE_CLI_AUTH`.
222
-
3. Visual Studio Code: set `AZURE_TEST_USE_VSCODE_AUTH`.
223
219
4. Azure Developer CLI (`azd`): set `AZURE_TEST_USE_AZD_AUTH`.
224
220
225
221
**Important:** these environment variables will only be successfully used if test credentials are fetched with the
@@ -611,4 +607,3 @@ For information about more advanced testing scenarios, refer to the [advanced te
0 commit comments