[2024]Digital Global Overview Report 2024 Meltwater.pdf
Strategies For Software Test Documentation
1. Strategies For Software Test Documentation Suriya G (suriyag at vishwak.com) Vishwak Solutions Pvt. Ltd.
2.
3. The testing can be done either Manually or by using Automated testing tools.
4.
5. The goal of a Tester is to find defects as early as possible.
6.
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)
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.
25.
26.
27.
28.
29. Assign: The assigned Developer’s responsibility is now to fix the bug and have it RESOLVED or give valid reasons.
30.
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.
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.
38.
39. Software Tester - The goal of a Tester is to find defects as early and fix them.