Completed
Last Updated: 18 Sep 2017 12:07 by ADMIN
Jan
Created on: 03 Mar 2017 13:33
Type: Bug Report
1
friendly element name not used in step description
Steps to reproduce:
1. Start recording
2. Highlight an element on a page and from quickstep menu select "Add to elements..."
3. Change to the "Element friendly name" dialog (BTW: In nearly all cases the menu appears in the background and you have to know to switch to it - user unfriendly, display it in front)
4. Set name
5. Add a step for the element (e.g. verify that text is something)
Result: 
* In the element explorer is friendly name
* In the step properties (Primary Target) is friendly name
* In the step description is some generated name (e.g. Verify 'TextContent' 'Contains' 'Sign in' on 'IdSSpan').  Where 'IdSSpan' is some generated name not used anywhere and 'SignInText' is friendly name. 
* When I try to reset name, the generated name is stuck. The only way to fix it is to choose again the same element using primary target in step properties.

Expected result:
The name in the step should be friendly name. It makes it pretty hard to discern if I added another element to the page or if an already existing one was used.

I have seen several feedbacks with similar/same problems, but they had comments that it was fixed long time ago so I am submiting a new one.
8 comments
ADMIN
Ivaylo
Posted on: 18 Sep 2017 12:07
This behavior has been fixed and will be included in the upcoming Test Studio release. Thank you for your patience and understanding.
Dean
Posted on: 29 Aug 2017 04:55
I am also having the same problem.

I record a test.
I give the elements friendly names say F1.
I record another test that utilises the same element.
Click on the test step and the element is named Sst in the test Step, but the highlighted element on the left side is F1, I have to rename element F1 for the test step to adopt the F1 element name. 

Thong
Posted on: 09 Aug 2017 12:25
I have the same problem as Jan. When can we expect a fix?
ADMIN
Ivaylo
Posted on: 28 Mar 2017 07:55
Hello Jan,

Thank you for your clarification. A bug has been added internally. You can follow this feedback item for the progress.

Thank you for your patience and cooperation.
Jan
Posted on: 27 Mar 2017 15:19
> I am not clear about your actions between steps 4 and 5. 

Step 4 - set a friendly name of the element in the dialog.
Step 5 - go back to the browser and try to record an action for the element you have just added with a friendly name, using quick step menu (e.g. verify that test or something).

ADMIN
Ivaylo
Posted on: 15 Mar 2017 07:41
Dear Anna,

Please note that for already recorded element, before adding a step after you rename the element you should refresh the elements in the element's explorer in order the change to be reflected in the Step Builder. Here is a short demonstration:

https://youtu.be/Luq-2t6OzOs

Thank you for your understanding.
Best Regards,
ADMIN
Ivaylo
Posted on: 15 Mar 2017 07:26
Dear Jan,

I am not clear about your actions between steps 4 and 5. Are you adding the element to the element's explorer? Because this is the proper action. If yes, then I am not able to reproduce the behavior you are describing here and I will need some extra help from you. Here is a short video with my approach which works as expected:

https://youtu.be/-5Wug6Igq5A

Let me know if there is something that I am missing.

Thank you
Anna
Posted on: 09 Mar 2017 10:43
I have a similar problem.

Rename an element in a friendly name in the element-explorer.
Than add a step to the element with an recording task.

--> the result is the same 
element explorer: friendly name
step properties (Primary Target): friendly name
step description: automatic generated name

It would be better, if the step description also handle with the friendly name.