Codeless Test Automation - Myth or Magic

Codeless Test Automation - Myth or Magic

• 1.
  ® WEBINAR Codeless Test Automation: Mythor Magic? January 31st, 2019 – Adam Sandman We will be starting the webinar shortly, please stand by… All phones will be automatically on mute until the Q&A.
• 2.
  ® 3 | 2/6/2019© Copyright 2006-2018 Inflectra Corporation Agenda Background The 10 Features Codeless Automation Tools Should Have 1. Smart Element Locators 2. Conditional Waiting 3. Control Structures 4. Easy Assertions 5. Modification Without Redo 6. Reusable Steps 7. Cross-Browser Support 8. Reporting 9. Ability to Insert Code 10. Continuous Integration Q&A
• 3.
  ® Background
• 4.
  ® 5 | 2/6/2019© Copyright 2006-2018 Inflectra Corporation ® How did this come about?  Angie Jones threw down the gauntlet to the makers of codeless automation tools:  https://techbeacon.com/app-dev-testing/10-features-every- codeless-test-automation-tool-should-offer  We published a whitepaper, taking up the challenge with Rapise:  https://www.inflectra.com/Ideas/Whitepaper/10-Features-Every- Codeless-Test-Automation-Tool-Should-Offer.aspx
• 5.
  ® 6 | 2/6/2019© Copyright 2006-2018 Inflectra Corporation ® OK, What is Rapise Anyway?  Rapise is a codeless test automation tool for web, mobile and desktop applications:
• 6.
  ® 1. Smart ElementLocators One of the biggest problems with test automation is that testers develop against an application at a given moment in time. When the application changes, those automation scripts may break.
• 7.
  ® 2. Conditional Waiting Record-and-playbacktools that require script authors to insert pauses between steps are tedious. Codeless tools should, at the very least, allow script authors to insert conditional waiting, but it would be even better if the tools took care of this behind the scenes.
• 8.
  ® 3. Control Structures Incoded automation frameworks, testers use loops and if-else clauses to control the flow of scripts. This is a necessary requirement for codeless solutions if the project is to be scalable.
• 9.
  ® 4. Easy Assertions Theprocess of adding assertions should be as simple as adding the navigational steps. Great consideration should be given to this feature, since it's the most important part of the test script.
• 10.
  ® 5. Modification WithoutRedo As the application under test changes, the test scripts need to change as well. This may require adding or removing steps from a flow, or slightly changing existing ones. Codeless automation tools should recognize this as inevitable and make it as simple as possible to accomplish this.
• 11.
  ® 6. Reusable Steps Codelesstools should allow authors to record common steps that they can then insert into any test flow. This would not only save time in authoring, but also promote reusability and make maintenance much simpler.
• 12.
  ® 7. Cross-Browser Support Testauthors should be able to record a scenario once on a given browser, and be able to play that recording on any other major browser.
• 13.
  ® 8. Reporting Adequate reportingis a must-have for test automation, especially when testers are executing hundreds—or thousands—of tests. An automatically generated report with details on what occurred, with screenshots would be very helpful.
• 14.
  ® 9. Ability toInsert Code No codeless tool can incorporate everything that's possible. So, test authors should have the ability to let testers insert code within the tests for those edge cases.
• 15.
  ® 10. Continuous Integration Inthe era of DevOps, test automation is a key ingredient in continuous integration and continuous deployment. Tests should integrate with such pipelines and automatically execute when triggered
• 16.
  ® 17 | 2/6/2019© Copyright 2006-2018 Inflectra Corporation Questions? Please feel free to unmute your line, raise your hand, or simply write your question in the Chat window.
• 17.
  ® 18 | 2/6/2019© Copyright 2006-2018 Inflectra Corporation Thanks for Watching Subscribe to Our Channel for More Videos on Software Testing http://www.youtube.com/inflectracorporation