Future of test automation tools & infrastructure
1 like1,967 views
The document discusses the evolution and future of test automation tools, focusing on custom frameworks, behavior-driven development (BDD), and advancements in user interface technologies. It emphasizes the need for structured and reusable code, integration with external libraries, and better reporting mechanisms for automation metrics. The document outlines steps for improving testing processes through examples and methods for efficient test execution and data handling.
Future of test automation tools & infrastructure
- 1. Future of Test Automation Tools & Infrastructure Anand Bagmar ThoughtWorks
- 2. Evolution Custom frameworks Record & Playback Core Framework
- 3. Custom Frameworks • Hybrid
- 4. Evolution What is next? Behavior Driven Development (BDD) Custom Frameworks Record & Playback Core Framework
- 7. Web catching up …
- 9. Spatial operating environment Professor John Underkoffler - MIT
- 10. Sixth Sense Technology Pranav Mistry
- 11. What this means for us? What we need to do? AND …. Think big!!
- 13. Features • Discovery • Execute tests • Author • From within or command line • Publish • Create run command • Plugin Manager • Remote machine(s) or locally IDE Runtime Debug Report • Regular debugger • Result Analysis functions • Charts & Graphs • Advanced • Archive debugger
- 14. Plugins Scheduling Language / Test data framework generators agnostic Integration Custom with external Reporting – tools & Trend analysis repositories Discovery Omniture tools Testing xPath Utilities UDD …
- 15. Get credentials Discovery Get credentials from external user data file Login Go to login page Login Get criteria from Get search external search criteria data file Search Query Search & buy ticket Return results Login Select ticket Get search results Enter ticket Buy ticket details Get card details Enter payment from external options data file Checkout
- 16. Creating new Tests Enter criteria Load View page results Make Login selection from results Select ticket Login Enter ticket Search details Checkout Checkout
- 17. How do we get there? • Write better structured / layered code • Reusability – productize it • Use external libraries instead of copying the code directly.
- 18. Example 1 – Omniture Testing • Generic approach • Minimum existing test modification Omniture_Methods.setRequiresOmnitureTesting(); • Test data defined in easy-to-understand XML • Can test multiple set of Omniture sections. • Extracted into a jar for easier reuse.
- 19. Example 2 – Custom Listener • Control test execution flow • Handle test dependencies • Critical Test Failures • Richer reports
- 20. Example 3 – Reporting • Provide visibility “due” for Test automation • Use the metrics that matter • Subscription / RSS feed • Archive