Class ServiceExtensionRunnerEndToEndTests
The JSON runner driven the way a command-line caller drives it: the extension-point suffix is the author's choice rather than forced, a Service-kind spec that names the wrong target field is told why, and two extensions generated one after the other into the same target folder leave a project whose assembly layout still compiles — proven on the asmdef files themselves (one per folder, unique names, every reference resolvable, no pre-existing script captured), since a headless EditMode run cannot perform the domain reload a real compile needs.
Inherited Members
Namespace: Serenity.ServiceExtensionCreator.Tests.Editor
Assembly: Serenity.ServiceExtensionCreator.Tests.Editor.dll
Syntax
public class ServiceExtensionRunnerEndToEndTests : MetaFileRaceGuardedFixture
Constructors
ServiceExtensionRunnerEndToEndTests()
Declaration
public ServiceExtensionRunnerEndToEndTests()
Methods
CreateFromJson_AppendExtensionPointSuffixFalse_UsesTheNameExactlyAsTyped()
Declaration
public void CreateFromJson_AppendExtensionPointSuffixFalse_UsesTheNameExactlyAsTyped()
CreateFromJson_ServiceKindNamingOnlyExtensionPointName_ExplainsThatTheServiceKindReadsAggregate()
Declaration
public void CreateFromJson_ServiceKindNamingOnlyExtensionPointName_ExplainsThatTheServiceKindReadsAggregate()
CreateFromJson_SpecWithoutTheSuffixField_KeepsAppendingTheExtensionPointSuffix()
Declaration
public void CreateFromJson_SpecWithoutTheSuffixField_KeepsAppendingTheExtensionPointSuffix()
CreateFromJson_TwoExtensionsIntoTheSameTargetFolder_LeaveAnAssemblyLayoutThatStillCompiles()
Declaration
public void CreateFromJson_TwoExtensionsIntoTheSameTargetFolder_LeaveAnAssemblyLayoutThatStillCompiles()
SetUp()
Declaration
public void SetUp()
TearDown()
Declaration
public void TearDown()