Ever wondered how some crowd testers climb up the leader-board faster than others? Are you keen to know why bugs get marked out of scope, duplicate or invalid? Here are the top 10 mistakes crowd testers must avoid:
1. Not reading the requirement thoroughly and/or not being clear about the requirement
This is the biggest mistake and the most costly mistake that testers make. After spending 30-60 minutes in testing and logging bugs, the bug would get marked as invalid or out of scope just because the tester did not read the requirement clearly and/or did not understand the requirement clearly. Spend at least 5 minutes to understand the client expectations and information which would be useful for testing. Invest your time in understanding the test requirement to make your testing process more effective.
2. Over focus of crowd testers on logging the most number of bugs instead of the quality of the bugs
It is great to log as many bugs as possible, but how many of them are getting marked valid is a very important question that you must ask yourself. A tester is considered good only when, the bug acceptance rate is more than 65%. Make the quality of the bugs you log, your top priority to succeed as a crowd tester.
3. Bug report which is unclear and has insufficient information to validate
All bugs with improper and insufficient information to reproduce the bug, including lack of visual proof like screenshots or videos get rejected. A report should be so clear that it should provide the step by step process to reproduce the issue and the exact environment information in which the bug was identified. It must include screenshot / video for more clarity so that when the developer checks the bug report they can easily reproduce the issue and fix it.
4. Not knowing what other testers are doing, and following a blindfolded approach
This is an approach where crowd testers do not do any planning and start testing blindly. To grow up the leaderboard testers should know and understand what other testers are focusing on and what has not been tested. They should be aware of the scenarios and the features that were missed out. They should then focus their attention on those areas that would help them stand out from the rest of the crowd.
5. Trying to just click around and find bugs in the application instead of in-depth testing
Testing is not about clicking to check if all the links are working but clearly understanding what each link is supposed to do. You should understand the data flow and the user experience that fulfills their needs in the application to succeed as a crowd tester.
6. Not thinking like an actual user and not thinking of scenarios which would have high impact
Each application has its purpose, and there could be 100 users who would use the same application for 100 different purposes, in 100 different ways. Testers should be able to relate and think of test cases / scenarios by putting themselves in the shoes of an end user who would use the website or App.
7. Logging bugs which do not matter and have less impact on the client and to their users
No application can be 100% bug-free. There could be many limitations in technology, design, operation etc. Understanding the difference between a bug and good practice is a knack crowd testers must master. For example verification of the actual existence of an email is a good practice however it is not mandatory for all the application to verify the same. Testers need to consider the severity of the application and criticality of the information stored in the database while logging the bugs.
8. Not understanding the domain, target audience, and information which can be useful for testing
This is again very similar to the blindfolded approach. Testers need to understand the application, its purpose, target audience and competitors. They must also read the user reviews and the comments to check if the application is doing what it claims to do.
9. Not having the required tools ready before testing
Before starting, check if you have the appropriate tools and technology to log bugs quicker and clearer. When you are well prepared, the possibility of the bugs getting marked valid is high. Don’t forget to check the tools for recording your screen, taking screenshots, getting logs and add-on’s for capturing additional information to add to your bug report.
10. Not learning from previous mistakes
A crowd tester’s job does not get over once the project is complete. If crowd testers wants to improve their performance and ranking, it is a good practice to go through the bugs which they were not able to identify, scenarios which they did not think of and the approach and tools which other testers have used. You can use this information to perform better in your next projects. When we do not take the steps to improve our skills as a crowd tester, we miss out on learning and also opportunity to earn more through crowd-testing platforms.
With the right approach and right attitude, crowd testing can enrich your career and take your software testing skills to a whole new level.
Got any more suggestions on mistakes that crowd testers can avoid? Feel free to add them in the comments below.
You can also check out the video below to learn more about, the 99tests Testing Community where you can work on paid projects and enhance your testing skills as a crowd tester:
This blog post is written by Bharath S, Director of Operations at 99tests. With over 10 years of experience in the software testing industry, he has led many critical high value projects and has organized many international level testing conferences and events.