rerecord-tests

name

rerecord-tests

description

Re-record the ai-projects live test suite, push only the recordings whose playback passes to the Azure/azure-sdk-assets repo, and open a PR for the updated assets.json. Use when test recordings are stale, a recorded test fails in playback in CI, or new recorded tests need fresh recordings. Wraps TEST_MODE=record / TEST_MODE=playback runs, dev-tool test-proxy push, and a single-file assets.json PR via the gh CLI.

Re-record ai-projects tests and publish recordings

Records the live test suite for @azure/ai-projects, verifies the new recordings play back green, pushes only the passing recordings to the Azure/azure-sdk-assets repo, and opens a PR that contains just the updated assets.json tag.

This package uses the asset-sync workflow: recordings live in Azure/azure-sdk-assets, not in this repo. The only file that lands in a PR is assets.json, whose Tag points at the pushed recordings. See sdk/test-utils/recorder/ASSET_SYNC_WORKFLOW.md.

When to Use

• Recordings are stale and the recorded test suite fails in playback mode.
• New recorded tests were added (e.g. after the author-tests skill) and need real recordings captured against live Azure resources.
• A deliberate re-record is requested to refresh assets.json.

Prerequisites

• Live Azure access. Record mode hits real Foundry resources. You must be authenticated (az login, or a working DefaultAzureCredential) and have the test environment variables populated. Key ones (see ): , , , , , plus the connection-id vars for the tool tests. Missing vars only fail the tests that need them — those recordings are simply not pushed (see "Only passing recordings", below).