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 to test any JS framework

Use DOM Testing Library with React

Kent C Dodds: [00:00] We'll start by making a function called `render` that's going to accept our `ui` right here. We'll say,`ui` Then we need to make a `container` that's a `div`. That's what we're going to `render` using ReactDOM.

### react.test.js
```jsx
function render(ui) {
  const container = document.createElement('div')
}
```

[00:16] We'll `import ReactDOM from 'react-dom'`. We'll say, `ReactDOM.render(ui, container)`. Then we'll `return getQueriesForElement`. We use that `getQueriesForElement` in this return on that `container`.

### react.test.js
```jsx
import {getQueriesForElement, fireEvent} from 'dom-testing-library'

function render(ui) {
  const container = document.createElement('div')
  ReactDOM.render(ui, container)
  return getQueriesForElement(container)
}
```

[00:35] If we pop open here, we're going to see that our test is actually failing. That's because in React, all the DOM event listeners for listening to click events are actually bound to `document.body` with React.

[00:47] We need this `container` to be inside the body. We'll say, `document.body.appendChild(container)`. That'll get our test passing.

### react.test.js
```jsx
import {getQueriesForElement, fireEvent} from 'dom-testing-library'

function render(ui) {
  const container = document.createElement('div')
  ReactDOM.render(ui, container)
  document.body.appendChild(container)
  return getQueriesForElement(container)
}
```

[00:55] There are a couple other optimizations here. I'm going to spread those utilities. I'm also going to pass along the `container`. I'm also going to pass along a `cleanup` method. That is going to say, `document.body.removeChild(container)`, so we can clean up that `container`.

[01:11] We also want to `unmount` the React component at the `container`. We'll say, `ReactDOM.unmountComponentAtNode(container)`. We'll `unmount` it. Then we'll remove it from the `container`.

### react.test.js
```jsx
function render(ui) {
  const container = document.createElement('div')
  ReactDOM.render(ui, container)
  document.body.appendChild(container)
  return {
    ...getQueriesForElement(container),
    container,
    cleanup() {
      document.body.removeChild(container)
    }
  }
}
```

[01:22] In our `test` here, we can also add `cleanup` and `cleanup` at the end. If we look at `document.body.outerHTML`, we'll see that the body is now empty. That way, any other tests that are using this `render` method won't have a `document.body` that's all messed up with previous test components.

### react.test.js
```jsx
test('renders a counter', () => {
  const {getByText, cleanup} = render(<Counter />)
  const counter = getByText('0')
  fireEvent.click(counter)
  expect(counter).toHaveTextContent('1')
  fireEvent.click(counter)
  expect(counter).toHaveTextContent('2')
  cleanup()
  console.log(document.body.outerHTML)
})
```

[01:41] In review, for React, for the `render` method, we create a `container` that's a `div`. We `render` the `ui` to that `container`. We append that `container` to the body. Then we get all the utilities for that `container`.

[01:52] We also return the `container` just in case they want to do a query selector. Then we run this `cleanup` so that we can unmount the component and remove that `container` child.


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 [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 [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 with HyperApp

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 React

Transcript

Use DOM Testing Library with React