Releases: Notorious-Coding/Notorious-Test
Releases · Notorious-Coding/Notorious-Test
3.1.0
3.0.0
v3.0.0
✨ Features
ConfiguredInfrastructureandAsyncConfiguredInfrastructureare replaced withIConfigurableInfrastructureinterfaces. Every infrastructures can be marked as configurable just by implementing this interface.
🛠 Technical
- Added C4 model architecture schema
v2.3.1 - Bug Fixes
v2.3.1
🐛 Bug Fixes
- Fixed a bug in NotoriousTest.SqlServer where the
SqlServerContainerAsyncInfrastructuredid not changes the database connection to point to the newly created database.
v2.3.0 - TestContainers and SqlServer integrations available !
✨ Features
- NotoriousTest.TestContainers is now available as a separate package.
- Provides a simple way to use TestContainers in your tests.
- For more information, see the Advanced Functionalities - TestContainers.
- NotoriousTest.SqlServer is now available as a separate package.
- Provide your tests with a SqlServer ready-to-use infrastructure !
- For more information, see the Advanced Functionalities - SqlServer.
🛠 Technical
- Simplified management of generic types in the
AsyncConfiguredInfrastructureandAsyncConfiguredEnvironmentclasses.
v2.2.0 - Environment configuration simplification and addition of ContextId
v2.2.0
✨ Features
- Introduced
ContextIdto uniquely identify infrastructures. For example, you can name your database with it.- In standalone mode,
ContextIdwill be a random GUID. - Within an Environment,
ContextIdwill be the environment identifierEnvironment.EnvironmentId
- In standalone mode,
- Removal of
IConfigurationProducerandIConfigurationConsumer, as it was not necessary. Orderproperty is now nullable and thus optional.
🛠 Technical
- Implemented multiple unit tests to enhance reliability.
- Several changes to improve consistency in package usage (naming, methods, etc.).
🐛 Bug Fixes
- Fixed a bug where
EnvironmentIdgenerated a new GUID on every reference. - Fixed a bug where the configuration was erased when using an object as the configuration in
AsyncConfiguredEnvironment<TConfig>.
v2.1.0 - Advanced Control Over Infrastructure Resets
What's New in v2.1.0
- Advanced Control Over Infrastructure Resets: Use the
AutoResetoption to control whether infrastructures reset automatically between tests.
The AutoReset option allows you to manage the lifecycle of your infrastructures with more precision. For example, in a multi-tenant application, database data is often isolated "by design." In such cases, it may be beneficial to skip the reset for the database infrastructure.