Keyword-driven Test Automation Framework


Published on

Презентация с 7-й встречи автоматизаторов, Минск, 28 декабря 2011-го.

Published in: Technology
  • Be the first to comment

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

No notes for slide

Keyword-driven Test Automation Framework

  1. 1. Keyword-driven Test Automation Framework Concept, features, architectureMisha Suboch
  2. 2. TAF is a program which helps to performautomation testing effectively. Let us see TAF: Features Test Architecture Automation Workflow Framework Future 2
  3. 3. 1. Features and Advantages2. Usage Workflow3. Architecture4. Artifacts5. Implementation in Your Project6. TAF Core Features 3
  4. 4. 1 Features and Advantages 4
  5. 5. 1 Keyword-Driven2 Product-independent3 Tool-Independent • Business Logic • GUI Objects4 Maintainability • Steps • Utilities 5
  6. 6. Keyword-drivenProduct-independentCompatible with any automation tools on the marketAligned with Continuous Integration Frameworks(single entry point, unified test reports, etc.) 6
  7. 7. 2 Workflow 7
  8. 8. 1 Initialization • Study Application2 • Mock up Test Scenarios Development • Implement Scenarios • Debug /Verify • Run Test Scenarios3 Usage • Create New Test Scenarios • Tune for New Build4 Maintainability • Implement New Steps 8
  9. 9. 3 Architecture 9
  10. 10. Test Scenario 1Test Scenario 2 Test Bug ListTest Scenario N TestComplete TAF TAF Core Custom Run TAF.exe Automation tool Another Automation tool XML HTML Test ReportsTool Specific 10
  11. 11. 11
  12. 12. Read ConfigsRead Test Suite/Unified Test ScenarioRead Bug ListLoad DataConstant variables • Stores • Substitute • Calculate ExpressionsCreate Execution ListRun Automation Tool TAFExecution Optional (Cleanup) CommandCreate Reports 12
  13. 13. 13
  14. 14. TAF Core code is generated using Test-Driven Development approach, it is very wellstructured and covered by unit tests (more than 300 passed unit tests validates TAF Corequality). 14
  15. 15. 15
  16. 16. ExecutionList.txt Automation TAF Core Tool TAF TestResultsSummary.txt1.When scenario is read and parsed, TAF Core generate Execution List and run Automation Tool TAF.2.After executing all tests, Automation Tool TAF generates Test Results Summary and exits.3.TAF Core reads Test Results Summary and generates final results. 16
  17. 17. 17
  18. 18. Tool Status of TAF support SilkTest Supported Test TestComplete Supported (TAF Core) Data Quicktest Pro Supported (TAF Core) Watir Supported (TAF Core) Test Selenium Supported (TAF Core)Scenarios Scripts Actions Test Cases Verifies Driver Controller Frames Screens Utilities 18
  19. 19. 19
  20. 20. 20
  21. 21. 21
  22. 22. 4 Artifacts 22
  23. 23. 23
  24. 24. Metrics Summary, Passed 24
  25. 25. Summary, Failed Summary, Failed with Bug LinkSummary, Known Issue 25
  26. 26. 5 Implementation in Your Project 26
  27. 27. Automation with TestComplete, Watir Automation with another tool:or QTP:Get Test Complete TAF / Watir TAF / QTP TAF Implement controller Develop test scenarios Develop test scenarios Implement steps Implement steps 27
  28. 28. 6 TAF Core Features 28
  29. 29. 1. Unique keywords in test scenarios allow you to generate unique text and numbers in specified format2. Ability to run several test scenarios at once, even if written in different automation tools3. Ability to use the same test scenario for different automation tools, when one tool could not cover all test configurations (browsers/OS).4.Unified test results (in .xml) across different automation tools/projects/applications provide integration options with external tools (like Cruise Control).5. Ability to mark failed test cases as known issue and link to related bugs in test results.6.Keywords Feature: Load/Repeat keywords allow to create data-driven test cases. Application keyword allow you to work in one test scenario (or even in one test case) with different applications. 29
  30. 30. 8. Arithmetic expressions calculation and Variables values substitution. Ability to exchange variables values between different test scenarios, automation tools or even when different test scenarios should be run one by one on different servers.9. Unified test scenario could be easily accessed for review by customer or business analyst (no programming knowledge required)10. Working with results: Auto-archiving of previous test results. Test results contains information about what workstation/server was used for scripts run, when and which TAF Core version they were generated by.11. Extensive configuration features: execution (run selected tests/complete scenario), results output, logging, etc. 30
  31. 31. Test AutomationFramework Misha Suboch 31