assertText, verifyText - Selenium IDE
assertText (target, pattern) , verifyText (locator, text)- Selenium IDE command
assertText and verifyText both get the text of an element (as defined by the locator) and check if it meets the requirement of the pattern. This works for any element that contains text.
Assert and verify commands are both useful for verifying condition match or not. The difference is that verify command will verify the condition and if it does not match, it will only show an error message in log area and the macro continues to run. With the assert command, if the condition does not match then it will stop remaining macro execution in the selenium IDE software testing tools.
assertText and verifyText Example
In this short example, we check for the presence of the texts "Welcome" and "Free Web Automation". If "Welcome" is missing, the macro stops since we used assert.
|verifyText||//*[@id="content"]/div/div/h2||Free Web Automation|
Difference between verifyText and verifyTextPresent in Selenium
The "verifyTextPresent" command is not for storing value of any target element, but could be used to verify that specified target text is available anywhere on the page or not. The UI.Vision RPA IDE does not support verifyTextPresent (and assertTextPresent) because we want to help reduce the zoo of previous IDE commands. In the modern UI.Vision RPA IDE verifyTextPresent can be easily recreated with storeText plus if.
On the storeTextPresent page you find an example that "simulates" verifyTextPresent by using storeText and then checks if the extracted text is correct. If not, it throws an error. The simulation of verifyTextPresent is actually better than the original: The old verifyTextPresent checks for the presence of the text in the entire page. This can often lead to false positives, and is not generally advised.
Related Demo Macros
DemoStoreEval uses many Asserts
The ready-to-import-and-run source code of all demo macros can be found in the Github repository testmacros folder.
Anything wrong or missing on this page? Suggestions?
...then please contact us.