So I recorded my first test, which is to login, nagivate to an entry form, and then work through the prompts until save. About 10 or 15 total steps.
It seems to replay the login stuff and anywhere where I am navigating, entering values in RadTextbox controls or clicking on RadButtons. It even seems to pick up the selection of items in a RadGrid. However when I hit a RadCombobox it stops working.
If it is helpful the RadComboboxes in question use Content Templates to show the options and are loaded via AJAX, one after the other.
I am a complete novice with Test Studio, but very familiar with Telerik's ASP.NET toolset - have spent a couple of hours fussing around and looking through online documentation, but not sure exactly what to try next. I don't know how to insert a WAIT line in the recorded steps, and my initial attempts to write code into the step to select a specific value have not worked...
Any pointers or online resources that address this scenario?
6 Answers, 1 is accepted
However when I hit a RadCombobox it stops working.
Can you give me more details about this... what exactly were you expecting to happen... what actually happened instead?
Sending us the exported Step Failure Details will usually contain most of the information we need to begin diagnosing any test failure problems. Find and click the Export button in that dialog then attach the generated .zip file.
Are there limitations to the complexity/size of a Web Page that can be Tested? Are there any known bugs with IE11?
I am running a fairly new 3rd Gen i7, 8GB RAM, Windows 8.1, etc - would be surprised if there is a problem with my hardware on this one...
Are there limitations to the complexity/size of a Web Page that can be Tested?
No hard limits. Of course the more complex a page is the more memory it will consume. Windows gets upset when it starts to run out of contiguous memory to allocate for objects. Running a 64-bit OS, because it can handle more memory, helps overcome out of memory conditions.
Are there any known bugs with IE11?
None related to recording. We have one for handling a download dialog during playback, but that's unrelated to this problem.
For us to dig deeper into this we'll need a way to repro the problem. Can you assist with this? The best way would be direct access to your application. If that is not possible a Fiddler trace of your application running normally in a browser often works. We can use the trace to simulate your web server for us. Be sure to click Clear Cache and check "Store binaries" and "Decrypt HTTPS traffic" before you start your capture.
Perhaps I should try to record using a different browser?
You certainly can try recording using a different browser. To me that's a workaround, not a fix to the actual problem. Based on your video it appears it may be related to a problem with the Test Studio translators, which are meant to enhance the recording. You can try disabling the RadInput translator. Again I consider this a temporary work around, not a fix.
Since the problem is sort of a "hang" (not a hard crash) I doubt we'll learn anything from our log, but please go ahead and generate one and send it to us just to be sure. I tried to repro the problem using our RadInput demo site, no luck. What we need mostly is a way that we can repro this problem here.