Azsdk Common Live And Recorded Tests

What it does

When your agent uses it

• : writing new tests
• Authoring Bicep templates
• Playback-only test runs without resource deployment

Example prompts

• “run live tests”
• “run recorded tests”
• “deploy test resources”
• “/azsdk-common-live-and-recorded-tests”

Requirements

• Compatibility (from SKILL.md): azure-sdk-mcp server, Azure PowerShell (Az module), local azure-sdk-for-{language} clone

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

1. 1Identify service directory — Determine the service directory for the package under test (e.g., keyvault, storage). This is required by the…
2. 2Check for existing deployment — Look for a .env file at either the service directory level (next to test-resources.bicep, e.g…
3. 3Verify Azure context — Run Get-AzContext to check for an active Azure PowerShell session. If the command fails because the Az module is…
4. 4Confirm deployment — Even if no existing .env file is found, confirm with the user before proceeding to deploy test resources. Deployment…
5. 5Deploy test resources — Run eng/common/TestResources/New-TestResources.ps1 with the service directory, tenant ID, subscription ID, and any…
6. 6Save environment — Capture the environment variables output by the deployment script. If the script writes a .env file, note its path…
7. 7Run tests — Call the azure-sdk-mcp:azsdk_package_run_tests MCP tool (do NOT run test commands directly in the terminal). Provide the…
8. 8Clean up — Ask the user whether to clean up test resources. If yes, run eng/common/TestResources/Remove-TestResources.ps1. If no, inform…

What it can do on your machine

Read from SKILL.md and the folder at commit 942ef24. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • dotnet
  • mvn
  • npm
  • go

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  azure-sdk-mcp server, Azure PowerShell (Az module), local azure-sdk-for-{language} clone

  From compatibility in the SKILL.md frontmatter.

Context cost

Azsdk Common Live And Recorded Tests loads about 1.5k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 115 tokens; SKILL.md has 746 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~115

When it runs · the whole SKILL.md, loaded when a task matches

~1.5k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~3.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:31

  for existing deployment** — Look for a `.env` file at either the service directory level  (next to `test-resources.bice

• NoteMentions a .env fileSKILL.md:33

  firm deployment** — Even if no existing `.env` file is found, confirm with the user before proceeding to deploy test res

• NoteMentions a .env fileSKILL.md:35

  ployment script. If the script writes a `.env` file, note its path. Otherwise, collect the environment variables from th

• NoteMentions a .env fileSKILL.md:36

  ve`, or `playback`) and the path to the `.env` file containing test environment variables. When tests run in record mode

• NoteMentions a .env fileSKILL.md:42

  ng the live test deployment specified in .env"

• NoteMentions a .env fileSKILL.md:53

  are being passed correctly. Verify the `.env` file path is correct.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Azure/azure-sdk-tools at commit 942ef24, republished under its MIT licence (© Azure). 746 words, ~1,514 tokens.

name

azsdk-common-live-and-recorded-tests

description

Deploy test resources and run Azure SDK tests in live, record, or playback mode. WHEN: "run live tests", "run recorded tests", "deploy test resources", "record tests", "run tests in record mode", "clean up test resources", "run tests against live resources". DO NOT USE FOR: writing new tests, authoring Bicep templates, playback-only test runs without resource deployment. INVOKES: azure-sdk-mcp:azsdk_package_run_tests.

compatibility

azure-sdk-mcp server, Azure PowerShell (Az module), local azure-sdk-for-{language} clone

license

MIT

metadata.version

0.1.0

metadata.distribution

shared

© Azure, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in plugins/azure-sdk-tools/skills/live-and-recorded-tests of Azure/azure-sdk-tools.

• SKILL.md
• eval.yaml
• references/test-modes.md
• references/test-resource-cleanup.md
• references/test-resource-deployment.md
• tasks/anti-trigger-write-tests.yaml
• tasks/anti-trigger.yaml
• tasks/cleanup-resources.yaml
• tasks/deploy-and-run-live.yaml
• tasks/record-with-env.yaml

Open the folder on GitHubat commit 942ef24