← All work

TestFirst 3.0

TestFirst 3.0

Role

UX Designer

Client

TestFirst

Year

2025

Tools

Figma, Claude Code, Photoshop

Impact

Simplified the end-to-end experience from onboarding to first test run in under 5 minutes, with stakeholder approval on the initial 3.0 release.

What's TestFirst?

TestFirst is a cloud-based QA platform built for small and medium teams — offering end-to-end test management and no-code automation without the complexity of enterprise tooling. I joined mid-project as the UX Designer to continue and ship TestFirst 3.0: a full redesign of the web application alongside the product's design system.

3 pillars of testfirst

What Needed to Change

TestFirst 2.0 was a web app and Windows desktop application built around speed — testers could run manual tests, write exploratory test cases on the go, annotate screenshots, manage test plans, and link bugs directly to Jira, all without leaving the app. Real users praised it: faster test execution, time-saving test case management, and a UI that didn't overwhelm.

But the cracks showed up in the details. Actions like editing or deleting a test case required right-clicking rather than obvious on-screen controls — small friction that added up across hundreds of test runs. Reports were not customisable, limited to only basic built-in formats. Key features like Test Case Fragments were desktop-only, and so was execution history — nothing carried to the web. Users noted a learning curve that made early adoption slow, and the platform was entirely locked to Windows with no path to Mac, Linux, or browser access.

For teams scaling up, these weren't minor inconveniences — they were blockers. 3.0 was the answer.

what needed to change

Scope and Direction

TestFirst 3.0 had a clear mandate: move the product from a Windows desktop application to a fully web-based platform, and introduce automation as a first-class feature alongside the existing manual testing workflow. The design scope was broad — seven core flows needed to be designed or significantly reworked, from onboarding new users all the way through to administration and settings.

Alongside the product flows, the design system had to be extended and refined to support the scale of 3.0.

The direction was clear: modern, scalable, and built for teams that needed both manual control and automation power in a single, cohesive interface.

platform wide design
building in the open

Onboarding & Guided Journey

Onboarding

First impressions set the tone for everything that follows. The onboarding flow was designed to get new users — whether setting up a fresh workspace or joining an existing team — through initial setup without friction or dead ends. The branching logic accounts for different entry points, so every user lands in the right place from the start.

Guided Journey

Once inside the product, the work isn't done. The Guided Journey picks up where onboarding leaves off — a series of contextual prompts that steer users toward completing their first meaningful action: creating a test case and executing it. Rather than a generic product tour, every step is goal-oriented, moving the user toward a real outcome rather than just showing them around.

onboarding and guided journey 1
onboarding and guided journey 2

Test Scopes

Test Scopes serves as the central management layer for organising and running tests. From here, testers can create scopes, generate test cases with AI, manage sources, and initiate test runs — with a test run table giving clear visibility into results at a glance. The actual test execution and editing happens deeper in the editor, but Test Scopes is where everything is organised, tracked, and kicked off from.

test scopes

Test Editor

The TF Editor is where testing actually happens. In automation mode, testers write their steps in Gherkin — plain-English Given, When, Then lines — on the left, while a live browser preview runs on the right. No switching tabs, no guessing.

Debug mode shows what the test is matching on the page, a log of everything it did, and the values it is holding, all in real time. Manual mode offers a clean structured alternative — a step-by-step table of actions and expected results for teams that prefer a non-code workflow.

Reusable test case fragments and a tree-structured library keep everything organised as test suites scale.

text editor

Extending the System

Three patterns carried the complexity of 3.0, and none of them existed in 2.0. Tree tables, for test suites that nest inside each other. Test run tables, for results that have to be scanned at a glance. And a sidebar navigation, replacing the menus the desktop app relied on.

The icon set was standardised on Material Symbols, adopted and adapted, so one visual vocabulary runs across every surface. Modal visuals were crafted with the same intent — a consistent shape for the moments where the product stops and asks for a decision.

tree tables
icons
domain components

Outcome

TestFirst 3.0 brought the product to the web, introduced automation as a first-class feature, and unified the experience around a single design system.

Seven core flows were designed or reworked, from onboarding through to administration and settings. The path from a new account to a first test run came down to under five minutes, and the initial 3.0 release shipped with stakeholder approval.

outcome

Reflection

Joining mid-flight as the sole designer forced a different way of working. There was no time for a discovery phase and no convention to follow. The fastest path forward was to learn the domain first — to understand what QA testers actually do — and let every design decision flow from there. The deeper my product understanding got, the sharper every screen got. Domain knowledge compounded faster than process ever could.

Keep exploring.