Hi,
I have a WPF application page where there are checkboxes which when are checked, the corresponding Radtileitems are displayed. When I add Quicktasks on visibility(element visible and collapsed) , the name of the RadTileItem get's changed to some other tile item.
I have added few example scenarios for your reference. please find the attachment for the same.
Steps 48-51 : Done for Output Alarm checkbox and tile item
Steps 52-55 : Done for Output REB checkbox and tile item (which comes right)
Steps 56-59 : Done for Input CEB checkbox and tile item
Please see the test step description to understand more about what the issue is about.
I want to check that when the checkbox is checked, the tile item is visible, maximise and check, minimise and check, uncheck and verify that the corresponding tile item visibility is collapsed.I have added snap shots of the issue. Please have a look on the same and help me in resolving this confusion.
Thanks & Regards,
Anju
I have a WPF application page where there are checkboxes which when are checked, the corresponding Radtileitems are displayed. When I add Quicktasks on visibility(element visible and collapsed) , the name of the RadTileItem get's changed to some other tile item.
I have added few example scenarios for your reference. please find the attachment for the same.
Steps 48-51 : Done for Output Alarm checkbox and tile item
Steps 52-55 : Done for Output REB checkbox and tile item (which comes right)
Steps 56-59 : Done for Input CEB checkbox and tile item
Please see the test step description to understand more about what the issue is about.
I want to check that when the checkbox is checked, the tile item is visible, maximise and check, minimise and check, uncheck and verify that the corresponding tile item visibility is collapsed.I have added snap shots of the issue. Please have a look on the same and help me in resolving this confusion.
Thanks & Regards,
Anju
1 Answer, 1 is accepted
0
Hi Anju,
The only time I've seen the behavior you're describing is when an element already exists with the same Find Logic, but with a different name. Typically if elements are truly duplicates (on the same page, with the same find attributes) Test Studio will not add the new element as a duplicate. It will record the new test step and reference the already existing element.
In order to investigate what is causing the issue we need to be able to reproduce it locally in our source code debugging environment. Please send us a copy of your WPF app or ask you developers to put together a small sample WPF app that has these controls and send it to us(in a .zip file). Keep in mind that we are communicating in a forum thread which is public and if you are willing to provide any sensitive information you should open a support ticket where all the information remains private and confidential.
Regards,
Plamen
Telerik
The only time I've seen the behavior you're describing is when an element already exists with the same Find Logic, but with a different name. Typically if elements are truly duplicates (on the same page, with the same find attributes) Test Studio will not add the new element as a duplicate. It will record the new test step and reference the already existing element.
In order to investigate what is causing the issue we need to be able to reproduce it locally in our source code debugging environment. Please send us a copy of your WPF app or ask you developers to put together a small sample WPF app that has these controls and send it to us(in a .zip file). Keep in mind that we are communicating in a forum thread which is public and if you are willing to provide any sensitive information you should open a support ticket where all the information remains private and confidential.
Regards,
Plamen
Telerik
Free summer webinars on advanced web automation tactics hosted by Jim Holmes & Adam Goucher.
Reserve your seat today!
Reserve your seat today!