Partial match for WPF nodes doesn't work properly

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 11 Apr 2014 08:20 by ADMIN

ADMIN

Boyan Boev

Created on: 17 Oct 2013 07:15

Type: Bug Report

Partial match for WPF nodes doesn't work properly

I renamed my node's friendly name and caption to check for partial match (~SSR-Viewer) and then recorded a few steps for which the elements were added under the partial match node name. 

After that I launched a new recorder and the newly recorded elements are coming under a new node with the full name, even the elements that are already under partial window name are created again under full window name.

6 comments

ADMIN

Daniel Djambov

Posted on: 11 Apr 2014 08:19

Telerik: The issue with merging nodes is fixed in our intenral releases from March and official release in April.

Anju

Posted on: 06 Mar 2014 23:28

Thanks Daniel. That was clear & really helpful. I think I was not clear enough in explaining the issue :) My problem in short is that 'the merging of the newly recorded window (along with its elements) with the already existing partial match window is not happening'. I have a support ticket raised on this with my test project depicting the above mentioned behavior- (Support ID: 750314). It would be great if you could have look.

ADMIN

Daniel Djambov

Posted on: 19 Nov 2013 14:19

Hi again and sorry for the late response. I will try to clear the confusion - I checked again your case and I think that your are mixing up the Recording behavior with Execution behavior. What you have described in the description of this feedback is that during recording, if you use partial match for a WPF window and then start recording again it will not record the new elements in the already existing partial title window, but will create a new window and will record new elements along with existing under the partial match window again. This is what I was referring as Designed behavior - it has been working like this in previous 2012.2 versions of the product also as well in the new 2013 R1 versions. This doesn't mean that the execution will stop working however, because after recording elements under the new window in this case, if you change the windows caption search criteria to use partial match and refresh elements tree, we will merge the newly recorded window (along with its elements) with the already existing partial match window and you will have 1 window with partial match where execution will work and find the elements in it properly. This is the point of the partial match for the window caption - to identify dynamic changes in windows captions during runtime Execution and properly locate elements in them. Hope I made it more clear this time. Please let us know if there is still something that you cannot solve with the existing behavior so we can address it.

Anju

Posted on: 31 Oct 2013 22:51

I am sorry but din't get why Daniel was talking it as expected behavior. Then what is the use of partial window match option? 

"How to Indicate a Partial Match for WPF Window Name" This is a question given in the TestStudio online documentation. Please read the answer to this and it will tell you that the current behaviour is not the expected behaviour. 

Moreover, this is not a project specific requirement. And the TestStudio version :2012_2_1420 handles the Partial window match perfectly well and the tests designed with one window name gets executed with another window name (with Partial Window Match).

If you still have queries, please let me know, I can give a demo on how it used to work in the previous version.

In short, this is not a new project specific feature request nor is it an expected behaviour.

(PS:-I am talking about  a WPF application)

ADMIN

Konstantin Petkov

Posted on: 31 Oct 2013 15:43

The window node name can be used in a coded step. If the user upgrades with this change in and Element Explorer nodes get merged, that can turn into a compilation error.

Technically speaking we can probably implement that request as a per-project option. One can check it manually if wants to have those nodes merged in the Elements Explorer taking the risk to break their project.

Feedback is welcome.

ADMIN

Daniel Djambov

Posted on: 31 Oct 2013 15:02

Telerik: This is the currently expected behavior to not merge wpf windows names when you use "~", because each time a new element is created it uses the default page identification logic and from elements point of view this is a new page and new element. Implementing requested behavior is a breaking change and will break other clients projects. We will consider it for future considerations.