• New Feature: Ability for creating, editing and/or applying a Data Filter from within the View Data File screen
  

  This release offers you a powerful, productivity-enhancing feature that will let you create and/or update a Data Filter from within the Data File screen when in the 'View' mode. So far, you were able to do that only using the Create/Edit a Data Filter screen. You now will also be able to "apply" a currently existing data filter or a newly created data filter on the data contained in the data file. You will also be able to create and apply a (temporary) data filter that you don't have to save.

  You also can copy to clipboard the row numbers associated with the filtered data in the data file (as a result of the application of a data filter), which then can be used as part of the maintenance of the "Application Test Driver Inputs" Data Files directly from the "Test Runs" and "Testing Contexts" screens, a feature rolled out as part of the Aug 1st, 2022 release.

  
  
  
  

  Click here to get started.

  
  
• Productivity-improving Enhancements within the View/Create/Edit Data Filter screen
  

  When creating/editing the data filter, you will be able to see more of the value field with a better use of the available screen real estate. More importantly, once you apply a data filter on a specific data file from within the view/create/edit data filter screen, you now will be able to use the premium/editor viewer to view and update long or structured content (like JSON, XML, JavaScript, etc.,) within the cells of your data files.

  Click here to see how you can create/update and view data filters within your automation projects.

  
  
  
  
• Enhancement: QaSCRIBE captures UI Element Names within your application in addition to the UI Element Locators
  

  With this release, QaSCRIBE will capture descriptive information (like a label, aria-label, etc), if available, for the UI elements that are operated upon (or interacted with) as part of a test instruction over and beyond all available locators that help the identification of that element during a test execution. This information will be shown within the Test Script screen in the view/create/edit mode. This will significantly help you correlate the locators that are captured to the UI element when you are trying to debug issues, if any, associated with the execution of your automated tests.

  

  When recording new test instructions within a new or an existing test script, you don't have to do anything additional for this information to be captured by QaSRIBE and for that information to be saved as part of your Test Script. For previously saved test instructions within previously existing test scripts, most likely this richer descriptive information may not be available. If this happens to be the case for your test scripts, please follow the instructions outlined here for your test instructions to be updated with the element's descriptive information.

  Based on your project level settings, the same element name information can also display on the Test Execution Results screen as well. This will help you debug failures, if any, associated with the test execution faster. Please note that the default value for this setting is for the UI Element Names, even if captured by QaSCRIBE and saved within your Test Script, to not display on the Test Execution Results screen. If you are interested in getting the UI Element Names display on the Test Execution Results screen, you must change the value of the setting by unchecking the checkbox and saving your updated settings.

  

  The screenshot below illustrates how the UI Element Names will display on the Test Execution Results screen.

  

  Click here to get started.

  
  
• Dropping of support for Manifest Version 2 based QaSCRIBE for Google Chrome
  

  On August 1st 2022, a new version of QaSCRIBE for Google Chrome was released. This new version is based on Manifest Version 3 is more secure, performant, and privacy-preserving than its predecessor.

  Included in the Release Notes for that release was a request for those of you using QaSCRIBE within Chrome to 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). Instructions were provided within this release notes for you to uninstall QaSCRIBE (based on Manifest V2) and to install the QaSCRIBE (based on Manifest V3) afresh.

  

  Please note that 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.

  If you do use QaSCRIBE within Chrome but have not yet uninstalled Manifest Version 2 based QaSCRIBE and install the Manifest Version 3 based QaSCRIBE, you must do so immediately. You will not be able to use the older version anymore as of this release. Click here for instructions to uninstall QaSCRIBE (based on Manifest V2) and to install the QaSCRIBE (based on Manifest V3) afresh.

  
  
• Ability for customers to initiate auto-provisioning of infrastructure for running your performance test cycles
  

  If you have a subscription that allows you to run all your performance tests within the Worksoft SaaS platform, this enhancement will offer you significant benefits. When scheduling your performance test cycles using the Worksoft SaaS Test Scheduler component, you now will be able to request the auto-provisioning of infrastructure necessary for you to run your test cycle that simulates a load of 1000s of concurrent users.

  You can do so within a new accordion that shows up as part of the Scheduler workflow (please see screenshot below). You must specify the max concurrency for your performance test cycle as well the list of email addresses to which you want all email notifications related to the scheduling, execution and reporting related to your performance test cycle. The max concurrency you pick, however, has to be equal to or less than the max concurrency supported by your Worksoft SaaS subscription for performance testing.

  

  Please note that you should not check off the checkbox "Provision infrastructure immediately" when you schedule test cycles for running your functional and/or cross-platform tests. You should use this checkbox only when scheduling test cycles for your performance tests.

  For more details, click here.
  
  

• 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