Adding Assertions and Verifications With the Context Menu
Before reading this you might want to read:
Adding Verifications and Asserts With the Context Menu:
QaSCRIBE records all the actions that you perform on the AUT. Apart from the action, you also have to have some assertions and verifications that which are not recorded.
This requires assert and verify commands.
To know more about these commands please refer to Commands for interfacing with the User Interface of your AUT(s).
With QaSCRIBE recording, go to the browser displaying your test application and right-click any element on the page. You will see a context menu showing verify and/or assert commands.
Also, notice that this shows many more commands, along with suggested parameters, for testing your currently selected UI element.
Try a few more UI elements. Try right-clicking an image or a user control like a button or a checkbox. Once you select these other options, the more commonly used ones will show up on the primary context menu.
Assert or Verify
Choosing between “assert” and “verify” comes down to convenience. There’s very little point checking that the first paragraph on the page is the correct one if your test has already failed when checking that the browser is displaying the expected page. If you’re not on the correct page, you’ll probably want to abort your test case so that you can investigate the cause and fix the issue(s) promptly.
On the other hand, you may want to check many attributes of a page without aborting the test case on the first failure as this will allow you to review all failures on the page and take the appropriate action. Effectively an “assert” will fail the test and abort the current test case, whereas a “verify” will fail the test and continue to run the test case.
The best use of this feature is to logically group your test commands, and start each group with an “assert” followed by one or more “verify” test commands.