testing-library-docs VS webdriver-bidi

Probably Enzyme was the first to popularize component testing in React by doing shallow rendering and expecting some things to be there in the React component tree. Then React Testing library came and took component testing to a whole new level.

18.react-testing-library

Jest has long been my favorite got to test runner when it comes to UI unit and integration testing. With tools like React Testing Library (Testing Library framework for React) you get the benefit of very easy to write and maintain tests, as well as a quick and efficient way to run our tests.

I'm writing an intergration test with Testing Library where I'm on a boards dashboard area and a user can click a button to create an item on the board. I'm using an intercepting route to do show the popup form. Once finished the user goes back to their area and should see the created board.

This article uses Jest and React Testing Library. It's okay if you want to use other libraries, the fundamentals in this article will help you there as well.

This is the idea behind Testing-Library from what I understand.

https://testing-library.com/

The Testing Library: The Testing Library offers guidance on best practices for testing user interfaces effectively, with a focus on user-centric testing.

There are great tools like Testing Library that render a single component in a single state and then programmatically inspect the resulting DOM. However, the salient details of the rendered HTML – like color, layout, and scale – are hard to express. So, the tests end up brittle (over-specified) or insufficient (under-specified).

LiveCodes provides many of the commonly used developer tools. These include Monaco editor (that powers VS Code), Prettier, Emmet, Vim/Emacs modes, Babel, TypeScript, SCSS, Less, PostCSS, Jest and Testing Library, among others. All these tools run seamlessly in the browser without any installations or configurations. It feels like a very light-weight version of your own local development environment including the keyboard shortcuts, IntelliSense and code navigation features.

fwiw, the Selenium project is now old enough to go to college (19 years this month!); it's not ready to retire just yet. (Side-note: Google Chrome is 15 years old. Age is just a number.) Selenium is still learning from other projects and implementing some new things. Specifically, check out the WebDriver BiDi project, adding a bidirectional protocol which was the core of what made Playwright and Puppeteer faster. Also, Selenium devs are working with the W3C to make this work for everyone.

https://github.com/w3c/webdriver-bidi

https://w3c.github.io/webdriver-bidi/

Is this new WebDriver BiDi available in any of these packages, and does it actually help with this?

If you want to learn more about WebDriver BiDi, you can read the WebDriver BiDi specification.

I guess I didn't understand what exactly you were talking about when talking about "this new standard": WebDriver BiDi or WebContainers.

WebDriver BiDi is on the standards track, that's true: https://w3c.github.io/webdriver-bidi/

One of the new features in the recently released Selenium 4 is support for new event-driven listeners which will be powered by the currently-in-draft BiDirectional (or BiDi) protocol (though the current Selenium implementation has some limitations, which we'll discuss later). In this article we'll discuss some of these new capabilities and demonstrate how to use them in Scala to inspect console logs and network requests made from the browser.

The new BiDirectional WebDriver Protocol is by far one of the most exciting recent developments in the Selenium project and it likely to deliver improvements in speed and stability that far outweigh expectations. As soon as it is available, it will become part of Nightwatch as well. You can follow the development on the Selenium website.

The explainer might be a better starting point: https://github.com/w3c/webdriver-bidi/blob/master/explainer....

There's also the webdriver-bidi spec being worked on by browser vendors that may provide a less hacky, more browser native CDP-style approach to this.