Tester's dictionary [S-Z] | Testing terms Glossary

Technical review 

A Technical review is a static white-box testing method which is conducted to spot the defects early in the project life cycle that cannot be detected by black box testing method.

Test Approach 

A test approach is define how testing should be carried out.

Test approach has two techniques:

• Proactive –In order to find and fix the defects this test design process is initiated and build is created.
• Reactive –Once design and coding are completed this type of testing is started.

Test Automation 

It is special software to control the execution of test cases and compare the actual outcome with predicted outcome.

Test Basis 

The test basis is the basic information user need in order to start test analysis and create test cases.

Test Bed 

Test Bed is an execution environment configured for software testing. It consists of specific hardware, Operating System, network topology, system software, configuration of the product to be under test and other applications.

Test Case 

It is  specific executable test that examines all aspects including inputs and outputs of a system and then provides a detailed description of the steps that should be taken, the results that should be achieved, and other elements that should be identified. Steps explained in a test case include all details even if it they are assumed to be common knowledge. Test cases are used as a technical explanation and reference guide for systems.

Test Case Design Technique

Test design techniques can be defined as high level verification steps that are created to design a product or software that is free from all kinds of defects. Test design techniques can be derived from business scenarios and are categorized based on the type of testing. Based on the criticality of your business scenario, test design techniques are prioritized into low, medium and high. The test design techniques allow the developers to execute the tests based on the risk factor.

Different type of test case design technique are :

• Black Box test case design technique
  • Boundary value analysis
  • Decision table testing
  • State transition testing
  • Equivalence class partitioning
  • Use case testing

• White Box test case design technique
  • Condition coverage
  • Decision coverage
  • Statement coverage

• Experience Based test case design technique
  • Exploratory testing
  • Fault attack

Test Suite 

A test suite, less commonly known as a validation suite, is a collection of test cases that are intended to be used to test a software program to show that it has some specified set of behaviors. Test suites often contain detailed instruction or goal for each collection of test case and information on the system configuration to be used during testing. A group of test cases may also contain prerequisite states or step and descriptions of the following tests.

Test Completion Criterion 

The completion criteria are what user needs to stop the testing or check for objective of testing is reached. The completion criteria are derived from the strategy and should be based on a higher the risk, risk analysis, the stricter the completion criteria, the lower the risk the less demanding and specific the completion criteria

Test Completion Report

It is summarized format of test metrics which submitted to all the stakeholders in the project after execution of test case.

Test Completion Matrix 

It is collection of metrics that are collected after completing the testing endeavor.

It consists of below columns:-

• Test case field
• Number of test cases executed
• Number of pass
• Number of fail
• Pass percentage
• Fail percentage
• Comments

Test Data 

A set of data created for testing new or revised applications. Test data should be developed by the user as well as the programmer and must contain a sample of every category of valid data as well as many invalid conditions as possible.

Test Data Management 

Test Data management is very critical during the test life cycle. The amount of data that is generated is enormous for testing the application. Reporting the results it minimizes the time spent for processing the data and creating reports greatly contributes to the efficiency of an entire product.

Test Driven Development

Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle: first the developer writes an (initially failing) automated test case that defines a desired improvement or new function, then produces the minimum amount of code to pass that test, and finally re-factors the new code to acceptable standards.

Test Driver 

Driver is a piece of code that passes test cases to another piece of code. Test Harness or a test driver is supporting code and data used to provide an environment for testing part of a system in isolation. It can be called as a software module which is used to invoke a module under test and provide test inputs, control and, monitor execution, and report test results or most simplistically a line of code that calls a method and passes that method a value.

Test Environment 

A testing environment is a setup of software and hardware on which the testing team is going to perform the testing of the newly built software product. This setup consists of the physical setup which includes hardware, and logical setup that includes Server Operating system, client operating system, database server, front end running environment, browser (if web application), IIS (version on server side) or any other software components required to run this software product. This testing setup is to be built on both the ends – i.e. the server and client.

Test Execution 

Test execution is the process of executing the code and comparing the expected and actual results. Following factors are to be considered for a test execution process:

• Based on a risk, select a subset of test suite to be executed for this cycle.
• Assign the test cases in each test suite to testers for execution.
• Execute tests, report bugs, and capture test status continuously.
• Resolve blocking issues as they arise. 

Test Management 

Test management most commonly refers to the activity of managing the computer software testing process. A test management tool is software used to manage tests (automated or manual) that have been previously specified by a test procedure. It is often associated with automation software. To manage the tests (like, keeping track of the same kind of data for a given set of tests,   knowing which tests need to run in a common environment, number of tests planned, written, run, passed or failed).

• Scheduling of tests to be executed (manually or by a test execution tool)
• Managing the testing activities (time spent in test design, test execution, whether we are on schedule or on budget) 

Test Maturity Model 

Test maturity model is based on capability maturity model describes an increasing series of levels of a software development in an organization. The higher the level better is the software development process and hence reaching each level is a time-consuming and expensive process.

Test Plan 

Test plan is the project plan for the testing work to be done. It is not a test design specification, a collection of test cases or a set of test procedures; in fact, most of our test plans do not address that level of detail. Many people have different definitions for test plans. 

Test Steps 

Test Steps describe the set of execution steps and expected results that are documented against each one of this steps.

Each step is marked pass or fail based on the comparison result between the actual and expected outcome. 

Test Strategy 

A test strategy is an outline that describes the testing strategy for the software development cycle. It is created to inform developers, project managers, testers and about some key issues in the testing process. This includes the objective of testing, methods for testing new functions, total time taken and project resources required, testing environment. 

Test Tools 

Tools from a software testing context can be defined as a product that helps in one or more test activities right from planning, creating a build,  requirements, test execution, defect logging, test execution  and test analysis. 

Thread Testing 

A thread is the smallest unit of work that a system can execute. Top-down testing method where the testing is carried out within the small unit.

Top down Integration Testing 

In this approach testing is done from main module to sub module. If the sub module is not completely developed a temporary program called STUB is created for to simulate the sub module.
Advantages:

• Advantageous if major flaw occurs toward the top of the program.
• Representation of test case is easier once the I/O function is added. 

Total Quality Management 

Total Quality Management (TQM) is a comprehensive and structured approach to organizational management that seeks to improve the quality of product and service through ongoing refinements in response to continuous feedback. TQM requirements may be defined separately for a particular organization or may be in adherence to established standards, such as the International Organization for Standardization's ISO 9000 series. 

Traceability 

The significance of traceability within test management tool (like HP Quality Center) ora requirement tool allows user to link between requirements and test cases.