Onboarding
Onboarding with QA Wolf is easy, but a few things need to be set up before we can begin developing a Test Plan and building your automated test suite.Timeline
1 to 2 weeks after contract start if all blockers are cleared.Onboarding to-dos
1
Connect your Slack, Teams, or Discord account with QA Wolf.
2
Send test environment credentials to your Account Executive, QA Engineering Lead, or Customer Success Manager. The environment needs to be stable and reachable before onboarding can begin.
3
Identify a Champion (day-to-day) point of contact for QA Wolf who can clear blockers and make decisions about your test suite.
Your QA team
Kick-off meeting
When Within 5 business days of the contract start date. Agenda- Introductions.
- Review coverage goals.
- Set expectations for the process.
- Align on milestones.
Action items
Product tour meeting
When Within 5 business days of the contract start date. Agenda- Introductions.
- Walk through your app.
- Identify testing priorities.
- Identify areas to avoid.
Action items
Implementation
Once we understand your application and testing priorities, we’re ready to start outlining a Test Plan and coding up your automated test suite.Timeline
- Planning phase: 2 to 4 weeks after the contract start date if all blockers are cleared.
- Test creation phase: The next 2 to 3 months after the Test Plan is approved.
Test planning to-dos
- Send over any existing test plans or internal priority lists. Anything you have is great: Google Sheets, a TestRail matrix, or just a list of priority features. If you don’t have anything, don’t worry — we’ll work with you to determine priorities and coverage areas.
- Export and send your existing E2E tests — if you have any. We can convert that code to QA Wolf outlines and test code, or avoid covered product areas if you plan to continue running and maintaining them internally.
First Test Plan review meeting
When Within 15 business days of the contract start date. Agenda- Introductions.
- Review the test plan.
- Re-confirm priorities.
- Provide feedback on the test plan’s coverage areas.
- Confirm the scope of work.
Action items
Final Test Plan review
When Within 20 business days of the contract start date. Agenda- Introductions.
- Recap feedback from the first review.
- Review changes/updates to the test plan.
- Review the AAA framework.
- Finalize the scope of work.
Action items
Common test planning blockers
- Your stakeholders aren’t aligned on testing goals and priorities, which prevents us from finalizing a Test Plan.
- Your team is unresponsive when QA Wolf reports possible bugs or asks for product clarification.
- Your team is unavailable to review the test plan.
Common test creation blockers
- Your test environment is too unstable to run end-to-end tests reliably. Read: Preparing an environment for QA Wolf test runs.