Test Management
Test Management
• Test Management is a process where testing activities are managed to ensure high-
quality and high-end testing of software applications.
• This method consists of tracking, organization, controlling process, checks the
visibility of the testing process in order to deliver a high-quality software application.
• There are a lots of test management tools out there. Some of them are made good
and some made are great.
• key features of great piece of test management.
1. Attractive user interface and easy to use design.
2. Traceability.
3. Facilitates scheduling and organization.
4. Monitoring and metrics.
5. Flexibility.
Test Management Phase
• This topic briefly introduces Test Management Process and shows you
an overview of Test Management Phases. You will learn more details about
each Test Management Phases in the next articles.
• It is a procedure of managing the software testing activities from start to
end.
• It provides planning, controlling,
tracking and monitoring throughout
the whole project cycle.
This process involves several activity
Planning and execution.
Planning
1.Risk Analysis and Solution
• Risk is the potential loss (an undesirable outcome, however not necessarily
so) resulting from a given action or an activity.
• Risk Analysis is the first step which Test Manager should consider before
starting any project.
• Because all projects may contain risks, early risk detection and identification
of its solution will help Test Manager to avoid potential loss in the future &
save on project cost.
2.Test Estimation
• An estimate is a forecast or prediction.
• Test Estimation is approximately determining how long a task would take to complete.
• Estimating effort for the test is one of the major and important tasks in Test Management.
3. Test Planning
• A Test Plan can be defined as a document describing the scope, approach, resources, and schedule of
intended Testing activities.
• A project may fail without a complete Test Plan. Test planning is particularly important in large software
system development.
• In software testing, a test plan gives detailed testing information regarding an upcoming testing effort,
including:
• Test Strategy
• Test Objective
• Exit /Suspension Criteria
• Resource Planning
• Test Deliverables
4.What is Test Organization in Software Testing?
• Test Organization in Software Testing is a procedure of defining roles in
the testing process.
• It defines who is responsible for which activities in testing process.
• Test functions, facilities and activities are also explained in the same
process.
• The competencies and knowledge of the people involved are also
defined however everyone is responsible for quality of testing process.
• Now you have a Plan, but how will you stick to the plan and execute it?
To answer that question, you have Test Organization phase.
• Generally speaking, you need to organize an effective Testing Team.
You have to assemble a skilled team to run the ever-growing testing
engine effectively.
Execution
1.Test Monitoring and Control
• What will you do when your project runs out of resource or exceeds the
time schedule? You need to Monitor and Control Test activities to bring it
back on schedule.
• Test Monitoring and Control is the process of overseeing all the metrics
necessary to ensure that the project is running well, on schedule, and not
out of budget.
Monitoring
• Monitoring is a process of collecting, recording, and reporting information about
the project activity that the project manager and stakeholder needs to know
• To Monitor, Test Manager does following activities
• Define the project goal, or project performance standard
• Observe the project performance, and compare between the actual and the
planned performance expectations
• Record and report any detected problem which happens to the project
Controlling:-
• Project Controlling is a process of using data from monitoring activity to bring
actual performance to planned performance.
• Test Manager takes action to correct the deviations from the plan. In some cases,
the plan has to be adjusted according to project situation.
Issue management
• It mentioned in the beginning of the topics.
• All projects may have potential risk. When risk happen it becomes an
issue.
• In life cycle of any project, there will be always an unexpected
problems and questions that crop up.
1. The company cuts down your project budget.
2. Your project team lacks the skills to complete project.
3. The project schedule is too right for your team to finish the project
at the deadline.
Integration testing
• Incremental integration testing
• Decremental integration testing
Software Metrics
• A measurement is an manifestation of the size, quantity, amount or dimension
of a particular attributes of a product or process.
Needs of software measurement:-
1. Create the quality of the current product or process.
2. Anticipate future qualities of the product or process.