This is a migrated thread and some comments may be shown as answers.

RadSplitter test not working

6 Answers 55 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
Bruce Hochstetler
Top achievements
Rank 2
Bruce Hochstetler asked on 23 Mar 2009, 04:42 PM
Hi,

I have a splitter with two panes, top/bottom, layed out horizontally. I've tried simply clicking on it... event=Click 'dev_RAD_SPLITTE__RadSplitBar1', then I try to very that the RadSplitter is collapsed - fails here. So then I tried invoking an event 'OnClick' then verifying the splitter was collapsed - fails also. So what's the trick?

Thanks,
Bruce

6 Answers, 1 is accepted

Sort by
0
Konstantin
Top achievements
Rank 1
answered on 23 Mar 2009, 06:17 PM
Hi Bruce,

Please invoke the OnMouseDown event over the split bar to expand/collapse the splitter panes. You should get "RadSplitBar" command recorded. The OnMouseDown is required by the RadSplitter controls.

-Konstantin
0
Bruce Hochstetler
Top achievements
Rank 2
answered on 23 Mar 2009, 06:53 PM
Hi Konstantin,

Ok after the mouse down, then what? I'm getting 'Invoke OnMouseDown event on td_RadSplitBar1'. I've tried following that with a 'Tab: click action', then verify 'RadSplitBar: is collapsed' - which fails.

Thanks,
Bruce
0
Konstantin
Top achievements
Rank 1
answered on 23 Mar 2009, 10:28 PM
Hmm, no, you should get: RadSplitBar: Command -> 'Expand' instead. Otherwise the action has been handled by the base translator and not the RadSplitter ones.

Let me ask you a couple of questions that will help us investigate the issue you get:

1. Is the application under test updated with the Q1 2009 release of RadControls for ASP.NET (AJAX)?
2. Do you work with the official release of WebUI Test Studio or the latest internal build (we've uploaded one containing bug fixes last week).
3. Can you check if you can record the expand/collapse action on a vertical split bar as well? If you haven't prepared app, you can use the RadSplitter live demos.

As soon as you get the expected SplitBar Collapse/Expand action handled, you can add SplitBar is collapsed/expanded verification to complete the test case.

You may also add pause after the test action execution to make sure the issue is with the recorded action and not the following verification. Just select the recorded step, open the properties in the property grid, locate the 'Pause' and select 'After'. The execution will stop after the action step so that you can see if the action succeeded or failed.

Based on your feedback we will investigate the issue and get back to you with our findings. Thank you!

-Konstantin
0
Konstantin Petkov
Telerik team
answered on 24 Mar 2009, 01:44 PM
Hello Bruce,

We isolated a problem with the split bar expand/collapse and managed to fix it. You can download the latest internal build and give it a go.

Note you need to execute the on mouse down event on the expand/collapse handler of the split bar available in the middle of the split bar element. I've recorded a small video to demonstrate the splitbar collapse action. I've used this live demo.

Hope this helps!

Kind regards,
Konstantin Petkov
the Telerik team

Check out Telerik Trainer , the state of the art learning tool for Telerik products.
0
Bruce Hochstetler
Top achievements
Rank 2
answered on 24 Mar 2009, 08:37 PM
Hi Konstantin,

It seems the latest internal build (2009.1.324) solved several problems. Prior to downloading this release though, I was finally able to get the MouseDown to recognize the RadSplitBar. When I did get it to work it was issuing an 'Expand' when it should have been 'Collapse'. I was able to go into the properties of that command and change the action from Expand to Collapse. Very cool! After installing the latest build, the MouseDown is found immediately and has the correct action.

Thanks,
Bruce
0
Konstantin Petkov
Telerik team
answered on 25 Mar 2009, 08:33 AM
Hello Bruce,

I'm glad those issues you were experiencing are now resolved.

Yes, indeed. We try to expose as many properties as needed for each action and verification so that the test steps are easily customizable. That's a great feature of the environment and I'm sure people would love it!

This is especially helpful when you have to update the tests after application under test change (like data change for example) -- upon failure you get the new value and just update the property in the property grid. I doubt it could be easier.

Let us know if you need further assistance.

Regards,
Konstantin Petkov
the Telerik team

Check out Telerik Trainer , the state of the art learning tool for Telerik products.
Tags
General Discussions
Asked by
Bruce Hochstetler
Top achievements
Rank 2
Answers by
Konstantin
Top achievements
Rank 1
Bruce Hochstetler
Top achievements
Rank 2
Konstantin Petkov
Telerik team
Share this question
or