Jasmine vs Pure Test

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.

Pure Test is a free, minimal test runner for projects using JavaScript runtimes and browsers. It supports Node.js, Deno, Bun, Cloudflare Workers, and browsers, and its API includes test suites, assertions, lifecycle hooks, spies, fake timers, and retry and timeout options. The CLI provides multiple reporters, test filters, file watching, sharding, and fail-fast execution. For CI, `--shard` splits test files across jobs and exits cleanly when a shard has no files. TypeScript test discovery requires `--ts` on Node.js; it is automatic on Deno and Bun. A Deno adapter registers tests as `Deno.test()` calls for use with `deno test` and its filtering and IDE workflows. The README includes migration guides for Jest and Vitest and notes compatibility with common mock methods. Pure Test does not isolate tests, so lifecycle hooks are recommended for managing state. The project is beta, and its APIs may change. It is Apache-2.0 licensed, with no paid plans stated.