Bug Tracking:
Why we need to do that?
To make you app with more quality. Providing the application with quality on time....
Why we need to do that?
To make you app with more quality. Providing the application with quality on time....
- Steps to reproduce is always the important one for testers...this is helpful for Tester/ Developer to resolve the issue as quick as possible.
- Reporter of the bug should always change the status of bug to closed.
- If a Bug is rejected/ duplicate/ defferred... No worries on that... We are keeping track of that too.
- If a bug is not reproducible means that doesn't mean no one can reproduce it... At least one person in team can provide the steps to reproduce the bug.
- Don't forget to keep track of version, release, build, Commit version...
- Bug ID should be mapped with your test cases. Then only in future, whoever reading on the test case will know the scenario.
- Mail conversation will help the tester to analyse more on major bugs... Don't miss to add detailed description in mail.
- Attach the mail conversation of bug and keep track of it with defect tracking tool.
- Share the test data with developer, If possible share the exception logs too.
- Share the detailed DB information of the bug...
- Keep the bug in large database and store them properly for different releases.
- Add the required new fields for different team, different location, Different ID, different track for each and individual bugs.
- Try to assign the bug to right person. then they can finish it off easily and faster.
100% of quality product is not possible... But we can provide 100% as per our knowledge.
No comments:
Post a Comment