Test Data - Food for your Test Automation Framework
2 likes6,473 views
This document discusses the importance of test data in test automation frameworks, highlighting its role in ensuring consistency and value in testing. It details the criteria for effective test data, including complexity, uniqueness, and the ability to mimic real-world scenarios. Additionally, it reviews various formats for specifying test data and offers implementation tips while acknowledging that the choice of patterns largely depends on the specific context.
Test Data - Food for your Test Automation Framework
- 1. TEST DATA – FOOD FOR TEST AUTOMATION FRAMEWORK Anand Bagmar Software Quality Evangelist
- 3. Why are you here?
- 4. Test Automation A PRACTICE THAT MAKES TEAMS SUCCESSFUL?
- 5. Test Automation A PRACTICE THAT MAKES TEAMS UNSUCCESSFUL?
- 6. Why do we do Test Automation?
- 9. How to get value from Test Automation?
- 10. Run on every change in the codebase Product & Test
- 12. o Repeatable o Deterministic o Indicates Quality
- 14. Test Data
- 15. WHAT IS TEST DATA? ¨ Input - Data required for test to execute ¨ Environment configurations ¨ Credentials ¨ URLs ¨ … ¨ Output - Expected Data as output of actions done on Product-under-test
- 16. What is a Design Pattern?
- 19. Why do we need to think differently about Test Data?
- 20. CRITERIA FOR TEST DATA ¨ Data is complex ¨ Needs to mimic “real” data ¨ Needs to be unique ¨ Data can be nested ¨ Though specified as static, may need to be Dynamic ¨ Data can be shared and reused
- 21. Case Study
- 23. 23
- 24. 24
- 25. 25
- 26. Code sample
- 27. What did we observe?
- 28. DIFFERENT WAYS TO SPECIFY TEST DATA ¨ In Test implementation ¨ In Test specification / intent ¨ In code … separate data structures / classes / etc. ¨ External files
- 29. TEST DATA SPECIFICATION EXAMPLES ¨ Excel ¨ CSV ¨ Property ¨ XML ¨ YAML ¨ Database ¨ Json
- 30. CRITERIA FOR SELECTION ¨ Easy to specify ¨ Easy to read and consume (by test framework) ¨ Ability to override specified data, easily ¨ Usable
- 31. TIPS FOR IMPLEMENTATION ¨ Consistent way to specify test data ¨ Read the data – as Business Entities ¨ Override as appropriate ¨ Create DSL to give meaning to data ¨ Use in test implementation ¨ Implement Test Data Entity Utilities – Build, Equals, Copy, Find, etc.
- 32. WHICH IS THE “BEST” PATTERN TO USE ?
- 34. Some tools
- 35. 35