Hi Ray,
As a possible workaround, I can suggest that you save the HTML code of the needed page (the outerHTML property of the Page.HTML object) to a text file instead of using the Web Comparison Checkpoint feature. When executing a test, save the actual HTML code of the page to another file and compare these files by using an external comparing tool (for example, WinMerge).
You can get the HTML code of a page in the following way:
var htmlCode = Sys.Process("IEXPLORE").Page("*").Application.Document.getElementsByTagName("HTML")[0].outerHTML;
Log.Message("HTML code", htmlCode);
| I see that for my optiin 2. that other users have requested that a web page comparison does not stop on the first error (e.g forum post by Pakinam Boghdady named 'About Web Comaprision Checkpoints ') so perhaps you will add this feature in the future |
We have such a suggestion in our database, and your request has increased its rating.