- Connect your Slack, Teams, or Discord channel.
- Choose an environment to test. If you’re not sure, we suggest starting with the environment just below production (e.g., staging or QA).
- Send environment credentials to your QA Lead by email, Slack, a password manager like 1Password, or input them directly into the QA Wolf platform. We’re flexible!
- Accept the invites to the Kick-off Meeting and Product Tour.
Onboarding
Onboarding with QA Wolf is easy, but there are a few things that you need to set up so 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.✅ Your onboarding to-dos
Send test environment credentials to your Account Executive, QA Engineering Lead, or Customer Success Manager.
👩💻 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.
| From your team | From our team |
|---|---|
| Point of contact during the sales process | Customer Success Manager |
| Champion (day-to-day) contact(s) who will be most hands-on working with us | QA Lead |
| Any other team members you’d like to include (engineers, product managers, etc.) |
| Your responsibilities | Our responsibilities |
|---|---|
| Connect a shared Slack, Teams, or Discord channel. | Learn about QA priorities and pilot goals. |
| Share your environment credentials. |
🔎 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.
| From your team | From our team |
|---|---|
| Product or engineering manager for each testable feature set | QA Engineering Lead |
| Test outliner |
| Your responsibilities | Our responsibilities |
|---|---|
| Internally align on the product(s) that QA Wolf will be working with and what areas are the highest priority to build coverage for. | Record the product tour. |
| Take detailed notes for test plan creation. | |
| Ask clarifying questions about priorities and product functionality. |
💀 Common onboarding blockers
These blockers can slow down onboarding progress. Please address them as soon as possible:- Your testing environment is unavailable, misconfigured, or unresponsive. Read 🎯 Preparing an environment for QA Wolf test runs
- Your environment is not able to send emails to the @qawolf.email domain.
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.
✅ Your 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 about it — 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 we can avoid the 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.
| From your team | From our team |
|---|---|
| Product or engineering manager for each testable feature set | QA Engineering Lead |
| Test outliner |
| Your responsibilities | Our responsibilities |
|---|---|
| Answer questions from the test outliners on Slack, Teams, or Discord. | Prepare detailed outlines for all tests within budget. |
| Field questions about the test plan and outlining process. | |
| Respond to outline feedback and changes in your team’s priorities. |
🔎 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.
| From your team | From our team |
|---|---|
| Product or engineering manager for each testable feature set. | QA Engineering Lead |
| Test outliner |
| Your responsibilities | Our responsibilities |
|---|---|
| Identify any remaining gaps or issues. | Convert all approved outlines to the AAA framework in preparation for coding. |
| Approve the scope of work. | Update outlines and priorities based on feedback from the first review. |
💀 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