Přeskočit obsah

Test Case Basics

This blog post may be valuable for beginners writing their first test cases.

What is a Test Case

A test case should contain:
- Title
- Description
- Purpose
- Preconditions
- Test steps
- Test step title
- Test step description
- Test step expected result
- Actual test step result
- Test case result

Test Case Best Practices

  • A test case should be always testing one functionality
  • A test case should be unambigous
  • A test step should always use natural language with whole sentences when describing
  • A test case should always test one requirement or one user story
  • There may be more test cases covering one requirement
  • The person writing a test case should have a precise knowledge about the application under test
  • A test case must be understandable for the tester executing the test
  • A test step should be described in a clear and precise way
  • Every step in a test case should have a result
  • Entering data in a form may be one step until anything changes
  • A test case should be written when a feature is finished (Test Driven Development may work a different way)
  • When writing end-to-end test cases, other test cases can be used when written reusable
  • For end-to-end test cases, choose the happy path first
  • Test cases now covering any requirement are either not necessary or you must report back to businees to change the requirements