In this Noser blog post I’ll explain how to make unit/integration testing fun again with Fluent Syntax.
Learn how to write short, simple and maintainable automated software tests with the fluent interface/builder
pattern. I’m also mentioning some other best practices for writing tests (without Fluent Syntax).
See the .NET sample projects on my GitHub repo to see fluent syntax in action.
Without Fluent Syntax
- Unit or integation tests are often too large, too complex and not maintainable.
- Writing good automated software tests usually fails when setting up the test data.
- Similar sample data is created over and over again throughout the code repository in many different ways.
- Some test cases don’t even fit on one screen anymore and I only know which attributes are relevant for my test if I have written the test myself.