Glossary of Terms beginning Alphabet-R
Race Condition / Coverage:
Race Condition is a cause of concurrency problems. It refers to multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access. It helps detect failure to synchronize access to resources. It is useful for testing multi-threaded programs such as in an operating system.
Ramp Testing involves continuously raising an input signal until the system breaks down.
Random Testing is 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.
Recoverability refers to the capability of the software product to re-establish a specified level of performance and recover the data directly affected in case of failure.
Recoverability Testing is the process of testing to determine the recoverability of a software product.
Recovery Testing involves testing how well a system recovers from crashes, hardware failures, or other catastrophic problems. It evaluates the contingency features built into the application for handling interruptions and for returning to specific points in the application processing cycle, including checkpoints, backups, restores, and restarts. This test also assures that disaster recovery is feasible.
Regression Testing involves repetition of testing on a previously verified program or application after the program has undergone some modifications with a view to extend the functionality or rectification of defects & to verify that no new defects have been introduced. Automated testing tools are quite useful in this type of testing.
Relational Operator Coverage:
Relational operator coverage is a metric, which reports whether boundary situations occur with relational operators (<, <=, >, >=). The hypothesis is that boundary test cases find off-by-one mistakes and uses of the wrong relational operators such as < instead of <=. Relational operator coverage reports whether the situation a==b occurs. If a==b occurs and the program behaves correctly, you can assume the relational operator is not suppose to be <=.
Release Candidate is a pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released).
Release Note is 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 a quality attribute pointing towards an extent to which the program can be expected to perform its intended functions with desired precision within a specific period of time or for a specified number of operations.
Reliability Testing is the process of testing to determine the reliability of a software product.
Replaceability is the capability of the software product to be used in place of another specified software product for the same purpose in the same environment.
Requirement refers to the statements given by the customer as to what needs to be achieved by the software system. Later on these requirements are converted into specifications which are nothing but feasible or implementable requirements. It is a set of conditions or capabilities 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.
Requirements-based Testing is 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.
Requirements Management Tool:
Requirements Management Tool is a tool that supports the recording of requirements, requirements attributes (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 Phase is the period of time in the software life cycle during which the requirements for a software product are defined and documented.
Resource Utilization is 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.
Resource Utilization Testing:
Resource Utilization Testing is the process of testing to determine the resource-utilization of a software product.
Result is 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 refers to the testing activities that must be repeated when testing is re-started after a suspension.
Re-Testing means testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions.
Reusability is a quality attribute pointing towards an extent to which a program can be used in other applications.
Review is an evaluation of a product or project status to ascertain discrepancies from planned results and to recommend improvements. Examples include management review, informal review, technical review, inspection, and walkthrough.
Reviewer is 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 is a factor that could result in future negative consequences; usually expressed as impact and likelihood.
Risk assessment when being referred to organizations involves evaluating existing physical and environmental security and controls, and assessing their adequacy relative to the potential threats of the organization.
Risk Analysis is the process of assessing identified risks to estimate their impact and probability or likelihood of occurrence. It broadly includes risk assessment, risk characterization, risk communication, risk management, and policy relating to risk. It is also known as Security risk analysis. Risk analysis when being referred to organizations involves identifying the most probable threats to the organization and analyzing the related vulnerabilities of the organization to these threats.
Risk-Based Testing is the testing oriented towards exploring and providing information about product risks.
Risk Control is the process through which decisions are reached and protective measures are implemented for reducing risks to, or maintaining risks within, specified levels.
Risk Identification is the process of identifying risks using techniques such as brainstorming, checklists and failure history.
Risk Management is the systematic application of procedures and practices to the tasks of identifying, analyzing, prioritizing, and controlling risk.
Risk Matrix refers to the representation of controls within an application systems used to reduce the identified risk, and in what segment of the application those risks exist. One of the dimensions of the matrix is the risk, while the second dimension is the segment of the application system and the controls are present at the intersections within the matrix. For example, if a risk is “incorrect input” and the systems segment is “data entry,” then the intersection within the matrix would show the controls designed to reduce the risk of incorrect input during the data entry segment of the application system.
Robustness is the degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions.
Root Cause refers to an underlying factor that caused a non-conformance and possibly should be permanently eliminated through process improvement.
Explanation to All Alphabets in the Glossary of Terms