Proper content and logical structure ensure that test cases are clear, reproducible, and reflect a real user journey.
1. Content Guidelines
Use clear, concise sentences: Each step should describe only one action.
Exceptions: Processes already covered elsewhere (e.g., logging in) can be referenced as a single summarized step (e.g., “Log in”) or include only essential steps.
Expected results:
No requirement for the number of steps to match the number of expected results.
Link expected results to steps using contextual sentences. Example: “When tapping the ‘X’ button, the application must [...].”
Avoid duplicating expected results across scenarios, unless context changes (e.g., new features after an account upgrade).
Highlight in-app names: Always use quotation marks for buttons, features, sections, etc. Example: Tap “Log In”.
2. Structure Guidelines
Start with the First Thing the User Sees
Begin with the initial screen, functionality, or flow presented in the app.
Ground the tester in a natural user experience.
Create a Journey, Not a List
Structure test cases as a logical flow through the application, reflecting real user paths.
Order by Minimal Navigation
Begin with scenarios requiring minimal navigation or state changes.
Example (Login screen):
No input → Tap “Log In” → Error
Invalid email → Tap “Log In” → Error
Invalid password → Tap “Log In” → Error
Valid input → Tap “Log In” → Success
Arrange scenarios in the natural order of appearance in the app.
Eliminate Redundant Setup/Navigation
Avoid repeating steps within the same section.
Continue from where the previous scenario ended unless a reset is necessary.
Minimize Cross-App or Section Jumps
For multi-app or back-end interactions, cluster related actions together.
This maximizes coverage while reducing unnecessary switching.
Keep Scenarios Cohesive
General navigation steps (“Next”) should be included in the first scenario for the next screen.
Navigation integral to a process (e.g., “Sign Up”) should remain in the same scenario.
Temporary detours (e.g., viewing a help article) should include both navigation to and from the dead-end page within a single scenario.
Summary Tip:
Structure test cases to follow the user’s natural progression, minimizing back-and-forth and repetition. This ensures efficient, clear, and realistic testing.
3. Example Test Case Structure
Test Case ID | Section | Test Case Name | Steps to Reproduce | Expected Result |
|---|---|---|---|---|
TC-01 | Account set-up process | Sign-up screen | Launch the application | Application launches to lobby screen
|
TC-02 | Account set-up process | Terms of Use | Select “Terms of Use” | User reaches Terms of Use page |
TC-03 | Account set-up process | Welcome → Home screen | Tap “Next” within Welcome screen | User taken to Home screen
|
4. Example: Initial App Flow
Lobby (Sign-up / Log-In Screen)
Check overall display, grammar, and button availability (“Sign Up,” “Log In,” language selection).
Sign-Up Flow
Test input fields, warnings for incorrect/empty input, and button responsiveness.
Enter valid information, complete account creation, verify redirection to Home screen.
Home Screen (Post Sign-Up)
Check overview, welcome message, and main features.
Log Out and Return to Lobby
Test log-out functionality, verify content, and ensure user is returned to Lobby.
Log-In Flow
Tap “Log In,” verify navigation, display, and element availability.
Test input validations and successful authentication.
Tips
Cover visual/content aspects first, then drill down into function and happy/unhappy paths.
Ensure all interactive elements on each screen/section are tested before moving on.
Merge steps when they form a single logical journey to reduce repetition.
Follow all the steps and you will become the master of test case creation!
Comments
0 comments
Please sign in to leave a comment.