Skip to content
Project referenceDevelopmentEngine ccf7d03f

Rendering import and shader authoring tests

Section titled “Rendering import and shader authoring tests”

Inno.Rendering.Assets.Authoring.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.

Material and raster state round-trip through asset serialization without replacing provider-owned roles, capabilities or choices. Metadata remains an open provider protocol. Import tests use one compilation model across graph shaders, materials and pipeline assets. Includes resolve from the candidate mount snapshot and declared plugin dependencies; a source library exports explicit graph functions.

Runtime export strips authoring graph/function artifacts while preserving shader identity and definition. Compiler failures cannot carry successful binary bytes; successful results copy adapter-owned bytes, bindings and diagnostics instead of retaining mutable producer storage.

The project declares the contract layer. Inspect the authoring tool and native requirements selected by the actual plan. Preserve real importer, source discovery and tool-result assertions; a runtime serialization pass does not replace shader authoring integration.

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.

Representative entry points are checked against the pinned source. The linked files retain all assertions and parameterized cases.

Read the complete assertions. Representative entry points:

  • MaterialAndPipelineState_RoundTripsThroughAssetSerialization
  • MaterialResolver_UsesProviderOwnedContractsRolesAndCapabilities
  • ShaderRasterState_RoundTripsWithoutLosingProviderChoices
  • MaterialMetadataRemainsAnOpenProviderProtocol

Read the complete assertions. Representative entry points:

  • LoaderUsesGraphShaderMaterialAndPipelineAssetsWithOneCompilationModel
  • ShaderIncludesUseTheCandidateMountSnapshotAndDeclaredPluginDependencies
  • RuntimeExportStripsGraphAndFunctionArtifactsAndPreservesShaderIdentityAndDefinition
  • OneShaderSourceLibraryExportsMultipleExplicitGraphFunctions

Read the complete assertions. Representative entry points:

  • FailedToolResultsCannotCarrySuccessfulBinaryBytes
  • ToolResultsCopyAdapterOwnedBytesBindingsAndDiagnostics
  • CompileAsyncUsesGraphLoweringAndTypedStages
  • AdapterFailureRetainsOriginalSourceLocationAndNoPartialProgram

Read the complete assertions. Representative entry points:

  • FrozenArtifactRecordsKeepTheirPersistentIdentitiesAfterOwnershipMoves
  • SemanticFingerprintIgnoresLayoutButIncludesPropertiesAndFrozenDependencies
  • ExpandedProgramCompilesWhileAuthoringExportRetainsTheSmallSourceGraph
  • TemporarilyEmptyInputNameRetainsItsMaterialDefaultWhileTyping

Read the complete assertions. Representative entry points:

  • ShaderCommitDetachesEveryNestedDeclarationOnInputAndOutput
  • FailedShaderCommitPreservesThePreviousDefinitionAndSerializedState
  • ShaderGraphRetainsCanonicalInputWhenTheAuthoringDefinitionIsEdited
  • MaterialSelectionAndResolvedPassDoNotPublishTheirMetadataArrays

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.