Lesson 14 Topic 1 Features
This article is a part of the Self-paced Learning Series for the Course: First-Hand Experience of Worksoft SaaS.Please refer to the link for more details on the Course.
Introduction of Worksoft SaaS Feature/Concept :: Lesson 14 :: Topic 1
1. Test Script Maintenance
Your Application under Test (AUT) may constantly go through changes that can impact test cases automated in Worksoft SaaS. This includes changes in AUT, layout, etc, which can impact the existing locators built during automation.
For example, you had a new release of the AUT to one of the lower environments, let's say QA. As part of the release, new functionality is rolled out, impacting the UI either by introducing new elements to the UI OR rearranging existing elements, which would result in, changes to the locators OR changes to the navigation. Unless automation is made in sync with these changes, either you will end up not testing the new functionality OR the automation will fail.
QaSCRIBE's rich features help you in assessing changes to the AUT and then make the required changes to the automation.
2. System Defined Variables
In Worksoft SaaS, a “System Defined Variable” is designed to cater to the need for reuse of a single Test Script which differs in behavior and layout. Worksoft SaaS helps you handle such behavior based on Environments (Environment Name or Environment URL), Testing Contexts (like different devices, browsers, browser versions, etc.), and Automation Assets (Data Files, Scenarios & Run Definitions).
Another use case of a System Defined Variable is where you have to verify the product details on mobile devices and desktop. When you assign the System Defined Variables in the script to execute on mobile devices and desktop, the execution condition would be based on the Testing Context selected during the Test Run.