Below are typical priorities of what to integrate first and which guides to follow.

Starting Out

• Ensure your team is invited to your instant messaging platform of choice (Slack, MS Teams, Discord, etc.)
• Ensure relevant team members have access to the QA Wolf platform.
• We will coordinate a time-based daily trigger on our end. Familiarize your team with how bugs are reported to the instant messaging platform and where to see them in QA Wolf for additional details.
  • We recommend to integrate QA Wolf with your issue tracker as soon as possible, so that these bug reports make it to the engineering team.
  • We recommend that you get in the habit of prioritize bugs in the QAW platform.

Automating Deploy Notifications and “Just in Time” Testing

• Work with our team to set a deploy trigger on the QA Wolf platform
• Configure your CI/CD platform to notify us of new deployments (Triggering test runs on deployment)
  • We recommend using our SDK (@qawolf/ci-sdk), but this can also be configured using raw network calls.
• Install our GitHub/GitLab integrations, if applicable (Install GitHub/GitLab App).
  • These will leave comments in the correct PR/MR for ease of viewing.

Use QA Wolf to Gate Releases and/or Inform CI/CD processes

• Use our SDK, GitHub action(s) or the raw API endpoint(s) to collect data about how successful a deploy to an environment was (Inspect Run Results Programmatically).
  • This step is usually where customers can expect to see whole team buy-in to the process, as well as spread the benefits to all members of the team
  • This is the step at which customers typically notice a reduction in escaped regressions to production, at the cost of a minor slow-down in release velocity.
• In the case of frequent (hourly or less) releases, micro-services and multi-repo setups and for larger teams, we recommend considering batched deploys and merge queues at this stage.
  • This will ensure that QA Wolf is spending time where it matters and reduces the time it takes for us to do a full QA Cycle on a release candidate.
  • It usually hits a good balance between deploy velocity, developer experience and productivity and focused QA processes.
    • Talk to us to learn more about the recommendations in this space!