pysa-integration-tests

Run and debug Pysa taint analysis integration tests with expected output updates.

7.2k|451|Updated Nov 10, 2017
One-click install
npx skills add https://github.com/facebook/pyre-check --skill pysa-integration-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pysa-integration-tests
Source: https://github.com/facebook/pyre-check/tree/main/.llms/skills/pysa-integration-tests
Command: npx skills add https://github.com/facebook/pyre-check --skill pysa-integration-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end integration testing for Pysa taint analysis, enabling reliable validation of test pipelines, expected outputs, and configurations across the integration suite.

Core Features & Use Cases

  • Run and debug taint integration tests located under source/interprocedural_analyses/taint/test/integration/.
  • Update and verify expected outputs including .models, .cg, .hofcg, and .overrides files to reflect changes in the analysis behavior.
  • Use when creating or updating integration tests to ensure end-to-end correctness within the Pyre/Pysa workflow.

Quick Start

Run all integration tests from the source/ directory using the dune-based test runner and refer to the SKILL.md instructions for per-test invocation.

Frequently Asked Questions about pysa-integration-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run end-to-end Pysa taint analysis integration tests?▼

Run Pysa taint analysis integration tests by executing the dune-based test runner from the source directory. The SKILL.md provides specific instructions for per-test invocation and interpreting results.

How do I update expected outputs like .models and .overrides files for Pysa tests?▼

Update Pysa expected outputs including .models, .cg, .hofcg, and .overrides files to reflect analysis behavior changes. Use the tooling commands described in the SKILL.md to verify end-to-end correctness.

What test artifacts are generated during Pysa integration testing?▼

Pysa integration testing generates .models, .cg, .hofcg, and .overrides test artifacts. These files capture taint analysis behavior, call graph data, and expected outputs for validating the integration suite.

Can I use dune to coordinate taint analysis integration tests in Pyre?▼

Yes, dune coordinates end-to-end Pysa taint analysis integration tests. The dune-based test runner executes tests located under source/interprocedural_analyses/taint/test/integration/ for validating the Pyre workflow.

Why are my Pysa integration tests failing after updating taint analysis configurations?▼

Pysa integration tests fail when expected outputs (.models, .cg, .hofcg, .overrides) no longer match current taint analysis behavior. Update the expected output files to reflect configuration changes and rerun.