New trends in testing automation


Published on

Trends in automation testing presentation given by Lior Katz, TACT testing at QA Extreme 2011 conference.

Published in: Technology
1 Like
  • Be the first to comment

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

No notes for slide

New trends in testing automation

  1. 1. New Trends in Testing Automation
  2. 2. Changing the conceptTest Automation frame work
  3. 3. Key Driven Test DefinitionKeyword Driven Testing is a comprehensive, cross-organization test design solution that bridges the gapbetween the Test Automation team and the rest of theroles involved in the testing process. It allows bothmanual testers and other subject-matter experts todesign, build and execute test automation scripts withoutany programming knowledge
  4. 4. Limitation of Testing AutomationProcess • Design – Specific design • Execution – separate execution and separate resultsMaintenance • Test Automation require maintenance shifting from version to versionExpertise • Automated Testing tool software developers • System experts • Test engineers
  5. 5. KDT advantages• Increase Testing Automation coverage• Faster ROI• Join effort between automated testing and Manual testing (Omnitest)• Manual testing and automation executed together
  6. 6. The KDT languageBasic Terms• Test case – A set of conditions or variables under which a tester will determine whether an application or software system is working correctly or not• Keyword - A word or identifier that has a particular meaning to the programming languageKDT Terms• Action – A perform action on a specific GUI object• Automated TC’s – a sequence of actions represent TC flow
  7. 7. When/Where to implement KDT• Testing Automation already implemented• Testing Environment ready to go• Keep all management requirement from Testing Automation aspects• Keep Automation developers update with the process• Massive amount of TC’s
  8. 8. Testing automation frame work – Layers structure 1 Mapping OR 2 Develop GUI & Business function 3 Develop scripts 4 Execution maintenance via QTP Testing automation frame work – Key Driven Test 1 Mapping OR 2 Develop Scripts via KDT 3 Generate QTP code 4 Execution via QTP maintenance via KDT tool
  9. 9. Work . Planning Development Execution Maintenance CommentFrameLayer No Develop GUI Execute via Very easy to planning and business QC or via maintain ONLY is needed function automated GUI function ONLY engine and Objects manual changes TC’sKDT All Need to Via the KDT Can be a planning develop tool problem, not via the infrastructure much experience KDT tool via automated with working tool projects
  10. 10. . OmniTest – OmniSys Via XLS file Tesnet – KDT HP BPT Test planner - Qualitest
  11. 11. .
  12. 12. .• KDT is the next Testing Automation generation• Current status KDT work as a POC in several places still need to Ripen in order to give the full ROI• KDT will: • empower the usage with Testing Automation tools • Force the organization to use Automated tools • Increase coverage • Solve maintenance issues • Shortage the development period• Current status: • No company is using a KDT tool as a stable testing environment • Maintenance issues still not resolve completely • Automation expert still take big part in the script development
  13. 13. Working in other project environment Testing automation in Agile environment
  14. 14. The old and “good” (?) water fall “The "traditional" model of software development lifecycle.” 1 Analysis 2 Design 3 Coding 4 Testing
  15. 15. The old and “good” (?) water fall Testing automation life cycle in water fall• Only regression testing covered by TA• Testing automation follow the manual testing versions (always regression testing of the previous version executed)• TA design always by the manual testing group• Execution Priority by the manual testing manager• Very easy to control and manage
  16. 16. Agile conceptEmphasize collaborative, integrated teams, frequentdeliveries, and the ability to adapt to changing businessneeds
  17. 17. Testing Automation in Agile environmentSince working increments of the software are releasedoften in agile software development, there is also a needto test often. This is commonly done by using automatedtests to minimize the amount of manual labor involved.Undertaking only manual testing in agile developmentmay result in either buggy software or slippingschedules, as it may not be possible to test the entirebuild manually before each release.
  18. 18. Testing Automation as part of the scrum team• Testing automation activities is part of the backlog document• Automation developer take part in all scrum stages• Automation status is part of the morning meetings• Testing automation is a MUST as part of the scrum testing scope• Automation developer works closely with all team members (Manual tester, Developer, PMO, etc…)
  19. 19. Testing Automation execution Scrum work flow• Testing automation execution occur after the first code delivery• Usually will try to use existing code• API execution is an advantage• Result analyze by the whole scrum team
  20. 20. Some Agile testing principles justify Testing Automation• Testing moves the project forward• Testing is not a phase – it’s a way of life (ongoing execution)• Every body test – Manual testers execute automation• Keep the code clean – rerun testing execution• Test Driven advantage – very easy to develop in automated testing
  21. 21. Testing Automation management process
  22. 22. !Common life cycle 1 Purchase the tool 2Recruit developers 3 Understand ROI 4 Fail to implement TTM – life cycle 1 Analyze the systems 2 Recruit developers 3 Understand ROI 4 Follow TTM Purchase the tools and managers methodology
  23. 23. " # $
  24. 24. # %& # # $ # !
  25. 25. Testing Automation Readiness 4• Developers• Stable environment• Understand business process• Tools readiness• Testing Automation environment readiness• Developers understand the project scope• Set expectation
  26. 26. 4 Testing Automation Stages• Sanity SET – Set of ~50 QTP scripts, verify that new build (version) ready for massive testing process• Quick ROI Developments – Packages can retrieve the investment immediately (e.g. API, data driven, data inflation)• Regression by modules So important to make sure NOT to develop all regression tests in one SET, “Before moving forward with the development stage, we need to analyze our system and divide it by modules, for each module to develop his own automation SET”• Data Inflation – Using our GUI interface can help with massive data changes
  27. 27. 4 Testing Tools Management Progress• Define the project scope• Follow up• Testing Automation methodology• Summary
  28. 28. Manage your testing project ALM
  29. 29. Application Lifecycle Management" # $ # $ ( ) # ) $ ) ) ) $
  30. 30. * + !+" ,
  31. 31. ALM Stages
  32. 32. Strategy• #•&• $ •- .
  33. 33. Requirement•/•0 $•• (
  34. 34. Quality•0•+•,
  35. 35. Operational•• (•
  36. 36. ALM Tools
  37. 37. The Tools
  38. 38. Open Source Open source toolsTesting tool for browser-based testing of webapplications A plug-in driven automated testing tool that separates applications into features and allows those features to be tied together independently An automated functional testing framework for web applications
  39. 39. Types of testing Automation Tools Tools cost money QTP – The MOST common testing Automation tool (41% of the market) Test Complete – support Extensive platforms Not supported as QTP Team System 10.00 Coded UI – Testing Automation tool by Microsoft
  40. 40. ! "# $
  41. 41.