Fixie is a relative newcomer to the .NET testing framework space. It throws away the idea of marking elements of test code with attributes in favour of a conventions based approach.
At a high level, what this means is simply naming things in test projects following a defined default (customized conventions are also supported) convention.
A Fixie test class with a single test inside it would look like the following, notice the lack of attributes and even using statements.
public class SomeClassTests
public void ShouldDoSomething()
After building the test will now show up in Visual Studio Test Explorer as the following screenshot shows.
Fixie knows this is a test because it matches the default conventions that come out of the box.
Fixie knows that this is a test class because it ends with “Tests” and it knows that the method is a test because it’s a public void method.
If these default conventions are not suitable for your project you can create your own custom conventions to customise the test discovery. There’s also a lot more to custom conventions, such as customising the test execution lifecycle and creating data-driven tests.
To learn more about Fixie, check out the docs or my Introduction to Fixie Pluralsight course.