Skip to content

Lesson 14 Topic 2 Features

← Worksoft SaaS Self Paced Learning - FHE - Supporting Articles 
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 2


1. Failed pop-up Locator
Let's say you have seen a notification on the recent AUT deployment and you want to find out if any of the recent changes impact the test script, then we perform an execution (recommendation local execution).

When the execution starts, QaSCRIBE picks up the commands of each instruction and performs a test on the element based on the locator sequence in the Target field. As QaSCRIBE captures multiple locators at the time of recording, the execution is able to use multiple locators. In case, all locators are modified and QaSCRIBE cannot find the element, then the execution stops at the impacted instruction. If one of the locators identifies the element, QaSCRIBE would proceed with the execution but will highlight the element in red.

A failed locator pop-up appears on mouse hover of the number icon in the Target field. In that list, all the available locators are displayed and the locator highlighted in red represents the failure along with the execution time for each locator. If the execution is successful with the consecutive locator, then the test will result as successful and the status will be displayed as completed.

In case all the locators fail, QaSCRIBE also has a mechanism to iterate the existing sequence of locators. This helps in the case where the locators are valid but are unable to be applied because the AUT page didn't load completely. So when QaSCRIBE starts iteration and if the AUT page has completely loaded by then, there is a good chance of one of the locators being picked up and the execution resulting in success. QaSCRIBE performs this iteration for 2 mins, which is a default time out duration and within that duration if the locators still don't match with the targetted AUT element, then the execution will result in failure. The number on the icon represents the number of iterations performed by QaSCRIBE.


2. Verify Validity of all locators
Every application is unique in terms of how the UI is laid out and there is no commonality in how the locators are defined. It is very much possible for the UI to have duplicate locators and/or one of the duplicated locators is in hidden state etc. To help you in such cases, Worksoft SaaS provides multiple options while you use QaSCRIBE to maintain test automation.

In the 'Design & Build' tab of the Test Script, On the Target field, there is an icon resembling a shield, that's called 'Verify validity of locators'. You can verify the validity of the locators on your Test Script, any time (before/after) executing test. This shield is in blue if the Test Script has never been executed, it shows red/green if the Test Script has already been executed(in this case, QaSCRIBE has already validated the locators at the time of execution)

You can manually verify the validity of locators for each instruction (in case it's not already validated) by clicking the shield icon. QaSCRIBE performs a validity check on the locators (based on your selection).

When we click the button (Verify validity of locators), we will see that there are 4 Validation types for selection:
  1. Identify invalid locators that can't individually match any element (visible/hidden) on the UI: When you select this option, it identifies the invalid/stale locators which do not match any UI elements.
  2. Identify the locators that individually match hidden (invisible) elements on the UI: On selecting this option, it identifies the locators of the invisible/hidden UI elements.
  3. Identify locators that individually match more than one visible/hidden element on the UI: When you select this option, it identifies the locators that match more than one visible/hidden UI elements.
  4. Identify all of the above: On selecting this option, it finds the locators with all the above-mentioned combinations (valid or invalid, visible or hidden, mapped to 1 or more elements, then this option can be used.
When you use the third option and the fourth option, you will see that QaSCRIBE does a pretty good job at identifying such locators when the test script is recorded but subsequent changes to the AUT can bring in such instances and it helps you bring notice to your Developers. This is one of the Signature features of Worksoft SaaS, as it is impossible to identify such instances with manual testing.

After the Validation type is selected, QaSCRIBE performs a quick check on the AUT and as a result, it displays an emoji icon for the respective locator.

There are four different icons you can possibly see, corresponding to the validation type selected:
  1. If the first validation type is selected (Identify invalid locators that can't individually match any element (visible/hidden) on the UI) then, locators are visually identified by the emoji in red.
  2. If the second validation type is selected (Identify the locators that individually match hidden (invisible) elements on the UI), then, locators are visually identified by the sad emoji in yellow with a blind eye icon, indicating that the same locator which was mapped to a visible element also found hidden elements mapped to it.
  3. If the third validation type is selected (Identify locators that individually match more than one visible/hidden element on the UI) then, locators are visually identified by the sad emoji in yellow with the count of the elements mapped to the locator, indicating that there are multiple elements both hidden and visible mapped to it.
  4. If the fourth validation type is selected (Identify all of the above) then, various emojis mentioned above are displayed on the respective locators.


Feedback and Knowledge Base

(thinking…)