Chapter 1: Fundamentals of Testing

Question 1

Why is Testing Necessary?

Answer 1

1. Human Error (mistake) -> Defect (fault, bug) -> Failure.
2. Measures the quality of the software.
3. Gives confidence in the quality.
4. Reduces the overall level of risk.
5. How much testing? It depends on risk, safety & project constraints.

Question 2

Testing Objectives

Answer 2

1. Finding Defects.
2. Preventing defects.
3. Providing information for decision-making.
4. Gaining confidence about the level of quality.

Question 3

7 Testing Principles (TEED PTA)

Answer 3

(TEED PTA)

1. Testing shows the presence of defects, not the absence of defects.
2. Exhaustive testing is impossible.
3. Early testing.
4. Defect clustering.
5. Pesticide paradox (Tests wear out)
6. Testing is context-dependent.
7. Absence-of-error fallacy.

Question 4

The Psychology of Testing

Answer 4

1. The mindset of Developer & Tester.
2. Communication in a constructive manner.
3. Test Independence.

Question 5

Why we make mistakes

Answer 5

(TTCL)

1. time pressure
2. tired
3. complexity of work products or processes
4. lack adequate training

Question 6

Test Activities and Tasks

Answer 6

(PMA I ET)

1. Test planning
2. Test Monitoring and control
3. Test analysis and design
4. Test implementation and execution – Creation of test suites (logical collection of cases)
5. Evaluating exit criteria and reporting
6. Test closure activities

Question 7

Best practices while reporting defects

Answer 7

1. Communicate findings in a neutral, fact focused way. Don’t criticize.
2. Be pessimistic and start with collaborations rather than battles

Question 8

Failures are caused by ___

Answer 8

1. Defects
2. Environment conditions
3. Malicious damage

Question 9

How much testing is enough depends on ___

Answer 9

1. Technical and business risks
2. Project constraints (time & budget)

Question 10

Why we do testing

Answer 10

1. Product satisfy requirements
2. Fit for purpose
3. Detect defects

Question 11

What is Testing?

Answer 11

Software testing is a set of activities to discover defects and evaluate the quality of software artifacts.

These artifacts, when being tested, are known as test objects.

Question 11

Testing vs QA

Answer 11

Testing is a form of quality control (QC)
QC is a product-oriented, corrective approach that focuses on those activities supporting the achievement of levels of quality.

QA is a process-oriented, preventive approach that focuses on the implementation and improvement of processes.

Question 12

Failures

Answer 12

Errors and defects are not the only cause of failures.

Failures can also be caused by environmental conditions

Question 13

Root cause

Answer 13

A root cause is a fundamental reason for the occurrence of a problem

Question 14

Testing shows the presence, not the absence of defects.

Answer 14

Testing can show that defects are present in the test object, but cannot prove that there are no defects.

Testing reduces the probability of defects remaining undiscovered in the test object, but even if no defects are found, testing cannot prove test object correctness.

Question 15

Defects cluster together

Answer 15

A small number of system components usually contain most of the defects discovered or are responsible for most of the operational failures.

This phenomenon is an illustration of the Pareto principle. Predicted defect clusters, and actual defect clusters observed during testing or in operation, are an important input for risk-based testing

Question 16

Tests wear out

Answer 16

If the same tests are repeated many times, they become increasingly ineffective in detecting new defects.

Question 17

Absence-of-defects fallacy

Answer 17

It is a fallacy (i.e., a misconception) to expect that software verification will ensure the success of a system.

Question 18

Test process

Answer 18

There are common sets of test activities without which testing is less likely to achieve test objectives.

These sets of test activities form a test process.

Question 19

Traceability between the Test Basis and Test

Answer 19

• Traceability of test cases to requirements can verify that the requirements are covered by test cases.
• Traceability of test results to riskscan be used to evaluate the level of residual risk in a test object

Question 20

Roles in Testing

Answer 20

a test management role and
a testing role

Question 21

Test management role

Answer 21

A test management role takes overall responsibility for the test process, test team and leadership of the test activities.

The test management role is mainly focused on the activities of test planning, test monitoring and control and test completion.

Question 22

Testing role

Answer 22

The testing role takes overall responsibility for the engineering (technical) aspect of testing.

The testing role is mainly focused on the activities of test analysis, test design, test implementation and test execution.

Question 23

Generic Skills Required for Testing

Answer 23

While being generic, the following skills are particularly relevant for testers:

• Testing knowledge (to increase effectiveness of testing, e.g., by using test techniques)
• Thoroughness, carefulness, curiosity, attention to details, being methodical (to identify defects, especially the ones that are difficult to find)
• Good communication skills, active listening, being a team player (to interact effectively with all stakeholders, to convey information to others, to be understood, and to report and discuss defects)
• Analytical thinking, critical thinking, creativity (to increase effectiveness of testing)
• Technical knowledge (to increase efficiency of testing, e.g., by using appropriate test tools)
• Domain knowledge (to be able to understand and to communicate with end users/business representatives)

Question 24

Confirmation bias

Answer 24

Confirmation bias can make it difficult to accept information that
disagrees with currently held beliefs.

Question 25

Whole Team Approach

Answer 25

In the whole-team approach any team member with the necessary knowledge and skills can perform any task, and everyone is responsible for quality.

Question 26

Independence of Testing

Answer 26

The main benefit of independence of testing is that independent testers are likely to recognize different kinds of failures and defects compared to developers because of their different backgrounds, technical perspectives, and biases.