- Ramp Testing
Continuously raising an input signal until the system breaks down - Random Testing
Testing a program or part of a program using test data that has been chosen at random - Recovery Testing
Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions - Regression Testing
Regression testing is any type of software testing which seeks to uncover bugs that occur whenever software functionality that previously worked as desired stops working or no longer works in the same way that was previously planned. - Release Candidate
A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs - Reliability Testing
Testing to determine whether the system/software meets the specified reliability requirements. - Requirements based Testing
Designing tests based on objectives derived from requirements for the software component - Resource utilization testing
The process of testing to determine the Resource-utilization of a software product - Risk-based testing
Testing oriented towards exploring and providing information about product risks - Sanity Testing
Brief test of major functional elements of a piece of software to determine if its basically operational - Scalability Testing
Performance testing focused on ensuring the application under test gracefully handles increases in work load - Scenario Testing
A scenario test is a test based on a hypothetical story used to help a person think through a complex problem or system. They can be as simple as a diagram for a testing environment or they could be a description written in prose. - Security Testing
Tests focused on ensuring the target-of-test data (or systems) are accessible only to those actors for which they are intended. - Session-based Testing
Session-based testing is ideal when formal requirements are non present, incomplete, or changing rapidly. It can be used to introduce measurement and control to an immature test process, and can form a foundation for significant improvements in productivity and error detection. It is more closely related to Exploratory testing. It is a controlled and improved ad-hoc testing that is able to use the knowledge gained as a basis for ongoing, product sustained improvement - Simulator
A device, computer program or system used during testing, which behaves or operates like a given system when provided with a set of controlled inputs - Smart testing
Tests that based on theory or experience are expected to have a high probability of detecting specified classes of bugs; tests aimed at specific bug types - Smoke Testing
A sub-set of the black box test is the smoke test. A smoke test is a cursory examination of all of the basic components of a software system to ensure that they work. Typically, smoke testing is conducted immediately after a software build is made. The term comes from electrical engineering, where in order to test electronic equipment, power is applied and the tester ensures that the product does not spark or smoke. - Soak Testing
Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed - Soap-opera testing
A technique for defining test scenarios by reasoning about dramatic and exaggerated usage scenarios. When defined in collaboration with experienced users, soap operas help to test many functional aspects of a system quickly and-because they are not related directly to either the systems formal specifications, or to the systems features-they have a high rate of success in revealing important yet often unanticipated problems. - Software Quality Assurance
Software testing is a process used to identify the correctness, completeness and quality of developed computer software. Actually, testing can never establish the correctness of computer software, as this can only be done by formal verification (and only when there is no mistake in the formal verification process). It can only find defects, not prove that there are none. - Stability Testing
Stability testing is an attempt to determine if an application will crash. - State Transition Testing
A test case design technique in which test cases are designed to execute state transitions. - Statement Testing
Testing designed to execute each statement of a computer program. - Static Testing
Analysis of a program carried out without executing the program - Statistical Testing
A test case design technique in which a model is used of the statistical distribution of the input to construct representative test cases. - Storage Testing
Testing whether the system meets its specified storage objectives. - Stress Testing
Stress testing is a form of testing that is used to determine the stability of a given system or entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results.Stress testing a subset of load testing. - Structural Testing
White box testing, glass box testing or structural testing is used to check that the outputs of a program, given certain inputs, conform to the structural specification of the program - SUT
System Under Test - Syntax Testing
A test case design technique for a component or system in which test case design is based upon the syntax of the input. - System Testing
System testing is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of Black box testing
Tags