1. Fundamentals Of Testing

Question 1

What is the definition of testing?

Answer 1

The process consisting of all lifecycle activities (both static and dynamic) that deal with the planning, preparation, and evaluation of a software product.

Question 2

What is the goal of testing?

Answer 2

Ensure that software meets all specified requirements, that it fulfils its purpose, and to find any defect conditions.

Question 3

What is the difference between testing and debugging?

Answer 3

Testing by testers, shows error effects
Debugging by Devs, finds analyzes and fixes error conditions in code

Question 4

What is the difference between verification and validation?

Answer 4

Verification checks that a software meets its specifications (requirement doc). Non/functional requirements

Validation ensures a software meets customer expectations, as spec may not reflect user needs

Question 5

What is quality control?

Answer 5

A product-oriented, corrective approach. Focus on achieving appropriate levels of quality. Testing is a form of QC. Test results fix defects.

Question 6

What is quality assurance?

Answer 6

Process-oriented, preventive.
Focus on process implementation and improvement. Everyone’s responsible.
Applies development and testing processes.
Test results provide feedback on performance of said processes

Question 7

What is an error?

Answer 7

Errors are mistakes made by people. Causes include time pressure, lack of training, complexity of subject

Question 8

What is a defect?

Answer 8

Errors produce defects, which are faults or bugs. Defects are found in documentation.

Question 9

What is a failure?

Answer 9

Unintended behaviour in software caused by defects or environmental conditions

Question 10

What is root cause analysis?

Answer 10

Finding the fundamental reason for a problem, in order to prevent/reduce the frequency of similar defects & failures

Question 11

Testing Principle 1. Testing shows…

Answer 11

Testing shows the presence, not the absence of defects.

Question 12

Testing principle 2. Exhaustive testing…

Answer 12

Exhaustive testing is impossible. (Prioritize to focus test efforts)

Question 13

Testing principle 3. Early testing saves…

Answer 13

Early testing saves time and money (shift left)

Question 14

Testing principle 4. Defects…

Answer 14

Defects cluster together (~Pareto principle of 80/20)

Question 15

Testing principle 5. Tests…

Answer 15

Tests wear out. (updates vital, except in automated regression testing)

Question 16

Testing principle 6. Testing depends…

Answer 16

Testing depends on context. (No universal approach)

Question 17

Testing principle 7. Absence…

Answer 17

Absence-of-defects fallacy. (Verification AND validation essential)

Question 18

The test process usually consists of which 7 processes?

Answer 18

Test planning, analysis, design, implementation, execution, completion. Monitoring and control throughout.

Question 19

What is the goal of test planning?

Answer 19

Define test objectives and select an approach to achieve them

Question 20

What is the goal of test monitoring and control?

Answer 20

Ongoing checks which compare actual process to the plan. Then taking actions required to meet the objectives of testing

Question 21

What is the goal of test analysis?

Answer 21

Defines “what to test?” by analyzing test basis for features to test. We define these conditions, then prioritize them. The test basis is verified to identify defects

Question 22

What is the goal of test design?

Answer 22

Defines “how to test?” by turning test conditions into test cases. We decide how much (coverage items) and where (test environment) we test, and what we need to do so (test data requirements, tools & infrastructure). Closely linked to test implementation

Question 23

What is the goal of test implementation?

Answer 23

We acquire the testware, create test suites/procedures including scripts (manual and automatic). We then prioritize the tests by arranging their execution schedule, then build and verify the test environment. Closely linked to test design, the more practical side.

Question 24

What is the goal of test execution?

Answer 24

Test! Manual or automated, in order of test schedule. Then log results, compare to expected results, analysis and reporting of anomalies based on failures observed

Question 25

What is the goal of test completion?

Answer 25

The official end of a round of tests, at release/end of iteration/completion of test level. We create change requests or product backlog for unresolved defects along with a test report to pass on to stakeholders. The test environment is shut down, and useful testware is archived/handed over

Question 26

What is testware?

Answer 26

Testware is the product of test activities. Any kind of output (test cases/procedures, logs, defect reports, change requests…)

Question 27

What are the roles in testing?

Answer 27

Test management, testing itself. Can both be done by same person.

Question 28

What is involved in the test management role?

Answer 28

The activity around testing: test planning, monitoring/control, and completion. Responsibility for the process, team and leadership.

Question 29

What is involved in the testing role?

Answer 29

Testing. So analysis, design, implementation and execution of tests

Question 30

What are the benefits of independent testing?

Answer 30

Recognize a variety of failures and defects.
Assumptions: disprove, verify, challenge
Perspective: background, bias, technical knowledge

Question 31

What are the drawbacks to independent testing?

Answer 31

Blame: for delays, finger-pointing at found defects
Ownership: devs lose responsibiliy for quality
Outsider: less collaboration/relationship with dev
Bottleneck