Class IsolatedIntegrationTests

Namespace

CMS.Tests

Assembly

CMS.Tests.dll

Allows integration tests to run in isolation as for each test a clean database with current schema and default objects is created.

[Category.IsolatedIntegration]
public class IsolatedIntegrationTests : AutomatedTestsWithLocalDB

Inheritance

object

AutomatedTests

AutomatedTestsWithData

AutomatedTestsWithLocalDB

IsolatedIntegrationTests

Inherited Members

AutomatedTestsWithLocalDB.AutomatedTestsWithLocalDBSetup()

AutomatedTestsWithLocalDB.AutomatedTestsWithLocalDBFixtureSetup()

AutomatedTestsWithLocalDB.AutomatedTestsWithLocalDBTearDown()

AutomatedTestsWithLocalDB.AutomatedTestsWithLocalDBFixtureTearDown()

AutomatedTestsWithLocalDB.GetTestUniqueIndex()

AutomatedTestsWithLocalDB.RefreshMacroSignatures(params string[])

AutomatedTestsWithLocalDB.GetExtraDatabaseConnectionStringName(string)

AutomatedTestsWithLocalDB.ExecuteWithAllDatabases(Action<string>)

AutomatedTestsWithLocalDB.EnsureExtraDatabase(string, bool)

AutomatedTestsWithLocalDB.GetCurrentTestDatabaseName()

AutomatedTestsWithLocalDB.ExecuteWithExtraDatabase(string, Action)

AutomatedTestsWithLocalDB.SharedDatabaseForAllTests

AutomatedTestsWithData.TestsWithDataFixtureSetup()

AutomatedTestsWithData.TestsWithDataSetup()

AutomatedTestsWithData.TestsWithDataTearDown()

AutomatedTestsWithData.TestsWithDataFixtureTearDown()

AutomatedTestsWithData.ResetAllFakes()

AutomatedTestsWithData.Fake()

AutomatedTestsWithData.Fake<TInfo>(InfoFakeSettings)

AutomatedTestsWithData.Fake<TInfo, TProvider>(bool)

AutomatedTestsWithData.Fake<TInfo, TProvider>(TProvider, bool)

AutomatedTestsWithData.FakeDynamicObjectType<TInfo, TProvider>(TProvider, string, bool)

AutomatedTestsWithData.FakeObject<TInfo>(int, Action<TInfo>)

AutomatedTestsWithData.GetTestGuid(int)

AutomatedTestsWithData.GetVirtualStorageProvider(string, string)

AutomatedTests.InitFixtureBase()

AutomatedTests.InitBase()

AutomatedTests.CleanUpBase()

AutomatedTests.CleanUpFixtureBase()

AutomatedTests.AddExtender(TestExtender)

AutomatedTests.GetTestExtenders()

AutomatedTests.RunExtenderAction<TCurrentLevel>(Action<TestExtender>, bool)

AutomatedTests.Dispose()

AutomatedTests.CleanUpDataContext()

AutomatedTests.TestMilestone()

AutomatedTests.ResetAppState()

AutomatedTests.InitApplication()

AutomatedTests.PreInitApplication()

AutomatedTests.RegisterTestServices()

AutomatedTests.EnsureServiceContainer()

AutomatedTests.EndApplication()

AutomatedTests.ApplicationInitialized

AutomatedTests.TemporaryAppPath

AutomatedTests.IsFirstTestInFixture

Extension Methods

DataExtensions.With<T>(T, Action<T>)

QueryExtensions.AsLiteral<T>(T)

QueryExtensions.AsValue<T>(T, bool)

Remarks

The isolated integration tests use LocalDB to create and drop databases when needed. It works with two types of database. The master database is created using SQL scripts from the solution. For each modification of this folder a new master database is created. The master database is detached after it has been created and its files are copied to create an instance database that a running test will use. The instance and master databases share a name, but the file names are different. The instance database is removed when a test finishes and a master database, that is out of date, is removed automatically.

Constructors

IsolatedIntegrationTests()

public IsolatedIntegrationTests()

Methods

IsolatedIntegrationTestsFixtureSetup()

Test fixture set up.

public void IsolatedIntegrationTestsFixtureSetup()

IsolatedIntegrationTestsFixtureTearDown()

Test fixture clean up.

public void IsolatedIntegrationTestsFixtureTearDown()

IsolatedIntegrationTestsSetup()

Test set up.

public void IsolatedIntegrationTestsSetup()

IsolatedIntegrationTestsTearDown()

Test clean up.

public void IsolatedIntegrationTestsTearDown()