> For the complete documentation index, see [llms.txt](https://senselab.gitbook.io/senselab-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://senselab.gitbook.io/senselab-docs/vendor/infection/infection/doc/nomenclature.md). # Nomenclature ## Table of Contents * [A](#a) * [Arid Node](#arid-node) * [Artefact Collection](#artefact-collection) * [AST](#ast) * [AST Enrichment](#ast-enrichment) * [AST Processing](#ast-processing) * [E](#e) * [Eligible Node](#eligible-node) * [H](#h) * [Heuristic Suppression](#heuristic-suppression) * [M](#m) * [Mutagenesis](#mutagenesis) * [Mutant](#mutant) * [Mutant Analysis](#mutant-analysis) * [Mutant Evaluation](#mutant-evaluation) * [Mutant Generation](#mutant-generation) * [Mutant Materialisation](#mutant-materialisation) * [Mutation](#mutation) * [Mutation Analysis](#mutation-analysis) * [Mutator](#mutator) * [P](#p) * [Parsing](#parsing) * [R](#r) * [Reporting](#reporting) * [S](#s) * [Source Collection](#source-collection) * [Subject](#subject) * [T](#t) * [Tracer](#tracer) * [Trace](#trace) * [References](#references) ## A ### Arid Node An [AST](#ast) node that, if mutated, would create unproductive [mutants](#mutant). Examples include calls to memory-reserving functions. [\[1\]](#references) ### Artefact Collection The gathering of prerequisites such as coverage reports or cache files. This typically involves either validating provided artefacts or running the initial test suite. ### AST Acronym for [Abstract Syntax Tree](https://en.wikipedia.org/wiki/Abstract_syntax_tree). A tree representation of the abstract syntactic structure of source code. Infection parses source files into this representation to perform mutations. ### AST Enrichment The traversal of the [AST](#ast) to add context, mark [arid nodes](#arid-node), identify [eligible nodes](#eligible-node), and similar preparatory tasks. ### AST Processing The building and enriching of the program representation. Encompasses [parsing](#parsing) and [AST enrichment](#ast-enrichment). ## E ### Eligible Node An [AST](#ast) node for which a [mutation](#mutation) can be generated. [\[1\]](#references) ## H ### Heuristic Suppression The application of heuristics to filter out mutations unlikely to provide value. Suppressed mutations bypass [mutant materialisation](#mutant-materialisation) and [mutant evaluation](#mutant-evaluation). [\[1\]](#references) ## M ### Mutagenesis The process of creating a [mutant](#mutant) from the original program. [\[2\]](#references) ### Mutant A program that differs from the original by having a [mutation](#mutation) applied. [\[3\]](#references) ### Mutant Analysis The phase encompassing [mutant materialisation](#mutant-materialisation) and [mutant evaluation](#mutant-evaluation). ### Mutant Evaluation The execution of tests against the mutant process(es) and recording of the outcome. ### Mutant Generation The traversal of the [AST](#ast) to yield [mutations](#mutation) for each [eligible node](#eligible-node). ### Mutant Materialisation The writing of mutated code to disc and spawning of an isolated process in which the mutation is applied. ### Mutation The result of applying a [mutator](#mutator) to a representation of a [subject](#subject) (e.g. AST, bytecode), representing a change to be applied. [\[3\]](#references) In the mutation testing literature, the terms "mutant" and "mutation" are often used interchangeably, as both refer to the change being introduced. ### Mutation Analysis The core mutation testing cycle: generate, filter, instantiate, evaluate. Encompasses [mutant generation](#mutant-generation), [heuristic suppression](#heuristic-suppression), [mutant materialisation](#mutant-materialisation) and [mutant evaluation](#mutant-evaluation). [\[3\]](#references) ### Mutator A definition of a possible transformation which, when applied to the [AST](#ast) of a [subject](#subject), produces a [mutation](#mutation). [\[2\]](#references) In the mutation testing literature, mutators are also known as "mutant operator", "mutagenic operator", "mutagen", and "mutation rule". ## P ### Parsing The creation of an [AST](#ast) for each source file. ## R ### Reporting The generation of a report summarising the execution results. ## S ### Source Collection The identification and collection of source files to mutate. ### Subject An addressable piece of code to be targeted for mutation testing. ## T ### Tracer A tool responsible for establishing a binding, a [*trace*](#trace), between a piece of source code and the tests that execute it. A tracer may work unidirectionally (i.e. finding the corresponding tests for a given piece of source code), bidirectionally, or in reverse. ### Trace An artefact produced by a [tracer](#tracer), associating a piece of source code with its corresponding tests. ## References *Note: These references indicate where a term is used or defined, not necessarily the original source that coined it.* 1. Goran Petrović, Marko Ivanković, Gordon Fraser, and René Just, "Practical Mutation Testing at Scale: A view from Google," *IEEE Trans. Softw. Eng.*, vol. 48, no. 10, pp. 3900–3912, Oct. 2022, doi: [10.1109/TSE.2021.3107634](https://doi.org/10.1109/TSE.2021.3107634). 2. Yue Jia and Mark Harman, "An Analysis and Survey of the Development of Mutation Testing," *IEEE Trans. Softw. Eng.*, vol. 37, no. 5, pp. 649–678, Sep. 2011, doi: [10.1109/TSE.2010.62](https://doi.org/10.1109/TSE.2010.62). 3. Richard A. DeMillo, Richard J. Lipton, and Frederick G. Sayward, "Hints on Test Data Selection: Help for the Practicing Programmer," *Computer*, vol. 11, no. 4, pp. 34–41, Apr. 1978, doi: [10.1109/C-M.1978.218136](https://doi.org/10.1109/C-M.1978.218136). *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://senselab.gitbook.io/senselab-docs/vendor/infection/infection/doc/nomenclature.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.