Scribd
Upload
75 views

Monitoring and Control

The document discusses monitoring and control in software testing. It covers test progress monitoring, reporting, and control. Test monitoring involves periodically checking the status of a test project and preparing reports to compare actual progress to plans. Common monitoring metrics include test coverage, schedule status, and economics. Data is gathered manually or via tools. Reporting communicates findings to stakeholders and supports decisions. Test control involves guiding actions based on monitoring to achieve best outcomes.

Uploaded by

Maria Holguin
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
75 views

Monitoring and Control

The document discusses monitoring and control in software testing. It covers test progress monitoring, reporting, and control. Test monitoring involves periodically checking the status of a test project and preparing reports to compare actual progress to plans. Common monitoring metrics include test coverage, schedule status, and economics. Data is gathered manually or via tools. Reporting communicates findings to stakeholders and supports decisions. Test control involves guiding actions based on monitoring to achieve best outcomes.

Uploaded by

Maria Holguin
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

Monitoring and Control

Agenda

● Monitoring and Control (PMC)


● Test Progress Monitoring
● Test Reporting
● Test Control
Monitoring and Control (PMC)

The purpose of Project Monitoring and Control (PMC) (CMMI-DEV) is to provide an


understanding of the project’s progress so that appropriate corrective actions can be taken
when the project’s performance deviates significantly from the plan.
What is Test Monitoring?
Test monitoring is the process related to periodically checking the status (measure progress) of
a test project.

It is a test management task where reports are prepared to compare the actuals against what
was planned. Metrics may also be used to assess progress against the planned schedule and
budget. Typically this is done by the QC Test Manager (Test Leader).
Purposes of Test Monitoring
What is test monitoring useful for?
•Feedback for the team and the test manager
•Visibility about test results
•Measuring the status of the testing, test coverage and test items
•Determining whether the work is done
•Gathering data
•For decision making
•For use in estimating future test efforts
Some Metrics

Some common metrics for test progress monitoring include:


•Completion of test environment preparation
•Extent of test coverage achieved
•Status of the testing progress
•Compared to various test milestones
•Economics of testing
•E.g., costs and benefits of continue test executions

Note: Detailed metrics will be explained on the Metrics module.


Gathering Data
How do we gather data for test monitoring?
•Manually
•Using documents, spreadsheets and simple databases
•For small projects
•Using automated tools
•For large teams, distributed projects and long-term test efforts
Reporting Test Status

What is reporting test status about?


•Communicating our findings to other project stakeholders
•Helping them understand the results of a test period
•Reports can be used to support conclusions, recommendations, and
decisions
Reporting Test Status

At any stage of the project, you need information that helps to understand how close
you are to reach the project quality goals.
Test reporting is concerned with summarizing information about the testing
endeavour, including:
● What happened during a period of testing, such as dates when exit criteria were
met.
● Analyzed information and metrics to support recommendations and decisions
about future actions, such as an assessment of remaining defects, the economic
benefit of continued testing, outstanding risks, and the level of confidence in
tested software.
Reporting Test Status (cont...)

● Metrics should be collected during and at the end of a test level in order to
assess:
✓ The adequacy of the test objectives for that test level.
✓ The adequacy of the test approaches taken.
✓ The effectiveness of the testing regarding its objectives.
How do we Report?

Test status can be reported in a variety of ways – according to:


•Preferences of the testers and stakeholders
•Needs and goals of the project
•Regulatory requirements
•Time and money constraints
•Limitations of the tools available for test status reporting
When to define our Test Report

The means for test status reporting should be considered early


•During the test planning and preparation periods
•In this phase
● Initial effective and efficient metrics should be selected and defined
upon project needs.
● Be sure that the exit criteria conditions are clearly tracked and
presented.
● Define how the testing progress and product quality are going to be
tracked and presented.
The Status Report
There is no a recipe that fits all the situations, you can take some template or create your own
reports.
The outline of a test summary report is given in ‘Standard for Software Test Documentation’
(IEEE 829)
Consider the Template of the QC Status Report provided by the current Globant framework.

Key information that you cannot omit:


● Sprint or Release scope
● Quality PBI status (PBI: Product Backlog Item)
● Testing progress
● Bugs still open that prevent a sign-off
● Open bugs accumulated if any
Common Considerations

How will you assess:


•Adequacy of the test objectives

•Adequacy of the test approaches

•Effectiveness of the testing


Test Control

Test control is about guiding and corrective actions to achieve the best
possible outcome for the project
Test control describes any guiding or corrective actions taken as a result of information and
metrics gathered and reported and their corresponding follow up. Actions may cover any test
activity and may affect any other software life cycle activity or task.

Examples of test control actions are:


● Re-prioritize tests when an identified risk occurs (e.g. software delivered late).
● Change the test schedule due to availability of a test environment.
● Set an entry criteria requiring fixes to be retested (confirmation tested) by a developer
before accepting them into a build.
Test Control - Taking Corrective Actions

What can be done to correct a delay?


•Additional test resources can be requested
•E.g., personnel, workstations, equipment, and tools

•The test execution plan itself can be adapted


•Test cases with low priority can be omitted
•Test cases with multiple variants can be run in just a single variant
•Consider only Test Cases that cover main or critical areas
Test Control - Taking Corrective Actions

Changes to test plan must be communicated clearly

● The testing Schedule must change accordingly in the testing plan

● The test manager has involve the stakeholders in formal communication


indicating the new schedule. Making certain that all parties involved now about
the changes (internal and external teams)
Q&A

Do you have any question? Please feel free to reach out to [email protected]
Thank You

You might also like