This question is locked. New answers and comments are not allowed.
I am trying to configure WebUI Test Studio to verify that I have a PDF document loaded in an IE Window using the Adobe PDF Plugin. The problem is that the WebUI Test Studio never seems to 'get' the update, so the DOM explorer never refreshes. The test will run, and navigate to the correct PDF (which is actually being generated from SSRS via the rs:Format=PDF), but then the test just hangs and times out, even though the PDF document is already loaded.
Ideas?
Ideas?
3 Answers, 1 is accepted
0
Hello Mitch,
Thanks for the post and the question. Unfortunately, WebUI will not be able to do any complex verifications or automation on the PDF page that it can for Html, Ajax, Rad, or Silverlight controls as there are no translators for PDF.
You should still be able to run recorded test step actions on the playback browser, such as Navigate to another page, Foward and Backward after loading the PDF page.
Please post back if such steps are not working after loading the page, it may be just that the next test step recorded after the PDF page navigation is expecting a certain page and the browser is not on that page yet.
Regards,
Nelson
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Thanks for the post and the question. Unfortunately, WebUI will not be able to do any complex verifications or automation on the PDF page that it can for Html, Ajax, Rad, or Silverlight controls as there are no translators for PDF.
You should still be able to run recorded test step actions on the playback browser, such as Navigate to another page, Foward and Backward after loading the PDF page.
Please post back if such steps are not working after loading the page, it may be just that the next test step recorded after the PDF page navigation is expecting a certain page and the browser is not on that page yet.
Regards,
Nelson
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
0
SuperXRAY
Top achievements
Rank 2
Rank 2
answered on 25 Feb 2010, 06:49 PM
That is true that it will eventually timeout and continue to the next step, but then it's not really testing the PDF is loaded, which is a key part in this project. This functionality does exist in a competitor's product, I just don't like the competitor. :)
If it's not available, I understand. Just know that I hate having to use a competitor's product. Telerik rules in my opinion, and I'd like to it keep as one of the main tools in our arsenal.
If it's not available, I understand. Just know that I hate having to use a competitor's product. Telerik rules in my opinion, and I'd like to it keep as one of the main tools in our arsenal.
0
Hi again Mitch,
Thanks for the compliments towards Telerik, it's appreciated. Again, unfortunately there is not a way to currently do complex automation or verification on a PDF opened in browser using WebUI.
The closest thing right now is to have a custom coded step that verifies the URL or Title of the browser when the PDF is launched like this:
Best wishes,
Nelson
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Thanks for the compliments towards Telerik, it's appreciated. Again, unfortunately there is not a way to currently do complex automation or verification on a PDF opened in browser using WebUI.
The closest thing right now is to have a custom coded step that verifies the URL or Title of the browser when the PDF is launched like this:
[CodedStep("Verifiy Title and URL")] public void MyCustomStep() { Assert.AreEqual(ActiveBrowser.Url, "http://ExpectedURL.pdf",true); // Or Assert.IsTrue(ActiveBrowser.Window.Caption.Contains("PDFBrowser Caption.pdf")); }Best wishes,
Nelson
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.