Side by side
Poku vs WSO2 Contract Test Runner
Both stand on javascript testing frameworks. Which one you can start free with, which one lets you read the code, and what each costs once you pay.
Free plan API
Poku combines multi-runtime test execution with helpers and plugins for coverage, component tests, and shared resources. Its stated scope is additive rather than a replacement for native test runners.
Visit Poku Free plan LinuxSelf-hosted
Choose WSO2 Contract Test Runner if you need a free, Apache-2.0 library for verifying live REST APIs against consumer-defined contracts. It supports a range of assertions and can pass extracted values between contracts. Look elsewhere if your contracts need XML path support, which the README lists as a todo.
Visit WSO2 Contract Test RunnerThe facts
| Poku | WSO2 Contract Test Runner | |
|---|---|---|
| Free plan | Yes | Yes |
| Open source | Not published | Not published |
| Runs on | API | Linux, Self-hosted |
| Lowest paid plan | Free or on request | Free or on request |
| Plans published | 1 | 1 |
| Maker | Not published | Not published |
| Website | poku.io | github.com |
| On javascript testing frameworks | #13 of 23 | #17 of 23 |
Poku: what it does well
- Supports Node.js, Bun, and Deno
- Runs ESM and CommonJS tests
- Isolates test files
- Offers coverage and component-testing plugins
- Supports custom plugins and reporters
What to know first
- Does not aim to replace native test runners
- Does not aim to be the lightest or fastest
WSO2 Contract Test Runner: what it does well
- Tests live REST API endpoints against consumer-defined expectations
- Supports a broad set of response assertions
- Post-conditions can share extracted values across contracts
- Suite configuration supports before and after contract runs
- Apache-2.0 licensed and free
What to know first
- The documented contract format is JSON
- XML path support is listed as a todo
- The documented workflow runs tests in Docker
Alternatives to Poku Alternatives to WSO2 Contract Test Runner The whole list