test-all

To run tests for modified services in a monorepo, you need a tool that detects changed files via git, discovers applicable test types, and executes them automatically. This Skill validates environment readiness and runs unit, integration, and e2e tests for affected microservices.

Automated test discovery in a monorepo identifies which services were modified by code changes and determines all applicable test types, including unit, integration, e2e, and performance tests. It ensures comprehensive coverage verification by targeting only the affected microservices.

Yes, you need git for change detection to identify modified services in your monorepo. The testing process relies on git history to determine which microservices changed, allowing it to selectively discover and execute relevant tests.

Yes, you can integrate this monorepo test execution into CI/CD pipelines and developer workflows. It validates the environment, runs all applicable tests for changed services, and produces a structured report detailing test results, failures, and coverage.

The best way to verify comprehensive test coverage after code changes is to automate detection of modified services, validate the testing environment, and execute all discovered test types. This generates a structured report summarizing results, failures, and overall coverage metrics.

A key limitation is the dependency on various language-specific test runners installed in your environment. If the required runners for a modified service's language are missing, environment validation will fail before test execution can proceed.