Browser automation frameworks have evolved dramatically from the early JavaScript-injected proxy architecture of Selenium RC (Remote Control, popularized in PHPUnit test suites) to the native browser control protocols of Selenium WebDriver (W3C WebDriver specification) and modern CDP/BiDi engines like Playwright. When maintaining legacy end-to-end test suites or migrating older PHPUnit Selenium tests to modern pipelines, engineers frequently need an authoritative reference mapping classic Selenium RC setup, action, query, and assertion methods to their modern counterparts.

Architectural Shift: Selenium RC vs. W3C WebDriver

In Selenium 1.x (Selenium RC), the test runner communicated with a standalone Java proxy server that injected a JavaScript automation harness (Selenium Core) directly into the browser frame. Every command—such as open(), click(), or waitForPageToLoad()—executed inside the browser's JavaScript sandbox, which introduced same-origin policy restrictions and synthetic event quirks.

Modern Selenium WebDriver (Selenium 4+) eliminates the JavaScript proxy entirely, communicating directly with native browser drivers (chromedriver, geckodriver) over the W3C WebDriver wire protocol and WebDriver BiDi. Explicit condition polling replaces brittle full-page wait calls.

Session Setup and Configuration Methods

In legacy PHPUnit Selenium RC suites, session parameters were configured via setter methods inside the setUp() lifecycle hook before invoking start(). In modern WebDriver, these settings are encapsulated inside browser capability options and timeout configurations.

Browser Navigation and DOM Action Methods

Action methods drive user interactions across the Document Object Model (DOM), including navigation, mouse clicks, keyboard input, form controls, and dialog handling.

DOM State Queries and Element Inspection

Instead of querying the DOM through string-based locator functions on the root client object, modern WebDriver scopes state inspection methods directly to resolved WebElement instances and WebDriver getters.

Assertions and Explicit Waits in Modern TypeScript Suites

Legacy PHPUnit Selenium bundled assertion helpers like assertElementPresent(), assertTextPresent(), assertElementValueEquals(), and assertVisible() directly into the test case base class. Because those assertions executed synchronously without automatic retry polling, single-page applications (SPAs) frequently suffered from flaky race conditions when asynchronous network requests delayed DOM rendering.

In modern Selenium 4 (TypeScript/Node.js), always pair explicit waits (driver.wait with until conditions) with DOM locators before asserting state:

import { Builder, By, until, WebDriver } from 'selenium-webdriver';
import assert from 'node:assert/strict';

export async function verifyCheckoutSubmission(driver: WebDriver): Promise<void> {
  await driver.get('https://example.com/checkout');

  // Replace legacy type() + clickAndWait() with explicit locator waits
  const emailInput = await driver.wait(
    until.elementLocated(By.css('input[name="customer_email"]')),
    5000
  );
  await emailInput.clear();
  await emailInput.sendKeys('architect@webdesigner.la');

  const submitButton = await driver.findElement(By.css('button[type="submit"]'));
  assert.equal(await submitButton.isEnabled(), true, 'Submit button must be enabled');
  await submitButton.click();

  // Replace legacy waitForPageToLoad() + assertTextPresent() with condition polling
  const confirmationBanner = await driver.wait(
    until.elementLocated(By.css('[data-testid="order-confirmed"]')),
    10000
  );
  await driver.wait(until.elementIsVisible(confirmationBanner), 5000);

  const bannerText = await confirmationBanner.getText();
  assert.match(bannerText, /Order Confirmed/i);
}

Key Migration Takeaways

• Eliminate Implicit and Fixed Sleeps: Replace waitForPageToLoad() and fixed timeouts with deterministic driver.wait(until.elementIsVisible(...)) predicates.
• Use Resilient DOM Locators: Prefer semantic attributes (data-testid, ARIA roles, or stable CSS selectors) over brittle XPath indices or auto-generated IDs.
• Decouple Driver Transport from Assertions: Keep WebDriver responsible for browser queries and delegate test assertions to native assertion libraries or auto-retrying expect matchers.