КАТЕРИНА АБЗЯТОВА «Ефективне планування тестування ключові аспекти та практичні поради»
- 2. 2
Kateryna Abzyatova
Senior Manual QA Engineer at Ciklum
more than 12 years of
professional experience,
working as a Manual QA
engineer (Desktop, Web and
Mobile applications)
conducted more than 100
interviews for the position of
QA (specialists from Ukraine,
Poland, Bulgaria, India)
passed 4 ISTQB certifications:
Foundations, Mobile, Agile
tester and Advanced Test
Manager
more than 8 years of
experience in mentoring
junior specialists and
3+ years of ISTQB Trainer
experience
- 6. 6
6
Test plan -A document describing the scope, approach,
resources and schedule of intended test activities.
It identifies amongst others test items, the features to be
tested, the testing tasks, who will do each task, degree of
tester independence, the test environment, the test
design techniques and entry and exit criteria to be used,
and the rationale for their choice, and any risks requiring
contingency planning. It is a record of the test planning
process.
Version 1 (IEEE 829)
- 7. 7
Test Activities and Tasks
Test planning consists of defining the test objectives and then selecting an approach that best achieves
the objectives within the constraints imposed by the overall context.
01 02 03 04 05
Test
Planning
Test
monitoring
and control
Test
analysis
Test
design
Test
implementation
Test
completion
Test
execution
06 07
- 8. 8
Test Activities and Tasks
Test monitoring and control. Test monitoring involves the ongoing checking of all test activities and the
comparison of actual progress against the plan. Test control involves taking the actions necessary to meet
the objectives of testing.
01 02 03 04 05
Test
Planning
Test
monitoring
and control
Test
analysis
Test
design
Test
implementation
Test
completion
Test
execution
06 07
- 9. 9
Test Documentation
Common types of test management documents
Test policy-describes
the organization’s
objectives and goals
for testing
Master test plan (or
project test plan)-
describes the
implementation of the
test strategy for a
particular project
Test strategy-
describes the
organization’s general,
project-independent
methods for testing
Level test plan (or
phase test plan)-
describes the
particular activities to
be carried out within
each test level
- 12. 12
12
Test planning activities
➔ Analyze the test basis (e.g., specific requirements or risks), test conditions and
the tests that cover them
➔ The approach to testing is clearly defined by the Test Manager, including which
test levels will be employed, the goals and objectives of each level, and what test
techniques will be used at each level of testing.
➔ Identify the methods for gathering and tracking the metrics that will be used to
guide the project, determine adherence to plan and assess achievement of the
objectives
- 13. 13
13
Test planning activities
➔ List the specific features of the software that are within its scope (based on risk analysis,
if appropriate), as well as explicitly identifying features that are not within its scope.
➔ Create traceability matrix and cost/delivery timescales
➔ Check availability of resources needed
➔ External dependencies and associated service level agreements (SLAs) should be
identified and, if required, initial contact should be made
- 16. 16
Understanding Testing Stakeholders
People are stakeholders of
testing when they have an
interest in the testing activities,
the testing work products, or the
quality of the final system or
deliverable.
The stakeholder’s interest can be
direct or indirect involvement in
the testing activities, direct or
indirect receipt of testing work
products, or direct or indirect
effect by the quality of the
deliverables produced by the
project or program.
- 17. 17
Understanding Testing
Stakeholders
While the testing stakeholders vary, depending on the
project, the product, the organization, and other factors,
they can include the following roles:
● Developers,
development leads,
and development
managers.
● Database architects,
system architects, and
designers.
● Marketing and
business analysts.
● Senior management,
product managers and
project sponsors.
● Project managers.
● Technical support,
customer support, and
help desk staff.
● Direct and indirect
users.