Skip to content

Latest commit

 

History

History
17 lines (9 loc) · 1.34 KB

README.md

File metadata and controls

17 lines (9 loc) · 1.34 KB

Beef.Test.NUnit

Unit and intra-domain integration testing framework. This capability leverages NUnit for all testing.

Upgrading from v4.x

NOTE: The Beef v5.x testing has now been replaced by the functionality available within UnitTestEx. Any functionality available within this assembly is intended to assist with the upgrading from Beef v4.x; contains a subset of the previous functionality. This assembly will likely be deprecated at the next major version.

Intra-domain vs. inter-domain testing

Intra-domain essentially means within (isolated to) the domain itself; excluding any external domain-based dependencies. For example a Billing domain, may be supported by a SQL Server Database for data persistence, and as such is a candidate for inclusion within the testing.

However, if within this Billing domain, there is an Invoice entity with a CustomerId attribute where the corresponding Customer resides in another domain (external domain-based dependency) which is called to validate existence, then this should be excluded from within the testing. In this example, the cross-domain invocation should be mocked-out as it is considered Inter-domain.

In summary, Intra- is about tight-coupling, and Inter- is about loose-coupling.