This is Sample basic testing process and one can use it and design a complex QA testing process.
How to Log Errors
Things to be included in the bug report:
- Put the Reporter’s Name on the bug. If there are questions we need to know who originated this report.
- Specify the Feature or Specification or part of the code. This facilitates assigning the bug to a developer assigned to that part of the product.
- Include a Brief Description of what the problem is.
- List Details including how to duplicate the bug (Steps to Replicate) and any other relevant data or clues about the bug. Start with how the computer and software is setup. List each and every step (don’t leave any out) to produce the bug. Sometimes a minor detail can make all the difference in duplicating or not duplicating a bug. For example, using the keyboard versus using the mouse may produce very different results when duplicating a bug.
- If the status isn’t ‘Submitted’ by default, change it to Submitted. This is a flag to the bug verifier that a new bug has been created and needs to be verified and assigned.
- Include all associated URLs.
- Environment Information needs to be added to identify if the issue is not environment related. Minimum information that will be required: OS, Browser and Version.
- The Severity* tells the reader of the bug how bad the problem is. Or in other words, say what the results of the bug are. Here’s a common list for judging the severity of bugs. There is sometimes disagreement about how bad a bug is. This list takes the guess work out of assigning a severity to bugs.
| Rating | Value |
| Emergency | An entire site is not accessible or an entire database is not accessible or corrupted. |
| Critical | A major function is not accessible and there is no workaround. |
| Moderate | A major function is not working but there is a workaround, a moderate function is not accessible and there is no workaround or a non-trivial part of a major function is not accessible or defective. |
| Minor | A minor function is not accessible or defective; a part of a minor function is not accessible or defective. |
* Severity should not be confused with Priority. Priority will be assigned by Business.
Appendix A – Priority Definitions
| Priority | Definition |
| 1 | Showstopper |
| 2 | Must be fixed in order to launch the product. This can represent a partial fix where applicable in order to move issue into P3 |
| 3 | The product can be launched but issue should be fixed with the next maintenance release |
| 4 | The fix should be scheduled for the future release |
