Keyword Driven Framework using WATIR

12,359 views

Published on

Presented in Stepin conference, Bangalore.

Published in: Business, Technology
3 Comments
6 Likes
Statistics
Notes
No Downloads
Views
Total views
12,359
On SlideShare
0
From Embeds
0
Number of Embeds
87
Actions
Shares
0
Downloads
624
Comments
3
Likes
6
Embeds 0
No embeds

No notes for slide

Keyword Driven Framework using WATIR

  1. 1. <ul><li>Keyword Driven Framework using WATIR </li></ul><ul><li>- Nivetha (nivetha@thoughtworks.com) </li></ul><ul><li>- Sripad (sripad@thoughtworks.com) </li></ul>
  2. 2. AGENDA Key Word Driven Framework How, Why, What Q & A
  3. 3. INTRODUCTION <ul><li>Test Automation Framework will reduce the amount of scripting required. </li></ul><ul><li>Test Automation Framework will accommodate changes with minimum effort. </li></ul>
  4. 4. About Agile Changes in requirements are encouraged Development will be done in Iterations Follows Test Driven Development Follows Continuous Integration process
  5. 5. Types of automation Record and playback Data Driven Keyword Driven Hybrid
  6. 6. Keyword Driven Framework
  7. 7. Architecture .txt Suite Variables file Processing inputs Core Engine Library Functions Customised Results Log Files
  8. 8. Sample Input File aka Test case .txt
  9. 9. Suite
  10. 10. Core Engine
  11. 11. Processing inputs
  12. 12. Library Functions
  13. 13. Customised Results
  14. 14. Customised Results
  15. 15. Approach Project Specific Keywords General Keywords Data Files Object mapping Cost Factor Technical feasibility Results Coding Standards Identify Keywords Develop Core Engine Structure input files Choose the tool
  16. 16. WATIR
  17. 17. About WATIR W eb A pplication T esting I n R uby WATIR development is led by Bret Pettichord and Paul Rogers O pen-source functional testing tool
  18. 18. About WATIR WATIR is a Ruby library that works with IE on Windows Tests can be run in the background Scripting is simple
  19. 19. Advantages The tester need only learn the &quot;Key Words&quot; required The Detail Test Cases can be written in Spreadsheet format containing all input and verification data Easier to write acceptance tests Transfer of knowledge is easier Easier to report bugs, copy from the input file and paste in Bug Reporting tool Application independent
  20. 20. Disadvantages Initial time and effort to develop the framework WATIR does not support plug in applications like Java Applet, Macromedia Flash. WATIR works only on IE Finding reference (name, id, value) to objects (text fields, buttons) may be tedious
  21. 21. <ul><li>WATIR </li></ul><ul><li>Tutorial –http://wtr.rubyforge.org/s101/doc/ </li></ul><ul><li>API Reference –http://wtr.rubyforge.org/rdoc/index.html </li></ul><ul><li>Home Page –http://wtr.rubyforge.org </li></ul><ul><li>Mailing list – wtr-general@rubyforge.org </li></ul><ul><li>Ruby </li></ul><ul><li>Home Page – http://www.ruby-lang.org/en </li></ul><ul><li>Discussion Forum -http://rubyforge.org/forum/forum.php?forum_id=958 </li></ul><ul><li>Tools Supporting WATIR </li></ul><ul><li>Recorder - WatirMaker - http://www.hanselman.com/blog/IntroducingWatirMakerRecordingForRubybasedWatir.aspx </li></ul><ul><li>Other Tools supporting WATIR - http://wiki.openqa.org/display/WTR/Tools+Supporting+Watir </li></ul>References
  22. 22. Questions ?

×