One Tester, Three Projects — How to Stay Sane and Not Lose Bugs

Monday morning. A tester starts with Project A — an e-commerce app, React, staging on AWS. At 10:30 they jump to Project B — a mobile app, Flutter, different test environment. After lunch — Project C, a legacy Angular system where just configuring the environment takes 15 minutes. Three projects, three Jira instances (or Jira + Linear + Trello), three sets of credentials, three different definitions of "ready for testing." This is daily life for a tester at a 10-50 person software agency.

The Reality of QA in Software Agencies — One Tester, Many Projects

The "State of Testing" report (PractiTest, 2023) found that 44% of testers work on more than one project simultaneously. At small and mid-size agencies, that number is higher — because hiring a dedicated tester per project is a luxury that 10-30 person shops simply can't afford.

This isn't an organizational problem you can solve with better planning. It's a budget constraint: a software agency makes money on developers, not testers. The tester is a "shared cost" split across projects, like office space or a Jira license. The result is that a tester must be effective on three fronts simultaneously — and that's physically impossible without losses.

The Cost of Switching Between Projects

Dr. Gloria Mark at UC Irvine (research published in "Attention Span," 2023) demonstrated that after every interruption — and a project switch is an interruption — it takes a person over 23 minutes on average to return to full concentration. For a multi-project tester, these interruptions happen 4-6 times per day.

It's not just about "getting back up to speed" on a project. Each project has its own context: a different repository, a different environment, a different set of test cases, a different user flow, different developers. The tester has to mentally "reload" the entire context — and that costs time and energy that could be spent on actual testing.

With 3-4 switches per day, that's 1-2.5 hours wasted on context switching alone. Over a month: 20-50 hours. The American Psychological Association, in a meta-analysis of multitasking research (Rubinstein, Meyer, Evans, 2001), showed that task switching can consume up to 40% of productive time — especially when tasks are complex, and QA work definitely is.

Which Bugs Get Lost When a Tester Is Stretched Thin

The bugs that require focus are the ones that disappear. Exploratory testing — where a tester doesn't follow a script but looks for non-obvious scenarios — is the most effective method for finding critical bugs. But it requires full attention and mental engagement. Under constant multitasking, testers fall back on scripts, because scripts can be executed mechanically. Exploration requires flow — and flow doesn't exist when you switch projects every 2 hours.

The second category of bugs that get lost are those that were "noticed but never reported." A tester testing Project A spots something strange. Before they can open Jira and write a report (10-15 minutes), they have to join the standup for Project B. After the standup they go back to Project A, but the context is gone — they don't remember the exact repro steps, didn't take a screenshot, didn't save the URL. The bug ships.

What This Means for Your Software Agency

You won't change the fact that one tester handles several projects. In a 10-30 person agency, that's an economic reality. What you can change is how much time the tester wastes on reporting itself — because that's the only parameter you can drastically reduce without additional headcount costs.

If reporting a bug takes 10-15 minutes, a multi-project tester physically can't report everything. If it takes under a minute — they can. Not because they work faster, but because reporting doesn't require a context switch. The tester stays in the app being tested, clicks, says what they see — and goes back to testing.

Voice2Bug works exactly this way. The tester clicks the browser extension — regardless of which project they're testing. They describe the bug via voice, take a screenshot or record a video. Under a minute. The report automatically goes to the right Jira project, with technical data and full context. No opening Jira, no searching for the right sprint, no switching between trackers. One click, one report, one project — even when the tester handles three.