Software Testing Terminology- M
maintainability: The ease with which a software product can be modified to correct defects, modified to meet new requirements, modified to make future maintenance easier, or adapted to a changed environment. [ISO 9126]
maintainability testing: The process of testing to determine the maintainability of a software product.
maintenance: Modification of a software product after delivery to correct defects, to improve performance or other attributes, or to adapt the product to a modified environment.
maintenance testing: Testing the changes to an operational system or the impact of a changed environment to an operational system.
management review: A systematic evaluation of software acquisition, supply, development, operation, or maintenance process, performed by or on behalf of management that monitors progress, determines the status of plans and schedules, confirms requirements and their system allocation, or evaluates the effectiveness of management approaches to achieve fitness for purpose.
manufacturing-based quality: A view of quality, whereby quality is measured by the degree to which a product or service conforms to its intended design and requirements. Quality arises from the process(es) used. [After Garvin] See also product-based quality, transcendent-based quality, user-based quality, value-based quality.
master test plan: A test plan that typically addresses multiple test levels. See also test plan.
maturity: (1) The capability of an organization with respect to the effectiveness and efficiency of its processes and work practices. See also Capability Maturity Model, Test Maturity Model. (2) The capability of the software product to avoid failure as a result of defects in the software.
maturity level: Degree of process improvement across a predefined set of process areas in which all goals in the set are attained.
maturity model: A structured collection of elements that describe certain aspects of maturity in an organization, and aid in the definition and understanding of an organization’s processes. A maturity model often provides a common language, shared vision and framework for prioritizing improvement actions.
Mean Time Between Failures: The arithmetic mean (average) time between failures of a system. The MTBF is typically part of a reliability growth model that assumes the failed system is immediately repaired, as a part of a defect fixing process. See also reliability growth model.
Mean Time To Repair: The arithmetic mean (average) time a system will take to recover from any failure. This typically includes testing to insure that the defect has been resolved.
measure: The number or category assigned to an attribute of an entity by making a measurement.
measurement: The process of assigning a number or category to an entity to describe an attribute of that entity.
measurement scale: A scale that constrains the type of data analysis that can be performed on it.
memory leak: A memory access failure due to a defect in a program’s dynamic store allocation logic that causes it to fail to release memory after it has finished using it, eventually causing the program and/or other concurrent processes to fail due to lack of memory.
metric: A measurement scale and the method used for measurement.
milestone: A point in time in a project at which defined (intermediate) deliverables and results should be ready.
mind-map: A diagram used to represent words, ideas, tasks, or other items linked to and arranged around a central key word or idea. Mind maps are used to generate, visualize, structure, and classify ideas, and as an aid in study, organization, problem solving, decision making, and writing.
mistake: See error.
modeling tool: A tool that supports the creation, amendment and verification of models of the software or system [Graham].
moderator: The leader and main person responsible for an inspection or other review process.
modified condition decision coverage: See condition determination coverage. modified condition decision testing: See condition determination testing. modified multiple condition coverage: See condition determination coverage. modified multiple condition testing: See condition determination testing. module: See component.
module testing: See component testing.
monitor: A software tool or hardware device that runs concurrently with the component or system under test and supervises, records and/or analyses the behavior of the component or system.
monitoring tool: See monitor.
monkey testing: Testing by means of a random selection from a large range of inputs and by randomly pushing buttons, ignorant of how the product is being used.
MTBF: See Mean Time Between Failures. MTTR: See Mean Time To Repair.
multiple condition: See compound condition.
multiple condition coverage: The percentage of combinations of all single condition outcomes within one statement that have been exercised by a test suite. 100% multiple condition coverage implies 100% condition determination coverage.
multiple condition testing: A white box test design technique in which test cases are designed to execute combinations of single condition outcomes (within one statement).
mutation analysis: A method to determine test suite thoroughness by measuring the extent to which a test suite can discriminate the program from slight variants (mutants) of the program.
mutation testing: See back-to-back testing.