Manual & Exploratory Testing and the QA Role
Automated tests are powerful, but they only check what someone thought to write down. Real software also needs human testing — especially exploratory testing, where a skilled person actively probes the app looking for trouble. And the people who specialize in this, QA, do an engineering discipline, not "clicking around".
The two kinds of testing aren't rivals; they catch different things. Automation handles the known and the repetitive; humans find the unexpected. A strong team uses both.
A building inspector is the right image: not someone who just runs down a checklist, but someone who pushes on things, opens what shouldn't open, and looks for what the blueprint never anticipated.
Manual vs Automated
Automated tests run by themselves, fast and repeatedly — perfect for checking known behavior on every change. Manual testing is a human using the software directly. Each catches what the other misses: automation reliably re-checks the things you already know to check, while a human notices the odd, the ugly, and the surprising that no script was written for. You want both, not one or the other.
Exploratory Testing
Exploratory testing is structured curiosity: a skilled tester roams the app trying the weird and the unexpected — the empty input, the huge input, the wrong order, the double-tap, the strange time zone. It's not random; it's informed guessing about where bugs hide, guided by experience. This is where humans shine and scripts can't follow, because it's about imagining what no one specified.
The QA Role
QA (quality assurance) is an engineering discipline focused on the software's quality as a whole. Good QA designs the overall test strategy, decides what to automate and what to explore, owns the question "is this actually ready?", and advocates for the user. It is emphatically not "the person who clicks around at the end" — it's a specialized engineering role that shapes how quality is built and verified across the whole project.
Usability and Accessibility
Human testing also covers things automation barely touches: is the app actually usable, and is it accessible — does it work for people with disabilities, like those using a screen reader? Accessibility isn't optional polish; it's a real requirement, and often a legal one. Checking that real people — including those who navigate differently — can actually use the software is a core part of quality, not an afterthought.
On Cadence, Nora doesn't just run the automated suite. She explores reminders by hand: she sets one for 11:59 PM, changes her phone's time zone, and force-quits the app mid-save. In doing so she finds a double-send bug that no unit test ever thought to check — because no one had imagined that exact sequence. That's exploratory testing finding what the scripts couldn't.
- "Automated testing makes human QA obsolete." Automation handles the known and repetitive; humans find the unknown and unexpected. They're complementary, not rivals — you need both.
- "QA just follows scripts and clicks around." Good QA designs the test strategy, owns quality, and explores with skill. It's a specialized engineering role, not idle poking.
- "Accessibility is optional polish for later." It's a genuine requirement — and frequently a legal one — that software work for people with disabilities. It belongs in the definition of quality, not an afterthought.
- Respecting QA as an engineering discipline — not "clicking around" — corrects a common misconception and helps you work well with QA on a team.
- Understanding that automation and humans catch different things explains why mature teams invest in both, rather than betting on one.
- Knowing exploratory testing exists, and what accessibility means, broadens your view of quality beyond "do the automated tests pass?".
Knowledge Check
How do automated and manual testing relate?
- They catch different things — automation the known, humans the unexpected
- Automation has completely replaced the need for any human testing
- Manual testing is always strictly better, so automation should be avoided entirely
- They are two different names for exactly the same activity
What is exploratory testing?
- A skilled tester probing the app for trouble, guided by experience
- Following a fixed, pre-written checklist of steps exactly as written
- Randomly clicking around with no thought or strategy at all
- An automated process that explores the app entirely on its own
Which best describes the QA role?
- An engineering discipline that designs test strategy and owns quality
- Just someone who clicks around the finished app right at the very end of the project
- The role that decides which features the product should have
- The role that writes most of the application's actual code
Why is "accessibility is optional polish" a confusion?
- It's a real requirement, often legal, that software work for people with disabilities
- Because accessibility only ever matters to a tiny handful of people
- Because accessibility just means making the app look more attractive
- Because accessibility should only ever be added at the end if there is spare time left over
You got correct