Conditional inspection selection tests
Section titled “Conditional inspection selection tests”Inno.Editor.Inspection.Tests owns the behavior described below. Use this guide to find relevant assertions and their environment; the scenario list is not a current passing result.
Behavior covered
Section titled “Behavior covered”ConditionalInspectorPeersResolveByPredicateAndRejectActualAmbiguity checks that inspection peers resolve through their declared predicates while actual ambiguity fails. This contract is distinct from rendering Inspector widgets or exercising native layout.
Environment and execution
Section titled “Environment and execution”The project declares the contract layer. Use the declared inspection and discovery references. Keep predicate selection and ambiguity assertions at the public boundary; native layout remains with its actual presentation owner.
Generate and inspect one validation plan, then execute that plan with its evaluated target, product and output properties. A focused test filter helps diagnosis; it does not replace required owner evidence. The pinned project file contains the actual references and metadata.
Scenario reference
Section titled “Scenario reference”Representative entry points are checked against the pinned source. The linked files retain all assertions and parameterized cases.
Conditional Inspection
Section titled “Conditional Inspection”Read the complete assertions. Representative entry points:
ConditionalInspectorPeersResolveByPredicateAndRejectActualAmbiguity
Extend safely
Section titled “Extend safely”Follow suite maintenance. Fixtures own their own sessions, temporary files and processes. Preserve thread, release and failure ordering; do not remove another owner’s lock or widen production visibility.