Terminology in software testing (part 4, N-R)
Another week, another article covering terminology in software testing. This fourth part covers another range of letters, with the aim of giving clarity to key testing terms.
Negative testing: A type of testing designed to demonstrate that a component or system does not work. The word ‘negative’ relates to the testers’ attitude rather than an approach or technique.
Non-functional testing: A test type evaluating the attributes of a component or system not relating to functionality. For example, this testing will focus upon efficiency, usability and maintainability.
Operational testing: This evaluates a component or system in its operational environment.
Operational environment: Essentially the environment in which hardware and software products are installed and will be used. This can include operating systems and database management systems.
Operational profile testing: This type of testing is statistical and looks at system operations and their probability of typical use.
Pair testing: Quite simply, two testers work together on one computer to find errors.
Performance testing: This type of testing literally determines the performance of the test subject.
Portability testing: A software testing type used to determine the portability of a software product. In other words, it looks at whether it can be transferred from one hardware or software environment to another.
Process cycle test: A type of testing in which test cases are designed to execute business processes.
Quality Assurance (QA): An aspect of quality management that provides confidence in quality requirements being met.
Random testing: Test cases are selected to match an operational profile, meaning that this technique can be used for testing reliability and performance.
Recoverability testing: This testing type determines the recoverability of a software product. In other words, it verifies whether or not the software product can re-establish a specified level of performance. It also checks that data can be directly recovered in case of a failure.
Regression testing: Used to test something that has been tested previously and then modified. The objective is to ensure that defects have not been introduced or uncovered following the changes made.
Reliability testing: A type of testing used to verify the reliability of a software product.
Requirements-based testing: Test cases are based on test objectives and test conditions born out of requirements.
Resource utilisation testing: A testing type used to determine the resource-utilisation of a software product. In other words, it tests the product’s capability to use appropriate amounts and types of resources.
Risk-based testing: A testing type geared towards exploring and providing information about product risks.
That is all for the latest in our series of articles exploring terminology in software testing. Let us know if we have missed anything important out!
Read our break down of software testing terms from A to C.
Go through the testing terms from letters D to H.