Much of a QA's work has been concentrated in necessary but highly operational tasks: reading documentation, interpreting requirements, designing test cases, documenting them, preparing data and maintaining regressions.
Bringing artificial intelligence into the testing cycle isn't about replacing the QA, but about freeing up time for the activities where they really add value: analyzing risk, exploring behavior, catching complex problems and improving product quality.
That's exactly the challenge TESSA was born to solve. Its purpose isn't to replace the tester's judgment but to amplify it: it automates repetitive tasks and speeds up the generation of testing assets —test cases, Gherkin scenarios, interface validations and case automation— so QA teams can focus on analysis, functional coverage and early defect prevention.
But what actually changes in a tester's day to day? How much more can a QA produce in a working day using TESSA? To answer that, let's compare an eight-hour day doing exactly the same work: first the traditional way, then with TESSA.
The starting point: it's 9:00 a.m.
A QA receives a new feature to validate. Like every day, there's a challenge ahead: turning a functional requirement into a battery of test cases that ensures product quality before it reaches end users.
The information received is the same in any scenario:
- A user story.
- Acceptance criteria.
- Business rules.
- Functional flows.
- Interface designs where applicable.
The goal is clear: understand what needs validating and design the test cases required to cover the feature. The only difference is whether they work the traditional way or with TESSA as an assistant.
A QA's day working manually
At 9:00 the requirement analysis begins. The first step is understanding the feature: reading the documentation, interpreting business rules, analyzing acceptance criteria and identifying the scenarios that should be validated. This stage takes roughly 1 hour.
Once the requirement is understood, the most important stage begins: turning that knowledge into test cases. Each case requires thinking through and documenting:
- Case name.
- Objective.
- Preconditions.
- Required data.
- Execution steps.
- Expected result.
- Additional validations.
On top of that, the QA has to cover different paths: positive scenarios, negative scenarios, alternative validations and edge cases.
According to the metrics collected, designing a test case manually takes roughly 30 minutes per case. After the initial analysis, 7 hours remain for design:
210 minutes available / 30 minutes per case
= 14 test cases per day
By the end of the day, this QA built approximately 14 test cases. It's detailed work that depends heavily on available time and on the professional's experience in spotting every possible scenario.
A QA's day using TESSA
Now picture the same scenario. It's 9:00 a.m. and the QA receives exactly the same requirement. The difference is having TESSA as an assistant throughout the design process.
The QA loads the information and starts working on the feature. TESSA helps analyze the requirement, identify scenarios and propose a first pass at test coverage, removing the need to read the full documentation and manually interpret rules and acceptance criteria. The QA still makes the decisions, validates the scenarios and brings the business knowledge, but no longer starts from a blank page.
After the initial analysis comes case generation. The measured difference is significant: the test scenarios generated with TESSA took roughly 2 min 20 sec, which puts a first version of the cases in hand almost immediately.
The QA's work doesn't disappear, though. The person still plays a fundamental role:
- Reviewing the generated cases.
- Adjusting business-specific rules.
- Removing duplicate scenarios.
- Adding functional knowledge.
Instead of spending a whole day on design, the QA gets a first version in minutes and can invest the rest of the time reviewing, enriching and validating functional coverage. That makes it possible to start testing almost in parallel with development, catch defects earlier and accelerate the entire quality assurance cycle.
TESSA's impact in numbers
To calculate a realistic daily productivity we allow an average of 5 extra minutes to review and adjust all scenarios after TESSA's first version. Since the QA saved the initial analysis, 8 hours were available for design.
| 8-hour day | Manual | With TESSA |
|---|---|---|
| Initial analysis | 1 hour | Assisted by TESSA |
| Time per case | 30 minutes | ~5 minutes of review |
| Cases by end of day | 14 | 96 |
That means 6.9x more operational capacity with the same working day and the same resource, and an 85% reduction in the time and cost needed to produce each case.
Want to see how it works on your own requirements? Discover TESSA or get in touch and we'll walk through it together.