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

Source the resource-limit loader before testing. It loads the ignored machine-local testing.env from the primary checkout, including from linked worktrees.

source .claude/skills/testing/load-env.sh

If testing.env doesn't exist, the loader uses safe defaults and the agent should suggest creating one (see testing.env.example). Never infer the machine profile or job limits from the hostname or CPU count.

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. Load machine-local environment and resource limits
source .claude/skills/testing/load-env.sh

# 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 with the machine-local parallelism limit
cmake --build build --parallel "$PYPTO_BUILD_JOBS"

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

# 5. Run tests
python -m pytest tests/ut/ -n "$PYPTO_TEST_JOBS" -v

Test Commands

# Run all tests
python -m pytest tests/ut/ -n "$PYPTO_TEST_JOBS" -v

# Run specific test file
python -m pytest tests/ut/core/test_error.py -n "$PYPTO_TEST_JOBS" -v

# Run specific test
python -m pytest tests/ut/core/test_error.py::TestErrorTypes::test_value_error_type -n "$PYPTO_TEST_JOBS" -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 "$PYPTO_BUILD_JOBS" 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: Source .claude/skills/testing/load-env.sh. If the machine-local config doesn't exist, use its safe defaults and 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 pass the explicit machine-local limit with --parallel "$PYPTO_BUILD_JOBS"; never use bare --parallel or derive the value from CPU count.
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
• Always use the explicit machine-local build and test job limits
• Check both build and test output
• Look for new warnings even if tests pass
• Report both successes and failures clearly