Software Test management, process of managing the tests. Software test management is also performed using tools to manage both types of tests, automated and manual, that have been previously specified by a test procedure.
Software Test management tools allow automatic generation of the requirement test matrix (RTM), which is an indication of functional coverage of the application under test (SUT). Software Test Management tool often has multi functional capabilities such as test ware management, test scheduling, the logging of results, test tracking, incident management and test reporting.
Software Test Management Process
Software Test Management Process is a set of activities from the start of the testing to the end of the testing. It gives a discipline to testing. When following a test process it gives us the plan at the beginning. Test process provides the facility to plan and control the testing throughout the project cycle. It helps to track and monitor the testing throughout the project. Provides transparent testing among stakeholders and maintains the conducted test for future reference. Affords deep level of detail of the testing that’s being carried out. Gives clear understanding of testing activities of prior project and post project to all the stakeholders. There are many tools (Tools such as QTest, JIRA, Team Service, Test Link.) available to manage the test process. Test process can be defined and practiced differently according to the necessity in the test. Explained below are the typical activities in the test process.
Test Plan:
Test plan served as an initial sketch to carry out the testing. Testing is being tracked and monitored as per the test plan. It gives a prior picture of the test challenge and aspect that will be carried out for the software. By maintaining a test plan we can manage the changes in the plan. When starting new projects, based on the lesson learned in the previous tests, the test plan needs to be improved to get better. Test plan explains the overview of particular requirement which needs to be tested, scope, functional and non-functional requirement, risk and mitigation, testing approaches, test schedule and deliverables and schedule, out of scope and assumption, test team and allocation, test environment, test activities mechanism and any other special note for testing.
Test Design:
Test design affords how to implement the testing. Typically creating test cases is with inputs and expected output of the system and choosing which test cases are necessary for the execution of the test. Tester should have a clear understanding and appropriate knowledge to set the expected result. By this, coverage of the testing is defined and the tester will not miss any scenario. There are two types of test design techniques one is static testing and the other one is dynamic testing. Static testing is used to test without execution mostly to artifacts like documents and dynamic testing is testing by executing the system.
Test Execution:
Manner of executing and testing the actual system result against the expected result is test execution. Test execution can be done manually and by using an automation suit. During the execution tester needs to make sure that the user’s need of the software is occupied in the software. Test execution is conducted by referring to the document created during test design as a step by step process. Tester needs to keep track while executing the test cases.
Exit Criteria:
Exit criteria determines when to stop the test execution. Exit criteria is defined during the test plan phase and used in the test execution phase as a milestone. Tester needs to set the exit criteria at the beginning, exit criteria may change during the project run as well. There are factors like client need, system stability and filled function that decide the exit criteria. Once the tester reached the exit criteria testing will be stopped. Below are some common exit criteria.
Test Reporting:
Test reporting gives the picture of the test process and result for the particular testing cycle. To define the element in the test reporting the first thing that needs to be considered is whom the audiences of the test report are. For example a project manager will like to see the high level picture of the testing, intermediate people will wish to view more detail and the client will expect the test reporting in the criteria such as requirement basis, feature basis. Test reports are prepared and communicated periodically like daily, weekly, month etc. This needs to be sent in different stages and time. In the future project results of test reports need to be analyzed and apply the lesson learned. Test reports contain elements such as test execution status, completed. percentage, plan vs. executed test cases, test environment, test execution by resources, risk and mitigation if any, defect summary, test scenario and conditions, any assumption, any note etc.
Software Test Management Responsibilities
- Software Test Management has a clear set of roles and responsibilities for improving the quality of the product.
- Software Test management helps the development and maintenance of product metrics during the course of a project.
- Software Test management enables developers to make sure that there are fewer design or coding faults.
