Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Record new tests on existing pages #1826

Open
techdragon opened this issue May 9, 2024 · 1 comment
Open

Record new tests on existing pages #1826

techdragon opened this issue May 9, 2024 · 1 comment

Comments

@techdragon
Copy link

techdragon commented May 9, 2024

馃挜 Regression Report

Since approximately the 3.4 version, new test recordings start a new browser window to navigate to the page. This significantly complicates recording tests of mobile specific functionality that requires having things like the Chrome DevTools open.

This is not a duplicate of #480 as that issue wanted to have playback and record on the existing page, which was marked as a duplicate of #440 which this is also not a duplicate of as that issue is specifically about making the play button work with the existing window session... I am specifically talking about being able to use the record feature on an existing page.

Last working version

Stopped working in version: 3.4.4

To Reproduce

Steps to reproduce the behavior:
Open Selenium plugin from Chrome, select record a new test

Expected behavior

If the last used recording window is on the base url, why does the Selenium IDE have to open a new browser window, it doesn't seem like an impossible task to keep a reference to the last used window and allow the reuse of that window.

Project file reproducing this issue (highly encouraged)

This issue is trivially demonstrable with an empty project.

Environment

OS: macOS
Selenium IDE Version: 3.17.2
Selenium SIDE Runner Version: Not Applicable
Node version: Not Applicable
Browser: Chrome
Browser Version: 124.0.6367.119

@toddtarsi
Copy link
Contributor

v3 is kinda end of maintainance, have you tried v4? Is this an issue there as well. If you're not on v4, I'd try it in about two days (getting the silicon to build non rosetta now, so it will be like 3x faster 馃弫 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants