TSQA: Something In The Way We Test
•
0 likes•10 views
This document discusses exploratory testing and compares traditional test case-driven approaches to more contemporary exploratory approaches. It notes that test cases are better thought of as outputs that convey relevant information rather than inputs used to direct testing. The document also emphasizes that exploratory testing is a verb describing the active process of doing testing rather than a noun referring to pre-defined tests. It advocates for change-focused testing and shares examples of moving from traditional test documentation like test case documents to more lightweight charters and specifications.
Recommended
More Related Content
Similar to TSQA: Something In The Way We Test
Similar to TSQA: Something In The Way We Test (19)
More from Maaret Pyhäjärvi
More from Maaret Pyhäjärvi (20)
Recently uploaded
Recently uploaded (20)
TSQA: Something In The Way We Test
- 1. @maaretp Something in the Way We Test by Maaret Pyhäjärvi
- 3. @maaretp Hiring a 15-yo as tester “Find conversation starters” “Document what you do exactly”
- 4. @maaretp Even a broken clock is right twice a day.
- 5. @maaretp Testing serves a purpose: catch information we may be missing.
- 7. @maaretp Cost of Documentation? … writing … reading … maintaining
- 8. @maaretp 5000 test cases My new project…. Validate that…. Verify that… Shall be… 100% of team changed
- 10. @maaretp 2003 insight: - Architecture doc => abstract - Test doc => concrete
- 11. @maaretp Read-time Awareness person reading for minute each Eleven (11) work-days
- 12. @maaretp A Smaller Sample Gen 0: 66 shall-statements Gen 1: 46 do-verify –statements, 12 manual Gen II: 18 [feature] charters
- 13. @maaretp Test cases are ideas not actions and that is why you cannot record them based on the clicks you do.
- 14. @maaretp Test cases are outputs from testing, not inputs to it.
- 15. @maaretp As outputs useful if: They convey relevant information without extensive investment to read
- 16. @maaretp Second Smaller Sample Gen 0: • 6 [feature] charters • 4 feature files with 40 executable specs • Developer intent captured in 209 unit tests, 7 integration tests, 16 UI tests
- 17. @maaretp Test case Charter Executable Example Ideas (title only)
- 18. @maaretp The Bigger Theme? 19 new tests 6 weeks overlap time remains Change-focused testing …a lot of work ahead of us
- 19. @maaretp Exploratory Testing the Verb Doing Testing INPUT OUTPUT
- 20. @maaretp Input Tester Domain knowledge Requirements and specifications Testing knowledge Miscellaneous knowledge Doing Testing INPUT OUTPUT
- 21. @maaretp Output Better tester Coverage Information incl. defects and change requests Documentation: Strategy Documentation:Tests Doing Testing INPUT OUTPUT
- 24. @maaretp 2020 2016 MIATPP Most Influential Agile Testing Professional Person #PayToSpeak #TechVoices #EnsembleTesting #EnsembleProgramming #StrongStylePairing #ExploratoryTesting #TestAutomation #ModernAgile #AwesomeTesters Maaret Pyhäjärvi (from Finland) Email: maaret@iki.fi Twitter: @maaretp Web: maaretp.com Blog: visible-quality.blogspot.fi (please connect with me through Twitter or LinkedIn) 2019, 2020, 2021 https://exploratorytestingacademy.com Ohjelmistotestaus ry https://techvoices.org