Test creation is usually an S-shaped curve with the highest priority and most complex tests done first, and lower priority, simpler tests done later. Tests start running as soon as they’re built and our goal is to provide as much value as quickly as possible, starting with your business-critical workflows.
Timeline
2–3 months from Test Plan approval
Typical blockers:
- Misalignment between stakeholders delays Test Plan finalization
- TK
Ways to speed up implementation
- Misalignment between stakeholders delays Test Plan finalization
- TK
CI/CD integration
We run the full suite once a day standard, which you can request to run multiple times per day or on deploy. The setup is easy: Add a curl command in your deployment pipeline that calls the QA Wolf platform.
If you’d like to poll for results to block deploys when tests fail, ask your QA Lead to help you set that up.
Bug reporting
Bug reports are created by QA Wolves when investigating a failing test. Our standard procedure is to send the bug report in the shared Slack or Teams channel.
We can also submit bug reports directly into your issue tracker (Jira, Asana, Linear, Clickup, etc.) with the same information that’s sent in Slack.
What's included in a bug report:
- Expected behavior and actual behavior
- Steps to reproduce
- Video of the headful browser run
- Loom video walk-through of the bug and relevant additional information
- Link to the test run with Playwright trace logs and HAR files
