Talk:Code coverage

This is the talk page for discussing improvements to the Code coverage article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Archives: Index, 1: 730 days

Computing: CompSci Mid‑importance

This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles

Mid

This article has been rated as Mid-importance on the project's importance scale.

This article is supported by WikiProject Computer science (assessed as Low-importance).

Things you can help WikiProject Computer science with:

Here are some tasks awaiting attention:

Article requests :
- Requested articles/Applied arts and sciences/Computer science, computing, and Internet
Cleanup :
- Computer science articles needing attention
- Computer science articles needing expert attention
Copyedit :
- Computing
Expand :
- Computer science
Infobox :
- Computer science articles without infoboxes
Maintain :
- Timeline of computing 2020–present
Photo :
- Find pictures for the biographies of computer scientists (see List of computer scientists)
- Computing articles needing images
Stubs :
- Computer science stubs
Unreferenced :
- WikiProject Computer science/Unreferenced BLPs
Project-related :
- Tag all relevant articles in Category:Computer science and sub-categories with {{WikiProject Computer science}}

Move?

If the lead identifies the topic as test coverage, then why wasn't the page moved to Test coverage?

As presently written, this page is only in a (relatively) Narrow Topic context in stating that test coverage is a synonym for code coverage. I can appreciate that in an exclusively coding and code-based testing environment, code coverage is the only test coverage there is and there is no point in making the distinction. If this page is limited to that context, because code coverage is a common name for the measures listed in the page, the lead should read either:

In computer science, code coverage, also known as test coverage, is a measure used ....

or

In computer science, test coverage, also known as code coverage, is a measure used ....

The phrase In computer science does not restrict "test coverage" to "code coverage", because requirements-based testing is also practiced within computer science, and its primary test concern is test coverage of requirements. A Broad Topic test coverage article would have to include the requirements-based testing definition that "test coverage" means coverage of the requirements.

test coverage 1. the degree to which a given test or set of tests addresses all specified requirements for a given system or component. 2. extent to which the test cases test the requirements for the system or software product. [IEEE 24765:2010]
test coverage "The degree to which a given test or set of tests addresses all specified requirements for a given system or component." [ IEEE 610.12-1990 ].
code coverage "A quality-assurance [test] strategy that ensures that all of the software has executed at least once. [Ganssle, Embedded Systems Dictionary]
MATLAB/Simulink Code Coverage "Collect code coverage metrics during software-in-the-loop (SIL) and processor-in-the-loop (PIL) simulations. You can use these metrics to show that the generated code does not contain unintended functionality."
MPLAB "To further simplify testing and diagnostics, Microchip also introduced MPLAB Code Coverage license, which determines parts of software that have or have not been executed with minimal impact to the application."
arm / KEIL / µVision User's Guide "The Code Coverage dialog provides statistics about the executed code." [1]
BULLSEYE Testing Technology "BullseyeCoverage is an advanced C++ code coverage tool used ..."
DO-178C's test coverage is a broader topic than this page since its testing must demonstrate complete and robust coverage of all requirements. In this context, "structural coverage" is an ancillary "evaluation of the code structure, including interfaces, exercised during requirements base testing." Here, the main point of "code coverage" is invoking "another set of eyes" searching for overlooked problems in the requirements.
LDRA Structural (Code) Coverage Analysis in embedded systems [2]
RAPITA : "Structural coverage analysis (also referred to as code coverage) is an important component of critical systems development."

See also: Talk:Fault coverage#Split

IveGoneAway (talk) 22:01, 15 February 2023 (UTC) 22:23, 15 February 2023 (UTC) 15:52, 17 July 2023 (UTC)[reply]

Code coverage in 1955

Code Analyzer for the Maniac computer. Analysis of problem codes on the Maniac, Math. Comp. 9 (1955), 14-20. MarMi wiki (talk) 19:57, 12 July 2023 (UTC)[reply]