Skip to content

Lesson 11 Topic 2 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 11 :: Topic 2


1. Using Assert and Verify Commands in Worksoft SaaS
As you know, QaSCRIBE records all of the actions that you perform on the AUT. In some cases, you may need to add additional validations like assertions and verifications that are not recorded.

Assert and Verify are commands which check to see if the state of the application corresponds to the expectations of the test. Choosing between “assert” and “verify” comes down to the criticality of your validation. 

For Example: If your test did not land on the correct page, you’ll probably want to abort it, so that you can investigate the cause and fix the issue(s) promptly. In this case, adding an “assert” command will meet your requirements, as it fails the validation and aborts the currently executing test. whereas, adding a “verify” command will fail the validation, however, it will still move ahead and continue the currently executing test. In most cases, you would be using 'verify' commands to do specific application validations as mandated by the test case.


2. Show Context Menu
There is a Context menu in Worksoft SaaS that helps add additional commands like assert, verify and many more commands along with suggested parameters that helps reduce your manual efforts.

It can be accessed while recording the test case when you right-click on a particular element in the AUT.

The Context menu displays the list of commands available for the selected element on the page. It also displays the number of locators available for a particular element or the entire page, if it is enabled in the Project Settings.

It is easy to add the commands using the Context Menu, all you have to do is decide which command you need from the options on the menu and select it and it will be added to the instructions in the Test Script.


3. Don't record instructions with 'Open' and related commands
While recording the instructions, there is an option called 'Don't record instructions with 'Open' and related commands'. Generally, QaSCRIBE records the Open command as the first instruction, to make it easy to record the WebURL's. 

However, if your instructions don't need to record the WebURL or if opening the WebURL is not applicable in your tests, then you can use this option.



Feedback and Knowledge Base