test-and-lint-runner

Focused tests and linting checks are executed by discovering the project's validation commands and running the smallest useful command for your changed files. This avoids triggering full, broad repository-wide validation suites unnecessarily.

Non-interactive syntax checks for Python and TypeScript are performed by applying timeout-aware validation. The system executes targeted builds or checks and reports failures clearly without requiring any interactive user prompts during the process.

Yes, automated linting, type checking, and build validation are supported for MCUB workflows. The system inspects project configurations to find and execute the appropriate validation commands for these specific environments.

Project validation commands are found through check discovery, which reads your project docs and config files. This discovery process ensures the correct tests and linting commands are selected before executing focused validation.

Failing tests and linting errors are reported through safe failure handling, which preserves the exact failing commands and relevant errors. This approach prevents the validation process from chasing unrelated issues across the project.

The test-and-lint-runner works with Python, JavaScript, TypeScript, and MCUB workflows. It selects and runs the smallest useful validation command for code changes across these supported non-interactive software projects.