Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
12 Cards in this Set
- Front
- Back
|
Test Case
|
A set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as to exercise a particular program path or to verify compliance with a specific requirement. |
|
|
Blocked test case
|
A test case that cannot be executed because the preconditions for its execution are not fulfilled. |
|
|
Traceability matrix |
A two-dimensional table, which correlates two entities (e.g., requirements and test cases). The table allows tracing back and forth the links of one entity to the other, thus enabling the determination of coverage achieved and the assessment of impact of proposed changes. Does not usually have text, has IDs for test and requirements. Best made early in the process as possible. |
|
|
Test basis |
All documents from which the requirements of a component or system can be inferred. The documentation on which the test cases are based. If a document can be amended only by way of formal amendment procedure, then the test basis is called a frozen test basis. |
|
|
Test case explosion |
The disproportionate growth of the number of test cases with growing size of the test basis, when using a certain test design technique. Test case explosion may also happen when applying the test design technique systematically for the first time. |
|
|
Equivalence partitioning |
A black-box test design technique in which test cases are designed to execute representatives from equivalence partitions. In principle, test cases are designed to cover each partition at least once. Synonyms: partition testing |
|
|
Domain analysis |
A black-box test design technique that is used to identify efficient and effective test cases when multiple variables can or should be tested together. It builds on and generalizes equivalence partitioning and boundary values analysis. |
|
|
Boundary value analysis |
A black-box test design technique in which test cases are designed based on boundary values. |
|
|
Decision table testing |
A black-box test design technique in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table. |
|
|
State Diagram |
A diagram that depicts the states that a component or system can assume, and shows the events or circumstances that cause and/or result from a change from one state to another. |
|
|
Show Stopper |
Bug that causes an implementation to stop and become essentially useless. This critical bug must be fixed for the development process to proceed further.
|
|
|
Test to Break |
http://softwaretestingcareers.blogspot.com/2012/03/how-important-is-test-to-break-attitude.html (finish making this card) |
