Presented in Stepin conference, Bangalore.

2. AGENDA Key Word Driven Framework How, Why, What Q & A

4. About Agile Changes in requirements are encouraged Development will be done in Iterations Follows Test Driven Development Follows Continuous Integration process

5. Types of automation Record and playback Data Driven Keyword Driven Hybrid

6. Keyword Driven Framework

7. Architecture .txt Suite Variables file Processing inputs Core Engine Library Functions Customised Results Log Files

8. Sample Input File aka Test case .txt

9. Suite

10. Core Engine

11. Processing inputs

12. Library Functions

13. Customised Results

14. Customised Results

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. WATIR

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. About WATIR WATIR is a Ruby library that works with IE on Windows Tests can be run in the background Scripting is simple

19. Advantages The tester need only learn the "Key Words" 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. 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

22. Questions ?