This SauceCon 2019 presentation from Troy Walsh focuses on creating automated tests that fail better. He discusses logging and how it can make our failures valuable; explores error handling and how it can be both a blessing and a curse, and also covers test data management and how it can make failing far more useful.
3. 3
Effective Test Data Management
» Sufficient
» Representative
» Reproducible
» Automated
» Deterministic?
» *Legal/ethical/safe
» Credible
4. 4
» Collaboration
› QA
› Dev
› Operations
» *Tools
› Informatica - Test Data Management
› CA - Datamaker
› Compuware - Test Data Management
› IBM - InfoSphere Optim Test Data Management
› Many many more
What Does It Take
6. 6
» Is it a bug
› “Works as designed”
› “Cannot reproduce”
› “Works on my machine”
» What caused it
› Data
› Application
› Integrations
› Etc.
» Is this really the problem
› Root cause
Challenges
7. 7
» Summary
» Context
› Browser, OS, Resolution, Time (UTC), user, etc.
» Steps to reproduce
» Expected results
» Actual results
» Artifacts
› Screenshots, videos, logs, etc.
Reporting
18. 18
» Have a test data management strategy
» Write automation as though you expect it to fail
» Have logging
» Take advantage of advanced logging capabilities
› Event firing
› Screenshots
› Console logs
» If you have a service like Sauce Labs, take advantage of it
› DevOps integration
› Video
› Extended debugging
Takeaways