Menu
The general approach for end to end testing in the project. Especially, when adding new features or diagnostics.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Write or update focused unit tests in the Pernix compiler codebase. Use when adding Rust test functions, covering a bug or feature with unit tests, or reviewing test clarity. Apply concise input, premise, and output contract comments especially to tests for pernixc_type and pernixc_solver; inspect and follow local conventions in other crates.
The general coding style for the project. This includes the general API design guide and acceptance criterias
Workflow for creating and updating syntax trees in the `pernixc_syntax` crate, including the `abstract_tree` macro pattern and the arbitrary module for property-based testing.
| name | e2e-testing |
| description | The general approach for end to end testing in the project. Especially, when adding new features or diagnostics. |
test in the current module (e.g., #[cfg(test)] mod test;).test or Test in symbol names within the test module (e.g., no test_function or TestBasicStruct, just use the bare descriptive name).Generally, when adding new features or diagnostics, it's better to add an end-to-end
test with snapshot testing. This can be found under the compiler/e2e/test/snapshot/
directory.
main.pnx file with source code that will trigger the diagnostic outputs.cargo nextest r -p pernixc_e2e -- --skip regression command to execute the test and generate snapshots. (NOTE: It's recommended to skip regression tests as they can be time-consuming and often unproductive).cargo insta review. Approved snapshots will be saved alongside the test files for future reference.