Software Testing Cycle Flashcards

(40 cards)

1
Q

It is also known as Software Testing Process

A

Software Testing Life Cycle

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

It defines the various stages / phases / activities in the testing of software

A

Software Testing Life Cycle

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

This STLC phase is where you review the business and software requirements and identify any defects in those specifications

A

Requirements Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

This STLC phase is where once you have gathered a general idea of what needs to be tested, you ‘plan’ for the tests.

A

Test Planning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

This STLC phase is where you design / detail your tests on the basis of detailed requirements / design of the software

A

Test Designing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

This STLC phase is where you setup the test environment (server / client / network, etc) with the goal of replicating the end-users’ environment

A

Test Environment Setup

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

This STLC phase is where you execute your Test Cases / Scripts in the Test Environment to see whether they pass/

A

Test Execution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

This STLC phase is where you prepare various reports for various stakeholders

A

Test Reporting and Closure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Work Product for this STLC Phase: ‘Review Defect’ Reports

A

Requirements Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Work Product for this STLC Phase: Test Plan, Test Estimation, Test Schedule

A

Test Planning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Work Product for this STLC Phase: Test Cases / Test Scripts / Test Data, Requirements Traceability Matrix

A

Test Designing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Work Product for this STLC Phase: Test Environment

A

Test Environment Setup

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Work Product for this STLC Phase: Test Results (Incremental), Defect Reports

A

Test Execution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Work Product for this STLC Phase: Test Results (Final), test Metrics, and Test Closure report

A

Test Reporting and Closure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

The First STLC Phase

A

Requirements Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

The Second STLC Phase

A

Test Planning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

The Third STLC Phase

A

Test Designing

18
Q

The Fourth STLC Phase

A

Test Environment Setup

19
Q

The Fifth STLC Phase

A

Test Execution

20
Q

The Last STLC Phase

A

Test Reporting and Closure

21
Q

This Software Testing Principle means that Testing can only reveal defects; it cannot prove that a system is defect-free.

A

Testing shows the presence of defects, not their absence

22
Q

This Software Testing Principle means that due to infinite scenarios and paths, testing everything is unfeasible. Prioritization is key.

A

Exhaustive testing is impossible

23
Q

This Software Testing Principle means that Catching defects early (e.g., during requirement reviews) prevents costly fixes later.

A

Early Testing Saves Time and Money

24
Q

This Software Testing Principle means The Pareto Principle (80-20 rule) applies —- most defects are found in a small portion of the system

A

Defects cluster together

25
This Software Testing Principle means Repeating the same tests over time reduces their effectiveness, Tests should evolve with the software
Beware of the Pesticide Paradox
26
This Software Testing Principle means that Testing strategies must be adapted to the type of software being testes (e.g., games vs safety-critical systems).
Testing is context-dependent
27
This Software Testing Principle means that a defect-free system is not necessarily useful if it does not meet user expectations.
Absence-of-errors is a fallacy
28
These are different stages of the software development lifecycle where testing is conducted
Software Testing Levels
29
A level of the software testing process where individual units of a software are tested.
Unit Testing
30
The purpose of this level is to validate that each unit of the software performs as designed
Unit Testing
31
A level of the software testing process where individual units are combined and tested as group
Integration Testing
32
The purpose of this level of testing to expose faults in the interaction between integrated units.
Integration Testing
33
A level of the software testing process where a complete, integrated system is tested.
System Testing
34
The purpose of this level is to evaluate the system's compliance with the specified requirements
System Testing
35
A level of the software testing process where a system is tested for acceptability
Acceptance Testing
36
The purpose of this test is to evaluate the system's compliance with the business requirements and assess whether it is acceptable for delivery.
Acceptance Testing
37
It is a separate level of Software Testing Levels that is just a type of testing that can be performed at any of the four main levels
Regression Testing
38
WHEN to test
Level
39
HOW to test
Method
40
WHAT to test
Type