The Test Guide Software Test Guide RSS Feed
*
Accessibility

Background

Software Testing Knowledgebase

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 

...R...

ItemDescription
ROI The return on investment (ROI) is usually computed as the benefits derived divided by the investments made.
If we are starting a fresh project, we might compute the value of testing and divide by the cost of the testing to compute the return.
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 attributes such as reliability and performance.
Re-testing Testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions.
Recoverability The capability of the software product to re-establish a specified level of performance and recover the data directly affected in case of failure.
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.
Relational operator Conditions such as is equal to or is less than that link an attribute name with an attribute value in a rule's premise to form logical expressions that can be evaluated as true or false.
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.
Reliability Is the probability that software will not cause the failure of a system for a specified time under specified conditions
Repeatability An attribute of a test indicating whether the same results are produced each time the test is executed.
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.
Requirements The degree to which a requirement is stated in terms that permit establishment of test designs (and subsequently test cases) and execution of tests to determine whether the requirements have been met.
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 attributes such as reliability or usability.
Resource utilization The capability of the software product to use appropriate amounts and types of resources.
For example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions.
Result The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and communication messages sent out.
Resumption criteria The testing activities that must be repeated when testing is re-started after a suspension.
Review A detailed check of the test basis to determine whether the test basis is at an adequate quality level to act as an input document for the test process.
Reviewer The person involved in the review who shall identify and describe anomalies in the product or project under review. Reviewers can be chosen to represent different viewpoints and roles in the review process.
Risk A factor that could result in future negative consequences; usually expressed as impact and likelihood.
Risk management Systematic application of procedures and practices to the tasks of identifying, analyzing, prioritizing, and controlling risk.
See The Risk Management Guide.
Robustness The degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions.
Roll in roll out (RIRO) Used on some systems to describe swapping.
Root cause An underlying factor that caused a non-conformance and possibly should be permanently eliminated through process improvement.
Rule A statement of the form: if X then Y else Z. The if part is the rule premise, and the then part is the consequent. The else component of the consequent is optional.
The rule fires when the if part is determined to be true or false.
Rule Base The encoded knowledge for an expert system. In a rule-based expert system, a knowledge base typically incorporates definitions of attributes and rules along with control information.

© RuleWorks - All Rights Reserved - Policy - - Sitemap