I am working on Trial version of Test Studio QA/Develop editions past 2 days. While recording operations on silverlight applications, i receive many strange errors. Please find attached error screenshots.
Screenshot1: "Memory Error.JPG"
Description: While recording steps in silverlight application using QA/Developer editions, i recieve this error.
Screenshot 2: "IE Crash.JPG"
Description: While recording steps in silverlight application using QA/Developer editions, some times we recieve this error. This error occurs on every machine (2 machines).
Screenshot 3: "Browser-Error.JPG"
Description: This error occurs very often. When we are recording the steps on silverlight application, then this error occurs and no recording is possible thenafter. We have to close the browser and restart recording process again. This error occurs on every machine (2 machines).
Screenshot 4: "Recorder Crash.JPG"
Description: Steps we followed to produce this error are like this-
Step 1: We already our silverlight application open in Browser. Now we click on dropdown button 'Recording ' and select option 'My application'(not the option 'Launch New recording Browser') from our QA/Developer edition.
Step 2: Now we perform some operation in our silverlight application. It throws error that recorder needs to be connected with the silverlight application. Please reload your application.
Step 3: If we still continue to record the steps ignoring the earlier error then it throws error as mentioned in 'Recorder Crash.JPG'.
Let us know if we are following wrong steps @Step 2. Application is already open then why tool is asking to reload the page?
Screenshot 5: "Test Runner Error.JPG"
Description: Couples of time when we tried to playback the recorded steps using Developer editions then it throws this error. If we close the error box mentioned in the screenshot and again try to playback, then it does not throw error and playback works as expected successfully
Kindly look in to these errors and give your feedback. Also let us know if have followed any wrong steps as we are using these past 2 days only. However we do have worked on other commercial Automation tools a lot.
Environment Details:
O/S : Windows XP
Browser: IE8
3 Answers, 1 is accepted
Screenshots 1, 2, 3, 5 all point to some sort of a memory problem. This could be:
1) A bug in the Silverlight application causing the error
2) A bad memory chip (though less likely since two machines are doing the same thing) - Test Studio is heavy on memory use that can cause bad memory problems to show up more than when using other applications.
3) Insufficient memory - If you have less than 1GB of memory installed we could just be running out of memory and running into problems as a result
4) A bug in Test Studio such that it's not correctly handling your Silverlight application. If this is the case we'll need a way of reproducing the problem locally in our development environment
Screenshot 4 sounds expected to me. The recorder must connect to the browser window prior to the browser loading your Silverlight application into it. This is a known limitation of Test Studio.
Cody
the Telerik team
Rank 1
Thanks for your reply,
we increased space on C drive and now we are not getting errors mentioned in Screenshots 1, 2, 3, 5.
But i have one query regarding the known limitation of Test Studio. Please refer the following scenario
Let say there is a one user registration form which contents two page. If i want to store 1 object of second page, then due to limitation of webstudio, i guess i have to follow steps
1. Launch Browser using tool
2. Open silverlight application
3. Fill up all mandatory values in first page of Registration and go to second page
4. Add the required object of the second page in the repository.
Kindly let me know is there any other shortcut? I am working on other commercial tool where we can directly add object from the second page without following above mentioned steps.
I am sorry but the 4 step sequence you describe is required by the Test Studio Silverlight recorder. Our Silverlight recording only works if our recording window is already open at the time you first navigate to your Silverlight application. That does mean you must go through your first page with the recorder active in order to get to your second page.
I have logged feature request 114714 for this issue.
Despite this minor limitation we believe our Silverlight recording is still the best on the market:
- We have a very rich set of actions you can perform
- We have a very rich verification capabilitities
- We include logic blocks (IF ELSE, Loops)
- We support a code behind model which you can use for very advanced Silverlight automation that are standard steps cannot do
- We support Silverlight out of browser recording and testing mode
I'll be happy to answer any other questions about our automation abilities against Silverlight applications.
Cody
the Telerik team