While filing an issue, many a time the tester miss to add additional details specific to the bug. They must have done all the normal procedures, say like, steps, expected and actual results, environment details and all should have filed along with the issue.

But still sometimes the customer ends up in asking for further information, which is in fact a bit frustrating for them. During those cases both parties [customer and tester] need to invest additional effort to make the bug report adequate.

So just ensure a few of the points below if your bug is any of this type.

#If your bug is onDon't miss to attach
1Partial visibility of some buttons or something like thatDetails of screen resolution
2Some sentence correctionsYour suggestions on how to rewrite the sentence
3Some overlapping related issuesDetails in both landscape and portrait mode
4Page load issues Speed test result

A bug title is read more frequently than any other part of the bug report. So it has to be meaningful and easily understandable.

For example,

A bug : In the application while the user go to ‘xxx’ tab and search for an item with numeric characters, the app crashes

Poorly written bug title: App crashes

Here the bug title doesn’t summarize the scenario behind the crash

An average bug title: Searching in the ‘xxx’ tab leads to a crash

Here again the bug title is actually creating a false impression of the bug.

It could have better reworded like, “App crashes on searching in the xxx tab with numeric characters

Infact my suggestion would be to revisit and update the bug title finally, once the report is made fully.

After describing the issue, steps, expected and actual results, just look at the bug title. Definitely, you can do betterment on the same at the final stage.

So initially while starting to file the bug, just add a sentence or even some random keywords in the issue. Or even sometimes, just put whatever comes to your mind, say “my family”. [but of course don’t forget to change it properly at the end].

And finally, once the entire report is ready, revisit the bug title and update it properly. Spend a little more time on the issue title and have two or three revised titles so that it becomes fully meaningful at the end.

Oops… that’s a show stopper one..

How did it happen..?

Most of the time when I try to reproduce  a crash issue I start thinking from the very first step and finally end up nowhere. Often the crash should have happened with the last step only.. Mostly it wouldn’t have any relation with the initial steps. So I am training myself to just recollect and redo the final steps.

Okay, so how all normally a show stopper issue or the so called crash issue happens in a mobile application?

I am adding a few of such checkpoints here…

  1. While the activity is playing in the app, just come out of the same by pressing the home button of the device and then try to return back
  2. Make the app in background by launching another app and then return to the app under test from recent window.
  3. Do interrupt the app via some mechanisms like phone calls or messaging
  4. Try an offline testing
  5. Try a test under weak battery
  6. Try offline-online switching frequently
  7. Landscape- portrait switching
  8. Access the app via multiple accounts at the same time
  9. Delete and already deleted item from the app if it’s shown for a while