QUnit vs WSO2 Contract Test Runner

QUnit is a free JavaScript testing framework first developed for the jQuery project. It runs in web browsers, Node.js, SpiderMonkey and Web Worker threads, so developers can test code in different runtime environments. Its APIs allow custom assertions, test runners and reporters. Browser releases have no runtime dependencies, and the project describes Node.js setup as requiring zero configuration and browser setup as minimal. For DOM tests, QUnit resets fixture markup after each test. Its browser reporter presents results and can include expected and actual values, assertion details and failure stack traces. Developers can rerun selected tests or modules and prioritize previously failing tests. Guides cover modules, asynchronous tests, callbacks and assertions, while plugins can add or modify capabilities such as DOM assertions, themes and JUnit XML reports. QUnit integrates with browser automation tools including Karma, Web Test Runner, Testem and WebdriverIO’s QUnit service. QUnit 3.0 is distributed through the jQuery CDN and npm, and is also installable with Yarn. For its ESM version, the compatibility guide lists Node.js 18+ and specified browser versions.

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.