Skip to content
Project referenceDevelopmentEngine ccf7d03f

Inno.Plugins.Tests verifies the Plugins contracts through their public entry points. Use this page to locate relevant assertions; it is not a report that these tests passed for your current change.

Plugin source tests reject corrupt materialized caches and rebuild them without changing package identity. Concurrent scans publish one complete immutable snapshot rather than mutable catalog or manifest state. Validated code plugins activate through their actual authoring, asset and module boundaries. Cache validation is separate from claiming that every platform can load a plugin.

The project declares the contract validation layer. Use the shared validation workflow to select its actual dependencies and environment. Inspect the pinned project file for package and project references.

A focused diagnostic from the engine root is:

Terminal window
dotnet test tests/plugins/Inno.Plugins.Tests/Inno.Plugins.Tests.csproj --configuration Debug --disable-build-servers -m:1 -nodeReuse:false

Use --filter FullyQualifiedName~MethodName to investigate one case. A filtered run does not replace the obligations in the validation plan. Restore the declared SDK, packages and any tool/process prerequisites before executing; preserve cancellation, thread and cleanup requirements.

These representative methods are preserved from the original reference and checked against the pinned source. The linked files contain all assertions and parameterized cases.

Read the assertions. Representative entry points:

  • CorruptedMaterializedCacheIsRejectedAndCanBeRebuiltWithoutChangingPackageIdentity
  • ConcurrentScansPublishOneCompleteImmutableSnapshot
  • PublishedPluginSnapshotsDoNotExposeMutableCatalogOrManifestState
  • CodePluginActivatesImmediatelyAfterValidation

Follow the shared suite-maintenance guidance. Preserve this suite’s owner-thread, resource-release and failure assertions when adding cases.