So far in this series, we’ve explored the concept of automated testing. We’ve seen that it’s nothing more than writing code to test other code. To mobilize this, we experimented with a custom console app that calls test functions that exercise the class we really wanted to test. We saw that this would show us when all the tests work–but also when they don’t, to help us catch breaking changes.
Last time, we saw an overview of automated testing and why it matters. We covered the high-level concepts of what it is and what it can mean for the quality and stability of our code. But we didn’t see any of it. Let’s look deeper here and get a peek of test code.
Well, what is it really? In the previous post we saw the definition: Automated tests are when you write code that tests other code.
This is an introduction to Automated Testing–an introduction. We’re starting from square one here, so if you’ve never heard of it, or if you’ve never tried it, or you’re interested in learning about it, then you’re in the right place. Over this series, we’ll start from the very beginning on what is automated testing, why it’s important, why we do it, and dip our toe in the water with examples in C#.