Default models: When no .pysa and no .config file is present, the test runner automatically provides default test models (_test_sink, _test_source, etc.). When either file is present, the test must be self-contained.

Debugging Test Failures

When a test fails because expected output doesn't match:

1. The test runner prints a diff (may be truncated for large diffs)
2. It creates .actual files for each mismatched output (e.g., format.py.models.actual)
3. Use diff to compare expected vs actual:

diff source/interprocedural_analyses/taint/test/integration/format.py.models \
     source/interprocedural_analyses/taint/test/integration/format.py.models.actual

If the test fails with type errors or analysis errors (not output mismatches), the issue is in the Python source or model definitions.

Updating Expected Files

If the output changes are expected (e.g., you intentionally changed the analysis):

# Automatically moves all .actual files to their expected counterparts
facebook/scripts/in_path/pysa-update-expected

This replaces each <name>.py.<ext> with the corresponding <name>.py.<ext>.actual.

Always review the diff before updating — run sl diff after updating to verify changes are intentional.

Creating a New Test

1. Create <name>.py under source/interprocedural_analyses/taint/test/integration/
2. Optionally create <name>.py.pysa (model file) and/or <name>.py.config (taint config)
3. Run the test — the runner auto-creates missing expected output files on the first run:

PYSA_INTEGRATION_TEST=<name>.py dune exec interprocedural_analyses/taint/test/integrationTest.exe

1. Review the generated .models, .cg, .hofcg, .overrides files
2. Commit all files together

Common Mistakes

• Wrong env var name: It's PYSA_INTEGRATION_TEST, not PYSA_TEST or similar
• Forgetting the .py extension: Use PYSA_INTEGRATION_TEST=format.py, not format
• Running from wrong directory: dune exec must be run from source/

…

architecture

帮助你快速理解 Pyre/Pysa 代码架构并定位关键实现位置