testing

name	testing
description	Verify testing coverage and run tests for PyPTO project. Use when running tests, checking test coverage, or when the user asks about testing.
context	fork

PyPTO Testing

You are a specialized testing agent. Build the project and run all tests to verify code changes haven't broken anything.

Environment Setup

If .claude/skills/testing/testing.env exists: Source it before testing.

[ -f .claude/skills/testing/testing.env ] && source .claude/skills/testing/testing.env

If doesn't exist: Skip and suggest creating one (see testing.env.example).

Testing Workflow

When working in a git worktree, always build and test from within the worktree — never copy .so files from the main repo. Create a build directory inside the worktree if one doesn't exist.

# 1. Activate environment (if testing.env exists)
[ -f .claude/skills/testing/testing.env ] && source .claude/skills/testing/testing.env

# 2. Configure CMake if build is not configured (worktree, fresh clone)
[ ! -f build/CMakeCache.txt ] && cmake -B build -DCMAKE_BUILD_TYPE=RelWithDebInfo

# 3. Build project (parallel)
cmake --build build --parallel

# 4. Set PYTHONPATH
export PYTHONPATH=$(pwd)/python:$PYTHONPATH

# 5. Run tests
python -m pytest tests/ut/ -n auto --maxprocesses 8 -v

Test Commands

# Run all tests
python -m pytest tests/ut/ -n auto --maxprocesses 8 -v

# Run specific test file
python -m pytest tests/ut/core/test_error.py -n auto --maxprocesses 8 -v

# Run specific test
python -m pytest tests/ut/core/test_error.py::TestErrorTypes::test_value_error_type -n auto --maxprocesses 8 -v

Test Structure

tests/ut/
├── core/          # Core functionality
├── ir/            # IR (nodes, expressions, operators, parser)
└── pass/          # Pass manager

Testing Checklist

• Project builds without errors
• No new compiler warnings
• All existing tests pass
• New features have tests
• Bug fixes have regression tests
• Tests in tests/ut/ (not elsewhere)

Common Issues

Issue	Solution
ImportError: No module named 'pypto_core'	export PYTHONPATH=$(pwd)/python:$PYTHONPATH
Tests fail after code changes	cmake --build build --parallel then re-run
Tests in wrong location	Move to tests/ut/
Build not configured (worktree/fresh clone)	cmake -B build -DCMAKE_BUILD_TYPE=RelWithDebInfo

Output Format

## Testing Summary
**Status:** ✅ PASS / ⚠️ WARNINGS / ❌ FAIL

### Build Results
[Compiler output, warnings/errors]

### Test Results
- Total: X | Passed: X | Failed: X | Skipped: X

### Failures
[Failed test details if any]

### Recommendations
[Actions to fix issues]

Decision Criteria

Status	Criteria
PASS	All tests pass, build succeeds, no new warnings
WARNINGS	Tests pass but new warnings or skipped tests
FAIL	Build fails or tests fail

Key Focus Areas

1. Environment: Check for and source .claude/skills/testing/testing.env if it exists. If it doesn't exist, show a helpful tip about creating it.
2. Build Setup: If build is not configured (no build/CMakeCache.txt), run cmake -B build to configure before building.
3. Build: Ensure project builds without errors or new warnings. Always use --parallel.
4. Python Path: Set PYTHONPATH correctly
5. Test Execution: Run all tests and analyze results
6. Coverage: Verify new features have tests, bug fixes have regression tests
7. Location: Ensure tests are in proper location (tests/ut/)

Remember

• Always rebuild before running tests
• Check both build and test output
• Look for new warnings even if tests pass
• Report both successes and failures clearly