Skip to content
DocumentationDevelopmentEngine ccf7d03f

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.

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”

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.