webdriver-bidi VS completions

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.

I am building _exactly_ the same thing for Playwright over at https://ray.run/. I think this is the future of writing tests no doubt. Planning to launch next week.

Note: Use page.goto('/') and have "baseURL": "http://ray.run" set in the playwright.config.ts file for concise code.

Your website https://ray.run/ does have that nostalgic early 2000s vibe, which is cool! Regarding the search functionality, you might want to explore open-source alternatives to Algolia.

Projects like Elasticsearch, Solr, or even using Google Custom Search can provide search capabilities without the cost. They might require a bit more setup and maintenance, but they can be budget-friendly options for a free community.

In case you need help or assistance with your project, feel free to contact us! https://www.ratherlabs.com

* Most of the pages I use are rendered at the request time, rather than build time

For context, this is the website https://ray.run/

Ensuring in-article hover definitions for terms on the https://ray.run/ blog.

I have added a zone to Cloud DNS (GCP) for https://ray.run/

I updated completions library to allow statically typed responses:

import { type Browser, chromium, test as base } from '@playwright/test'; import getPort from 'get-port'; import { playAudit } from 'playwright-lighthouse'; export const test = base.extend<{}, { browser: Browser; port: number }>({ browser: [ async ({ port }, use) => { const browser = await chromium.launch({ args: [`--remote-debugging-port=${port}`], }); await use(browser); await browser.close(); }, { scope: 'worker' }, ], port: [ // eslint-disable-next-line no-empty-pattern async ({}, use) => { // Assign a unique port for each playwright worker to support parallel tests const port = await getPort(); await use(port); }, { scope: 'worker' }, ], }); test.describe('Accessibility Testing with Lighthouse', () => { test('should pass the Lighthouse accessibility audit', async ({ page, port, }) => { await page.goto('https://ray.run/'); await playAudit({ page, port, thresholds: { accessibility: 100, }, }); }); });

import { test } from '@playwright/test' test.beforeEach(async ({ page }) => { await page.goto('https://ray.run/login') await page.fill('#username', 'admin') await page.fill('#password', 'password123') await page.click('#login-button') expect(await page.url()).toContain('/dashboard') }) test('should display user profile', async ({ page }) => { await page.click('#profile-button') expect(await page.textContent('body')).toContain('Admin User') }) // Other tests...