Bug reporting via memes

"A picture is worth a thousand words" - well, who has not heard that before but as with most things simple we might not give it its due because it's easily understood. 

 In our team we have a pretty straight forward process to deal with bugs. I demo it to the dev, and add a sticky on the board for it to be fixed. Most of the time the fixes take priority, so we can move the stories across. It works well for our context.

 Today, when working from home I wanted to share a bug with my dev - list view loosing placeholder image data on scroll on android. I typed the steps to reproduce on slack and then followed it with the below image 



The team loved it... (Yea, you read that right! dev's loved the bug report ;)
It was fun and made the point clear... 
I bet it would look stunning on the kanban board compared to the long list of words on a sticky...

Comments

yagsy said…
What a great idea. It's fast, it brings immediate attention for the whole team to become involved.
January 3, 2016 at 11:58 PM
Amandeep Singh said…
Sounds like a great idea, Sharath.

Memes work wonders if used the right way - gets the job done and keeps the fun alive within the team ;)

Interestingly, I submitted a similar meme'd bug report on slack and below is what the Meme I got back in reply read from my developer as it was a Friday and I was insisting my dev to deploy it so we could close a bug before new week kicks in :P

Don't have the meme now, but it read something on these lines "Request deployment on a Friday and I will deploy you" - the meme had rambo with a gun in the backdrop :D

Fun, isn't it?
January 4, 2016 at 9:56 PM
Sharath Byregowda said…
Thanks for the comments JeanAnn and Amandeep.

@Thats brilliant Amandeep, check if you can find it and post it here. I would love to see that.
January 5, 2016 at 4:01 PM
Matt Frampton said…
Love this idea!

Do you have a favourite meme of the sprint type award? :)
January 9, 2016 at 10:13 PM
Post a Comment

Popular posts from this blog

Exploratory testing, Session based testing, Scripted testing…concertedly

In my last assignment a mix of exploratory, session based and scripted testing helped won an award, appreciation by managers & stake holders at our organization. The quotes from our award certificate “ QA team has come up with some intelligent testing techniques to validate the product. The customer test team was not able to find even a single critical bug after delivery ” Though the award was a small one in terms of the award categories our organization have, it meant a lot to me and the team, because this was the first time the team used exploratory approach. The assignment was not pure exploratory or session based, in fact it was supposed to be scripted, but a mix of all three exploratory, session based and scripted testing helped us learn, enjoy, and meet our mission. The assignment started off with developing test cases. We wrote test cases based on the initial requirement document provided. We did come up with a large number of test cases, of which most were re-written, some ...
Read more

Regression Checks + Regression testing = Regression testing?!

One of the questions I find hard to answer when I use exploratory test techniques in my project is,”How do you run regression tests? How do you prioritise them? Do you automate them? Do you document regression test cases?” And then a bunch of questions follow. Let me define the context. I work closely with developers; we use either Scrum or Kanban - which ever best suits our project, product owner, business. We do not believe in individual metrics, blame games, stringent processes, and heavy documentation. All we care about is to deliver high quality software. This does not mean that there is no process, metrics or documentation. We have them all, but they are there to meet our needs and to help those who will come onboard to support/maintain the software. Regression Checks At the start of a story, testers pair up with developers to develop feature files using SpecFlow. Some call it Acceptance Test Driven Development and others Behaviour Driven Development [I am yet to figure out the d...
Read more

What do you do when you find a bug?

What do you do when you find a bug? Hold on do not answer it right now. Let me first set the context. You are part of an agile team. The developers sit opposite to you. You are testing a feature in a session. You are time bound and have the good habit of capturing notes when you test. When you now find a bug what do you do? Assuming that you have taken enough notes you go on to write a good bug description and may capture a screen shot, video of the bug and continue with your session. At the end of the session do you Open the defect tracking tool (wait for it to load), enter all the fields for a bug, upload necessary evidence and have the tool share the defects with your dev team? Or Open the defect tracking tool (wait for it to load), enter all fields for a bug, upload necessary evidence and then compose an email to the dev team with the bug id’s/descriptions? Or Walk to the developer share your notes; reproduce it if required, work together to identify the problem? I work in ...
Read more