September 2024
Intermediate to advanced
743 pages
27h 48m
English
If you verify the functionality of components through testing, that’s already worth a lot. However, testing is only effective if as much code as possible is executed as a result of the tests. Writing hundreds of tests has no point if only a fraction of the code of a component is called and thus tested.
But how can you ensure that all code is called by tests if possible, and how can you determine which code doesn’t get called by tests (yet)?
The answer to this question is provided by special tools that determine the test coverage or code coverage. These tools are started in the background when a test is executed and record exactly which lines of code and which code branches are called in the code under ...
Read now
Unlock full access