Jump to content


content comparison in testing


  • Please log in to reply
2 replies to this topic

#1 Guest_arpoodle_*

Guest_arpoodle_*
  • Guests

Posted 03 July 2008 - 02:32 PM

I'm currently evaluating WAPT, and would like to know if it's possible to verify the expected output of a page?
One of the issues we occasionally encounter is due to an issue in the load balancer and session persistance, where the repeat requests aren't sent to the same server, and so some of the content isn't rendered properly, as it doesn't have the session information to determine the relevant content.

Is there a way to check this content within the test parameters, as the page still loads "correctly" as far as the http status codes are concerned.

Thanks

a

#2 Guest_Paul Deen_*

Guest_Paul Deen_*
  • Guests

Posted 04 July 2008 - 11:17 AM

QUOTE (arpoodle @ Jul 3 2008, 03:32 PM) <{POST_SNAPBACK}>
Is there a way to check this content within the test parameters, as the page still loads "correctly" as far as the http status codes are concerned.


Sort of. What you can do is check for text on the page you're expecting. So if you purchased an order, you could make sure the response you get back from the server contains the literal text "Order Successful".

Personally I think this is somewhere that WAPT could be improved, for example, check the destination of 302 redirects would be nice. Someone else suggested have regular expression support there too. As far as I'm aware there is currently no way of doing these things at the moment.

Even so, I think the literal text will help you a lot

Cheers,

Paul

#3 Guest_arpoodle_*

Guest_arpoodle_*
  • Guests

Posted 07 July 2008 - 11:07 AM

QUOTE (Paul Deen @ Jul 4 2008, 12:17 PM) <{POST_SNAPBACK}>
Sort of. What you can do is check for text on the page you're expecting. So if you purchased an order, you could make sure the response you get back from the server contains the literal text "Order Successful".



Any idea if that works for the HTML source, or just the rendered textual content?

One of the issues I have is that some CSS isnt being loaded properly due to this flaky session persistance, so the text is there, but it's all formatted and coloured wrongly. Being able to check the source code for text matching Would solve my problem.

thanks

a




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users