By Test Object: Functional & Beyond
What This Module Is About
Most beginners learn one way to look at software: "Does it work?"
That's a start. But it's only one lens. 🔬
This module gives you three lenses:
- Functional — Does the software do what it's supposed to do? (Requirements verification)
- Non-functional — Does it do it well? (Performance, security, usability, accessibility)
- UI/UX — Does it look right and feel intuitive? (Visual correctness and user experience)
These aren't competing approaches — they're complementary. A login form can pass all functional tests (valid credentials work, invalid ones are rejected) while failing non-functional tests (takes 8 seconds to respond) and UI/UX tests (the error message is invisible against the background).
Seeing all three dimensions is what separates a thorough QA from someone who just clicks through happy paths.
What You'll Learn in This Module
- 📋 What functional testing verifies and how requirements become test cases
- ⚡ What non-functional testing covers — the "ilities" that nobody mentions until prod is on fire
- 🎨 The difference between UI testing (does it look right?) and UX testing (does it feel right?)
- 🐞 How to identify which dimension a bug belongs to
- 🔍 Practical examples from real testing scenarios
Module Lessons
- Functional Testing — Does It Even Work? — Input, process, output: the core model of functional verification against requirements
- Non-functional Testing — How Does It Work? — Performance, security, usability, and accessibility as testing dimensions
- UI/UX Testing — Beauty & Usability — Visual correctness, Figma as source of truth, and why confused users are bugs
🏅 Complete all three lessons to earn the Multi-Lens Tester badge — for QAs who never look at a product through just one eye.