testing

End-to-end testing for CLI applications with pytest and vcrpy involves implementing structured test plans, VCR-based recordings, and subprocess flows. This skill enforces the _resolve_cli pattern to ensure reliable execution across local development and CI pipelines.

Documenting CLI test plans and results requires generating a TEST.md file containing Part 1 for the test plan and Part 2 for the results. This documentation-driven workflow ensures reliable software delivery for unit, E2E, and subprocess tests.

Subprocess testing for CLI tools in a CI pipeline uses the _resolve_cli subprocess pattern to ensure reliability. This approach supports stable parsing and execution across local development, CI pipelines, and pre-release validation.

Yes, vcrpy works with browser-delegated authentication flows in E2E tests by using VCR-based recordings and test fixtures. This ensures stable parsing and reliable testing for auth workflows and RPC-like interactions.

Before running E2E tests for CLI applications, you need pytest, vcrpy, and related tooling available in your environment. You also need a structured test plan covering unit, E2E, and subprocess flows for your cli-web apps.

VCR-based recordings for CLI testing provide stable parsing and reproducible results across local development and CI pipelines. Unlike mocking, VCR recordings capture real auth workflows and RPC-like interactions for reliable pre-release validation.