A Stack Overflow thread inspired this series. There is time that we get a headache by just thinking of creating a new unit test. For that particular class which we have to do so much setup to do an assertion.…
Continuing the series of posts to explore different testing aspects in asp .net core. We’re going experiment with Test Server to create integration tests. Test Server is a new features that asp .net core is bringing. It creates a browser…
In this new series of posts, I want to show different aspects of testing an ASP.NET core application. I will start in this post showing how to create unit tests for controllers. Then I am going to talk integration test…
A Stack Overflow thread inspired this series. When maintaining unit tests, sometimes, we have to update the setup data, because of a new feature, for example. To do this, we go to the setup method and change the data to…
The assertion in unit tests is the phase where we verify if the test result is what we expect. This phase is straightforward, usually it is just one line. But it is not very readable, because it looks something like…
Pass/Fail Patterns are the most basic unit test patterns, they are our first way to tell if the production code is working as it should. The Simple-Test Pattern The Simple-Test pattern has the objective to test only one thing at…
A Stack Overflow thread inspired this series. When we find a bug, the tendency is to create or update a unit test to reproduce and validate the error. Instead of improving an existing test and without necessity, the developer creates…
You can download this article project on GitHub. Sometimes when doing unit test, we encounter subsequent calls to the same method. When mocking a method the default behavior is to always return the same result. In this post, I will…
You can download this article project on GitHub. In this post, I’ll show how to use the in-memory feature of Entity Framework core to create unit tests involving the database. Let’s jump right in! Create unit tests using a real…
A Stack Overflow thread inspired this series. Every once in a while we stumble upon a particular unit test which takes ages to run, taking more than 10 seconds sometimes. Whenever a slow poke test is created, it takes more time to run…
