"alert text" gives "Unhandled alert: alert must be confirmed or dismissed before test can continue. Alert text: ..etc..." about hsac-fitnesse-fixtures HOT 6 OPEN

I don't know. Maybe you can check with a debugger what is happening exactly (where this error is being raised in code).
Getting the alert text of course expects the alert to be present.

Maybe some generic handling (which is active before or after the actual alertText method) throws this error? I've had similar issues in the past when I created subclasses where I forgot to take into account alert handling. It could be something from the subclasses of BrowserTest that are being used, or something in BrowserTest itself.

Given that error only occurs sometimes makes it very hard to track down. Without some additional details I'm afraid I won't be able to help you

from hsac-fitnesse-fixtures.

I've searched the source code from hsac-fitnesse-fixtures , and found only lines that catch an UnhandledAlertException (in BrowserTest.java and AllFramesDecorator.java), but no lines that throw such an exception .

I have the feeling that the webdriver throws an UnhandledAlertException when it shouldn't. I don't see how generic handling before or after the actual alertText method would be responsible for throwing such an alert; nor do see a reason for such generic handling code to intercept an UnhandledAlertException in case of an alertText method.

On page https://www.w3.org/TR/webdriver2/#user-prompts it says:

When a user prompt appears, it is the task of the subsequent command to handle it. If the subsequent requested command is not one listed in this chapter, an unexpected alert open error will be returned.

The command "Get Alert Text" is allowed when an alert is present. So no "unexpected alert open error" should be generated.

What should I do to confirm that the webdriver is the root cause ? Maybe show in the W3C Protocol data that the browser driver generates an "unexpected alert open error" when it shouldn't ?
Webpage https://www.browserstack.com/guide/architecture-of-selenium-webdriver , section Architecture of Selenium 4 WebDriver , shows the W3C Protocol connecting "Selenium Client Libraries" and "Browser Drivers" .
Maybe I can set a breakpoint somewhere in the Selenium Client Library .

from hsac-fitnesse-fixtures.

Does executing this snippet:

|script|browser test                                        |
|open  |https://the-internet.herokuapp.com/javascript_alerts|
|click |Click for JS Alert                                  |
|show  |alert text                                          |
|confirm alert                                              |
|click |Click for JS Confirm                                |
|show  |alert text                                          |
|confirm alert                                              |
|click |Click for JS Prompt                                 |
|show  |alert text                                          |
|dismiss alert                                              |

Give you the same exception in some cases?

In terms of setting breakpoints, I would start at get alert text and step into the selenium code from there

from hsac-fitnesse-fixtures.

I ran the snippet 20 times, and never got the "Unhandled alert" .

from hsac-fitnesse-fixtures.

Is it possible to set the log level of the webdriver ?
That might shed some light onto the problem.

https://www.selenium.dev/documentation/webdriver/browsers/edge/
shows java system properties
EdgeDriverService.EDGE_DRIVER_LOG_PROPERTY
and
EdgeDriverService.EDGE_DRIVER_LOG_LEVEL_PROPERTY

I've tried these with command that starts FixtureDebugTest.main . That didn't work. The log file location doesn't get written to.

And I've tried these as value for COMMAND_PATTERN at the top of the test script:

!define COMMAND_PATTERN {java -DEdgeDriverService.EDGE_DRIVER_LOG_PROPERTY=C:\Users\PBEMMELE\paul\tmp\FixtureDebugTest\log.txt -DEdgeDriverService.EDGE_DRIVER_LOG_LEVEL_PROPERTY=ALL -cp %p %m}

Doesn't work either: the log file doesn't get written to.

from hsac-fitnesse-fixtures.

From looking at code from https://github.com/SeleniumHQ/seleniumhq.github.io/tree/trunk/examples/java
I found the correct command :
!define COMMAND_PATTERN {java -Dwebdriver.edge.logfile=C:\Users\PBEMMELE\paul\tmp\FixtureDebugTest\log.txt -Dwebdriver.edge.loglevel=all -cp %p %m}

The hope is, that the log file will provide some clue when the Unhandled alert arises.

I'm not sure how to make sense of the contents of the log file; it contains many lines, and I guess I'll have to look up the protocol for DevTools WebSocket .
And use grep to look at specific lines .
For example, for the test snippet suggested by tnch 5 days ago, that opens https://the-internet.herokuapp.com/javascript_alerts , I got the following lines when using some grep command:

from hsac-fitnesse-fixtures.