WaitForNewBrowserConnect throws exception for Firefox 57.0.2 (64-bit)

[Tauseef]

Hi,

I am using Telerik Testing Framework for UI automation. I have a test in which WaitForNewBrowserConnect() is throwing an exception only in Firefox browser and the same test works fine in IE, Chrome. Previously when we faced this issue, we resolved by using SetNewBrowserTracking(True). But however, no approach is working for now. We also tried calibrating the Firefox browser after the update but to no avail.

      .SetNewBrowserTracking(true);
                docLink.MouseClick(); 
                myManager.WaitForNewBrowserConnect("help", true, 30000);
                myManager.ActiveBrowser.WaitUntilReady();
                myManager.SetNewBrowserTracking(false);
                result = myManager.ActiveBrowser.PageTitle;// Getting the Help title to a string.
                myManager.ActiveBrowser.Close();//Closing the Help

 

Setup details - 

Browser - Firefox Quantum (57.0.2 (64-bit))

Extension - Progress Test Studio Version 2017.3.103.1    

Testing Framework - 2017.3.1206.0 (ArtOfTest)

[Tauseef]

We have also tried to check the browser collection count after opening a new browser window. By using the below line of code -

.Wait.For<Manager>( => brw.Browsers.Count > 1, myManager, 15000);

However the Browser.Count never increments(It is probably not able to identify the new browser window at all).

We are able to reproduce this issue every time. Also tried changing the timeout to various values to no avail.

Attaching stackTrace of exception.

[Tauseef]

We are able to repro this issue for open in new window . Also tried to check if browser collection is updated using the below line of code -

.Wait.For<Manager>( => brw.Browsers.Count > 1, myManager, 15000);

But the count never increments(looks like it is not able to identify the new window).

Now the problem is if we are not able to close this new window. The next instance of firefox opened for next test case never executes because it hangs into "Extension loaded" page in the browser window. This "Extension loaded" issue we are seeing in both chrome/firefox. Even if one instance of these browsers is open then it goes into "Extension loaded" hang state and no further test case execution happens.

We also tried changing the timeout to various values but to no avail.

Attaching the stack trace of exception

 

[Nikolay Petrov]

Hello Tauseef,

Thank you for this feedback.

Unfortunately, I was not able to reproduce such problem on a sample web app using the following sample Testing Framework scenario:

Manager.Settings.Web.DefaultBrowser = BrowserType.FireFox;
Manager.Current.LaunchNewBrowser();
ActiveBrowser.NavigateTo("https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_win_open");
FrameInfo frInf = new FrameInfo("iframeResult", "", "", 0);
Browser frame = ActiveBrowser.Frames[frInf];
var btnToOpenNewWin = frame.Find.ByContent<HtmlButton>("Try It");

// open new window
btnToOpenNewWin.Click();

Manager.Current.Wait.For<Manager>(brw => brw.Browsers.Count > 1, Manager.Current, 10000);

Please provide sample scenario over a public facing application that could reproduce the reported problem. I suggest to check on Firefox settings if the browser is calibrated appropriately as well.

Thank you in advance for your cooperation. I'm looking forward to hear from you.

Best Regards,
Nikolay Petrov
Progress Telerik

 

 

[Tauseef]

Hi Nikolay,

I have tried executing after calibrating the browser using the given link. It still fails.

we are using Fitnesse server to start UI automation. Could it be causing any problem?

I have captured logs using FiddlerCap. Will share them with you once get permission. I don't, will try to create/repro using sample public facing app.

Thanks

[Nikolay Petrov]

Hello Tauseef,

At this point we don't have any reports from our customers related to FitNess server usage. 

If you provide a Fiddler trace we will have a chance to reproduce the problem on our end. Please, provide a sample test scenario that follows trace recorded scenario. Bellow are listed steps necessary to produce re-usable Fiddler trace for your reference:

1) Start Fiddler - note no browser should be open
2) Click Clear Cache
3) If your site uses HTTPS click (Tools -> Fiddler Options -> HTTPS ->) Decrypt HTTPS traffic
4) Start Capture
5) Launch a browser
6) Clear the cache of the browser
7) Navigate to the page and perform actions that lead to the problem
8) Stop Capture
9) Save Capture
10) Put the .SAZ file into a .zip file and attach that to this support ticket
11) Record a simple test with Test Studio that follows your manual actions - attach it to the ticket as well

I'm looking forward to hear from you.

Best Regards,
Nikolay Petrov
Progress Telerik