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

Use DOM Testing Library with Dojo

Kent C Dodds: [00:00] Let's go ahead. We'll start by making a `render` function for rendering a Dojo `WidgetBase` component that's going to accept our `ui`. The type is going to be a `Constructor` of `WidgetBase`. It's a `Constructor` of something that extends the `WidgetBase`.

### dojo.test.js
```javascript
class Counter extends WidgetBase {
  count = 0
  increment() {
    this.count++
    this.invalidate()
  }
  render() {
    return v('div', [v('button', {onclick: this.increment}, [`${this.count}`])])
  }
}
```

[00:16] Then we'll go ahead and make our `container = document.createElement("div")`. Then we'll make our `Projector` as a `ProjectorMixin` of that `ui`. Then we'll make our `projector` instance, `new Projector()`.

[00:31] We'll set this `projector` instance `async` to be `false` to make our tests a little bit easier to work with and `projector.append` to that `container`. Then we can `return` our `getQueriesForElement` on that `container`. Our tests are passing.

### dojo.test.js
```javascript
function render(ui: Constructor<WidgetBase>) {
  const container = document.createElement('div')
  const Projector = ProjectorMixin(ui)
  const projector = new Projector()
  projector.async = false
  projector.append(container)
  return getQueriesForElement(container)
}
```

[00:47] Let's also add the `container`. We'll spread across those `getQueriesForElement` so that people can access the `container` if they need. That gets things working.

### dojo.test.js
```javascript
function render(ui: Constructor<WidgetBase>) {
  const container = document.createElement('div')
  const Projector = ProjectorMixin(ui)
  const projector = new Projector()
  projector.async = false
  projector.append(container)
  return {
    container,
    ...getQueriesForElement(container)
  }
}
```

[00:56] In review, we've got this `render` method that creates a `container` and then uses `ProjectorMixin` from the Dojo framework and passes in our `ui`, which is a `Constructor` based on the `WidgetBase`.

[01:09] Then we create our instance of the `projector`. We make `projector.async` as `false` to make testing a little bit easier. Then we `append` the `projector` to that `container`. Then we return `getQueriesForElement` so that we can use it in our typical `dom-testing-library` test.


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 [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 Dojo

Transcript

Use DOM Testing Library with Dojo