To use DOM Testing Library with [HyperApp](https://github.com/jorgebucaran/hyperapp), we’ll write a custom render function that utilizes the getQueriesForElement function. HyperApp renders and re-renders asynchronously, so we’ll use a custom `fireEventAsync` utility function to ensure that the app has re-rendered after every event we fire.

Use DOM Testing Library to test any JS framework

Use DOM Testing Library with HyperApp

Kent C Dodds: [00:00] For `hyperapp`, we're going to make a function called `render`. This one's going to accept an object as the first argument, and it's going to accept `state`, `view`, `actions`, and then we'll make our `container`, `document.createElement("div")`.

### hyperapp.test.js
```javascript
function render({state, view, actions}) {
  const container = document.createElement('div')
}
```

[00:15] Then we're going to use `hyperapp.app`, and we'll pass `state`, `actions`, `view`, and `container`. Then we'll go ahead and `return getQueriesForElement`, and we'll pass `container` to that. Now, `hyperapp` actually will `render` everything asynchronously, and all of our events that we're firing are asynchronous, meaning it's going to wait until the next tick of the event loop before it continues on for the rest of the test.

### hyperapp.test.js
```javascript
function render({state, view, actions}) {
  const container = document.createElement('div')
  hyperapp.app(state, actions, view, container)
  return getQueriesForElement(container)
}
```

[00:41] This is because `hyperapp` is implemented to update the app on the next tick of the event loop any time a `state` update happens. That applies also when you initially `render`. We need to actually turn this into an `async` function, which we can `await` the `wait` utility from `dom-testing-library`.

### hyperapp.test.js
```javascript
function render({state, view, actions}) {
  const container = document.createElement('div')
  hyperapp.app(state, actions, view, container)
  return getQueriesForElement(container)
}
```

[00:57] With that, our tests are now passing.

### hyperapp.test.js
```js
test('renders a counter', async () => {
  const {getByText, getByTestId} = await render({state, view, actions})
  const counter = getByText('0')
  await fireEventAsync.click(counter)
  expect(counter).toHaveTextContent('1')
  await fireEventAsync.click(counter)
  expect(counter).toHaveTextContent('2')
}
```

In review, for `hyperapp`, we use `async`, and we use our `fireEventAsync` utility here, which effectively is `fireEvent` with an `await` inside of each one of those events.

### fire-event-async.js
```js
const fireEventAsync = {}

Object.entries(fireEvent).reduce((obj, [key, val]) => {
  obj[key] = async (...args) => {
    const ret = val(...args)
    await wait()
    return ret
  }
  return obj
}, fireEventAsync)
```

[01:11] Then it waits to the next tick of the event loop. Then we create our `container`. We start `hyperapp` with the `state`, `actions`, and `view`, and then we wait for the next tick of the event loop before returning the `getQueriesForElement`.

[01:24] Then when people use our `render` method, they're going to `await` it to make sure that the DOM is ready for us to start making our queries with `dom-testing-library`.


The person using your application components shouldn’t have to know or care what framework(s) you used to write your application. Guess what: Neither should your tests. 

This course explores the 

. You’ll get hands-on experience writing tests for any JavaScript framework, giving you the confidence you need to ship your JavaScript application with your framework of choice.

Intro to Use DOM Testing Library to test any JS framework

To use DOM Testing Library with [React](https://reactjs.org/), we’ll write a custom render function that utilizes the getQueriesForElement function. Because React binds all event handlers to the body we’ll have to append our container to the body and we’ll add a cleanup method to unmount the component and cleanup the DOM. If you like this, checkout [react-testing-library](https://github.com/kentcdodds/react-testing-library).

If you like this, checkout [React Testing Library](https://testing-library.com/react).

Use DOM Testing Library with React

To use DOM Testing Library with [Preact](https://preactjs.com/), we’ll write a custom render function that utilizes the getQueriesForElement function. Because preact re-renders asynchronously, we’ll use a custom fireEventAsync function to ensure that the app has re-rendered after every event we fire. If you like this, checkout [preact-testing-library](https://github.com/antsmartian/preact-testing-library).

If you like this, checkout [Preact Testing Library](https://testing-library.com/preact).

Use DOM Testing Library with Preact

To use DOM Testing Library with [jQuery](https://jquery.com/), we’ll create a DOM node and apply our jQuery plugin to that DOM node, then we can use getQueriesForElement on that DOM node to get the queries we need to start writing out our tests.

Use DOM Testing Library with jQuery

To use DOM Testing Library with [Dojo](https://dojotoolkit.org/), we’ll write a custom render function that utilizes the getQueriesForElement function and dojo’s widge-core utilities.

Use DOM Testing Library with Dojo

To use DOM Testing Library with [AngularJS](https://angularjs.org/), we’ll write a custom render function. We’ll pass our template and angular module we’d like to use for bootstrapping a mini-app inside a div we create, then use getQueriesForElement for that mini-app container. From there we can use all the regular utilities we enjoy from dom-testing-library.

Use DOM Testing Library with AngularJS

To use DOM Testing Library with [Angular](https://angular.io/), we’ll write a custom render function that utilizes the getQueriesForElement function. Here we need to create a test bed testing module which we’ll use to get a native element for our container.

If you like this, checkout [Angular Testing Library](https://testing-library.com/angular).

Use DOM Testing Library with Angular

To use DOM Testing Library with [VueJS](https://vuejs.org/), we’ll write a custom render function that utilizes the getQueriesForElement function. Vue is another library that re-renders asynchronously, so we’ll use that custom fireEventAsync to ensure that we wait until the next tick of the event loop before making further queries. If you enjoy this, checkout [vue-testing-library](https://github.com/dfcook/vue-testing-library).

Use DOM Testing Library with VueJS

To use DOM Testing Library with [Mithril](https://mithril.js.org/), we’ll write a custom render function which mounts a mithril component and then utilize the getQueriesForElement function on the container where it’s been mounted. Mithril is unique in how it re-renders so we’ll use dom-testing-library’s `wait` function for our assertions.

Use DOM Testing Library with Mithril

To use DOM Testing Library with [Svelte](https://svelte.technology/), we’ll write a custom render function that utilizes the getQueriesForElement function. We’ll take the svelte template and create a constructor for that as well as the data to interpolate. Then we can use dom-testing-library queries as normal.

If you like this, checkout [Svelte Testing Library](https://github.com/testing-library/svelte-testing-library).

Use DOM Testing Library with Svelte

To use DOM Testing Library with [from-html](https://github.com/m3g4p0p/from-html), we’ll write a custom render function that utilizes the getQueriesForElement function. In our situation we’ve made a custom “component” class for from-html, we mount that manually and then we can use DOM Testing Library's queries on the container we create.

Use DOM Testing Library with HyperApp

Transcript

Use DOM Testing Library with HyperApp