Description
Test management most generally alludes to the action of dealing with the PC programming testing process. A test administration device is programming used to oversee tests that have been already indicated by a test method. It is frequently connected with automation software.
The planning, estimating, monitoring and controlling of test activities, is known as Test Management. It is typically carried out by test engineers. Following are the some of the test management used in software testing, such as:
- Test Management & Control
- Planning
- Estimation
- Monitoring and Control
- Configuration Management
- Risk Analysis
- Incident Management
- Defects Control
Conceptual
figure
Description
Arranging the in an ordered manner is known as Test Management. Test Management is also performed during Manual and Automation testing. Test control describes any guiding or corrective actions taken as a result of information and metrics gathered and reported. It includes the following measures, such as:
- Prioritize the coverage and reduce test coverage on low priority test cases.
- Rework effort.
Description
Planning will decide the outlook and describing then purpose of testing. Planning ought to be made by IEEE 829 principles. Planning decides the risks and extension. It will plan test examination and configuration exercises. Test planning is the key for the analyzer, to communicate with the product invocation groups.
Description
Test Estimation is an activity which tells how much time it will take to complete the task. It estimates about some of the measures such as :
Time is very important resource in project, because project has to deliver within the time to client.
To complete the project how much money is needed.
Resource includes apparatus, mankind, finance, required to finish the project.
Human skill will show more effect on project because person with low testing skills takes more time to complete the project.
- Time
- cost
- Resources
- human skill
Description
The importance for monitoring the progress is visibility about test activities. By monitoring, how much work has completed in preparing the test case is known and also test case execution is known. If the test plan is going out the track, by controlling, bring it back. Against affect, change the number of test iterations. Modify the Entry and Exit criteria.
Description
Configuration Management is a procedure for collecting the changing data in project when it changes from module to module. Configuration items are are distinguished in Configuration Management which changes from module to module. Test arranges, Test plan, Test cases, Actual result, Expected result are the results of Configuration Management in testing.
Description
Risk analysis is a procedure of portraying, speculating, arranging hazard. Risk is a chance of risk, inconvenience. So it requires strong investigation and administration. When risks are consider and detect, they should be overseen.
Description
Any unforeseen occasion that happens amid testing that requires consequent remedy is known as Incident Management. Incidents ought to be pursued from analysis and classification to modifying and arranging the solution. most widely recognized occurrence in programming. Open, new, assign, fixed, retest, close are the parts in bug life cycle.
Description
To convey a quality programming product to the client, imperfections ought to be handled. It ensure that the strategy, method, technique are going as per the task or not. It mainly focuses on execution to discover a bug. In the event that the analyzer discover more deformities, then the unwavering quality will increments.
Key Points
- To enhance the proficiency of testing, Test Management will assume a major part.
- There will be much better adaptability, convenience in testing.