Intern vs Wallaby comparison of testing frameworks
What are the differences between Intern and Wallaby?

Intern

https://github.com/theintern/intern

Wallaby

https://github.com/elixir-wallaby/wallaby
Programming language

JavaScript

Elixir

Category

Unit Testing, Functional Testing

Intergration Testing, Browser Automation

General info

Intern is minimal test system for JavaScript designed to write and run consistent.

Intern is a complete test system for JavaScript designed to help you write and run consistent, high-quality test cases for your JavaScript libraries and applications. Using Intern we can write tests in JavaScript and TypeScript using any style like TDD, and BDD. Intern can run unit tests in most browsers that support ECMAScript

Library for end-to-end intergration testing for Elixir apps

Wallaby supports concurrent feature testing (i.e multiple tests can run concurrently) as well as browser management
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

No

Client-side
Allows testing code execution on the client, such as a web browser

Yes

Intern is a complete test system for JavaScript It Runs in the browser and can test any front-end component and functionality

Yes

It works well for automated E2E testing; Wallaby also has an experimental Chrome Driver that works well
Server-side
Allows testing the bahovior of a server-side code

Yes

Since it is a complete testing system that can test any type of JavaScript code, it can test server-side behaviour and components as well

N/A
Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

N/A

N/A

Group fixtures
Allows defining a fixed, specific states of data for a group of tests (group-fixtures). This ensures specific environment for a given group of tests.

N/A

N/A

Generators
Supports data generators for tests. Data generators generate input data for test. The test is then run for each input data produced in this way.

N/A

Licence
Licence type governing the use and redistribution of the software

FreeBSD License

MIT License

Mocks
Mocks are objects that simulate the behavior of real objects. Using mocks allows testing some part of the code in isolation (with other parts mocked when needed)

Intern uses the Dojo Toolkit’s AMD loader. To mock, you should be able to just use the standard AMD 'map' feature, else you can use third party libraries like sinon.js

Yes

Available through third party libraries like Mock and Mockery
Grouping
Allows organizing tests in groups

Yes

You can group tests into Suites which may be specified as file paths or using glob expressions, there is typically one top-level suite per module.

N/A

Other
Other useful information about the testing framework