Class InstallTaskCriticalityRuleTests

Serenity.Global.Infrastructure.Editor.InitializationPipeline.InstallTaskCriticalityRule read against the REAL composition root, and the shipped install-task assets measured against it — one rule, one source, no second list to keep in step.

Inheritance

object

InstallTaskCriticalityRuleTests

Inherited Members

object.ToString()

object.Equals(object)

object.Equals(object, object)

object.ReferenceEquals(object, object)

object.GetHashCode()

object.GetType()

object.MemberwiseClone()

Namespace: Serenity.InitializationPipeline.Tests.Editor

Assembly: Serenity.InitializationPipeline.Tests.Editor.dll

Syntax

public class InstallTaskCriticalityRuleTests

Constructors

InstallTaskCriticalityRuleTests()

Declaration

public InstallTaskCriticalityRuleTests()

Methods

ForInstallMethod_FoundationModule_IsCritical()

Declaration

public void ForInstallMethod_FoundationModule_IsCritical()

ForInstallMethod_MethodTheCatalogDoesNotDescribe_IsCritical()

Declaration

public void ForInstallMethod_MethodTheCatalogDoesNotDescribe_IsCritical()

ForInstallMethod_OptionalNonFoundationModule_IsNotCritical()

Declaration

public void ForInstallMethod_OptionalNonFoundationModule_IsNotCritical()

ForInstallMethod_UnresolvableInstallerType_IsCritical()

Declaration

public void ForInstallMethod_UnresolvableInstallerType_IsCritical()

ShippedInstallTasks_AreFound()

Declaration

public void ShippedInstallTasks_AreFound()

ShippedInstallTasks_CarryTheCriticalityTheRuleDerives()

Every shipped install task carries the criticality the rule derives from its own module, so a project that boots the shipped pipeline halts on exactly the modules the game cannot run without. A task's Id is its install method name — that is what authors it — so the rule reads the Id.

Declaration

public void ShippedInstallTasks_CarryTheCriticalityTheRuleDerives()