Say bye to (static) screenshots

Screenshots in a bug report always play a big role. It saves lots of explanation and makes developer’s life easier. But sometimes static screenshot won’t be good enough to convey the message. Screen Recording would be good alternative in this case, But when considering the size of the recorded file, it may also not be the ideal solution.

So how about having a screenshot, with all the steps of a bug. Sounds cool, right ?

Say hello to gif

.gif image format is very small in size and can be easily uploaded to the bug tracking softwares in a few minutes.

How to create a .gif easily

First install ImageMagic via Homebrew ( Instructions on installing Homebrew can be found in here)

$ brew install imagemagick

Let’s take a Gmail login as our example. A user goes to the Gmail login and enters the user name. Then clicks on the Next button and enters the password ( Incorrect one in this scenario ) and clicks on the Sign In button. User gets an error message.

Assuming our intention is to show this error message to a developer, below would be the simplified steps to reproduce.

Steps to reproduce

  1. Go to the Gmail Login
  2. Enter the user name
  3. Click on the Next button
  4. Enter the Password
  5. Click on Sign In button

Observe thatThe email and password you entered don’t match

In ordinary way, you will attach a screenshot of message you observed. But not today.

  1. First take screenshot of each step, starting from Step#1 to Step#5
  2. Open a terminal and go to the location of the screenshots ( Most cases this would be the desktop )
  3. All your screenshots will be save with <ScreenShot tag><time stamp>.png format ( Eg: Screen Shot 2016-01-08 at 4.35.36 PM )
  4. Type the below command and hit enter.
$ convert -delay 20 -loop 0 Screen*.png MyFirstGif.gif

20 : In above command, defines the speed of your animation. Higher value for this would create a slower animation

MyFirstGif.gif : Name of the .gif ( This will be created in the same folder/location where your screenshots are in )

Tip: Once you take the all screenshots of your steps, create a folder and move all these screenshots to that folder. Then execute the command. So then there won’t be any mix up with your old screenshots.


This is our GIF image

This is a pretty simple scenario taken for this blog post for explanation purposes. This would be much more helpful when a QA guy reporting a complex bug with good number of steps. Also this might good for when reporting a UI issues.

Try this & make your bug report more interesting in 2016 – Be Awesome!

Image_For_QADummyAbout the Author 
Chamal is a Software Quality Assurance engineer with over 3+ years of experience. When he is not working, he can be found either reading a book or browsing Zomato or Yamu. He shares his personal thoughts on his personal blog.
You can contact him on LinkedIn or twitter


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s