Chapter 1
-- Summary --
-- Questions & Answers
-- Exam Questions distribution --
Swipe for more
Kalboussi Karim
Examinable Learning Objectives :
Level 1 : Remember (K1)
- The candidate will remember, recognize and recall a term or concept.
- Action verbs : Identify, recall, remember, recognize.
- Exmaple : Identify typical test objectives.
rim
Level 2 : Understand (K2)
- The candidate can select the reasons or explanations for statements related to the
topic, and can summerize, compare, classify and give examples for the testing concept.
- Action verbs : Classify, compare, contrast, differentiate, ditinguish...
- Exmaple : Explain the activities of the review process.
Level 3 : Apply (K3)
Ka
- The candidate can carry out a procedure when confronted with a familiar task, or
select the correct procedure and apply it to a given context.
- Action verbs : Apply, implement, prepare, use.
- Exmaple : Apply test case prioritization.
Chapter 1 Question Distribution in the Exam :
- There is a total of 8 questions required for Chapter 1 :
si
K1 = 2 questions
K2 = 6 questions
K3 = 0 questions
- Number of points for this chapter = 8
us
lbo
rim
rim
rim
Ka
Ka
Ka
si
si
si
Ka
us
us
us
lbo
lbo
lbo
Ka
Ka
Ka
Kalboussi Karim 02
Summary of Chapter 1
1.1 What is Testing ?
1.1.1 (K1) identify typical test objectives
rim
- Evaluating work products (requirements, user stories, designs and code).
- Triggering (causing) failures and finding (identifying) defects.
- Building confidence in the quality of the test object.
- Reducing the level of risk of inadequate software quality.
- Verifying that documented/specified requirements are met.
- Ensuring required coverage of a test object.
Ka
- Verifying that a test object complies with contractual, legal and regulatory
requirements.
- Providing information to stakeholders so they can make informed decisions.
- Validating wether the test object is complete and meets user/stakeholders
expectations.
1.1.2 (K2) differentiate testing from debugging
- Debugging is the process of finding, analyzing, and removing defects.
si
- Debugging is concerned with locating defects (locating defects only when we do
dynamic testing) and fixing these defects.
- Testing can directly find defects in the test object when we do static testing.
us
- Testing can trigger failures that are caused by defects.
- Testing does not find the cause of defects !
- Debugging does not fix the cause of defects !
- Debugging does not fix failures !
- Debugging is a non testing activity !
lbo
1.2 Why is testing so necessary ?
1.2.1 (K2) Exemplify why testing is necessary
- Testing indirectly contributes to higher quality test objects.
- Testing provides a means of directly evaluating the quality of a test object at
various stages of the SDLC.
Ka
- Testing provides users with indirect representation on the development project.
- Reviews increase the quality of requirements specifications and lead to fewer
changes being needed in derived work products.
- Static testing is used by developers to identify defects in their program code
earlier than can be achieved through dynamic testing.
- Testing may also be required to meet contractual or legal requirements, or to
comply with regulatory standards.
Kalboussi Karim 03
1.2.2 (K1) Recall the relation between testing and quality assurance
- Quality Control(QC) is a product-oriented corrective approach and Quality
Assurance(QA) is a process-oriented preventive approach.
- Testing is a form of quality control (QC).
- Test results are used by both (QA) and (QC) teams, used by (QA) teams to
rim
provide feedback on how well the development and test processes are
performing, and used by (QC) teams to fix defects.
1.2.3 (K2) Distinguish between root cause, error, defect, and failure
- Human beings make errors (mistakes), which produce defects ( faults/bugs),
which in turn may result in failures.
Ka
- If a defect in a code is executed, the system may fail to do what it should do, or
do something it shouldn’t, causing a failure.
- Failures can be caused by errors, defects, or environmental conditions.
- A root cause is a fundemental reason for the occurence of a problem, a root
cause is a situation that leads to an error.
- Root causes are identified through root cause analysis.
si
1.3 Testing principles
1.3.1 (K2) Explain the seven testing principles
Testing shows the presence, not the absence of defects : If no defects are
us
found, testing cannot prove test object correctness.
Exhaustive testing is impossible : Rather than attempting to test exhaustively,
test techniques, test cases prioritization, and risk-based testing should be used
to focus test efforts. (Exhaustive testing is not feasible except in trivial cases).
Early testing saves time and money : To find defects early, both static testing
lbo
and dynamic testing should be started as early as possible.
Defects cluster together : A small number of system components usually
contain most of the defects discovered, responsible for most of the operational
failures. (Predicted and actual defect clusters are an important input for risk-
based testing).
Tests wear out : Repeating same tests becomes ineffective in detecting new
defects. Existing tests and test data may need to be modified.
Ka
Testing is context dependent : Testing is done differently in different
contexts.
Absence-of-defects fallacy : It is a fallacy to expect that software verification
will ensure the success of a system, in addition to verification, validation should
also be carried out.
Kalboussi Karim 04
1.4 Test activities, Testware and test Roles
1.4.1 (K2) Summarize the different test activities and tasks
Test activities may appear to follow a logical sequence, but they are
implemented often iteratively or in parallel.
rim
Test planning : Defining test objectives and selecting an approach that best
achieves the objectives.
Test monitoring & Control : Monitoring is the ongoing check of all test
activities and comparaison of actual test progress against the plan. Control is
about taking actions necessary to meet the objective of testing.
Test analysis (What to test?) : Analyzing the test basis to identify testable
features, to define and prioritize associated test condidtion, together with the
Ka
related risks and risk levels. test basis and test objects are also evaluated to
identify defects they may contain. Test analysis is often supported by the use
of test techniques.
Test Design (How to test?) : Elaborating test conditions into test cases and
other testware, identification of coverage items, which will help specify test
cases inputs. Defining the test data requirements, designing the test
environment and identifying any other required infrastructure and tools. Test
si
techniques can be used to support this activity.
Test implementation : Includes creating or acquiring the testware necessary
for test execution (test data, ...). Test cases can be organized into test
procedures and are often assembled into test suites.
us
Test execution : Running test in accordance with the test execution schedule.
Actual test results are compared with the expected results.
Test completion : Change requests or product backlog items created for any
unresolved defects. Test environment is shutdown to an agreed state. Any
testware that may be useful in the future is identified. A test completion
lbo
report is created and communicated to the stakeholders. Test activities are
analyzed to identify lessons learned and improvements for future iterations,
releases, or projects.
1.4.2 (K2) Explain the impact of context on the test process
The way testing is carried out will depend on a number of contextual factors like
Ka
the SDLC, team members (skills, knowledge, level of experience...), identified
product risks, market needs, specific regulations, criticality of the test object,
technical factors (type of software, technology used...), project constaints
(scope, time, budget...), organizational factors (structure, existing policies,
practices...), tools (availablity, usability, compliance...) and also stakeholders
(needs, expectations, willingness to cooperate...)
Kalboussi Karim 05
1.4.3 (K2) Differentiate the testware that supports the test activities
Testware is created as output work products from the test activities :
Test planning : Test plan that contains test schedule, risk register and entry and
exit critera. Risk register is a list of risks together with the risk likelihood, risk
rim
impact and risk mitigation.
Test monitoring & Control : Test progress reports, documentation of control
directives and risk information.
Test analysis : Prioritized test conditions and defect reports (regarding defects
in the test basis).
Test Design : Prioritized test cases, test charters, coverage items, test data
requirements and test environment requirements (elements needed to build it).
Ka
Test implementation : Test procedures, automated test scripts, test suites, test
data, test execution schedule, test environment items (drivers, simulators...)
Test execution : Test logs and defect reports.
Test completion : Test completion report, action items for improvements,
lessons learned and change requests.
1.4.4 (K2) Explain the value of maintaining traceability
si
It is important to establish traceability throughout the test process between the
test basis elements, testware associated with these elements, test results and
us
detected defects. Traceability of test cases to requirements is performed to verify
that the requirements are covered by test cases, traceability of test results to
risks to evaluate the level of residual risk in a test object, traceability between
user requirements and test execution results provides a means of measuring
project progress against buisness goals. Good traceability makes it possible to
determine the impact of changes, and also make test progress and completion
lbo
reports more easily understandable.
1.4.5 (K2) Compare the different roles in testing
Test management role : Takes overall responsibility for the test process, test
team and leadership of the test activities. This role is focused on the activities of
test planning, test monitoring & control, and test completion.
Ka
Testing role : Takes overall responsibility for the engineering (technical) aspect
of testing (evaluating test basis and test object, defining test environment
requirements, assessing the testability of a test object). The testing role focuses
on the activities of test analysis, test design, test implementation, and test
execution.
Kalboussi Karim 06
1.5 Essential skills and good practices in Testing
1.5.1 (K2) Give examples of the generic skills required for testing
Testing knowledge, thouroughness, carefulness, curiosity, attention to details,
good communication skills, being a team player, analatyical thinking, critical
rim
thinking, creativity, technical knowledge, and domain knowledge.
1.5.2 (K1) Recall the advantages of the whole team approach
- Any team member with the necessary knowledge and skills can perform any
task, and everyone is responsible for quality. The whole team approach (practice
coming from Extreme programming) improves team dynamics, enhaces
Ka
communication and collaboration and creates synergy.
- Testers help buisness representatives to create suitable acceptance tests.
- Testers collaborate with developers to define and agree on the test strategy.
1.5.3 (K2) Distinguish the benefits and drawbacks of independance
of testing
- The independance of testing makes the tester more effective at finding defects
si
due to differences between the author’s and the tester’s cognitive biases.
- Independant testers are likely to recognize different kinds of failures and defects
compared to developes because of their different backgrounds, technical
us
perspectives and biases. (developers are not objective about their code).
- Independant testers can verify, challenge, or disprove assumptions made by
stakeholders.
- Independant testers may be isolated from the development team, which may
lead to a lack of collaboration, communication problems, or an adversial
relationship with the development team.
lbo
- The independance of testing level are :
No independance : Work products are tested by their author.
Some independance : Work products are evaluated by the author’s peer from
the same team.
High independance : Work products are evaluated by testers outside the
Ka
author’s team but within the same organization.
Very high independance : Work products are evaluated by testers outside the
organization.
Swipe for the questions part
Kalboussi Karim 07
Questions from Chapter 1
in the ISTQB exam
1.1.1 (K1) identify typical test objectives
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 08
rim
Ka
si
1.1.2 (K2) differentiate testing from debugging
us
lbo
Ka
Kalboussi Karim 09
rim
Ka
si
us
lbo
1.2.1 (K2) Exemplify why testing is necessary
Ka
Kalboussi Karim 10
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 11
1.2.2 (K1) Recall the relation between testing and quality assurance
rim
Ka
si
us
1.2.3 (K2) Distinguish between root cause, error, defect, and failure
lbo
Ka
Kalboussi Karim 12
rim
Ka
si
us
lbo
1.3.1 (K2) Explain the seven testing principles
Ka
Kalboussi Karim 13
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 14
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 15
1.4.1 (K2) Summarize the different test activities and tasks
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 16
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 17
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 18
rim
Ka
si
1.4.2 (K2) Explain the impact of context on the test process
us
lbo
Ka
Kalboussi Karim 19
rim
Ka
si
1.4.3 (K2) Differentiate the testware that supports the test activities
us
lbo
Ka
Kalboussi Karim 20
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 21
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 22
rim
Ka
1.4.4 (K2) Explain the value of maintaining traceability
si
us
lbo
Ka
Kalboussi Karim 23
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 24
1.4.5 (K2) Compare the different roles in testing
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 25
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 26
1.5.1 (K2) Give examples of the generic skills required for testing
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 27
rim
Ka
si
1.5.2 (K1) Recall the advantages of the whole team approach
us
lbo
Ka
Kalboussi Karim 28
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 29
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 30
1.5.3 (K2) Distinguish the benefits and drawbacks of independance
of testing
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 31
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 32
rim
Ka
si
us
lbo
Ka
Kalboussi Karim 33
Conclusion
In this document :
We identified the examinable learning
objectives.
We presented the probability of
questions for each part of chapter 1.
We summarized chapter 1.
We provided section-wise questions
and their answers for chapter 1.
If you need any assistance or
have questions, feel free to
reach out! 😊
Karim Kalboussi
[email protected]
