Automation Darker

Continuous testing

From Manual Testing to Continuous Testing [Webinar Recap]

Increasingly popular business initiatives to scale Agile, evolve DevOps, and adopt Continuous Delivery all have a tremendous impact on software testing—especially for the vast majority of testing that’s still dominated by manual testing efforts.

However, test automation is difficult. That’s why test automation rates are still below 25%, despite decades of test automation tools. Now, expectations for Continuous Testing are making test automation even more vital—and, in many senses, more challenging. What’s a tester to do?

For some practical tips, watch the on-demand webinar, Test Automation for Manual Testers: Transitioning to Continuous Testing. Tricentis’ Ingo Philipp begins by taking a look at why Continuous Testing is essential for Agile and DevOps, explores what changes are required, then explores several approaches for meeting expectations. The session concludes with a step-by-step demonstration on how to automate testing without coding or scripting.

Some key takeaways from the webinar include:

  • Continuous testing requires us to significantly increase test automation—which in turn requires increasing API testing and using service virtualization to ensure that automated tests can run consistently and repeatedly, even if the application under test’s dependent components are unstable or inaccessible for testing.
  • Record and replay test automation tools = 1st generation test automation. This includes linear frameworks, such as Selenium, where every scenario in your mind is represented by a distinct, isolated script. Often these tests can be executed only 3-5 times before they break.
  • Modular data-driven test automation tools = 2nd generation test automation. This includes modular, data-driven, and keyword-driven frameworks that provide some level of reuse and abstraction.
  • Model-based test automation tools = 3rd generation test automation frameworks. This represents frameworks that separate the business logic from the technical information so business users and subject matter experts can quickly define and update test cases as applications change—without any coding or scripting.
  • The maturity of a test automation framework is based on its stability, modularity, flexibility, readability, and maintainability. The more mature the test automation framework, the better it can respond to change (in technical details and/or business logic).
  • To effectively automate end-to-end testing, you need a way to integrate automation across all of the technologies involved in your business transactions (e.g., HTML, Java, .NET, mobile, SAP, mainframes, etc.). If you use different frameworks for different technologies, it’s important to find a way to integrate them and get them to “speak the same language.”

If you’re ready to try your hand at test automation, you can start a free trial of the industry-leading Tricentis Tosca today—no credit card required. Our free test automation video tutorials will guide you through every step of the process.