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;
7 Cards in this Set
- Front
- Back
|
Types of SW testing? |
1. White box testing 2. Black box testing 3. Gray box testing |
|
|
SW testing |
Testing is the process of establishing confidence that SW or system does what it is supposed to doobjective Testing is a way to access the quality of the SW and to reduce the risk of SW failure in operation |
|
|
Principles of Testing |
1. Testing shows the precence of bugs 2. Exhausive testing is impossible 3. Early testing 4. Defect clustering 5. The pesticise paradox 6. Testing is context dependent 7. Abcence of errors fallacy |
|
|
Errors? |
A human action producing an incorrect result When programers make errors, they introduce faults in to code. Or any person involved in development activities can make error, which injects a fault into a deliverable. |
|
|
Faults/Bugs |
A fault is manifestation of a human error in SW Faults can be caused by requirements, designs or coding errors |
|
|
Failure |
Failure is a deviation of a SW from its expected behavior/delivery/service |
|
|
Test process |
- test activities and task - test work products - tracebility between test basis and work products |
