| |
Glossary |
|
| |
............................................................................................................................... |
|
| |
Acceptance Testing: Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.
|
|
| |
|
|
| |
Agile Testing: Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm. See also Test Driven Development . |
|
| |
|
|
| |
Automated Testing:
- Testing employing software tools which execute tests without manual intervention. Can be applied in GUI, performance, API, etc. testing.
- The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.
|
|
| |
|
|
| |
Backus-Naur Form: A metalanguage used to formally describe the syntax of a language. |
|
| |
|
|
| |
Basic Block: A sequence of one or more consecutive, executable statements containing no branches. |
|
| |
|
|
| |
Basis Path Testing: A white box test case design technique that uses the algorithmic flow of the program to design tests. |
|
| |
|
|
| |
Baseline: The point at which some deliverable produced during the software engineering process is put under formal change control. |
|
| |
|
|
| |
Benchmark Testing: Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration. |
|
| |
|
|
| |
Black Box Testing: Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component. |
|
| |
|
|
| |
Bottom Up Testing: An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested. |
|
| |
|
|
| |
Boundary Testing: Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests). |
|
| |
|
|
| |
Bug: A fault in a program which causes the program to perform in an unintended or unanticipated manner. |
|
| |
|
|
| |
Boundary Value Analysis: BVA is similar to Equivalence Partitioning but focuses on "corner cases" or values that are usually out of range as defined by the specification. his means that if a function expects all values in range of negative 100 to positive 1000, test inputs would include negative 101 and positive 1001. |
|
| |
|
|
| |
Breadth Testing: A test suite that exercises the full functionality of a product but does not test features in detail. |
|
| |
|
|
| |
Capture/Replay Tool: A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools. |
|
| |
|
|
| |
Cause Effect Graph: A graphical representation of inputs and the associated outputs effects which can be used to design test cases. |
|
| |
|
|
| |
Code Walkthrough: A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions. |
|
| |
|
|
| |
Compatibility Testing: Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware. |
|
| |
|
|
| |
Concurrency Testing: Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores. |
|
| |
|
|
| |
Conformance Testing: The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing conformance to a formal standard. |
|
| |
|
|
| |
Conversion Testing: Testing of programs or procedures used to convert data from existing systems for use in replacement systems. |
|
| |
|
|
| |
Data Dictionary: A database that contains definitions of all data items defined during analysis. |
|
| |
|
|
| |
Data Flow Diagram: A modeling notation that represents a functional decomposition of a system. |
|
| |
|
|
| |
Debugging: The process of finding and removing the causes of software failures. |
|
| |
|
|
| |
Defect: Nonconformance to requirements or functional / program specification. |
|
| |
|
|
| |
Dependency Testing: Examines an application's requirements for pre-existing software, initial states and configuration in order to maintain proper functionality. |
|
| |
|
|
| |
Depth Testing: A test that exercises a feature of a product in full detail. |
|
| |
|
|
| |
Endurance Testing: Checks for memory leaks or other problems that may occur with prolonged execution. |
|
| |
|
|
| |
End-to-End testing: Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate. |
|
| |
|
|
| |
Exhaustive Testing: Testing which covers all combinations of input values and preconditions for an element of the software under test. |
|
| |
|
|
| |
Functional Specification: A document that describes in detail the characteristics of the product with regard to its intended features. |
|
| |
|
|
| |
|
|
| |
|
|
