Automation is used in test scenarios; the operator reviews the order and manually starts the cycle. The report is delivered by email.
Defining the scope
Scope is based on the testing link, app purpose and flows you want checked. Do not include sensitive access information in checkout notes. Discuss specific devices, languages, accounts or paid actions with support first.
Test cycle and delivery
After coordinating app access and scope, the operator starts the cycle manually. Starter covers a 14-day QA cycle and Pro a 16-day cycle. Findings are shared in an email report. Ask before purchase if you have a specific start-time requirement.
What makes a finding useful
- The affected screen or flow and the tested build.
- Steps needed to reproduce the issue.
- The difference between expected behavior and the observed result.
- Scope limitations and areas that could not be verified.
The dashboard and the report
The website dashboard shows a sample app and sample progress. It is not the source of your real order or test status. Use email support for order and delivery questions.