How to Test Anything — 100 Features Every QA Should Practice

Published by SoftwareTestPilot

PDF • 38 pages • Workbook • Beginner to Advanced • Manual Testing

Published 21 September 2026 • Updated 22 September 2026

Included in QA Notes Vault

Preview this resource below, or unlock the complete QA Notes Vault for ₹199 lifetime access.

Build test cases for any feature quickly and completely.

Already bought the Vault?

Like this resource? Unlock this plus 89+ other QA notes with lifetime Vault access.

Overview

For each feature, first write your own scenarios. Then compare your thinking with the prompts in this workbook. The goal is to learn a reusable testing method: understand the feature, identify data and states, test happy paths, challenge assumptions, inspect integration points, and look for risks that appear only under failure or concurrency. Understand Purpose, actor

What you'll learn

Understand any feature before testing it
Partition inputs and states
Check integrations and data flow
Find ways to break the feature
Observe logs, errors and side effects

Topics covered

manual-testing

1. Understand
2. Partition
3. Integrate
4. Break it
5. Observe

Preview from this resource

Inside this PDF

100 real product features - from Login, Search and File Upload to Payments, APIs, Webhooks, Caching, Data Migration and Release Validation. For every feature: what to validate, high-value practice scenarios, and one senior-level edge case to develop stronger QA thinking. Use it for interview preparation, test-case practice, exploratory testing, onboarding and day-to-day QA

How to Use This Workbook

Do not memorize test cases. For each feature, first write your own scenarios. Then compare your thinking with the prompts in this workbook. The goal is to learn a reusable testing method: understand the feature, identify data and states, test happy paths, challenge assumptions, inspect integration points, and look for risks that appear only under failure or concurrency. 1. Understand Purpose, actors, preconditions, dependencies and business rules 2. Partition Positive, negative, boundary, state, role, data and platform scenarios 3. Integrate API, database, third-party, queue, notification and downstream effects 4. Break it Timeouts, retries, concurrency, stale data, partial failure and abuse

Senior QA challenge: What happens after password change while old sessions are still active?

02 Signup / Registration Validate: Account creation, field validation, duplicate prevention and verification. Practice: Valid signup; duplicate email/phone; weak password; invalid formats; optional fields; repeated submit. Senior QA challenge: Can two concurrent signup requests create duplicate accounts? 03 Forgot Password Validate: Identity verification, token lifecycle and safe recovery. Practice: Known/unknown account; expired link; reused link; password policy; throttling; multiple requests. Senior QA challenge: Does requesting a new reset link invalidate older

Senior QA challenge: Should other active sessions be terminated after a password change?

06 Social Login Validate: OAuth flow, account linking and error recovery. Practice: First login; existing-email match; revoked consent; cancelled flow; missing profile data; callback failure. Senior QA challenge: Can social login accidentally create a second account for the same

A short extract taken from the first 8 of 38 pages. The complete notes are in the QA Vault.

Skills covered

Manual Testing

Who this resource is for

Fresher
Manual Tester
Automation Tester
QA Engineer