equadrat Framework Test

The idea of the equadrat Framework is to provide APIs to build applications with an architecture of highly decoupled components. Every single component, aspect or pattern is represented by interfaces. The framework provides a standard implementation for these but each type can be replaced by a custom implementation.

The framework is not about reimplementing components, but making them available using common interfaces.

Getting started

You can use most of the components by simply instantiating them. This is maybe the easiest way to evaluate the framework.

If you're using an IOC/DI container such as Microsoft Extensions DependencyInjection or if you want to use the built-in IOC framework, you can use the bootstrapper and bootstrapper modules to register the framework to the IOC.

Usage

[TestClass] public sealed class MyUnitTest: MSTestExtDITemplate // This requires equadrat.Framework.Test.MSTest.Extensions.DependencyInjection NuGet package. { protected override void RegisterDependencyModules(ICoreBootstrapperModuleRegistry moduleRegistry) { // Use the module registry to register bootstrapper modules. Usually each assembly has its own bootstrapper module. moduleRegistry.CoreFramework().RegisterBaseModule(); base.RegisterDependencyModules(moduleRegistry); } protected override void ConfigureServices(IServiceCollection serviceCollection) { // Optional: declare other services as usual. // serviceCollection.AddSingleton<>(); base.ConfigureServices(serviceCollection); } [TestMethod] public void MyTest() { // You can use the factory to resolve services: // this.Factory.GetInstanceOf<...>(); // this.Factory.ServiceProvider.GetRequiredService<...>(); // ... } }

Have a look at the example applications on equadrat.net and in the wiki.

Interesting components

This is a list of some (not all) components of the framework which might be interesting for you.

Unit tests