How to Determine the Size of a Bug on MyCrowd QA

Knowing what size a bug is can be challenging for testers. Here is some general and specific guidance to help you.

The goal is to provide our customers with the best testing possible so they can improve their site and apps. As a tester you will be compensated by the bugs that you find. Different types of bugs are worth different amounts. The descriptions are below, but keep in mind that we all work for the Customer. We need to find bugs that make a difference not just little edge cases they will probably never experience. The more complex a bug is and the more it impacts the user experience, the more you will get paid. DO THIS: Provide value to the customer. Test complicated flows of the website and use cases that end users might take. Try to discover bugs before a user does. DON’T DO THIS: Dont’ spend all your time looking for edge cases or strange scenarios that a real users might never encounter. While these might technically be defects, they have limited value to our customers. WHAT IS YOUR REPUTATION and HOW DOES IT RELATE TO BUG SIZES? Every tester has a reputation score. This score consists of many factors, but the most important ones are: 1) how many bugs have you submitted, 2) what is the average size of the bugs you submit, 3) how often do your bugs get accepted, 4) how often do your bugs get rejected, 5) how do other testers rate you. Everything you do on the system affects your reputation. The higher your reputation, the more you will be permitted to do on the platform. If your reputation drops below a certain level you could get suspended or asked to leave the community. Remember, the reputation is here so that we can provide our customers with valuable testing. If you enter bugs that are the wrong size, it will hurt your reputation. If you validate bugs that are the wrong size, it will hurt your reputation.

BUG SIZES AND EXAMPLES:

TINY: No impact to user experience or ability of site/ app to perform its purpose. Would not cause abandonment. Typos, missing punctuation, basic grammar errors, tiny visual defect.

SMALL: Small impact to the user experience, probably wont affect usage or cause abandonment. Minor form issues (edge cases for form functionality or validation.) Visual defects like broken or missing images and overlapping elements. Broken links, buttons and incorrect URLs that can be verified in one click.

MEDIUM: Significant impact to the user experience. Would probably cause user struggle and possible abandonment of the site/ app. Major form issues (incorrect error messages or validation, issues when submitting valid form data.) Major functionality defects (Unexpected results, broken paths requiring multiple steps to reproduce), disconnected or interrupted service, infinite loops or extremely long pauses between actions.

LARGE: Extra large impact to the user experience. Would cause abandonment or block usage of the site/ app. Crashes, lockups, incorrect data, incorrect calculations. Must be reproducible, include steps to reproduce, be well documented and include XYZ info. Stack info? Video of failure?