Lesson 14 Topic 6 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 6
1. My Project Settings - Test Scripts Design, Build and Maintenance
While working on 'Verify Validity of Locators' and 'Magic Wand' you have seen QaSCRIBE throwing some popovers and ask you to choose certain options. These settings are in 'My Project Settings' if you wish to override the defaults. In this lesson, we will review the list of settings available.
Verify validity of the locators that identify UI elements:
When you have clicked on 'Verify Validity of all locators' you have observed that Worksoft SaaS has shown a popover. And we proceeded by choosing to leave the default option 'all of the above'. Every time you use this feature, if you want Worksoft SaaS to do all validations instead of you have to choose one of them, you can force QaSCRIBE to not show the popover at all thereby reducing the number of clicks you need to perform. Select the second option in the setting 'Perform all the checks when the user clicks on the 'Verify Validity of Locators' icon' for overriding the default.
Magic Wand Application Mode:
When you have used Magic Wand to correct the locators, QaSCRIBE has performed necessary actions like updating existing locator types when they are invalid, pushing the locator used as reference i.e. the magic wand is chosen, adding new locator types when available, etc. This is default behavior. But, if you would like to take individual decisions, you can choose the second option 'Automatically apply based on User Prompts'. When you chose this option and try applying Magic Wand, you will see an additional popover with all available options for updating locators.
There is a third option which disables Magic Wand capabilities in QaSCRIBE. While we don't see why you would choose this option, we would like to caution that you don't choose as this forces you and your team to spend more time updating locators.
Execution contexts for Automatic Magic Wand Application:
There is a third option which disables Magic Wand capabilities in QaSCRIBE. While we don't see why you would choose this option, we would like to caution that you don't choose as this forces you and your team to spend more time updating locators.
Execution contexts for Automatic Magic Wand Application:
This setting allows you to disable 'Magic Wand' feature in QaSCRIBE. While the option is provided, we don't see a reason why you will not choose to use this option. This is one powerful feature in QaSCRIBE that allows for a lot of time be saved while debugging and maintaining the automation
The settings listed below are the options that show up when you choose option 2 in the Settings listed under Seq no. 2 i.e. when Magic Wand is applied QaSCRIBE will show all the below settings for the user to choose. By setting the default ones here and using option 1 in the above setting, you can avoid having to mention these every time.
The settings listed below are the options that show up when you choose option 2 in the Settings listed under Seq no. 2 i.e. when Magic Wand is applied QaSCRIBE will show all the below settings for the user to choose. By setting the default ones here and using option 1 in the above setting, you can avoid having to mention these every time.
If Magic Wand is enabled for auto-application within Test Instruction pane, specify the 'default' option for 'updates' to previously existing locators.
Four options are available under this setting with the first one (Automatically update only those locators that failed a validity check) being system default. In some instances, an AUT may have different locators on different browsers and devices. This could have been done for any number of reasons. To account for such idiosyncrasies in AUT behavior, QaSCRIBE provides you options to not update some are all of the locators based on the other options you choose. While the second one only updates locators that are after, the locator for which the magic wand is used the third option will only update the locators if they are identifying a different element in the AUT. You may also choose not to update any of the other locators.
If Magic Wand is enabled for auto-application within Test Instruction pane, specify the 'default' option for 'deleting & reordering' of invalid locators
The default option chosen by QaSCRIBE reorders locators such that all the valid ones are top and invalid ones pushed to the bottom. But you can override the option by choosing to delete all invalid locators. This keeps your test script clean. Also, you can choose not to change the order OR do nothing.
If Magic Wand is enabled for auto-application within Test Instruction pane, specify the 'default' option for 'addition' of new locators
The default option allows for new locator types to be added if any found. And they are added at the bottom of the current list. You can also choose not to add new locator types found if you don't want to use them. For example, you may not want to record locator type 'id' because they are dynamically generated and every time there is a deployment to the env, they tend to change.
Magic Wand - Option for Automatic Updates to Locators of Other Test Instructions within Test Script(s) when user clicks 'Save' at the 'Locator' level within the Test Instruction edit/add pane.
Four options are available under this setting with the first one (Automatically update only those locators that failed a validity check) being system default. In some instances, an AUT may have different locators on different browsers and devices. This could have been done for any number of reasons. To account for such idiosyncrasies in AUT behavior, QaSCRIBE provides you options to not update some are all of the locators based on the other options you choose. While the second one only updates locators that are after, the locator for which the magic wand is used the third option will only update the locators if they are identifying a different element in the AUT. You may also choose not to update any of the other locators.
If Magic Wand is enabled for auto-application within Test Instruction pane, specify the 'default' option for 'deleting & reordering' of invalid locators
The default option chosen by QaSCRIBE reorders locators such that all the valid ones are top and invalid ones pushed to the bottom. But you can override the option by choosing to delete all invalid locators. This keeps your test script clean. Also, you can choose not to change the order OR do nothing.
If Magic Wand is enabled for auto-application within Test Instruction pane, specify the 'default' option for 'addition' of new locators
The default option allows for new locator types to be added if any found. And they are added at the bottom of the current list. You can also choose not to add new locator types found if you don't want to use them. For example, you may not want to record locator type 'id' because they are dynamically generated and every time there is a deployment to the env, they tend to change.
Magic Wand - Option for Automatic Updates to Locators of Other Test Instructions within Test Script(s) when user clicks 'Save' at the 'Locator' level within the Test Instruction edit/add pane.
Magic Wand - Option for Automatic Updates to Locators of Other Test Instructions within Test Script(s) when user clicks 'Save' at a 'Test Instruction' level within the Test Instruction edit/add pane.
Magic Wand - Option for Automatic Updates to Locators of Other Test Instructions within Test Script(s) when user clicks 'Save' at a 'Test Script' level.
The three settings above are for the same functionality with the trigger being different. The functionality is to allow QaSCRIBE to update other instructions in the test script if it founds that the updated locator is available in one or more of the instructions. You can opt-out of this functionality but it is recommended that you don't do that as it can increase manual effort or cause your test to fail. The default setting forces QaSCRIBE to show impacted test instructions and let the user review before submitting the change. But if you are comfortable with the logic applied by QaSCRIBE, maybe after a few iterations, you can choose to let QaSCRIBE make these changes silently.
Given that you can save a single locator or save single instruction or save test script on a whole, three different settings are provided so that you can choose to have different behaviors for every trigger.