Skip to content

Creating and debugging tests

Helping QA Wolf automate tests and provide better test coverage.

Role
  • Product strategy
  • UX design
  • UI design
QA Wolf IDE with the travel insurance test selected in the file tree, its code in the editor, and the Howl Hotel browser preview alongside it.

IDE for testing

QA engineers create, run, and debug end-to-end user flows in one place instead of jumping across tools.

The code stays visible while engineers switch between the browser, run history, and test details. They can inspect what the app did and look back at earlier runs while working on the same test.

Browser output, test details, and run history share a panel beside the editor.

Automated tests

Generating test code is only the first part. Running and validating that hundreds of new user flows actually work on your app is how QA Wolf scales quality.

I designed the workspace to keep the flow list, code, and automation progress together. Engineers can follow progress across the batch and open a flow to see what's happening with that test.

Each attempt stays visible as the job progresses, so engineers can follow what happened.

As we worked on the IDE, team members wanted to optimize features that IDEs like VS Code already had. I regularly reminded the team that QA Wolf is not an IDE company, and asked us to focus less on those features.

Our value was in automating tests and providing better test coverage. I wanted us to focus on the parts of the platform that could do more of that work autonomously.