Code coverage - Wikipedia
In software engineering, code coverage is a percentage measure of the degree to which the source code of a program is executed when a particular test suite is run. A program with high test coverage has more of its source code executed during testing, which suggests it has a lower chance of containing undetected software bugs compared to a program with low test coverage.[1][2] Many different metrics can be used to calculate test coverage. Some of the most basic are the percentage of program subroutines and the percentage of program statements called during execution of the test suite. Test coverage was among the first methods invented for systematic software testing. The first published reference was by Miller and Maloney in Communications of the ACM, in 1963.[3] To measure what percentage of code has been executed by a test suite, one or more coverage criteria are used. These are usually defined as rules or requirements, which a test suite must satisfy.[4] There are a number of coverag
Code coverage - Wikipedia Jump to content From Wikipedia, the free encyclopedia Metric for source code testing This article is about coverage based on source code. For coverage based on requirements, see Test coverage . Program execution General concepts Code Translation Compiler Compile time Optimizing compiler Linking Execution Runtime system Executable Interpreter Virtual machine Intermediate representation (IR) Types of code Source code Object code Bytecode Machine code Microcode Compilation strategies Ahead-of-time (AOT) Just-in-time (JIT) Tracing just-in-time Compile and go system Precom
related reading
- Cyclomatic complexityen.wikipedia.org
- Software Engineering at Googleabseil.io
- Reading 2: Testingweb.mit.edu
- Cognitive load is what mattersminds.md
- Coupling (computer programming) - Wikipediaen.wikipedia.org
- Your job is to deliver code you have proven to worksimonwillison.net
- CSC 151 - Unit Testingeikmeier.sites.grinnell.edu
- Write code that is easy to delete, not easy to... — programming is terribleprogrammingisterrible.com
- The Joel Test: 12 Steps to Better Code – Joel on Softwarejoelonsoftware.com
- Google Testing Blog: How Much Testing is Enough?testing.googleblog.com
- What Is Linting + When to Use Lint Tools | Perforce Softwareperforce.com
- How to Write Clean, Testable Codeyoutube.com