Reusable test support and fixtures
Section titled “Reusable test support and fixtures”Use a shared public testing boundary when a scenario needs controlled content, a real process, a native Editor session or a collectible generation. These libraries are not independently passing test suites. Their consumers own execution and evidence.
Build a real fixture
Section titled “Build a real fixture”| Need | Support contract |
|---|---|
| Frozen content with deliberate payload corruption | In-memory content store |
| Prepared contract execution with complete process diagnostics | Isolated process host |
| The calling test’s explicit source and SDK output owner | Repository input resolution |
| Actual panels, native input and an authoring project | Native Editor fixtures |
The returned services and streams retain their documented ownership; a public support library is not exempt from API contracts because its source lives under tests/.
Exercise failed admission and generation changes
Section titled “Exercise failed admission and generation changes”- Duplicate importers intentionally conflict despite different extensions.
- The content-cache probe coordinates real cross-process readers.
- The private module dependency distinguishes dependency resolution from module replacement.
- First and replacement module generations share a stable identity but expose different behavior.
- The invalid module candidate must remain rejected.
- Discovery source A and source B exercise explicit source filtering and removal.
- Collectible rendering contributors expose failed-graph callback retention.
- Collectible scene types exercise Missing recovery and rollback after a rejected restore.
Do not correct deliberate invalid data into a valid product, hold fixture instances in static engine state or count an empty dotnet test invocation on a fixture as coverage. Use the consuming test owner and its selected plan.