Software testing is an integral part of the product development process. The key objective is to find all critical issues in the software in time to fix it before releasing it to the public. The sooner you find the bugs, the more time and money you can save. The onus of finding these critical bugs that can decide the success of a product falls on software testers. To find high quality defects, you can follow certain protocol & tips that can make your software testing process thorough & effective.
In our webinar session, “How To Be Successful In 99tests: Tips To Log High Quality Defects”, we have covered some of the top software testing tips and hacks for logging high quality bugs. You can use these tips to find bugs more effectively. You can also watch the complete recording of our webinar session here:
Tip 1: Invest time in understanding the requirements.
Even before you begin logging the bugs, it is important that you invest time and effort in understanding the testing requirements. Read and understand what is the scope and what aspects are out of scope for the testing project. Go through the known bugs section and check out the bugs logged by other testers so that you don’t log a duplicate bug. Investigate the steps that they followed to reproduce the bug. Don’t forget to test the app in the correct build.
Tip 2: Use clear & crisp title
Use a clear and crisp title for logging a bug. Product owners, project managers & developers often scan through the title to priorities the bug and fix it. A well written title can often be sufficient for the bug to be fixed. Don’t make the title a long sentence. It is good to be descriptive enough so that it is clear what the bug is.
“The title is your pitch to the developers to increase curiosity and take it up for fixing.”
Tip 3: Write clear & accurate descriptions
Choose the correct feature/component, priority, bug type & device information. Write clear and accurate bug descriptions. Include the correct attachments (screenshots, video, Logs etc). Present the actual and expected results.
Tip 4: Describe the other details accurately.
Give short and crisp description on the issues. Do not add any other redundant or unwanted information. There are loads of other data which are pre-filled like the following:
- Bug type:Functional, GUI, Content, Crash etc defines the type of issues. Choosing the write type is very critical for the client to prioritize and assign it to developers.
- Priority & Severity: Check out the priority descriptions at 99tests here- https://99tests.com/dosanddonts
- Component: Choose the right component.
- Device: Choose the device in which the testing has been done. If you are a crowd tester, make sure that your tester profile is updated with the latest devices available that is required for the project.
- Mention the correct URL in which the bug was found.
- Additional Info: There are certain projects which would require you to fill additional information. Do read the instructions carefully before starting the testing process.
Tip 5: Give a proper description
Give a clear step by step description on how to reproduce the bug. Identify the cause of the bug by analyzing the root cause. Add the console Information (F12 / Firebug/Developer toolbar etc). Give the input data, & persona’s.
Proofread any bug report before you submit it. Incorrect grammar or wording can be very confusing and discouraging. The validator, the client & developer should be able to understand and reproduce the bugs just by reading the description.
Tip 6: Provide proof of the bug
A picture speaks 100 times more than words. Take the full and clear screenshot of the page showing the bug. Mark the area which has the issue and annotate on the screen shot. The screenshot should be of Jpeg format.
For video proof, ensure a clear focus on the screen. Keep the video short i.e within 15-30 sec max. It is highly recommended that you have an audio along with it so that you can communicate the observations and highlight the focus area. As far as possible keep the video in mp4 format.
Do include crash log attachment: A mandatory and critical information to be attached when reporting crash bugs. If the attachment is very big, add the video or screenshot in zip file. This can be saved in Google drive or Dropbox and shared with the client.
Tip 7: Analyze actual versus expected result
Clearly mention, what happened when certain actions were done and what is that you are not happy about. In the expected result, clearly mention what should be the fix and how do you expect the application to behave.
Tip 8: Useful testing tools
Here is a list of useful tools you can utilize during the testing process:
A) For Desktop: Windows and Mac
Recording: A Powersoft Mac Screen Recorder, Faststone capture(Win), QuickTime Player(Mac), Screencastify
Screenshot: Lightshot(Mac) and Screencast-O-Matic
Console: F12, Burger Icon – Developer toolbar, Firebug
Spell Check: Grammarly
B) For Android
Recording: A-Z Screen Recorder, Mobizen
Log: Alogcat, Android ADB, Android Studio
C) For iOS
Recording: Screen Mirroring, Connect to your mac record screen, AirShou, Reflector
Log: Connecting device with system and get the log from itunes or App Data (Mac OS X: ~/Library/Logs/CrashReporter/MobileDevice)
With these tips, you can make your day to day testing activity more effective and log high quality bugs. You can access the summary of these tips on Slideshare:
Write For Us: Want to write for us? We’d love to publish guest post from testers & QA experts who can offer unique & useful perspectives in software testing. Share your own testing experiences & tips with our readers.
To get featured, mail us your article at Pankaj@99tests.com with subject line ‘Guest Blogging’. Don’t forget to provide a short bio & social links for your byline at the end of the post. We allow 1 do-follow link to your website from the article body, as long as it is not promotional. Do write to us, if you’d like to learn more.