Software Testing

Beginner path · lesson 21 of 35

BeginnerFundamentals4 min readPublished November 12, 2026

How to think like a software tester

Thinking like a tester is a set of habits you can learn: questioning assumptions, imagining different users, asking 'what if?' and noticing what's odd. Here are the habits and the quick checklists testers use.

On this page

Key takeaways

  • A tester's mindset starts with one question: "How could this fail?" Builders ask how it works. Testers ask how it doesn't.
  • It's a set of learnable habits: question assumptions, change your point of view, vary the data, follow anything odd.
  • Short checklists called heuristics give you test ideas fast when you don't know where to start.

From "does it work?" to "how could it fail?"

When people build something, they think about how it should work. That's their job.

A tester looks at the same thing differently. Not "does it work?", but "under what conditions does it stop working?" That isn't pessimism. It's the question nobody else on the team is paid to ask full time.

Six habits of a tester's mind

1. Question assumptions

Every requirement hides assumptions. "The user enters their date of birth." Which format? What if they're born on 29 February? What if they're 120? What if they leave it empty?

Look for words like always, never, all and only. They're often where the gaps hide.

2. Change your point of view

Use the product as different people would:

  • A first-time user who doesn't know where anything is.
  • An expert who uses keyboard shortcuts and moves fast.
  • An impatient user who double-clicks everything and presses back.
  • Someone with a disability who uses a screen reader or only a keyboard.
  • Someone trying to cheat, such as reusing a coupon or changing a price in the request.

3. Vary the data

Most bugs hide in data nobody tried. Use a quick checklist like the ones in Elisabeth Hendrickson's Test Heuristics Cheat Sheet:

  • Zero, one, many: an empty cart, one item, 500 items.
  • Too big, too small, just right: the shortest and longest allowed values, then one beyond.
  • Special characters: accents, emoji, apostrophes (O'Brien), very long words.
  • Dates and times: leap years, time zones, midnight, end of month.

4. Think about the environment

The same feature can behave differently on a slow network, a small phone screen, an old browser, in another language or with another time zone set.

5. Think about time and order

What if two people edit the same record at once? What if a step is done twice, or out of order? What if the session expires halfway through?

6. Follow what's odd

A tiny flicker, a slow response, a message that's slightly different from yesterday's. Good testers don't ignore these. They're often the visible tip of a bigger problem.

What happens when nobody asks "what if?"

Real-world example · Therac-25, 1985–1987A fast typist and a deadly race

The Therac-25 was a radiation therapy machine. Between 1985 and 1987, it gave massive radiation overdoses to six patients. Some of them died.

Investigators Nancy Leveson and Clark Turner traced key accidents to the software. One problem appeared when an experienced operator edited the treatment settings quickly. The software could miss the change and set the machine up in a dangerous state.

Earlier models had hardware safety locks that would have stopped this. The Therac-25 relied on software alone, which was trusted because it had worked in normal use.

Lesson: "what if the user is faster than we expect?" is a tester's question. So is "what if this safety check fails?" Asking them, and testing them, matters most where the stakes are highest.

Practise the mindset

  1. Pick an everyday object or app, such as a lift, a vending machine or your banking app.
  2. List 10 ways it could fail. Use the habits above: other users, odd data, bad timing.
  3. Rank them by how likely and how harmful they are.
  4. Try the safe ones on software you're allowed to test.

Do

Ask questions with curiosity: "What should happen if the user's session expires during payment?" It invites the team to think with you.

Don't

Ask questions as accusations: "Did nobody think about expired sessions?" The same question, but it makes people defensive instead of helpful.

Check yourself

A form has a field: 'Number of tickets (1–10)'. Using the habits above, list at least five things you'd try.

Show answer

Some ideas: 0, 1, 10 and 11 (boundaries); -1; 5.5; letters like "abc"; an empty field; a very large number like 99999999999; pasting text with spaces like " 3 "; double-clicking Buy; buying while another user buys the last tickets; and checking the total price for each valid amount.