Chrome certificate selection window closes automatically - issue

1 Answer 109 Views
Test Configuration Test Execution
aplicaciones
Top achievements
Rank 1
aplicaciones asked on 11 Jun 2021, 09:24 AM

Hello Forum,

I haven't seen this precise issue/question in this forum, that's why I open this thread.
The issue started happening when we upgraded from Telerik Testing Framework 2019 (191.2.12.0) to version 2021 (211.3.9.0)

Our code hasn't changed except for the Telerik Testing Framework version.

Previous behavior (the correct or expected one)
In our test, one of the steps involves  Accepting a Client Certificate Window.
We normally achieve this by :
- clicking the button that triggers the Client Certificate Selection WIndow in Chrome,
- we wait a couple of seconds and then we Send an "Enter" to the screen.

Despite the fact, this might not be the best approach or practice, it's been working perfectly, for years.

But after we upgraded to version 2021:
- After clicking the button that triggers the Client Certificate Selection Window it gets automatically closed without the possibility to accept this certificate. Thus, we don't get authenticated.

There's no change in our code, just the version of the Telerik Testing Framework.
We are only interested in testing it with Chrome (that's our requirement)

Environment:

- Windows Server 2016 Standard Edition

- Chrome 91.0.4472.101 (Official Build) (64-bit)

I would appreciate any help. I may have done something wrong or skipped something but as far as I can see the only change is the Telerik Testing Framework version.

Sebastian Inones

1 Answer, 1 is accepted

Sort by
0
Accepted
Elena
Telerik team
answered on 14 Jun 2021, 02:13 PM

Hi Sebastian,

I am sorry to know you experience any difficulties after upgrading to the latest Testing Framework version and will be happy to assist you with resolving this. 

Based on the description it seems that the issue is related to this specific certificate popup and how it is recognized in Test Studio. Most probably in the latest version of the Testing Framework, this certificate dialog matches the Confirm dialog definition and is being treated as such.

Although this is only an assumption with the current details on hand, it is probably closed immediately because of a specific setting value. This setting is the UnexpectedDialogAction one, which defines how the test execution should behave in case an unexpected dialog appears on screen. The options are DoNotHandle, HandleAndContinue and HandleAndFailTest. The assumption is that this is set to HandleAndContinue and thus the certificate popup is immediately closed.

I am not familiar with the overall test solution you work on and if you are actively using this particular setting to handle some specific scenarios with its help. If you are not aware of such, you can try to set this setting to DoNotHandle and then the code you used until now, should work again.

Manager.Settings.UnexpectedDialogAction = UnexpectedDialogAction.DoNotHandle;

This will change the setting value in the particular test. Please, check how are the settings managed in the particular project and how you should apply the change in overall. 

There is one more suggestion based on the above mentioned assumptions - you can replace the code used to handle this certificate popup with a confirm dialog handler. It is also used to handle an alert dialog. And since you only press Enter to handle the certificate dialog, this is the dialog handler which will match the dialog and handle it. 

Please, check these suggestions and let me know if you need additional assistance on trying any of these. Otherwise, I will appreciate your feedback on the occurrence and if any of the listed options fixed the misbehavior. 

Thank you in advance for your cooperation.

Regards,
Elena
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Test Studio course! Check it out at https://learn.telerik.com/.
aplicaciones
Top achievements
Rank 1
commented on 15 Jun 2021, 10:45 AM

Hello Elena,

Thanks a lot for the provided answers. Both suggestions make complete sense.

We are currently not setting any value for :
Manager.Settings.UnexpectedDialogAction
So, that might do the trick ;)

Currently, we have decided to keep the Framework 2019 in the production environment as we need this test to run every single day. But, as soon as I can manage to invest some time with the provided alternatives you've suggested I'll let you know.

Thanks a lot for the quick answer.
Regards,
Sebastian Inones
Elena
Telerik team
commented on 15 Jun 2021, 12:46 PM

Hi Sebastian, 

Thanks for your follow up. Of course, it is better to keep the working state on the production environment and change it when you have the time to evaluate and find the cause of the misbehavior. 

So, take your time and check the shared suggestions when suitable. In case you need any further assistance on this, do not hesitate to get back to us.

Thank you for your time in advance.

Regards,
Elena

aplicaciones
Top achievements
Rank 1
commented on 06 Jul 2021, 08:54 AM

Hello Elena,

I was able to try what you suggested.
That's :
Manager.Settings.UnexpectedDialogAction = UnexpectedDialogAction.DoNotHandle;

So, now our code is working fine with version 2021.
I guess that default setting were changed between version 2019 and 2021.

Thanks again for your help.
Elena
Telerik team
commented on 06 Jul 2021, 09:24 AM

Hi Sebastian, 

Thank you for confirming that the suggested solution works for you. I am pleased to know you can use the latest Test Studio version without issues.

Regards,
Elena

Tags
Test Configuration Test Execution
Asked by
aplicaciones
Top achievements
Rank 1
Answers by
Elena
Telerik team
Share this question
or