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

Intern

https://github.com/theintern/intern

Behat

https://docs.behat.org/en/latest/
Programming language

JavaScript

PHP

Category

Unit Testing, Functional Testing

Functional/Acceptance Testing

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

Behat is an open source Behavior-Driven Development framework for PHP.

Behat uses the StoryBDD subtype of behaviour-driven development (the other subtype is SpecBDD); This means the tests we write with Behat look rather like stories than code. It is inspired by Ruby's Cucumber
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

To enable Behat to test a website, you need to add Mink and a browser emulator (selenium maybe, though slow) to the mix. Mink methods are the connector between Behat and an extensive list of available drivers, and they provide a consistent testing API.
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

Yes

Behat can be used for Data Integrity Testing to verify that database operations are functioning properly
Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

N/A

Yes

One can use the 'Doctrinefixturesbundle' to create the required fixture loaders and load them in our Behat scenarios when required, using the 'BeforeScenario' hook.
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

Yes

Behat allows for group fixtures
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.

By use of third party libraries like moodle-behat-generators
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

By using third party libraries like Mock and Prophecy
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.

Yes

You can use tags to group features and scenarios together, independent of your file and directory structure
Other
Other useful information about the testing framework