0tahG01S4Ny9rgMqoa1AeU0awAZ8veyCXxaGhzyS6Mw



When the time is right for a QA?


Testing could be useful in all stages of the project life cycle, but generally – sooner, the better.

What is the usual quote?


For a casual project with 2 000 – 5 000 daily active users testing is bidding between 600 and 4000 USD.

It’s best to aim at 200 hours of testing per build so the task could be executed within 4 days by the team of 5-6 testers.

What is essential to start?


a) Platforms for the current test iteration – iOS, Android, Amazon, all together or separately;

b) Builds and where to find them – mobile build distribution service or a package copy .apk/.ipa;

c) Aim of the current iteration – for example, “Focus on the Q1 event questline – specification attached.”;

d) Deadlines for test execution – starting when the new build is available and finishing when you need it done;

e) Reports, their desired frequency and format – daily, weekly, upon completion of the task. Check out our Report Template;

f) Documentation for the project, if there is any available – our team is able to develop any test documentation you might need to use;

g) Bug tracking system – we are able to use anything that your team is already working with – JIRA, Trello, Google Sheets, uTrack, etc;

h) A place to communicate (Slack, RingCentral, Skype, etc.) and a person with a strong knowledge of the project (we call it a Pillar Tester);

i) Cheat menu and/or test accounts to speed up progression without disrupting the system. We could offer recomendations on creating it too;

j) The invoicing process – per task, per sprint, weekly, monthly. SWIFT payments are preferable. The requisites will be indicated in the Agreement;

How often do I need to test my project?


That depends on your development cycle and actual content on an update.

Could be ranging from testing several updates per week to one test run per month.

How many testers do I need in a QA team?


It strongly depends on the project complexity and the frequency of updates.

For a project like C.A.T.S. – on a second year after the release it’s best to have a 4-6 full-time QA’s

And we also throw 6 more QA’s to execute periodic extensive testing of new updates in a matter of days before the release.

– If you need to run basic testing for 120 hours in 5 days – a team of 3 will do.

– If your plan is to cover 400 hours of testing in two iterations, 5 days each – a team of 5 QA’s will be enough.

– If the schedule is tight and the scope is 1 280 hours per month – up to 8 testers on a full-time basis will be needed.

Who will be involved in testing my project?


Each new task will be handled by top-performing QA with sufficient qualifications to manage the project.

We rarely switch Project Leads, so knowledge will be accumulated by the team throughout the testing period.

The team will be able to deliver its top expertise after a few iterations when they get to know the project better.



SnoopGame QA is 44 testers in 4 teams, from Trainee to Senior and the Head of QA who oversees the workload distribution.

Don’t forget the Accounting, Office Management, System Administration, Business Development, SMM, HR, and Cleaning staff.

Will the project become perfect after testing and debugging?


After the round of testing and debugging, we can verify that the project meets all of the requirements and quality criteria.

The project is “perfect” in terms of QA when it processes any user input in any given environment without unexpected behavior.


Request a quote