There is testing, and then there is testing. Some of it feels like a chore, and some of it just feels like it makes sense.
When I started integration testing my ASP.NET API:s, it felt like one of those things that just made sense! I was able to quickly and easily call an API endpoint, and verify the result. Something that makes my life as a developer a lot easier. And on top of that, it not only gives me confidence that my API works as it should, it also makes sure that any changes I make are backwards compatible. Not to mention that the tests actually become pretty great documentation of how to use the API as well. Giving me all the things tests are supposed to give, but I never really felt like unit tests gave me. It's a win-win-win thing.
However, there are some challenges that we need to address before we end up at this utopia. Things like being able to use a database during the tests. Handling security. Mocking 3rd party dependencies that can't be used during testing. But these are all things that we can overcome.
In this talk Chris will show you how to solve these things and set up an easy to use integration testing environment for your ASP.NET Core API:s.
Chris Klug is a developer badass-as-a-service that either creates or solves problems depending on who you ask. He loves creating and building things. Whether it be a new application, a new kitchen or a new RC helicopter, you will see him building things all the time. Most of the time, that means writing code and solving problems for clients at a company called Active Solution in Stockholm though. Except for the many days he spends at conferences and usergroups, talking about doing things he is passionate about, and for the days he goes mountain biking, IPSC shooting, kiteboarding or RC helicopter flying. For the last 15-something years, he has been solving problems for customers, and loving it. But if he gets to choose, he'll go to the beach and kitesurf every day!
