Money Shed member Spike241 has been earning some seriously big amounts of
Online Testing Jobs : uTest
Late last year I discovered uTest through The Money Shed Toolkit. It’s now 3 months later and I’ve just made $1000 in one month.
I hope that this guide will help some of you to earn a little (or a lot) extra from the comfort of your own homes.
I’ll start by saying you don’t have to spend anything to get started. All you need is a computer and/or a smartphone and you’ll be ready to start testing. You don’t need any previous testing experience either, I didn’t when I started. You do need to know your way around your testing device in order to explore the app you are testing and in order to add screenshots and videos when required.
What is uTest?
uTest is basically a crowdsourcing platform for app and website testing.
Developers hire uTest to find problems in pre-release or live apps so that they can be fixed before they become an issue for customers. This way they can test multiple devices and multiple OSes in a short space of time.
Testers are rated on their activity and the quality of their work. These ratings are shown as a percentage and are likely to change from day to day. As testers progress and take part in more projects they can earn one of 5 badges: Rated, Proven, Bronze, Silver and Gold.
Bronze – Gold testers earn a bonus on all approved bug reports, up to 10%!
There are 4 types of tasks that testers complete: Test Cases, Exploratory Testing, Bug Fix Verification and Reviews.
Most Test Cases include set steps to follow. The tester must determine whether the app is working as it should throughout these steps and Pass or Fail them. For example: if the tester is asked to click on a tab and the page does not load or the app crashes then that step would have Failed.
Occasionally Test Cases do not have set steps. For these Cases the tester must choose their own path through the app or website and document the steps they have taken and any bugs that they found.
Test Cases have a set payment which will be displayed before you claim them.
Exploratory Testing works exactly the same as the free Test Cases. Testers work their way through the app checking that features such as Log Ins, Settings etc are functioning correctly.
The tester then submits bug reports for issues they encounter e.g app crashes, pages not loading properly, settings changes not saving. There are many examples of bugs that testers encounter every day.
This is the area where you can earn the most money but the downside is you are competing with the other testers in the project. Each bug can only be submitted by one tester, any duplicates will be rejected. All submitted bugs are listed and there is a search box so testers can check their bug has not been submitted before.
Evidence of the bug must be submitted as part of the report e.g screenshots, videos, logs of the bugs occurring.
The Project Manager and developer will then decide which bugs are valid based on the scope and how the app should work. Bug reports are not a place to submit opinions e.g “I think this would work better if…”, that’s what the Reviews are for.
Approved bugs will be rated from Somewhat to Exceptionally valuable, which determines how much the tester will be paid for the bug. Pay levels are clearly displayed in the Overview before testing begins.
Bug Fix Verifications are specific types of Test Cases.
After a bug report is submitted, the app developer may attempt to fix the bug and invite the tester to check that the bug is fixed. This is a very simple test and typically pays $1.75 but it usually only takes a few minutes.
The Review tab gives a short list of questions for the tester to answer. These are typically asking for opinions on the design and usability, features and performance of the app (did the pages load quickly, did the app crash a lot). Most pay out $4 for ~5mins work, although sometimes there are more questions and the pay is increased to compensate.
Firstly, you need to create a profile at www.utest.com
This is a simple sign up form, you don’t even need to fill in the About Me section.
You then create an Expanded Profile, without this you will not receive any work from uTest. This is the part where you let uTest know what devices you have, your availability and any previous testing experience you may have. Don’t lie, lack of experience will not prevent you from receiving project invites!
Once you have completed your Expanded Profile you can either wait for an invite to the Sandbox Program or check the Projects Board on www.utest.com to see if you are eligible for any of the projects listed.
The Sandbox Program is an ‘audition’ project. It is a chance to show uTest what you can do.
It is unpaid and you complete a short Test Case and submit 2 bugs from the website they give you.
Sandbox invites are usually sent out within 1-2 weeks of joining but if you don’t receive one then you can apply to join.
You will receive invites to projects by e-mail. Some projects have limited spaces and fill up quickly so try to check your e-mails regularly.
You can read through the Overview to get a feel for the project before you accept or decline.
Declining an invite will not have a negative effect on your rating but ignoring it will.
The Overview will also tell you which device you should be using to test (based on your Expanded Profile). Some will list multiple devices and you can use any one or a combination of them to test.
At the beginning you may only get 1-2 invites a week but if you submit quality work you will probably receive multiple invites a day. I am much more selective about projects now.
It can be very nerve wracking when you first start out but each project has it’s own chat room where you can ask questions. There is also a uTest forum and University. The University has loads of useful information and courses on getting started and the different types of testing.
Payments are sent out on the 15th and the last day of the month (or the next working day if these fall on a weekend) via Paypal.
If you have any questions then you post on the uTest thread
I know it may seem overwhelming but it helps to go through the process one step at a time. I didn’t have a clue what I was doing when I started but I learned by reading through courses, the forum and by taking part in as many different projects as I could.