~hackernoon | Bookmarks (4)

Code coverage is a poor metric for indicating whether or not your code has been tested well. Instead, we should invert the metric, and use the term “Legacy Code”.

Automated tests are a way to test your software without spending too much time. There are three types of tests: unit, integration, and end-to-end. Let's dive deep into every kind and understand why we need each. Unit tests are fast. Isolation allows them to run them at any point in time, locally and on CI, without spinning up the dependent services / making API...

Unit test coverage – the percentage of source code for which unit tests have been written - is a measure of how much of an application’s source code is 'touched' by tests. While 100% coverage is often unattainable (because not all code may be suitable for testing), 70% to 80% coverage are considered a robust testing suite. Automated test generation tools can be especially...

Performance tests are useful for uncovering bottlenecks, and scalability issues. In this article, I want to show you how to build several testing scenarios for your service using K6.