How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

run-tests-and-coverage - Prompt

Name: run-tests-and-coverage
Author: juanroyofullstack

Prompt file imported from juanroyofullstack/donet-aspire-server (.github/prompts/run-tests-and-coverage.prompt.md). Copyright stays with the author.

Run tests and coverage

Run the .NET tests in this repository and generate a code coverage report, including an HTML version for visual inspection.

Instructions

Use the test project path provided by the user.
If no path is provided, default to:
- tests/NetAspireServer.Application.Tests.csproj
Before running the tests, delete stale coverage artifacts from the repository root to avoid mixing old XMLs from other suites:
- rm -rf TestResults CoverageReport
Run the command:
- dotnet test --collect:"XPlat Code Coverage" --results-directory TestResults --settings coverlet.runsettings
After the test run, generate an HTML coverage report from the Cobertura XML with ReportGenerator using:
- reportgenerator -reports:"TestResults/**/coverage.cobertura.xml" -targetdir:"CoverageReport" -reporttypes:Html
Show:
- the summary of the executed tests
- whether the coverage report was generated
- the path of the generated XML coverage file
- the path of the generated HTML coverage report
If tests fail, stop and summarize the errors clearly.

Expected behavior

Work from the repository root.
Use coverage collection explicitly.
Generate both the raw XML and the HTML report.
If the project does not exist, report it and suggest the correct path.

# Run tests and coverage Run the .NET tests in this repository and generate a code coverage report, including an HTML version for visual inspection. ## Instructions 1. Use the test project path provided by the user. 2. If no path is provided, default to: - tests/NetAspireServer.Application.Tests.csproj 3. Before running the tests, delete stale coverage artifacts from the repository root to avoid mixing old XMLs from other suites: - rm -rf TestResults CoverageReport 4. Run the command: - dotnet test <project-path> --collect:"XPlat Code Coverage" --results-directory TestResults --settings coverlet.runsettings 5. After the test run, generate an HTML coverage report from the Cobertura XML with ReportGenerator using: - reportgenerator -reports:"TestResults/**/coverage.cobertura.xml" -targetdir:"CoverageReport" -reporttypes:Html 6. Show: - the summary of the executed tests - whether the coverage report was generated - the path of the generated XML coverage file - the path of the generated HTML coverage report 7. If tests fail, stop and summarize the errors clearly. ## Expected behavior - Work from the repository root. - Use coverage collection explicitly. - Generate both the raw XML and the HTML report. - If the project does not exist, report it and suggest the correct path.

Install run-tests-and-coverage and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "prompt": "# Run tests and coverage\n\nRun the .NET tests in this repository and generate a code coverage report, including an HTML version for visual inspection.\n\n## Instructions\n\n1. Use the test project path provided by the user.\n2. If no path is provided, default to:\n - tests/NetAspireServer.Application.Tests.csproj\n3. Before running the tests, delete stale coverage artifacts from the repository root to avoid mixing old XMLs from other suites:\n - rm -rf TestResults CoverageReport\n4. Run the command:\n - dotnet test <project-path> --collect:\"XPlat Code Coverage\" --results-directory TestResults --settings coverlet.runsettings\n5. After the test run, generate an HTML coverage report from the Cobertura XML with ReportGenerator using:\n - reportgenerator -reports:\"TestResults/**/coverage.cobertura.xml\" -targetdir:\"CoverageReport\" -reporttypes:Html\n6. Show:\n - the summary of the executed tests\n - whether the coverage report was generated\n - the path of the generated XML coverage file\n - the path of the generated HTML coverage report\n7. If tests fail, stop and summarize the errors clearly.\n\n## Expected behavior\n\n- Work from the repository root.\n- Use coverage collection explicitly.\n- Generate both the raw XML and the HTML report.\n- If the project does not exist, report it and suggest the correct path.", "variables": [], "notes": "Runs .NET tests and generates XPlat Code Coverage for a specific project. Mode: agent.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/juanroyofullstack/donet-aspire-server", "path": ".github/prompts/run-tests-and-coverage.prompt.md", "ref": "d2d67d01dc63824dd720e0f6f3e4df32d73087bf", "url": "https://github.com/juanroyofullstack/donet-aspire-server/blob/d2d67d01dc63824dd720e0f6f3e4df32d73087bf/.github/prompts/run-tests-and-coverage.prompt.md", "key": "juanroyofullstack/donet-aspire-server/.github/prompts/run-tests-and-coverage.prompt.md" } } }

run-tests-and-coverage

About

Run tests and coverage

Instructions

Expected behavior

Use it

Install run-tests-and-coverage and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews