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

DOH

https://dojotoolkit.org/reference-guide/1.10/util/doh.html

Behat

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

JavaScript

PHP

Category

Unit Testing

Functional/Acceptance Testing

General info

D.O.H means Dojo Objective Harness, it's a test framework for the DOJO web apps which tests and runs on the browser and on cloud test execution services like Browserstack

Dojo is a Typescript framework build for modern web application, and D.O.H is a basically unit test library to test JavaScript functions and custom widgets

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

DOH is both flexible and extendable and runs in many environments including many browsers to test various front-end functionalities and components

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

Pieces of back-end code can be tested with DOH as it performs Unit tests. It is flexible enough to test server-side behaviour and functionality

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

It has various fixture methods like setUp(), tearDown() and Performance test fixtures which are just like a regular test fixtures, but with extra options. Specifically, it uses 'testType' to mark it as a "perf" test, which instructs the D.O.H. runner to treat the tests as performance and use the calibrate and execute test runner

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.

Yes

It supports group fixtures

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.

N/A

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)

N/A

By using third party libraries like Mock and Prophecy
Grouping
Allows organizing tests in groups

Yes

There is a function that allows you to group tests, the 'doh.register(...)' function. It's most commonly used for registering Unit Tests

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