Pay4Bugs: Quick Guide to Testing a Product

Pay4Bugs makes it easy to get real people testing your hot new product before it goes out the door with bugs that can hurt your brand image and reputation.

You can have your production product or latest beta build submitted to testers within minutes with just a few easy steps.

Step 1 – Sign up for a Pay4Bugs Customer Account

Sign up is quick and easy.  You can sign up for a Pay4Bugs PayGo account for free with no monthly fee or sign up for a Pay4Bugs Monthly Plan for access to more advanced features perfect for teams and enjoy a free 1 month trial.

You will be selecting how much money you are willing to pay for each bug and will need purchase enough Pay4Bugs Credit to cover the budget of your assignment.  Unused credit is refundable according according to our generous refund policy, so there’snever any risk.

Step 2 – Create a new Project

Once you’ve signed up and logged in, click on the “Projects” menu option and then click on “New Project” to create a new project!

New Pay4bugs Project Screenshot

Enter your product’s name and provide a brief description.  Provide a link to your product website or a place to download your software.  Click on the “Create this project” link when you’re done.

New Pay4Bugs Project Form Screenshot

Step 3 – Create a Testing Assignment

Now that your new project has been created, you need to create an assignment for testers so that they know what you want them to test. Click on the “create one” link to make a new assignment.

A newly created Pay4Bugs project with no assignments

A project can have one assignment or multiple assignments.  The scope of each assignment is up to you. You can ask testers to stress your product according to the protocol you provide, test a specific new feature, look for typos or simply report anything they would consider a bug. For this example, we’re going to create a single assignment asking testers to report any problems they find with our new product.

New Pay4Bugs Assignment Description Screenshot

You set the the Bug Bounty, the price testers are paid per valid bug, on a per assignment basis.  Set it higher for more difficult assignments.  A higher Bug Bounty attracts more testers and entices testers to spend more time testing your product.  The budget you set will help you control spending.  Your budget must be no more than your available credit balance.

In the example below, the customer has $219.00 of credit that has not been assigned to the budget of another assignment and can be budgeted to this assignment.  The customer has decided to set the budget to $100 and pay testers $3.00 for each bug.  This assignment will automatically be paused after 33 bugs have been submitted until the customer logs on and reviews the submitted bugs for validity. Since this customer has purchased our Enterprise monthly plan, she pays no additional per bug fee.

Click on “Add new assignment” when you’re finished

New Pay4Bugs Assignment Financials Screenshot

Step 4 – Start the Testing

Your new Pay4Bugs assignment is ready to go! Click on the green start button to enable your assignment.

New Pay4Bugs assignment is ready to send to testers

Step 5 – Sit back and relax as the bug reports come streaming in

You will be notified by email when testers submit new bugs and have the opportunity to approve or reject each bug.

Pay4Bugs let's you approve or reject each bug. You decide!

If you feel that a certain bug report is a waste of your time, click the Junk/Spam button and the offending tester will be banned from ever submitting a bug report to any of your projects again.

Use the reasoning box to let testers know why you made your decision.  When you receive an excellent bug report, don’t hesitate to offer praise!

Questions? Contact Pay4bugs Support. Start your risk-free Pay4Bugs trial today!

Tag:, ,

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>