policyengine-testing-patterns

PolicyEngine testing patterns enforce standardized YAML structures organized under gov/states/[state]/[agency]/[program] directories with consistent naming for test cases, variables, and files. Follow the period directory hierarchy and case-naming scheme to ensure quality and repeatable test outcomes across unit and integration test suites.

Period handling rules in PolicyEngine tests enforce supported period formats to maintain consistency across test cases. These rules apply to both variable tests and integration tests, ensuring that policy-change handling and period specifications follow standardized patterns throughout your test suite.

Unit and integration tests must be separated by file structure guidelines within the gov/states/[state]/[agency]/[program] hierarchy. Unit tests are named after variables and placed under proper period directories, while integration tests follow the same directory structure but serve different validation purposes.

Standardized naming conventions require consistent test case names and people identifiers throughout your PolicyEngine test suites. These conventions enforce case naming, output formatting, and variable naming schemes to maintain readability and enable automated validation of test structure.

Yes, PolicyEngine testing patterns standardize validation across all state and agency program structures. The patterns apply universally to the gov/states/[state]/[agency]/[program] directory organization, ensuring consistent quality standards regardless of which program or agency you're testing.