a) Test Management Process:

Test Management: It concerned with both test resource and test environment management. It is the role of test management to ensure that new or modified service products meet business requirements for which they have been developed or enhanced.

Test Management Process:

1. 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 test challenge and aspect that will be carried out for the software.
2. 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.
3. Test Execution : Manner of executing and test the actual system result against the expected result is test execution. Test execution can be done manually and by using automation suit. During the execution tester needs to make sure, that the user’s need of the software is occupied in the software.
4. 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 mile stone. Tester needs to set the exit criteria at the beginning, exit criteria may change during the project run as well.

5. Test reporting gives the picture of 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 an 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.

   

1. Naming and storage conventions for test artifacts: Every test artifacts(test specification, test case, test results and so on)have to be named appropriately and meaningfully. It enables

a) Easy identification of the product functionality.

b) Reverse mapping to identify the functionality corresponding to a given set of tests. e.g. modules shall be M01,M02.Files types can be .sh, .SQL.

In addition to file naming conventions, the standards may also stipulate the conventions for directory structures for tests. These directory structures are mapped into configuration management repository.

2. Documentation standards: Documentation standards specify how to capture information about the tests within the test scripts themselves. It should include:

a. Appropriate header level comments at the beginning of a file that outlines the functions to be served by the test.

b. Sufficient inline comments, spread throughout the file

c. Up-to-Date change history information, reading all the changes made to the test file.