A checkpoint verifies that expected information is displayed in a Web Application while the test is running. This page explains how to "translate" the checkpoint terminology used in literature and certain web testing programs (e. g. QTP ) into iMacros commands that perform the same task.
A text checkpoint checks that a text string is displayed in the appropriate place on a web application.
Any TAG command is automatically a keyword assert command. So to add a text checkpoint, simply click on the text that you want to check.
TAG POS=1 TYPE=LI ATTR=TXT:Comprehensive<SP>CRM<SP>capabilities
This TAG line is now a text checkpoint! If the text is not found, iMacros will report an error. If you want to report an error if a text is found, use FAIL_IF_FOUND:
TAG POS=1 TYPE=LI ATTR=TXT:Comprehensive<SP>CRM<SP>capabilities CONTENT=EVENT:FAIL_IF_FOUND
An image checkpoint checks the values of an image on a web application.
Web Table Checkpoint
A table checkpoint checks information within a table on a web application. iMacros allows you to extract a complete table and then verify its content via the Scripting Interface. You can also adress specific table elements with the Relative Extraction / Relative TAG command feature and verify them directly in the macro.
An XML checkpoint checks the contents of individual XML data files or XML documents that are part of your Web application.
iMacros can save XML documents and/or return the content of an XML to the calling script. You can use the standard XML functions available in all modern scripting languages to test the XML content in details (e. g. use Microsoft.XMLDOM in VBS).
iMacros can monitor the page load and rendering time with the STOPWATCH command.
A database checkpoint checks the contents of databases accessed by your web site. iMacros can interface with databases via its Scripting Interface. You can verify database content directly in the scripting language that you use.
A page checkpoint checks the characteristics of a web page.