agilab-testing

Quick, targeted test strategy for AGILAB (core unit tests, app smoke tests, regression).

⭐3stars🔀1forks📁View on GitHub🕐Updated Jan 9, 2026

When & Why to Use This Skill

The AGILAB Testing skill provides a streamlined and targeted testing strategy designed to validate code changes efficiently. It focuses on core unit tests, application smoke tests, and regression testing using pytest and uv, ensuring high software quality and reliability by prioritizing local validation and minimizing unnecessary test overhead.

Use Cases

  • Targeted Code Validation: Execute specific unit tests for modified files to get immediate feedback during the development cycle without running the entire suite.
  • Smoke Testing: Perform quick health checks on the application to ensure core functionalities are operational after updates or deployments.
  • Regression Testing: Run comprehensive tests across the repository to identify and resolve any breaking changes introduced by new code.
  • Coverage Optimization: Add lightweight unit tests for pure functions and helpers to improve code coverage without requiring complex environments like GPUs or network access.
nameagilab-testing
descriptionQuick, targeted test strategy for AGILAB (core unit tests, app smoke tests, regression).
licenseBSD-3-Clause (see repo LICENSE)
updated2026-01-09

Testing Skill (AGILAB)

Use this skill when validating changes.

Philosophy

  • Start small and local: run only the tests that cover the files you changed.
  • Avoid “fixing the world”: do not chase unrelated test failures.

Common Commands

  • Core tests (repo root):

    • uv --preview-features extra-build-dependencies run --no-sync pytest src/agilab/core/agi-env/test
    • uv --preview-features extra-build-dependencies run --no-sync pytest src/agilab/core/test
  • Whole repo tests (if needed):

    • uv --preview-features extra-build-dependencies run --no-sync pytest

Adding Coverage (Easy Wins)

  • Add narrow unit tests for pure functions/helpers (path resolution, parsing, small transforms).
  • Prefer tests that don’t require network, GPUs, or large datasets.