Software Testing

Beginner path · lesson 10 of 35

BeginnerFundamentals4 min readPublished November 12, 2026

Functional vs non-functional testing

Functional testing checks what the software does. Non-functional testing checks how well it does it: speed, security, accessibility and more. Users need both.

On this page

Key takeaways

  • Functional testing checks what the system does: does the feature give the right result?
  • Non-functional testing checks how well it does it: is it fast, secure, easy to use, accessible, reliable?
  • A feature can work perfectly and still fail users because it's too slow, insecure or unusable. Test both.

The difference in one example

Take a login form.

  • Functional: a correct email and password log you in. A wrong password shows an error.
  • Non-functional: login takes under two seconds, works with a screen reader, still works with 5,000 users at once, and the password isn't sent in plain text.

The first list is about behaviour. The second is about qualities.

Functional testing

Functional testing compares the software's behaviour with its requirements, user stories or business rules.

Typical questions:

  • Does the calculation give the right result?
  • Does the right error appear for invalid input?
  • Is data saved, updated and deleted correctly?
  • Does each user role see what it should, and nothing more?

Most of the test cases a beginner writes are functional. Techniques like equivalence partitioning and boundary value analysis help you choose them.

Non-functional testing

Non-functional testing checks the quality characteristics of the system. The international standard ISO/IEC 25010 lists them. The ones you'll meet most often:

CharacteristicQuestion it answersExample test
PerformanceIs it fast enough, under real load?1,000 users search at once; results in under 2 seconds.
SecurityCan it be misused or attacked?A user can't open another user's invoice by changing the ID in the URL.
UsabilityCan people use it easily?A new user completes signup without help.
AccessibilityCan people with disabilities use it?Every action works with a keyboard and a screen reader.
ReliabilityDoes it keep working, and recover?The app recovers after the database restarts.
CompatibilityDoes it work in different environments?Checkout works on current Chrome, Safari and Firefox, and on mobile.
MaintainabilityIs it easy to change and fix?Usually checked through code reviews and static analysis.

Non-functional problems are real problems

It's tempting to treat speed or accessibility as "nice to have". Users and courts don't.

Real-world example · Domino's Pizza, 2016–2019A pizza order a screen reader couldn't place

In 2016, Guillermo Robles, who is blind, sued Domino's in the US. He said he couldn't order a pizza on its website or app using a screen reader.

In 2019, a US federal appeals court ruled that the Americans with Disabilities Act applied to Domino's website and app. The US Supreme Court declined to hear Domino's appeal later that year, so the case went ahead.

Ordering pizza worked. The functional tests would have passed. But for a blind customer, the site didn't work at all.

Lesson: accessibility is a quality characteristic that decides whether some users can use your product at all. It deserves real testing, not an afterthought.

How to include both

  1. Ask about non-functional requirements early. "How fast is fast enough?" "How many users?" "Which browsers?" If nobody knows, that's a risk worth raising.
  2. Add quick non-functional checks to everyday testing. Try the keyboard, a slow network or a phone, not just the happy path on a fast laptop.
  3. Plan the bigger tests. Load tests and security reviews need preparation, tools and sometimes specialists.

Do

Write measurable non-functional requirements: "Search returns results in under 2 seconds for 95% of requests with 500 users."

Don't

Accept vague ones like "the system should be fast and user-friendly". You can't test them, so nobody will.

Check yourself

Users report that a report export gives the correct numbers but takes 4 minutes to finish. Is that a functional or non-functional problem?

Show answer

Non-functional: a performance problem. The function works, because the numbers are correct. But how well it works isn't acceptable to users.