Static copy
Copied from docs/en/governance/standards-and-testing.md in https://github.com/poppy-team/aipo-lang (MIT). Pinned to revision ce47c4e070404fc41722ccd8e2b7b808b99062a8, blob f0d33115348a86cb500b8a1c88bd6f0943688094. The source repository remains canonical; this copy is refreshed through a sync pull request, not live.
Aipo's engineering integrity is upheld by an exhaustive automated test pyramid and strict compilation standards in Rust 2024.
Every commit and pull request must cleanly satisfy 100% of the following verification gates:
cargo fmt --check: Canonical source code formatting.cargo check --workspace --all-targets: Zero compilation errors across all workspace targets.cargo clippy --workspace --all-targets -- -D warnings: Zero warnings allowed under strict linter flags.cargo test --workspace: 100% passing across over 500 unit and integration tests.cargo doc --workspace --no-deps: API documentation compiles with zero broken links or warnings.graph BT
Fuzz["Continuous Fuzzing (libFuzzer)"] --> Diff["Differential Conformance (Rust VM vs Node.js)"]
Diff --> Conf["Conformance Suite (40+ canonical programs & diagnostics)"]
Conf --> Integ["Integration Tests & Host ABI Sandboxing"]
Integ --> Unit["Unit Tests & Proptest (Lexer, Parser, Sema, IR, VM)"]Verifies pure functions, Bytes boundary clamping, UTF-8 character indexing in Source, and mathematical invariants with proptest.
End-to-end scenarios validating VM lifecycle with headless Poppy simulation, generational handle isolation, and capability denials.
Execution of canonical test programs asserting exact standard output and process termination codes.
Concurrent execution of each test program on the native Rust VM and Node.js via emitted JavaScript, asserting identical semantics.
Massive fuzz testing injection on Lexer and Parser ensuring the compiler rejects malformed input gracefully without panicking.