Closed devantler closed 2 years ago
I suppose we could add some kind of pattern matching method, e.g.
var result = Types
.That()
.ResideInNamespace("Example")
.Should()
.HaveMatchingClass([some kind of funky regular expression])
.GetResult();
However, I am not sure how useful this would be. After all, ensuring a test class is created for each functional class is no guarantee of a meaningful unit test suite. I would be more inclined to use a test coverage tool like SonarQube for managing test coverage.
Can this tool be used to enforce creation of unit test classes, and enforce their paths so e.g. a project with the following classes:
... would require an accompanying test project with the following classes: