inferno-dom is legacy and will not work. What method you are talking about here? This documentation https://github.com/infernojs/inferno/tree/master/packages/inferno-test-utils or something else?

This function requires a DOM.

So where do I get the DOM? why need the DOM? isn't there an option similar to react-test-renderer that does not require the dom as the parameter. You just give it the component and that's it.

@aprilmintacpineda Something like this could work

let container;

beforeEach(() => {
    container = document.createElement('div');
    document.body.appendChild(container); // This is needed for synthetic events fe. clicks
});

afterEach(() => {
   render(null, container); // Tear down, to remove events
   document.body.removeChild(container);
});

describe('', () => {
    it('your test', () => {});
});

That's going to require mocking the document.body because running tests is on nodejs environment, document.body does not exists there, right?

Basically, what I want to do, is I want to be able to do this with inferno-js

https://github.com/aprilmintacpineda/react-context-api-store/blob/master/__tests__/provider.spec.js

Notice that I did not have to mock anything about the DOM. All I needed to do was call renderer.create(<div>I'm a component</div>) and that's it.

Inferno is made DOM in mind. There are no plans to build Inferno native. You need jsDOM If you want to run tests in Node

Somebody could build custom renderer that fakes out native DOM APIs providing some simple objects

@sprlwrksAprilmintacpineda If you want simple out of the box testing for your components you could use enzyme along with enzyme-adapter-inferno.

Support for V6 will be coming shortly hopefully

The second parameter of render is used to target rendering. It could be Html Node, element, or similar fake JS object (jsDOM?)