Test Management or Test Administration is the process of managing testing activities to ensure high-quality testing of the software application. The method consists of organizing, controlling, ensuring traceability and visibility of the testing process to deliver the high-quality software application. It ensures that the software testing process goes as expected.

THE TEST MANAGEMENT PROCESS

The Test Management Process is a procedure for managing software testing activities from start to finish. The test management process provides facilities for planning, controlling, tracking and monitoring throughout the project cycle. The process includes several activities, such as test planning, design and test execution. It gives an initial plan and discipline to the software testing process.

There are two main parts of the test management process:

• Planning
  1. Risk analysis
  2. Test estimation:
  3. Test planning
  4. Testing Organization
• Implementation
  1. Test monitoring and control
  2. Problem management
  3. Test report and evaluation

THE PLANNING

1. Risk analysis and solution

Risk is the potential loss (an undesirable outcome, but not necessarily so) resulting from a particular action or activity.

A risk analysis is an initial task that the TestManager must perform before starting a project. Because all projects can contain risks, early risk detection and solution identification will help the TestManager avoid potential loss in the future and save on project costs. This analysis also aims to make the right decisions during the project to deliver on time without losing quality.

2. Test estimation:

A Test Estimate is to approximate how long it will take to complete a task. Estimating test effort is one of the most important tasks in Test Management.

What are the benefits of proper estimation?

1. Accurate test estimates lead to better planning, execution and monitoring of tasks under the attention of a test manager.
2. Ensures more accurate planning and helps achieve results with greater confidence.

3. Test planning

A test plan can be defined as a document that describes the scope, approach, resources and schedule of the intended test activities .

A project can fail without a complete test plan. Test planning is especially important in the development of large software systems. When testing software, a test plan provides detailed testing information about the upcoming testing effort, including:

• Test Target
• Scope determination
• Criteria for closing/suspension
• Resource Planning
• Test results

4. Test Organization

Test organization in software testing is a procedure for defining roles in the testing process. It defines who is responsible for what activities in the 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, but everyone is responsible for the quality of the testing process.

THE IMPLEMENTATION

Now you have a plan, but how do you stick to the plan and execute it?

In general, you need to organize an effective testing team. You must assemble a competent team to make the ever-expanding test engine work effectively.

1. Test monitoring and control

What will you do if your project runs out of funds or exceeds its schedule ? You need to monitor and control testing activities to get it back on track.

Test monitoring and control is the process of monitoring all metrics necessary to ensure that the project is going well, on schedule and not off budget.

Supervision

Monitoring is a process of collecting, recording and reporting information about the project activity that the project manager and stakeholders need to know

To verify, Test Manager does the following activities:

• Defining the project goal or project performance standard
• Observe project performance and compare actual and planned performance expectations
• Record and report any detected problem

Check

Project control is a process that uses data from monitoring activities to bring actual performance to planned performance.

In this step, the Test Manager takes action to correct the deviations from the plan. In some cases, the plan must be adapted to the project situation.

2. Problem management

All projects can have potential risk. When the risk occurs, the risk becomes a problem.
In the life cycle of any project, unexpected problems and questions will always arise.

For example:

• Company lowers project budget
• The project team does not have the skills to complete the project
• The project schedule is too tight for the team to complete the project by the deadline.

Risk to be avoided during testing:

• Missing the deadline
• Exceeding the project budget
• Loss of customer confidence

When these issues arise, you must be ready to address them or they could potentially affect the outcome of the project.

3. Test Report & Evaluation

The project has been completed. It is now time to look back at the trajectory.

The Test Evaluation Report” describes the results of the Testing in terms of Test coverage and exit criteria. The data used in the test evaluation are based on the test results and the summary of test results.

The Test Team always issues an opinion on the quality of the system. This information is then used by stakeholders to decide whether it is a good idea to launch the product or not.