Jasmine vs WSO2 Contract Test Runner

Jasmine is a free, open-source framework for testing JavaScript code in browsers and Node.js. Tests use JavaScript’s describe/it structure and expect matchers. The jasmine-core package has no external dependencies, and the framework does not rely on other JavaScript frameworks. For Node, developers can install the package locally with npm and run it using npx jasmine; the standalone distribution runs browser specs without other tools or a web server. Jasmine supports ES modules, and its Node setup can also load CommonJS modules. The jasmine-browser-runner supports interactive browser runs and CI execution with headless Chrome or Sauce Labs. It can also connect to Sauce Labs or a user’s own Selenium Grid as a remote browser grid. Runners can be configured, reporters and matchers customized, and spec order randomized. The project lists JavaScript and TypeScript support, parallel execution and built-in mocks. Browser and Node compatibility follows a rolling window, so older platforms may receive best-effort support or be dropped in minor releases. The FAQ notes that the unmaintained karma-jasmine adapter depends on jasmine-core 4.x, which can limit access to newer Jasmine features. The project uses the MIT License and directs users to GitHub for issues and contributions.

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.