Component Testing With WebdriverIO

Running component tests allow you to mount, render and interact with a single Enhance component in isolation. To ensure that test conditions are as close as possible to the real world, we recommend to run them in actual browser rather than using e.g. JSDOM which is just a JavaScript implementation of web standards provided by browsers. To run Enhance component tests you can use WebdriverIO as a browser automation framework. It is based on the WebDriver protocol, a browser automation web standard which guarantees that your tests interact with your components as closely as possible to how a user would.

To add a WebdriverIO test harness to your project, run:

npm init wdio@latest ./

The command initializes a configuration wizard that helps you set-up the test harness. Make sure to select on the first question: “Where should your tests be launched?” the answer: “browser - for unit and component testing in the browser”.

An example test file should be created. Replace the content with e.g.:

import { expect, browser, $$ } from '@wdio/globals'
import enhance from '@enhance/ssr'

// see actual component here:
import MyHeader from '../../app/elements/my-header.mjs'

describe('Enhance Framework', () => {
  it('should render MyHeader element correctly', async () => {
    const html = enhance({
      elements: {
        'my-header': MyHeader
    const actual = document.createElement('div')
    actual.innerHTML = (html`<my-header></my-header>`).replace(/<\/?\s*(html|head|body)>/g, '')
    expect(await $$('img').length).toBe(2)

You can find the WebdriverIO API docs at and the full example for Enhance component testing on GitHub. If you have any questions, join the project’s Gitter channel.

Community Resources

Visit Enhance on GitHub.
Join our Discord server to chat about development and get help from the community.
Follow Enhance in the Fediverse. We're huge fans of the IndieWeb!