Selenium v4 bindings

[toddtarsi]

This is to get ahead of any user issues and provide a bit of forecasting.

Currently, we export formats for Selenium v3.

I'm planning to add v4 export bindings as part of Selenium IDE v4. I'm sorry for any trouble this is causing you.

If you'd like to help by proposing new v4 bindings in the meantime, I would appreciate that and I'll definitely take a look at merging them to the v3 branch asap.

It's not that I'm opposed to them. It's simply that I think the best action for the health of the IDE tooling is to get an electron version of the IDE out, which will resolve a lot of fundamental issues with the emulated-js approach.

Thanks, and please feel free to weigh in with comments or feedback in this thread. I'm listening.

[NikkTod]

Hello and a happy 2022 :)

Not sure if this is the place and if it is possible to have, but I like to suggest somening when it comes to exports to different languages. I have recentlly chekced the Playwright recording tool and I found something that could be of a great help if people want to export a test and run it via pipleine (e.g. Azure DevOps).

I am comparing the waiting functionality of the tools.

Right now, I think, if running the tests via the side runner or the extention there are build-in wait commands. So not a lot of problem can happen. But what about if you export the test in C# and run it via the dotnet framework...

I good thing I saw from this Playwright recording tool is that it actully records and exports your code with auto-awaits functionality, this way you wont have any problems of running the test on other frameworks. Like the following examples:

await page.GotoAsync("https://google.com"); await page.ClickAsync("[class="react-toggle-track"]");

And one question to you @toddtarsi, do you know when is expected this Electron version to come out?

[toddtarsi]

@NikkTod - Happy 2022, nice to hear from you!

For the auto-waiting, I'd like to support that on the non-assert type interactions, but some of that will come down to how much each language binding provides for doing that in an easy way. For JS, I'm competent enough that I could make it work. Unfortunately, I'm a lot less confident in C#, Java, etc. I've heard this a lot as a resounding win by Playwright (its always bullet point number one haha), so its definitely on everyone on the team's radar. I'll definitely keep it in mind when I get to the v4 export formats.

Realistically, probably about 3 months, around April, and that's for the minimum necessary feature footprint. Record, breakpoints, playback from any point, save, load, core plugin support, export to v4.

That's what I'm aiming for at least.