testing-workflow

Container-based testing executes your test suite in a isolated, reproducible runtime environment. This eliminates false negatives caused by host configuration differences. Use pytest within your devcontainer to run fast unit tests or full slow suites with guaranteed consistency across machines.

Running pytest in a container guarantees your tests execute in the exact runtime conditions your code will face in production. Host machines have varying dependencies, configurations, and environment variables that can cause tests to pass locally but fail elsewhere. Container execution removes these variables.

During in-container test validation, retrieve API tokens programmatically using environment setup steps that extract credentials securely. The testing workflow includes steps to obtain and inject API tokens so authentication workflows can be tested without manual credential entry.

Before running pytest, reset your environment to reflect the latest code and dependencies by executing the devcontainer setup script, then wait for initialization to complete. This ensures all required packages and configurations are current before test execution begins.

Yes, the container-based workflow supports running both fast unit tests for rapid feedback and full slow suites for comprehensive validation. Both execution modes run inside the devcontainer to maintain consistent runtime conditions and reduce environment-related test flakiness.