Test Automation - Insights Into Frameworks by Anup Patnaik, QA InfoTech


Published on

Tools and techniques for automated test execution have been around even before the activity of testing was seen as independent of debugging. And with growing complexity of software, companies have embraced test automation as an integral part of their test strategy. This is primarily to augment human testing in order to meet goals ranging from increasing test coverage on greater number of platforms to shorter release cycles. However, it is surprising to see how many of these projects fail. According to some industry estimates, 85% of these projects fail to bring any real ROI.

Along with answering the all important questions of what to automate and when to automate, test managers need to understand the implications of using the various tools, techniques and frameworks. And this choice is largely determined by the mission that the project needs to accomplish. Will only the underlying tool suffice, what would be the limitations? Should you be using a keyword driven framework or should you be designing a domain specific language on top of your tools? Given a fast changing application, which of the many approaches will work better? Which one can be learnt and adopted faster by a large team of human testers? These and many other questions can be answered only by the experience of applying the approaches to real projects.

In this talk, based on our long experience of working on test automation projects, we help test managers understand and answer similar questions. We trace maturity of automated testing from tools to frameworks, and detail out the nuances and pit-falls of the approaches in the wake of a given mission. In addition we show how using the many open source tools test mangers can develop robust yet cost-effective solutions.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Test Automation - Insights Into Frameworks by Anup Patnaik, QA InfoTech

  1. 1. Test Automation – Insights into<br />using Frameworks & Techniques<br />Anup Patnaik, Director Quality Engineering &<br />New Initiatives<br />
  2. 2. What’s in there?<br />What went wrong – A little story<br />Why is it hard – Goals Vs Reality<br />Action Based Frameworks<br />Page Object Patterns<br />Domain Specific Automation<br />Putting it all together – DIAT<br />Conclusion<br />Agenda<br />
  3. 3. No Name Inc.<br />Automated!<br />“The Product”<br />Test Engineers<br />Test Automation Engineers<br />
  4. 4. So many of them, really!<br />Wow Bugs<br />
  5. 5. What went wrong?<br />Oops!<br />“The Product”<br />!!??##??!!<br />Test Engineers<br />Test Automation Engineers<br />
  6. 6. A glance<br />Goals Vs Reality<br />
  7. 7. What’s the message?<br />Learning<br />Doing Test Automation right is Hard!<br />Let’s not paint a rosy picture<br />
  8. 8. The language of automation<br />Actions<br />Easy action based automation using keywords for user actions<br />
  9. 9. How is it done<br />Actions<br />Excel based input with libraries written in the tools language<br />FitNesse + Selenium<br />FitNium<br />
  10. 10. What’s lacking<br />Actions<br />What did we loose on the way<br />Flexibility – can we loop over, can we handle large data files<br />What is still missing<br />A clear structure<br />
  11. 11. UI Model Based<br />Page Objects<br />UI Modules that know about themselves<br />We know where to change when a piece of UI changes<br />Tip on Tool - Tellurium<br />
  12. 12. Let’s talk in the language of business<br />DSL<br />Domain specific actions that let you write English like automated test scripts<br />Clean mapping of requirements to automated scripts<br />
  13. 13. An Implementation<br />DSL<br />
  14. 14. What’s lacking<br />DSL<br />What did we loose on the way<br />Flexibility again (of composing user actions at the top level)<br />What is still missing<br />Supporting needs e.g. compatibility testing<br />
  15. 15. Test Lifecycle<br />DIAT<br />Distributed Intelligent Automated Test Framework<br />
  16. 16. A good recipe<br />DIAT<br />FitNesse<br />Selenium<br />Distributed Intelligent Automated Test Framework<br />Test Run<br />XP_FF3 – TC 1<br />Vista_IE7 – TC 2<br />DIAT Client - Agent<br />Test Case 1<br />Test Data 1<br />VmWare<br />VM Host<br />Test Data 2<br />
  17. 17. Real Implementations<br />Example<br />
  18. 18. What’s the message?<br />Learning<br />There is no silver bullet<br />
  19. 19. reachme: anup@qainfotech.com<br />All content / information present here is the exclusive property of QA InfoTech Pvt. Ltd. The content / information contained here is correct at the time of publishing. No material from here may be copied, modified, reproduced, republished, uploaded, or posted in any form without prior written permission from QA InfoTech. Unauthorized use of the content / information appearing here may violate copyright, trademark and other applicable laws, and could result in criminal or civil penalties.<br />Copyright © 2009 QA InfoTech Pvt. Ltd.<br />