Stop 01 · QA & Software Testing FoundationsTopics · 1/9

What QA Engineers Actually Do

In short

Developers build the feature. QA engineers make sure it actually works for real people, on real phones, with messy real inputs, before a customer finds the bug first.

QA engineers verify that software actually works as intended and catch defects before users do — a mix of designing test scenarios, executing them (manually or via automation), and reporting issues clearly.

The purple blob tastes a spoonful from a big cooking pot in a busy wedding kitchen.

Think of it like this

The wedding kitchen taste tester

At a big wedding, someone tastes every dish before it reaches 500 guests. Too much salt? Dal undercooked? They catch it in the kitchen, not at the table. A QA engineer does that tasting for software.

Watch it happen

One feature passing through QA

Read story

Plan tests

Run tests

Report bug

Retest

1/5A new story arrives: 'Users can apply a coupon at checkout.' QA reads it and asks what happens with expired coupons.

The big ideas

What you need to know

Find problems before users do

A bug found on the test server costs a quick fix. The same bug found by customers costs money, trust and angry reviews.

Prevent, not just detect

Good QA asks awkward questions while requirements are being written, so some bugs never get coded at all.

Clear communication is the job

A bug nobody understands never gets fixed. Half of QA work is writing things a busy developer can act on.

Automate the boring repeats

Checks you run every release, like login and payment, get turned into scripts so humans can explore new things.

See it in code

Walk through the code

text

1Test:      Login with a wrong password2Steps:     1. Open the login page3           2. Enter a valid email4           3. Enter a wrong password5           4. Click "Log in"6Expected:  "Incorrect password" shown, user stays logged out7Actual:    Blank white screen8Status:    FAIL, bug raised

1/3Steps are written so anyone on the team can repeat them exactly.

This is the everyday unit of QA work: a check with clear steps, what should happen, what did happen, and a verdict.

Save yourself the pain

Common mistakes

Oops

Thinking QA means randomly clicking around hoping something breaks.

Do this instead

Most QA work is planned: reading requirements, designing checks, running them and reporting clearly.

Oops

Believing QA is responsible for every bug that reaches users.

Do this instead

Quality is the whole team's job. QA makes risks visible early so the team can decide well.

Your mission

Test an app you use every day

~20 min

Quick check

A QA engineer reads a new requirement and asks, 'What should happen if the coupon has expired?' What is this an example of?

Go deeper

1Read 2-3 'day in the life of a QA engineer' posts from different companies.
2List the last 3 bugs you've personally encountered in an app and consider how they might have been caught.
3Notice how much of the job is thinking about what could break, not just confirming what works.