Bug report is a technical document used to describe an issue of the tested application failure found during test, helped stakeholders understand the problem, reproduce and resolve it. A good bug report will help us save a lot of time on figuring out the root cause as well as giving decision on fixing it. Good bug report is not only about its content but also about your pre-works before writing it. Following tips will help to write an effective bug report:
Whenever you experiencing an issue during test, quickly find a shortest description for the issue and: Try to discuss with your closet team (usually QA team) to see ensure it is new but not spend much time on that Issue is never reported before Some time issue is new but according some technical limitations, we should consider it as limitation and ignore it. try to find on your bug tracking tool to ensure that the issue is new and valid If there is already bug logged, have a look to see if you can provide more valuable information, e.g. more step, more condition, the reproducible build number… Otherwise just ignore it, that will not only help time of write the bug report but also save time of other member in analyzing the issue. Reported a duplicated bug will waste not only your time but also the assigned person who will try to resolve it.
Or at least has a sequence of failure occurs for intermittent issue. Try to retest the flow that issue occurs and note down all steps as well as relevant information to provide to the bug report.
For intermittent bug, try to find how many times of executing a flow the issue will occur.
Ex: Sometimes sending email to external network is failed because of firewall/antivirus so it is not the problem failure. The issue should be ignored.
When experience issue and it is reproducible, try to figure out to see if is there any other areas in the tested application having the issue. For example, in an application, user has phone number attribute and the design says that phone number must have exactly 10 digits.
Precondition: Provide some precondition steps before going to actually main flow, sometimes it is skipped as steps also mentioned in step to reproduce. Usually the precondition is picked from the relevant test case to save time of writing bug report.
Would you like to work with the coolest IT guys in Vietnam? Apply to one of the following jobs:
Job requires a high level of technical skills and experience within Microsoft technologies and offers high salary, exciting projects, and constant challenges in terms of technology and design.Tell me more
Want to have fun developing innovative Xamarin products? We are developing a number of exciting games and social applications of our own as well as supporting third party clients.Tell me more
Job requires both good English as well as the ability to understand complex technical subjects and systems. You will mainly be writing SEO articles and guidelines for our many products.Tell me more
Knowing Ionic framework or NodeJs is a plus, but is not mandatory.
2 Senior Developer positions in an Offshore Development Center team. You will work directly with a Danish Project Manager at our Vietnam office. The initial project is for a multinational French company.Tell me more
1 Senior QA/Test Engineer in an Offshore Development Center team. You will work directly with a Danish Project Manager at our Vietnam office. The initial project is for a multinational French company.Tell me more