voyager-testlisted

# Run Tests Execute tests for Voyager SDK components targeting Axelera AI hardware ## Instructions Run tests based on the specified scope: **$ARGUMENTS** {{INCLUDE common/voyager-sdk-setup.md}} {{INCLUDE common/voyager-task-integration.md}} ### Step 1: Environment Setup - Read `.voyager-runtime.json` before choosing tests: - `package_for_linux`: run host-safe static/unit checks only and report that hardware/runtime tests were not executed. - `execute_on_device`: hardware/runtime tests may run when the SDK and device are visible. - The setup include (Step 0/Step 3) activates the SDK environment (`venv/` or `axelera-env/`); verify with `python -c "import axelera"`. - Test configuration lives in the SDK's `pyproject.toml` under `[tool.pytest.ini_options]` (testpaths: `tests`, `internal_tools_tests`, `run_tests.py`). Plain `pytest` from the SDK root uses those paths. - Install optional pytest plugins (`pytest-cov`, `pytest-xdist`, `pytest-html`, `pytest-random-order`) only when the user approves environment mutation. ### Step 2: Test Scope Identification Parse test scope from arguments: - `all`: Run all tests - `unit`: Run unit tests only - `runtime`: Run runtime-specific tests - `<module>`: Run tests for specific module - `<file>`: Run specific test file - `<pattern>`: Run tests matching pattern ### Step 3: Running Tests with Pytest This is the canonical flow; the SDK has no tox configuration. ```bash # Run all tests pytest tests/ # Run specific