Hi, first time poster here.
Sorry for the abstract title, it's just that I'm experiencing various issues with Test Studio and I thought I'd keep them all in one thread.
Is that okay or should I make separate threads for each issue?
5 Answers, 1 is accepted
Okay, I'll be posting here. (sorry for the crappy paint skills and/or inability to explain my problems in technical terms)
I have been assigned to record tests for some hospital records we're working on. This is one of the issues that come up.
In the image there's a date picker. When you click the little clock, the time picker opens, which has hours and minutes. If I click on the hours, a more specific picker opens with 24 selections and alternatively the same thing happens for the minutes. Now, I recorder myself setting the time using those pickers. The first PickSpan playbacks normally, though the playback gets stuck on the second one.
Note that it does not always get stuck (I've re-recorded this many times, in one playback it passes, but gets stuck on another date picker). Simulating a real click does not help.
Thanks in advance for your replies.
Let me address this question first:
Is that okay or should I make separate threads for each issue?
Generally we prefer unrelated technical problems on separate threads or support tickets. That way we can more easily track what is resolved, how it was resolved, and what isn't resolved yet. A quick list of questions are fine to group together. Also technical problems that are very closely related are fine to group together.
Moving on, let's tackle your date/time picker issue. From a very high level, my first reaction is don't try to automate such UI controls. Automating these are very tricky, time consuming and brittle. You usually end up spending considerable time maintaining a test like this. Most Date/Time pickers will populate an input field once the selection has been made. So instead I recommend recording a step that directly types the date/time into an input field. If your input field is set to ReadOnly i.e. you cannot type into it, I recorded this video how you can set text on such a field:
http://www.screencast.com/t/xuKBBFKoS
Let's work the problem from this angle instead of trying to solve the problem of automating the date/time picker.
Regards,
Cody
Telerik
Hello Cody,
That doesn't really answer my question. I want to know why this happens. There are 2 date pickers, they are the same, so why isn't the record/playback functionality the same for them? Why does one playback normally and the other is screwed up?
I need to auto-test every element, because in the end these tests will be put into prod stage. Would editing the test in code help?
Since the time picker automatically sets the current time, the test wouldn't pass, because the time had changed.
I just made it so the picker is identified by its class name and not by value.
This was kind of a no-brainer, to be honest. Thanks again, Cody. (also, really supportive answers as I've read in the other threads, good job :)
Good detective work on your part! I'm glad you came up with a workable solution.
Regards,
Cody
Telerik