sitefinitysteve
Top achievements
Rank 2
Iron
Veteran
Rank 2
Iron
Veteran
sitefinitysteve
asked on 09 Apr 2013, 12:40 PM
...90% of the time my tests are just superficial "does a page work", or "this url should not work"
Browse to page, make sure there's no YSOD, done. However the actual test has to be some "hacky" thing like looking for an element which wouldnt exist on a YSOD page.
Could we add a new test step that just "automatically" looks for a crash page...So like in my test project I could give TS my error page Urls, and then I would add this new step in to say
- Browse to Page
- Check for 500
or
- Check for 404
or
- Check for Error
Then internally that magic test step would determine if the resulting url is one of my error pages and\or a YSOD. This would also let me fire up a series of PURPOSELY bad urls to throw at it to hope they 404 or 500.
Browse to page, make sure there's no YSOD, done. However the actual test has to be some "hacky" thing like looking for an element which wouldnt exist on a YSOD page.
Could we add a new test step that just "automatically" looks for a crash page...So like in my test project I could give TS my error page Urls, and then I would add this new step in to say
- Browse to Page
- Check for 500
or
- Check for 404
or
- Check for Error
Then internally that magic test step would determine if the resulting url is one of my error pages and\or a YSOD. This would also let me fire up a series of PURPOSELY bad urls to throw at it to hope they 404 or 500.
3 Answers, 1 is accepted
0
Hi Steve,
Boyan Boev
the Telerik team
Test Studio cannot constantly monitor for HTTP errors during the functional test.
Since YSOD screens are regular web pages with a DOM tree you can use a standard verification step to verify them where you expect to appear (i.e. if the page contains HTTP error 404).
I recorded a short video for a demonstration.
Hope this helps.
Boyan Boev
the Telerik team
Quickly become an expert in Test Studio, check out our new training sessions!
Test Studio Trainings
Test Studio Trainings
0
sitefinitysteve
Top achievements
Rank 2
Iron
Veteran
Rank 2
Iron
Veteran
answered on 12 Apr 2013, 12:20 PM
Not asking to constantly monitor, just asking for a test step that can automatically detect that a page has crashed instead of the 2 minute authored test and 40 click method you just showed :)
Make me a PITS issue if you could please...I'm sure I'm not the only one who would want this
Make me a PITS issue if you could please...I'm sure I'm not the only one who would want this
0
Hi Steve,
Boyan Boev
the Telerik team
I have filed your feature request, which you can follow in our Feedback Portal.
We appreciate your feedback, which we rely on to improve our product.
Boyan Boev
the Telerik team
Quickly become an expert in Test Studio, check out our new training sessions!
Test Studio Trainings
Test Studio Trainings