-
Diversity
-
Worldwide testers
- Different mentalities
- Target your main users
- 24/7
- Languages, time zones
-
Mobile devices
- Fragmentation
-
Different devices
- The very new
- The Very old
- Some popular in between
- All relevant OS are available
-
Payment
- Per bug?
- Effort?
- ROI
-
Management
- Do you have an available full time project manager working with you?
- Who will coordinate with the tester?
- Who will train them?
- Who will give them the assignments and see they are followed?
- Will they review the bugs first, eliminate duplications, make sure they are clear and written well?
- Testers will sign an NDA
- How do we track of testing effort?
-
Number of testers
- Scalable from 1 to as many as is relevant
- Scalable in short notice
-
Quality of work
-
Ask to review other companies reports including bug reports
- Written clearly
- Acceptable format like steps to reproduce, expected/actual...
- Logs attached (if you gave instructions about it)
Screen shots etc.
- Bugs are written in understandable English
- Can they assess usability?
- Do they do Exploratory well?
- Do they execute TC well?
- What is their bug opening standard?
- How do they define severity/priority?
- Do the testers have grading?
What is the grading classification?
Can we chose testers by grading?
-
CS Company
- Stable
- Have experience
-
Clients are satisfied
- Google search
- Talk to clients
-
Availability
- Availability from the assignment to results.
- Will the testers be available for debug?
- How fast do they work?