Now that we have completed the implementation of our application, it is time for us to talk about testing it. Of course, we test our application to make sure things works as expected and that the future changes to our code-base do not break our application's functionality.
One thing to keep in mind here, is that we are writing our tests after we have completed our implementation. However, there are times when we write our tests before our application's code.
The idea is that we write our tests first and expect them to fail since there is no implementation of the code. Then, as we implement our application, our tests start passing and we can be sure that the implemented code behaves as expected.
You may choose this approach over implementation first and testing later for your projects, but I would like to emphasize the point that, regardless of the approach, you need to write some automated tests!
With that in mind, in this chapter we are going...