The document outlines the key steps in a software testing life cycle including test plan preparation, test case design, test execution and logging, defect tracking, and test reporting. It provides details on each step such as how test plans define the overall testing approach and objectives, test cases define what to test and expected results, and defects identified during testing are tracked, assigned a severity, and prioritized for resolution.

1. Testing Life Cycle(TLC) Test plan preparation Test case design Test execution and Test Log preparation Defect Tracking Test report preparation

2. TLC Test Plan : A document that defines the overall testing approach is called Test Plan. Test Case Design : Document that defines what is selected to test,and describes the expected result is called Test Design.Set of procedures inorder to find out the defects. Test Execution : Executing the test cases.

3. TLC Test log : Pass and fail information will be stored in this test log. Defect tracking : All the failed items will come under the defect tracking. (closing defect) Test report : Reports are generated during the TLC.Final test summary report. (generated at the end of testing for making decisions)

4. Test Plan Preparation (manual) Test Objective : A test objective is simply a testing “goal”.It is a statement of what the tester is expected to perform during the testing activity. Test strategy : 1. Techniques that are going to be used during the testing. 2. What types of tests must be conducted. 3. What stages of testing are required.(e.g.unit,system)

5. Test Risk Analysis: A risk is a condition that can result in a loss.The risk that may occur/arise during the analysis of the testing. * The probability that the negative event will occur.

6. Risk identified - - - Unavailability of resources - software hardware etc . Mitigation plan - - - What are the ways to overcome

7. Test schedule & Resources Task Duration Resource Test plan 3 1 Test design 5 3

8. Roles and Responsibilities Test Manager - Manages the entire testing activity (approve). Test leader - Prepare the test plan, Review test case, monitor defect tracking and Reports Preparation. Test Engineer - Prepare test case design and Daily reports.

9. Communications Approach The communications during the project will be informed through this communication approach.

10. Test Environment The Test Bed for the Testing Activity is identified. Like, * Software Requirements. * hardware Requirements.

11. Automated Test Tools Identify which tools is used for each individual test Should know the test level criteria

12. Test Case Design (manual) Test case ID : Sys_xyz_o1 Test case description : A short note about the testing. Test case procedure : Each and every step has to be mentioned in test case procedure. Test inputs (or) Test Data : Input data

13. Expected result : The Expected out come of the test case. Test Execution Actual result : What we have received is the actual result. Expected result = Actual result then the test is pass otherwise it is fail.

14. Test Log * Failed test case are going to be the defects Fail dfgdfg Sys_xyz_01 Pass hgfhgfh Sys_xyz_02 Test status/Result Test Case Description Test Case ID

15. Defect Tracking All the failed test execution/defects will come under the defect tracking. Defect Tracking Contains : Defect Id : Sys_def_xyz_o1 Test case Id : Sys_xyz_o1

16. Defect Tracking Defect Description : Specify the defect. Defect Recovery procedure : Repeating the same test cases with some modifications.

17. Defect Status The Current Status of the defects New Open Fixed Reopen Closed Rejected

18. Defects Severity Critical Major Minor

19. Defect Classification Defects that affect limited areas of functionality that either can be worked around or ignored Minor/Trivial Major functions disabled or incorrect Non-conformance to standards Defects that cause incorrect behavior with known workaround Important areas of the system are affected which would not cause operational failure Major System inoperable Implementation that does not meet the requirement Defects that may cause the system to hang, crash, produce incorrect or unexpected behavior, corrupt user data with no work around Critical

20. Defects Priority High Moderate Low