01 • User Journey
Think beyond individual screens
A customer journey is the complete path a user follows to reach a goal. A QA engineer tests the connections between screens, services, devices, and data—not only the appearance of one page.
Sign up → verify the account → select a location → add an item → apply an offer → pay → receive confirmation.
Questions to ask
- Can a new and returning customer complete the journey?
- Is data preserved when the user moves between screens?
- What happens when the network is slow or unavailable?
- Does the experience recover after an interruption?
02 • Test Coverage
Build balanced test scenarios
Strong coverage includes successful behavior, failures, boundaries, interruptions, permissions, and accessibility—not only the happy path.
The expected journey with valid data and no interruptions.
Invalid input, rejected payments, expired offers, and errors.
Minimum, maximum, empty, and unusually long values.
Logged in, logged out, first-time, returning, and interrupted users.
03 • Platforms
Test consistently across devices
The same feature can behave differently across browsers, operating systems, screen sizes, and connected devices.
Record the test environment
- Application version or build number
- Device, browser, and operating-system version
- Environment such as QA, staging, or production
- Account, location, test data, and network conditions
04 • Defect Reporting
Make every bug report actionable
A useful defect gives another person enough information to reproduce, understand, prioritize, and verify the problem.
Clear title • environment • preconditions • numbered steps • expected result • actual result • severity • evidence.
Example title: Checkout — Place Order remains disabled after entering a valid payment method on iOS.
05 • Practice Lab
Design tests for an ordering journey
Imagine a customer uses a mobile app to choose a location, add an item, apply a promo code, pay, and receive an order confirmation.
Write at least eight tests: two happy paths, two negative paths, one boundary test, one interruption test, one cross-platform test, and one accessibility or usability observation.
06 • Knowledge Check