• New Feature: Creating & Maintaining "Application Test Driver Inputs" Data Files directly from "Test Runs" and "Testing Contexts" screens
  

  The Worksoft SaaS “Test Scheduler" (click here if you want a refresher on the power it offers) lets you create and execute test cycle(s) and trigger the autonomous triage of failed tests, ML based re-execution of flaky tests, if any, and finally the generation of reports for those test cycles. One of the 3 inputs to the Scheduler is the “Application Test Driver Inputs” data file(s). These data files contain a listing of the actual tests (combinations of run definition - data - testing platform) that will get executed within one or more test cycles that the Scheduler triggers for execution.

  The automation test suite in your project may include hundreds or thousands of tests. This will correlate to hundreds or thousands of rows in the “Application Test Driver Inputs” data file(s).

  This release offers you a couple of powerful features that will help you efficiently and rapidly create and enhance/maintain the “Application Test Driver Inputs” data file(s) that are consumed by the Test Scheduler within your project.

  Directly from the "Test Runs" screen and/or for a specific Run Definition’s "Testing Contexts" screen, you now will be able to:

  • Create new “Application Test Driver Inputs” data file(s) with the tests (rows) automatically being populated.
  • Append additional tests (rows) to previously existing “Application Test Driver Inputs” data file(s).

  These features, if put to proper use, will yield significant effort and time savings within your automation projects. Can’t wait to benefit from these features? Click here to get started.

  
  
  
  
• QaSCRIBE for Google Chrome based on Manifest Version 3
  

  A new version of QaSCRIBE for Chrome is available for your to install and benefit from This new version is based on Manifest Version 3, an initiative of the Chromium project. The current version of QaSCRIBE for Chrome is based on Manifest V2. Support for any Chromium-based browser extension (like QaSCRIBE) built on Manifest V2 ends in June of 2023.

  

  Please note that a manifest file is the blueprint of a browser extension. It includes information such as the version number of the extension, the title of the extension, and permissions needed to run the extension. Manifest V3 is more secure, performant, and privacy-preserving than its predecessor. It is an evolution of the extension platform that takes into consideration both the changing web landscape and the future of browser extensions.

  You MUST manually uninstall QaSCRIBE ((based on Manifest 2) that is currently installed in your Google Chrome and install the new QaSCRIBE version (based on Manifest 3). Click here for instructions to uninstall QaSCRIBE (based on Manifest V2) and to install the QaSCRIBE (based on Manifest V3) afresh.

  If you are currently using QaSCRIBE for Mozilla Firefox, you do NOT have to uninstall and install QaSCRIBE afresh. You can continue to use the version of QaSCRIBE that is currently installed within your Firefox browser.

  
  
  
• QaSCRIBE for Microsoft Edge
  

  With this release, you have the ability to author test scripts from within Microsoft Edge. So far, you were able to do the script authoring with QaSCRIBE from within Google Chrome and Mozilla Firefox. MS Edge is the latest addition to the list of supported browsers.

  

  If Microsoft Edge is the primary browser that is used by the end users of your company's applications and/or it is the primary browser used by your development and QA teams within your company, you should install QaSCRIBE for MS Edge right away.

  To install QaSCRIBE for MS Edge, login into the Worksoft SaaS portal using MS Edge and navigate to the "Download Center" page from the hamburger menu and follow the instructions detailed in this article.

  
  
• Support for OAuth 2.0 protocol for tests interacting with REST services
  

  OAuth 2.0 is the industry-standard protocol for authorization. OAuth 2.0 focuses on client developer simplicity while providing specific authorization flows for web applications, desktop applications, mobile phones, and living room devices.

  It is an open protocol that allows secure authentication for access to a user's data, without handing out the user's username and password. It’s often described as the valet key of software access. A valet key only allows access to certain features of your car. For example, you can't open the trunk or glove compartment using a valet key.

  

  Worksoft SaaS now supports OAuth 2.0 based authentication within tests that have to interact with REST APIs that only support OAuth 2.0 protocol.

  A set of new commands are available for you to use to implement support for OAuth protocol within your tests. Please refer to the section ”Auth type: OAuth 2.0” in this article to learn and implement the newly available commands.

  
  
• Browser/Device Platforms - Newly Supported and Support Phasing Out
  
  
  
  
  
  
  

Share your ideas – Help us improve Worksoft SaaS!

We could not have gotten Worksoft SaaS to where it is without some brilliant ideas from all of you. Keep the suggestions and ideas for improvement flowing!

To submit an idea or vote on some of the features requested by other customers, click here