Atlas › 11 Manual Testing Fundamentals › Writing Test Cases☰ Read as one page
Writing Test Cases
1.1OverviewA test case is a contract between you and the future. Someone who has never seen the feature — including you in six months — must be able…1.2Anatomy of a Good Test CaseEvery test case, regardless of your tooling (TestRail, Zephyr, Google Sheets, or plain Markdown), should include these fields:1.3Common MistakesThese are the most frequent problems that make test cases unreliable:1.4The Given/When/Then TemplateThis format, originating from BDD (Behavior-Driven Development), works even outside Cucumber or Gherkin frameworks. It forces you to…1.5Test Case MaintenanceWriting test cases is only half the job. Maintaining them is the other half.1.6Practical ExerciseWrite test cases for a password reset feature with these requirements: - User clicks "Forgot Password" on the login page - User enters…1.7Key Takeaways- A test case must be executable by someone who has never seen the feature - Include ID, title, preconditions, steps, expected result, and…