selenium-ide
selenium-ide copied to clipboard
SeleniumHQ
close command completes but traps an error
🐛 Bug Report
I have test cases that open other browser windows/tabs. When I go to clean up, I select each of the windows (using the unique Window Name I've given each one) and then issue the close command. This works fine until I close the last window. The close command works, but it traps an error and the test case stops running. The error does not explain the problem.
To Reproduce
Run the attached *.side file; it will run a crippled version of two PHP scripts running on a test machine. It will open 3 browser windows/tabs and then close all three; then execution "... ended with 1 error(s)". (It can do no harm, only one database read request is made and nothing is produced. I have attached the contents of the execution log. Check the last line and notice the error just after the close command successfully completes.
Expected behavior
Expect the "last" close command to work (which it does) and not produce an error which stops execution (which it does not).
Project file reproducing this issue (highly encouraged)
I've attached a project file, remove the ".txt" from the attachment
Environment
OS: Windows 10 Pro ver. 22H2 (19045.3208) Selenium IDE Version: 3.17.4 Selenium SIDE Runner Version: N/A Browser Version: Firefox 115.0.2 (64 bit) and MS Edge (114.0.1823.82 (64-bit) Test_Close_Window.side.txt execution_log.txt
@RobCofer - I should caution you, I'm not really doing much beyond total break fix with v3 anymore. Manifest v3 is kind of a death knell for the extension. My main focus is getting v4 rolling and out of alpha:
https://github.com/SeleniumHQ/selenium-ide/releases/tag/4.0.0-alpha.44
@RobCofer - But you can bet your boots I'll try it in v4 and let you know what I see 😄
Thanks for the information. Looks like v4 has been in alpha for just over a year now. Sounds like the problem I'm reporting won't be fixed in v3 and I'll need to wait until v4 "goes live".
@RobCofer - v4 is getting pretty stable now. I'm releasing x.58 as an alpha tonight, and if I don't see any issues for a week or two, I might anoint it as a "beta candidate".