Web comparison checkpoint
I have downloaded the trial version of TextComplete to assess if it can be used to support our automated regression test needs and other general testing requirements. Our platform is web based ...
Forum Discussion
Hi Allen,
Thank you for your reply. I think I now understand much better what tags are being compared and not being compared depending on the otions selected.
This leaves with a problem that I seem to have two options to avoid my original problem (that the current date and time is present on all of our web pages so all web page checkpoint comparisons fail if entire page is compared):
1. I compare only Image, Link and Input Tags. The problem with this is that there are lots of tags I want to compare that are not one of these three types. If I do not compare these tags it is not a proper test.
2. Compare the entire page and accept that every comparison will fail because of the date/time difference. I was hoping to use this option and then just look at each comparison failure in the log to see if anything else other than the date/time tag had failed in the comparison. However, the web page comparison error log only logs the first web page difference so I will only ever see the date/time difference as it appears at the beginning of the page.
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.
If you have no more suggestions regarding how I can avoid my issue then it seems we will not be able to adopt your product for our rgression testing as it is unable to compare web pages where certain elements always differ (i.e. date and time in my case) and there appears to be no workaround to compare these type of web pages.
Regards
Ray
Thank you for your reply. I think I now understand much better what tags are being compared and not being compared depending on the otions selected.
This leaves with a problem that I seem to have two options to avoid my original problem (that the current date and time is present on all of our web pages so all web page checkpoint comparisons fail if entire page is compared):
1. I compare only Image, Link and Input Tags. The problem with this is that there are lots of tags I want to compare that are not one of these three types. If I do not compare these tags it is not a proper test.
2. Compare the entire page and accept that every comparison will fail because of the date/time difference. I was hoping to use this option and then just look at each comparison failure in the log to see if anything else other than the date/time tag had failed in the comparison. However, the web page comparison error log only logs the first web page difference so I will only ever see the date/time difference as it appears at the beginning of the page.
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.
If you have no more suggestions regarding how I can avoid my issue then it seems we will not be able to adopt your product for our rgression testing as it is unable to compare web pages where certain elements always differ (i.e. date and time in my case) and there appears to be no workaround to compare these type of web pages.
Regards
Ray