Strategies For Software Test Documentation by Suriya G of Vishwak.com for Anna University Workshop on testing

1. Strategies For Software Test Documentation Suriya G (suriyag at vishwak.com) Vishwak Solutions Pvt. Ltd.

3. The testing can be done either Manually or by using Automated testing tools.

5. The goal of a Tester is to find defects as early as possible.

7. Missing: A specified or wanted requirement is not in the built product. This can be a variance from specification, an indication that the specification was not implemented. (given in specification but missed out in application)

11. Test Case.

12. Test Procedure.

13. Test Log.

16. Testing Schedules (testing tasks and milestones)

17. Environment Needs (hardware and software)

18. Test Items (what should be tested)

19. Risk and Constraints

24. The results are either the test passed, meaning that the actual and expected results were identical, or it failed meaning that there was a discrepancy.

29. Assign: The assigned Developer’s responsibility is now to fix the bug and have it RESOLVED or give valid reasons.

31. Deferred / Waived: If lead / verifier / developer considers that the bug is “Not valid” then they should give valid reasons to change the status to Deferred or Waived.

32. Re-Opened: If bug still exists not satisfied with the solution in the new build then tester should open the bug again by selecting the status as RE-OPENED.

34. Priority - Priority is the order in which developer has to fix the bug.

35. High Priority & High Severity: A show stopper error which occurs on the basic functionality of the application. (E.g.. A site maintains the student details on saving record if it doesn't allow to save the record then this is high priority and high severity bug.)

36. High Priority & Low Severity: The spell mistakes that happens on the cover page or heading or title of an application.

37. High Severity & Low Priority: The application generates a show stopper or system error but on click of link which is rarely used by the end user.

39. Software Tester - The goal of a Tester is to find defects as early and fix them.

40. Defects - Wrong,Missing and Extra

41. V&V - Verification "Are we building the product right " and Validation "Are we building the right product "

42. Testing Documentation - Test Plan, Test Case, Test Procedure, Test Log, Test Report.

43. Test Plan - A document describing the scope, approach, resources, and schedule of intended testing activities.

44. Test Case - A set of test inputs, executions, and expected results developed for a particular objective.

45. Test Procedure - A document, providing detailed instructions for the execution of one or more test cases.

46. Test Log - The Test Log records the details of what Test Cases have been run, the order of running, and the results of those tests.