unable to work with Outlook email body
Posted: Mon Sep 22, 2014 2:29 pm
I've posted to the forum on Thursday, Sept 18 but have yet to receive a solution, so now I'm takng advantage of our support package. the forum thread is http://www.ranorex.com/forum/wrong-flav ... t6047.html
Essentially, we have a project which tests our add in for MS Outlook. UP to Sept 18, Ranorex was recognizing the email body as a WordDoc, and we were able to enter and read text within that. On Thursday, this changed somehow, and now Ranorex recognizes the object only as an element. We can instrument it as GDI but that doesn't help.... we only get a collection of RawText objects that way.
I have also noticed that one of our 2 development machines is reporting the Caps attribute as uiautomation, and the other as accessible. We are working from the same SVN source, with the same versions of Ranorex, Outlook and Windows.
Other differences also occur besides the WordDoc issue. On the machine that displays "Caps: accessible", all objects are recognized as elements and can't be accessed.
This whole situation is very unfortunate, as we were scheduled to demo our work with the Outlook Addin to the company this past Friday. The demo did not go well.... we had to show past results and state that we're waiting for feedback from the Ranorex support team in order to address an issue which has recently blocked the tests from running....
Essentially, we have a project which tests our add in for MS Outlook. UP to Sept 18, Ranorex was recognizing the email body as a WordDoc, and we were able to enter and read text within that. On Thursday, this changed somehow, and now Ranorex recognizes the object only as an element. We can instrument it as GDI but that doesn't help.... we only get a collection of RawText objects that way.
I have also noticed that one of our 2 development machines is reporting the Caps attribute as uiautomation, and the other as accessible. We are working from the same SVN source, with the same versions of Ranorex, Outlook and Windows.
Other differences also occur besides the WordDoc issue. On the machine that displays "Caps: accessible", all objects are recognized as elements and can't be accessed.
This whole situation is very unfortunate, as we were scheduled to demo our work with the Outlook Addin to the company this past Friday. The demo did not go well.... we had to show past results and state that we're waiting for feedback from the Ranorex support team in order to address an issue which has recently blocked the tests from running....