Please enable JavaScript.
Coggle requires JavaScript to display documents.
Stop Writing Dumb Test Cases - Coggle Diagram
Stop Writing Dumb Test Cases
Why are Scripted Tests Dumb?
Take a lot of time to write - for a short time writing
Take time to keep maintaining
Limit the tester from looking at other scenarios
Most people only follow them once or twice and then ignore them
Provide a false sense of completion or coverage
People tend to abuse them as training documents for new employees
Why are Scripted Tests Good?
Ensure we do not forget, specially when we are repeating a test or working under pressure
Allow to schedule work and distribute it among the team
Serve as notes or even evidence of past runs
Provide a basis for measuring and reporting
Help to expand the team in times of demand and pressure
What are the alternatives to Test Cases?
Exploratory and Session Based Testing
Ad Hoc Testing
Bug Bashes / Safaris
Working with User Stories and/or Requirements
Heuristic-based Testing
Who said a Scripted Test needs to be Low Level?
We can have multiple levels of scripted tests
We can have multiple types of scripted tests
Scripted tests can use any of the "other" techniques
Every Test exercise is in a spectrum of Fully Scripted to Fully Exploratory
Different Techniques to include in your tests
Scripts
Objectives
Checklists
Heuristics
Charters
What if - scenarios
Negative scenarios
Bug verifications
Different levels of tests
Low level feature
Integration
End to end
Regression
Sanity
Smoke
Checklist
Importance of matching a test to the tester
Testing Specialist
Developer (knows functionality -vs- doesn't know)
Tech employee (support / services / sales)
Non Tech employee
Customer / Partner
General Tips for Test Writing & Maintanence
Organize and group them by multiple parameters
Have sets that work together
Have a system to review them periodically
Tests that are not run should be archived
Tests should be alive and updated on the fly
Debrief testing operations