Documentation Index Fetch the complete documentation index at: https://docs.qawolf.com/llms.txt
Use this file to discover all available pages before exploring further.
QA Wolf Full Service pairs your team with a dedicated QA engineering team that builds, runs, and maintains your automated test suite. If you’re evaluating QA Wolf, book a demo to talk through your coverage goals.
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.
1 to 2 weeks after contract start if all blockers are cleared.
Connect your Slack, Teams, or Discord account with QA Wolf.
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.
Identify a Champion (day-to-day) point of contact for QA Wolf who can clear blockers and make decisions about your test suite.
When Within 5 business days of the contract start date.
Agenda
Introductions.
Review coverage goals.
Set expectations for the process.
Align on milestones.
Attending From your team From our team Point of contact during the sales process Customer Success Manager Champion (day-to-day contact) who will be most hands-on working with us QA Lead Any other team members you’d like to include (engineers, product managers, etc.)
Action items Your responsibilities Our responsibilities Connect a shared Slack, Teams, or Discord channel. Learn about QA priorities and onboarding goals. Share your environment credentials.
When Within 5 business days of the contract start date.
Agenda
Introductions.
Walk through your app.
Identify testing priorities.
Identify areas to avoid.
Attending From your team From our team Product or engineering manager for each testable feature set QA Engineering Lead Test outliner
Action items 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.
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.
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.
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.
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.
Attending From your team From our team Product or engineering manager for each testable feature set QA Engineering Lead Test outliner
Action items 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.
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.
Attending From your team From our team Product or engineering manager for each testable feature set QA Engineering Lead Test outliner
Action items 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.
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.
