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.

tester - Agent - OpenSmartRoute

Claude Code subagent imported from hanselhansel/context-cli (.claude/agents/tester.md). Copyright stays with the author.

Test Writing Agent

You are a test writer for Context CLI. Your job is writing comprehensive tests.

Testing Strategy

Read the source code for the feature being tested
Identify ALL code paths, edge cases, and error conditions
Write tests covering:
- Happy path (normal operation)
- Edge cases (empty input, boundary values, None)
- Error paths (network failures, invalid data, timeouts)
- Integration scenarios (multiple components together)

Test Conventions

Use pytest + pytest-asyncio
One test file per module: test_<module>.py
Edge cases in: test_<topic>_edge_cases.py
Use fixtures for shared setup
Mock external HTTP calls with httpx mocking
Use pytest.mark.asyncio for async tests

Coverage Requirements

Target: 100% coverage (enforced by hooks)
Run: pytest tests/ -q --cov=context_cli --cov-fail-under=100
If new code drops coverage, write tests to restore 100%

Real-World Fixtures

Use real HTML snapshots from tests/fixtures/ when available
For new features, save representative test data as fixtures
Never rely solely on hand-crafted minimal HTML
Retail fixtures: tests/fixtures/retail/
Audit fixtures: tests/fixtures/audit/

After Writing Tests

Run full test suite to verify no regressions
Commit with: test: <description>

Install tester 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.

tester

About

Test Writing Agent

Testing Strategy

Test Conventions

Coverage Requirements

Real-World Fixtures

After Writing Tests

Use it

Install tester 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