ISTQB FOUNDATION 4.0 | Tutorial 52 | Test Monitoring & Test Control | Test Metrics | ISTQB Tutorials
Summary
TLDRThis tutorial delves into the ISTQB Foundation Level Certification, focusing on Chapter 5.3 about managing test activities, specifically test monitoring, control, and completion. It explains the importance of monitoring project progress and taking corrective actions through test control when deviations occur. The video introduces test matrices as tools for consistent progress measurement, covering various aspects of testing such as defect, risk, and coverage. It also touches on test completion activities and the types of reports involved, aiming to equip test managers with the knowledge to select appropriate matrices for effective testing.
Takeaways
- π The tutorial is focused on Chapter 5 of the ISTQB Foundation Level certification, specifically on test monitoring, control, and completion.
- π Monitoring is about consistently measuring the ongoing progress of a project against a plan, considering factors like cost, time, and effort.
- π Test control involves taking corrective or guiding actions as a result of deviations observed during monitoring activities.
- π Test matrices are formulas and calculations used to measure various aspects of testing activities, such as defect, risk, coverage, and confidence.
- π Test control uses information from monitoring to provide control directives, guidance, and corrective actions to ensure effective and efficient testing.
- π¦ Examples of control directives include reprioritizing tests, re-evaluating test item criteria, adjusting test schedules, and adding resources when necessary.
- π Test completion involves collecting data from completed test activities to consolidate experience and other relevant information at project milestones.
- π Test matrices help show progress against the plan, schedule, budget, current quality of the test object, and the effectiveness of test activities.
- πΊοΈ The analogy of using Google Maps for navigation illustrates the concept of monitoring and control in testing, where the app acts as a matrix guiding the tester.
- π Some high-level examples of matrices include project progress, test progress, product quality, defect, risk, coverage, and cost matrices.
- π‘ The responsibility of selecting and measuring matrices lies with the test manager, who must understand and apply them to monitor various testing activities.
Q & A
What is the main focus of Chapter 5 in the ISTQB Foundation Level certification tutorial?
-Chapter 5 focuses on managing test activities, with a particular emphasis on test monitoring, control, and completion in the context of the tutorial.
What does the term 'monitoring' refer to in the context of project management?
-In project management, 'monitoring' refers to the consistent progress measurement of ongoing project activities, ensuring that the plan is being followed and adjusted as necessary.
What is the purpose of test control in the context of testing activities?
-Test control is the corrective or guiding action taken as a result of deviations observed from the monitoring activity, ensuring that the testing process stays on track and meets its objectives.
What are the common activities that might be predefined as part of test control planning?
-Common activities in test control planning may include reprioritizing tests, re-evaluating test item criteria, adjusting test schedules, and adding new resources when necessary.
What is the role of a test manager in the context of test control activities?
-A test manager is responsible for taking appropriate control actions when deviations are observed during monitoring. This includes making decisions that may not have been planned for and require immediate attention.
What are test matrices, and how do they relate to monitoring in testing?
-Test matrices are formulas and calculations used to measure and monitor various aspects of testing activities, such as defect risk, coverage, and confidence, helping to assess progress and quality.
According to the tutorial, what information does test monitoring gather, and how is it used?
-Test monitoring gathers information about testing progress, which is used to assess whether the test exit criteria are satisfied and to measure the effectiveness of testing towards its objectives.
What are some examples of control directives in test control?
-Examples of control directives include reprioritizing tests when a risk occurs, re-evaluating test item criteria due to rework, adjusting test schedules for delays, and adding resources when needed.
What is the significance of test completion in the testing process?
-Test completion is a critical activity that consolidates data from completed test activities, including test RAR and other relevant information, and occurs at project milestones such as the completion of a test level or project.
What are the two types of reports mentioned in the tutorial related to test completion?
-The two types of reports mentioned are the test progress report and the test completion report, which provide updates on the ongoing testing and a comprehensive overview upon completion, respectively.
Can you provide an example of how test matrices can be used in a practical scenario?
-An example of using test matrices is like using Google Maps for navigation. The maps provide a planned route (plan), and as you travel (monitoring), if you deviate from the route (deviation), the maps reroute you (control), ensuring you reach your destination efficiently.
Outlines
π Test Monitoring and Control Basics
This paragraph introduces the fundamental concepts of test monitoring and control within the context of the ISTQB Foundation level certification. It explains that monitoring involves tracking the progress of a project against a plan, considering factors such as cost, time, and effort. Deviations from the plan prompt corrective actions known as test control, which can vary based on the specific deviation observed. The paragraph emphasizes the role of the test manager in selecting appropriate control actions, which may not always be predefined but are crucial for guiding the project back on track. It also introduces test matrices as tools for consistent monitoring, which are formulas and calculations aiding in the measurement of various testing activities.
π Understanding Test Matrices and Their Applications
The second paragraph delves into the specifics of test matrices, which are formulas and calculations used to measure and monitor testing activities. It mentions that while over 100 matrices exist to cover the entire testing lifecycle, the paragraph provides a high-level overview suitable for test managers. The matrices serve to show progress against the plan, the current quality of the test object, and the effectiveness of test activities. The paragraph uses an analogy of using Google Maps for navigation to explain the concept of monitoring and control, highlighting how matrices act as guides for test managers. It also lists various types of matrices, including project progress, test progress, product quality, defect, risk, coverage, and cost matrices, emphasizing their importance in managing different aspects of testing and project management.
Mindmap
Keywords
π‘ISTQB Foundation Level Certification
π‘Test Monitoring
π‘Test Control
π‘Deviation
π‘Test Manager
π‘Test Matrices
π‘Test Completion
π‘Test Progress Report
π‘Coverage
π‘Risk Matrices
π‘Quality
Highlights
Introduction to managing test activities in Chapter 5 of the ISTQB Foundation Level certification.
Explanation of test monitoring and control as part of test management.
Monitoring is about consistent progress measurement of ongoing project plans.
Importance of monitoring cost, time, and effort in project management.
Test control as a corrective action in response to deviations from the plan.
Test control activities are corrective or guiding actions resulting from monitoring deviations.
Responsibilities of the test manager in taking appropriate control actions.
Introduction to test matrices as tools for consistent monitoring of progress.
Definition of test matrices as calculations and formulas for measuring testing entities.
Overview of the syllabus on test monitoring, control, and matrices from the ISTQB.
Test monitoring involves gathering information to assess test progress and exit criteria.
Examples of control directives such as reprioritizing tests and adjusting schedules.
Concept of test completion, collecting data from completed test activities.
Test completion activities occur at project milestones like test level completion or project cancellation.
Introduction to test progress and completion reports, to be covered in the next tutorial segment.
Discussion on the selection of test matrices by test managers for monitoring.
Examples of test matrices including project progress, test progress, product quality, and risk matrices.
Explanation of how test matrices help measure the effectiveness of testing activities.
Analogy of using Google Maps for monitoring and control activities in testing.
Conclusion and invitation for further queries and exploration of the topic.
Transcripts
Hello friends and greetings for the day
welcome back to another tutorial on
istqb Foundation level certification we
are in chapter 5 talking about managing
the test activities and moving on to the
next segment which is 5.3 test
monitoring test control and test
completion in this particular tutorial
we'll be talking about the monitoring
and control along with
matrices
as a part of chapter 1 however we have
given you a very high level
understanding on what exactly monitoring
control and matrices are in simple word
monitoring is all about keeping and
consistent progress measurement on the
ongoing progress of the project of
course a plan is created but until
unless you keep an eye on how exactly
the plan is being progressed as we have
multiple factors to take care of like
the cost the time the effort Etc thus it
becomes very important that how exactly
the things are being done if in case we
find a deviation as an output of the
monitoring we look forward to take an
appropriate control action and that
control action is what we refer to as
test control however a test control
activity is defined as a corrective or
guiding action which is taken as a
result of deviation observed from the
monitoring activity now control actions
can be very very appropriate to that of
the deviation observed thus it may not
be certainly can be standardized so but
uh there could be some some of the
common activities which we quite often
observe in our projects we may predefine
them as well as a part of the planning
itself but certainly most of the things
are very undetermined which you may not
have planned so you may have to take as
a test manager a very very appropriate
control action and that's where this
becomes the major responsibilities of
the test manager not a test engineer and
when it comes to the test mates these
are those weapons what we can use to
consistently monitor the ongoing
progress so matri are generally some
sort of calculations and formula which
helps you measure an entity within the
life cycle of testing so let's quickly
have a look on what exactly the cbus is
trying to say and deep dive into the
same definitions what we just discussed
so as we talk about the syllabus the
test monitoring is concerned with
gathering information about testing this
information is used to assess test
progress and to measure whether the test
exit criteria or the test task
associated with the exit criteria are
satisfied such as meeting the target for
the coverage of the product risk
requirements or acceptance criteria in
simple words anything what you do can be
very well measured and must be monitored
for their ongoing progress if in case we
observe a deviation we have to take
appropriate control action at the same
time if I'm talking about the test
control uh test control uses the
information from the test monitoring to
provide in a form of the control
directives guidance and the necessary
corrective action to achieve the most
effective and efficient testing examples
of control directive include
reprioritizing test when an identified
risk occurs re-evaluating whether a test
item meets entry or exit criteria due to
rework and adjusting the test schedule
to address a delay in delivery of the
test environment or even adding new
resources when there is a need for it so
in simple words they have just given you
some sample examples from different
point of view but however those things
what happens in reality would be very
very particular very very specific in
terms of controlling the deviations
observed so that's how we talk about the
control however in the introduction we
are also talking about what is test
completion so test completion certainly
collects data from the completed test
activities to consolidate The Experience
test RAR and any other relevant
information the test completion
activities occur at a project Milestone
such which as when a test level is
completed and aile iteration is finished
which is a Sprint a test project is
completed or sometime even canceled or
suspended a software system is released
or a maintenance release is completed
that means completion is one of the
major activity of the test process if
you remember from the chapter one
completion phase basically gathers
everything together but however we do
have two types of report that is test
progress report and test completion
report but just hold on we'll be talking
about this in our next next segment of
the same tutorial there we will cover in
deep time that what is test completion
report and how does it vary from the
test progress report in this tutorial
we're just targeting the monitoring and
control which are limited to the
definition now let's quickly look at
what are the test matrices and get some
good examples of it well here in this
particular part we will be talking about
the test matrices test matrices are as I
told you some formula and calculations
which measures any kind of activity any
kind of task which you perform in tes
in simple words or a very high level we
can monitor anything what happens in
testing including test defect risk
coverage confidence and this five
parameters covers everything what you do
in testing so all those metes are not
getting discussed in the foundation
level however if you are interested you
can always go and download the test
manager syllabus to get more details
about these matrices we have 100 plus
matrices available to measure or monitor
anything in entire testing life cycle
but right here we're just giving you a
very high level introduction because
test managers are the one who are
responsible to select the matrices and
measure them from time to time okay so
when it comes to test matrices the these
are gathered to show progress against
the plan schedule and budget the current
quality of test object and the
effectiveness of test activities with
respect to the objectives or an
iteration goal that means the overall
objective of the testing could could be
very easily measured with help of these
matrices in fact in very simple example
if I have to travel from point A to
point B and then I certainly take help
of Google Maps or vs or other kind of
options what you have on your cell phone
and the Google Maps say for example
gives you three different routes to
reach the put destination B but you
chose one of them being shortest and
taking less time however when you are
traveling from point A to point B the
plan when you search on the maps it said
that it will take you 1 hour of time to
get there but it does not mean it would
be exactly the same when you start
traveling right so when you start
traveling you consistently keep an eye
on the Google Maps as the lady says take
left in 100 meter continuous trade for 1
kilometer or she says take second exit
from the roundabout Etc and that's what
is called as monitoring you're
consistently listening to that lady
consistently following the directions
and listening to that person and
following it right but as soon as you
take a wrong turn probably you continue
straight and you are supposed to take
left the maps reroutes you stating that
hey if possible make a U-turn right and
that's does control that's a control
activity and in this entire discussion
the Google Maps was playing the role of
Matrix okay so let's quickly see some
good examples of the matrices from
different perspective however we will
not be very detailed here so some high
level examples are right here the
examples of matrices include
project progress matrics which includes
things like test completion resource
utilization or test effort applied so
far second test progress Matrix these
are all related to progress of testing
like test case implementation progress
test environment preparation progress
number of test case run not run pass or
fail overall test execution time also
talk about product quality matrices
availability response time meantime to
failure defect matrices like number and
ities of defect found or fixed defect
density defect detection percentage risk
matrices which includes at any point of
time the number of risk remaining to be
resolved or mitigated coverage matrices
requirement coverage code coverage
statement coverage decision coverage
path coverage whatnot there are so many
coverage as options available and also
to talk about the cost matrics which are
more from the project perspective so
cost of testing organizational cost of
quality so if you look at the matrices
uh kind of like once again you would
understand that hey we just discussed
almost everything what happens in
testing right from the test defect risk
coverage and people confidence and at
the same time not only these things but
we also talked about the project
matrices the product matrices the
process matrices and the people matrices
like resource utilization if you think
that you need one more extra resource to
do automation then you have already
exhausted all your resources for other
activities and that's where you need one
more person to be hired so we do have
many things to talk about right all the
parameters all the different matrices
does it becomes a very huge thing for a
test manager to take a call about but
for now all you need to understand is
there are something called as matrices
and each one of them whatever we discuss
right now has a formula behind the
screen okay but at this point of time
you need not worry that how exactly it's
being calculated at this point you just
need to know that what is a matric and
what are the examples of it right so
that's all from this particular tutorial
team should you have anything else feel
free to comment below I'm always there
to address your queries and answer them
well till then keep learning keep
exploring keep understanding the context
thanks for watching the video team and
happy
[Music]
learning
Browse More Related Video
ISTQB FOUNDATION 4.0 | Tutorial 53 | Test Progress Report | Test Summary Report | CTFL Tutorials
ISTQB FOUNDATION 4.0 | Tutorial 6 | 1.4 Test Activities, Testware & Test Roles (Part-2) | CTFL
ISTQB FOUNDATION 4.0 | Tutorial 57 | Tool Support for Testing | Test Tools | ISTQB Tutorials
ISTQB FOUNDATION 4.0 | Tutorial 43 | Sample Questions on Chapter 4 | ISTQB Foundation Exam Questions
ISTQB FOUNDATION 4.0 | Tutorial 49 | Test Pyramid | Testing Quadrants | Test Management | CTFL
ISTQB FOUNDATION 4.0 | Tutorial 5 | 1.4 Test Activities, Testware & Test Roles (Part-1) | CTFL
5.0 / 5 (0 votes)