Module 2 · Manual testing, end to end Lesson 4 of 15
Turning requirements into test scenarios
A requirement describes what should happen; a scenario describes how you will check it. Every requirement needs at least one positive case and one negative one, and a requirement that cannot be tested should be sent back.
The concept
A requirement is a sentence about what the system should do; a scenario is how you would check it. "Candidates can save a job" becomes: saving works, the saved list shows it, it survives a reload, saving twice does not duplicate, and the count on the profile matches. One sentence, five scenarios.
Read the requirement and write three columns — what must be true, what should happen, what would be wrong — then turn every row into a case. This is where a fresher tester earns their place: a developer reads the code, and you read the requirement and ask about the case nobody has considered.
Requirement: "A user may reset a password by email."
Scenarios:
an email that exists -> email sent
an email that does NOT exist -> the SAME generic message (no user leak)
a malformed email -> validation error
clicking the link after it expires-> a clear "link expired" message
submitting twice quickly -> only one email
The requirement gives the happy path; you write the rest.Common mistakes
The mistake is testing only the positive path. "The customer receives the order confirmation" passes; "the customer sees a clear message when the email cannot be sent" is the one that finds the bug. Requirements always leave gaps, and the gaps are your job.
Worked example
"The password must be strong" is untestable until somebody writes the rule: at least eight characters, one digit. Now it is a test case, and the person who asked for the rule is the person you ask.
Your practice task
Take one page of a specification from any open-source project and write the positive and negative scenario for each sentence.
Do this before moving on. Reading a solution teaches the shape of it; typing it teaches you.
Key takeaway
A requirement is a sentence about what the system should do; a scenario is how you would check it.
Keep your place in this course
A free account saves which lessons you have finished and unlocks the certificate. The lesson itself stays free to read.
Create free account or sign inCourse complete
You finished every lesson.
Your certificate is ready, and the projects you built are the proof to attach to an application.
Almost there
15 lessons left of 15
Finish every lesson to unlock the certificate. Each one ends in a practice task — do them and the final project brief writes itself.