Execution wont click Item in Dropdown

[Yan Jun]

Hi,

I have this problem where I have a few test cases interacting with the same dropdown in a same screen.

Case A : The execution was OKAY if the flow is as below :

1. login

2. go to the screen

3. Interact with the elements in the screen ( Textbox, checkbox, dropdown)

4. Verify elements.

5. log out OR click the "Cancel" button which reset all the fields in the screen.

6. Repeat step 1 to 5 if i logout OR repeat step 3 to 5 if i click the "Cancel" button ( with different interaction and verification but mostly with the same elements)

 

Case B : Since i wanted to reduce the execution time with only login once and make sure to reset the screen even after save, i build the execution flow as below :

1. login 

2. go to the screen.

3. Interact with the elements in the screen ( Textbox, checkbox, dropdown)

4. Verify elements.

5. Repeat Step 2 to 4 but with different interaction and verification but mostly with the same elements

I skipped the login part for the next time i go to the same screen because the screen will be refreshed and the changes will not be saved . This is when the execution won't click the item in the dropdown. The steps to handle other elements(textbox,checkbox) are working fine.

The way i handle the dropdown field is I will add the span that represents the dropdown and the list item inside it separately. Then I will use the step builder to click each of the element. I cannot use KendoInput: Toggle Combo because this step is not stable for the AUT i am testing. This AUT is using Kendo UI for jQuery.

For this case(Case B), it seems that it clicks the dropdown span, but it wont click the list item inside. This happens only when i go to the same screen for the second time and onwards. For Case A, the execution will click both of the element no matter how many times it goes to the same screen.

This behaviour happens in test case execution and also test list execution.

Have anyone encountered this kind of problem before?

Thank you.

[Plamen Mitrev]

Hi Yan Jun,

Looking at the details you shared, I can't say what might be causing this different behavior. I would suggest you to check the DOM tree for any differences between both case A and B, especially for the dropdown that is causing issues.

If you do not notice anything suspicious that could be causing the issue, please attach the .tstest files for both cases and share access to the application under test. If that is not possible for you, try to record a test against a publicly accessible page that simulates the misbehavior. In addition to that, attach the exported step failure details and Test Studio application log. That will allow me to troubleshoot it on my end and advise you further.

I am looking forward to hearing from you.

Regards,
Plamen Mitrev
Progress Telerik