TesterArmy Client Test Suite Handoff (Delivery)
A handoff with 8 steps: Confirm the client's repository is connected and the GitHub Actions or GitLab CI trigger is active.
By InnovaAI ResearchPublished
What are the steps?
TesterArmy Client Test Suite Handoff (Delivery)
- 01
Confirm the client's repository is connected and the GitHub Actions or GitLab CI trigger is active
Open the project settings and verify the integration shows a live connection. A test suite that only runs manually will not catch regressions on pull requests, so the CI trigger is the handoff baseline.
- 02
Audit stored credentials, OAuth links and OTP inboxes before transferring ownership
TesterArmy authenticates flows through stored credentials, OAuth and one-time passwords routed to dedicated inboxes. Walk each entry with the client contact and confirm the inbox is one the client controls, not an agency-owned address.
- 03
Re-run every plain-language flow description and capture the pass/fail table as the handoff record
Trigger a full manual run across web, iOS and Android targets. Export or screenshot the single results table showing status, platform, environment and trigger so the client has a dated baseline of what passed at handoff.
- 04
Verify Slack alert routing points to the client channel, not the agency workspace
Send a deliberate failing run and confirm the alert names the failed step and what the agent observed in the client's Slack channel. Remove agency members from the alert path so retainer exit does not silence their notifications.
- 05
Set the scheduled production run cadence and document the timezone
Scheduled runs against production are separate from pull request runs. Agree the daily or hourly cadence in writing and record it in the handoff note, since a schedule left at agency default will fire at the wrong hour for the client's team.
- 06
Map each flow description to the client's own product owner and record who edits it
Plain-language descriptions are editable by anyone with project access. Name the client-side owner for each flow so future copy changes to the app do not silently break a test the agency wrote and nobody maintains.
- 07
Transfer or downgrade the TesterArmy plan and reconcile run volume against the tier
Hobby includes up to 250 test runs at $99 monthly, Startup up to 1,000 at $299 monthly. Count the runs the handoff suite consumes per month and confirm the client sits on a tier with headroom, or the suite will stall mid-cycle.
- 08
Deliver the coverage map and a written note that client-facing reports carry TesterArmy branding
TesterArmy publishes no white-label program, so dashboards and reports show its brand. State this in the handoff document so the client is not surprised when they open results under an agency retainer.
More on TesterArmy
- StrategyWhy TesterArmy Turns QA Retainers Into Recurring Revenue for Agencies
- ConceptTesterArmy Run-Ceiling Margin Model
- Evaluation RuleTesterArmy Rule: Adopt When Client Merge Cycles Outpace Manual QA, Not Before
- Decision FrameworkTesterArmy: Buy vs Skip (Agency QA Automation Decision)
- Failure PatternWhy Agencies Fail With TesterArmy When Plain-Language Tests Meet Real Client Auth Flows
- Implementation BlueprintTesterArmy Retainer QA Deployment (7-10 days)