Making property based testing easier
summary
Prototype readSpec tool converts universally-quantified test properties and stateful test models into plain English and shows counterexamples and generated sequences. Claim: the transformation is feasible and useful for nontechnical stakeholders. Evidence: tool runs quickly on most FP7 PROWESS artifacts, output length fits stakeholder needs, one complex model needs extra resolution time, some developers prefer reading code but several nontechnical users and developers read the generated text and suggest new test scenarios after reading.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:34Get people involved
- 3:33Cucumber
- 5:13Clones
- 6:52Writing unit tests
- 7:32Modelbased testing
- 11:53Writing callbacks
- 13:27Testing without Cucumber
- 15:59Unit testing scenarios
- 17:25Pilot studies
- 19:43Results
- 22:27Interview
related talks
01h 24mIntroduction to Property Based Testing
46mProperty-based testing:You won't look at your tests the same way ever again
28mLanguage Support for Property-Based Testing
36mProperty-Based Testing: Unveiling the Truth on Test Reduction
36mIntroduction to stateful property based testing
30mProperty Based Testing: From Theory to Practice
51mProperty-Based Testing
14mVerify, but test: extracting property-based tests from F* specifications