requirements management tool

A tool that supports the recording of requirements, requirements ributes (e.g. priority, knowledge responsible) and annotation, and facilitates traceability through layers of requirements and requirements change management. Some requirements management tools also provide facilities for static analysis, such as consistency checking and violations to pre-defined requirements rules.

requirements-based testing

An approach to testing in which test cases are designed based on test objectives and test conditions derived from requirements, e.g. tests that exercise specific functions or probe non-functional ributes such as reliability or usability.

requirement

A condition or capability needed by a user to solve a problem or achieve an objective that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document. [After IEEE 610]

replaceability

The capability of the software product to be used in place of another specified software product for the same purpose in the same environment. [ISO 9126] See also portability .

reliability testing

The process of testing to determine the reliability of a software product.

reliability growth model

A model that shows the growth in reliability over time during continuous testing of a component or system as a result of the removal of defects that result in reliability failures.

reliability

The ability of the software product to perform its required functions under stated conditions for a specified period of time, or for a specified number of operations. [ISO 9126]

release note

A document identifying test items, their configuration, current status and other delivery information delivered by development to testing, and possibly other stakeholders, at the start of a test execution phase. [After IEEE 829]

regulation testing

See compliance testing.

regression testing

Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software, as a result of the changes made. It is performed when the software or its environment is changed.

Regression-averse testing

ISTQB Glossary  definition 

"Testing using various techniques to manage the risk of regression, e.g., by designing re-usable testware and by extensive automation of testing at one or more test levels."

In Simple English,

Any test effort or technique you follow to avoid re occurrence of old closed defects and ensure functionality that was working earlier still works is regression averse testing.

Field Notes 

• While most testing efforts are by design regression averse by design for software or services development process.
• Maintanence, integration and up-gradation projects typically are not regression averse by design. 
• In such projects, regression averseness needs to be carefully planned and implemented.

For Example:

• Having a standard set of test data for which a screen needs to pass is a good regression averse testing technique.
• Automation of base functionality is another regression averse testing technique.

recovery testing

See recoverability testing.

recoverability testing

The process of testing to determine the recoverability of a software product. See also reliability testing.

recoverability

The capability of the software product to re-establish a specified level of performance and recover the d directly affected in case of failure. [ISO 9126] See also reliability.

record/playback tool

See capture/playback tool.

recorder

See scribe.

reactive testing

Testing that dynamically responds to the actual system under test and test results being obtained. Typically reactive testing has a reduced planning cycle and the design and implementation test phases are not carried out until the test object is received.

Rational Unified Process

A proprietary adaptable iterative software development process framework consisting of four project lifecycle phases inception, elaboration, construction and transition.

random testing

A black box test design technique where test cases are selected, possibly using a pseudo-random generation algorithm, to match an operational profile. This technique can be used for testing non-functional ributes such as reliability and performance.

RACI matrix

A matrix describing the participation by various roles in completing tasks or deliverables for a project or process. It is especially useful in clarifying roles and responsibilities. RACI is an acronym derived from the four key responsibilities most typically used Responsible, Accountable, Consulted, and Informed.