Testem vs WSO2 Contract Test Runner
Testem
github.comWSO2 Contract Test Runner
github.comSide by side
| Figure | Testem | WSO2 Contract Test Runner |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 1 |
| Spec score · JavaScript Testing Frameworks | 7.7 (#10) | 7.1 (#19) |
| License | The repository identifies the project as MIT licensed. | The repository identifies its license as Apache-2.0. |
| Purpose | Testem runs JavaScript tests in real desktop browsers, Node, Chrome, or a configured launcher. | It is a consumer-based contract testing library that calls live REST API endpoints and compares their responses with predefined contract responses. |
Plans
In their own words
Testem
Testem is a JavaScript test runner for running tests in Node.js, real desktop browsers, or a launcher you configure. It supports Jasmine, QUnit, Mocha, and custom framework adapters, and can be used for unit, integration, end-to-end-style, or custom test setups. Browser runs can use Chrome, Firefox, Safari, or Edge, including a Headless Chrome launcher. In development mode, a terminal interface watches project files and reruns tests after relevant changes; CI mode can run tests in available browsers in parallel. Testem includes CI reporters for TAP, dot, xunit, and TeamCity, with custom reporters available. Listed preprocessing support includes Babel, TypeScript, Browserify, ESLint, JSHint, JSLint, and CoffeeScript. Its API provides startDev, startCI, and startServer modes, and coverage reporting is supported. It works with GitHub Actions, Jenkins, and TeamCity. Testem is free and open source under the MIT license, and runs on Linux, macOS, and Windows. It requires a supported Node.js runtime: ^22.17.0, ^24.0.0, or >=26.0.0.
WSO2 Contract Test Runner
WSO2 Contract Test Runner is a free, Apache-2.0-licensed library for consumer-based testing of live REST API endpoints. It sends requests and compares returned data with expected responses defined in JSON contracts. A contract can include a request, expected response, assertions, and optional post-conditions. Assertions cover status codes, JSON body and header paths, exact values, regular expressions, emptiness, structures, arrays, and objects. Tests run through Docker by mounting contract and configuration files into the documented image workflow. Suites can run contracts before or after tests, with before-suite contracts running synchronously. Post-conditions can place extracted values into suite-scoped or global environment variables, and contracts can pause for a specified number of seconds. The sample setup uses bearer authorization, cookies, a certificate keystore, and a client truststore. XML path support is listed as a todo. Deployment is Linux and self-hosted.