test-proxy

Publish test recordings and assets using the test-proxy CLI.

2.6k|2.2k|Updated Dec 6, 2011
One-click install
npx skills add https://github.com/Azure/azure-sdk-for-java --skill test-proxy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-proxy
Source: https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/ai/.workflow_docs/test-proxy
Command: npx skills add https://github.com/Azure/azure-sdk-for-java --skill test-proxy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of publishing test recordings and assets to a remote repository, ensuring consistency and efficiency in testing workflows.

Core Features & Use Cases

  • Recording Publication: Pushes test recordings and associated assets using the test-proxy CLI.
  • Asset Management: Facilitates the management and distribution of testing artifacts.
  • Use Case: When preparing to release a new version of a service, use this Skill to upload all newly generated test recordings and assets to the central test-proxy repository for validation and archival.

Quick Start

Use the test-proxy skill to push recordings and assets using the command test-proxy push -a assets.json.

Frequently Asked Questions about test-proxy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish test recordings and assets to a remote repository?

To publish test recordings and assets, use the test-proxy CLI to push testing artifacts to a designated repository. This automates the upload process for validation and archival, ensuring consistency across testing workflows.

What do I need to push test recordings using the test-proxy CLI?

To push test recordings, you need the test-proxy CLI installed and an assets JSON file present in your environment. These prerequisites facilitate the upload of testing artifacts to the central repository.

When should I upload test recordings and assets to a central repository?

You should upload test recordings and assets when preparing to release a new version of a service. Pushing newly generated testing artifacts to a central test-proxy repository ensures they are properly validated and archived.

How does the test-proxy push command work for managing testing artifacts?

The test-proxy push command works by taking an assets JSON file as input and uploading the specified test recordings and associated assets to a remote repository. This facilitates the management and distribution of testing artifacts.

What is the best way to automate publishing test recordings for validation?

The best way to automate publishing test recordings is using the test-proxy CLI with an assets JSON file. Running test-proxy push -a assets.json uploads all testing artifacts to a central repository for consistent validation and archival.