Package Exports

@open-wc/testing-helpers
@open-wc/testing-helpers/fixture.js
@open-wc/testing-helpers/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@open-wc/testing-helpers) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Testing Helpers

Part of Open Web Component Recommendation open-wc

We want to provide a good set of defaults on how to facilitate your web component.

In order to efficient test webcomponent you will need some helpers to register and instantiate them.

::: tip Info This is part of the default open-wc recommendation :::

Test a custom element

import { fixture } from '@open-wc/testing-helpers';

it('can instantiate an element', async () => {
  const el = await fixture('<my-el foo="bar"></my-el>');
  expect(el.getAttribute('foo')).to.equal('bar');
}

Test a custom element with properties

import { html, litFixture } from '@open-wc/testing-helpers';

it('can instantiate an element with properties', async () => {
  const el = await litFixture(html`<my-el .foo=${'bar'}></my-el>`);
  expect(el.foo).to.equal('bar');
}

Test a custom class

If you test a mixin or you have multiple base classes that offer a various set of options you will find yourself in the situation of needing multiple custom element names in your tests. This is rather dangerous as custom elements are global so you do not want to have overlapping names in your tests. Therefore we recommend using a special function for it.

import { fixture, defineCE } from '@open-wc/testing-helpers';

const tag = defineCE(class extends MyMixin(HTMLElement) {
  constructor() {
    super();
    this.foo = true;
  }
});
const el = fixture(`<${tag}></${tag}>`);
expect(el.foo).to.be.true;

Test a custom class with properties

For lit-html it's a little tougher as it does not support dynamic tag names by default.
This is using a "workaround" which is not performant for rerenders. As this is usually not a problem for tests it's ok here but do NOT use it in production code.

import { html, litFixture, defineCE, unsafeStatic } from '@open-wc/testing-helpers';

const tagName = defineCE(class extends MyMixin(HTMLElement) {
  constructor() {
    super();
    this.foo = true;
  }
});
const tag = unsafeStatic(tagName);
const el = litFixture(html`<${tag} .bar=${'baz'}></${tag}>`);
expect(el.bar).to.equal('baz');

Timings

If you need to wait for multiple elements to update you can use flush.
By default it will be a timeout of 2ms but it will use a window.flush method if set.

import { flush, aTimeout, html, litFixture } from '@open-wc/testing-helpers';

const el = await litFixture(html`<my-el .foo=${'bar'}></my-el>`);
expect(el.foo).to.equal('bar');
el.foo = 'baz';
await flush();
// or as an alternative us timeout
// await aTimeout(10); // would wait 10ms
expect(el.shadowRoot.querySelector('#foo').innerText).to.equal('baz');