Writing good tests
Implementing tests for an application is an investment to free you up from the stress that a new project could give you. Thanks to these tests, you can be (pretty) sure of implementing new features or fixing bugs without breaking the existing software. Unfortunately, writing tests often gets sacrificed whenever a project is running out of time. This is also an activity that many consider to be boring and frustrating, due to the many blockers you may face by testing an HTTP server, such as the server port already in use. So, the tests are often written quickly and without the required attention.
We can say that an application’s test suite is successful under the following conditions:
- It’s automated – you just need to click a button to get many hours’ worth of work done
- It’s easy to maintain – adding a new test must be easy, and it should not take more time than developing the feature itself
- Running the tests...
