Jasmine

Overview

Jasmine is a JavaScript testing framework for browser and Node.js code. It is best suited to developers who want a self-contained framework with configurable browser and Node test workflows.

Key features

Specs are written in JavaScript using describe and it blocks with expect matchers. The jasmine-core package has no external dependencies, and Jasmine does not rely on other JavaScript frameworks, so it can add a testing layer without requiring a broader framework choice.

For browser testing, jasmine-browser-runner supports interactive runs and CI through headless Chrome or Sauce Labs, and can connect to a user's own Selenium Grid for remote browsers. The standalone distribution runs specs directly in a browser without other tools or a web server, a practical option for small or self-contained checks.

Node projects can install Jasmine locally with npm and invoke it using npx jasmine. Node setup supports ES modules and CommonJS. Configurable runners, custom reporters and matchers, randomized spec order, parallel execution and built-in mocks give teams meaningful control over how tests run. Jasmine supports JavaScript and TypeScript, but not parameterized cases.

Pricing

Jasmine is free and open source under the MIT License. Its plan costs nothing, with no usage limits stated; there is no free trial because the software is already free. There are no paid tiers or seat quotas to weigh, making it suitable for individual developers and teams that want to adopt it without a software license charge.

Platforms

Jasmine supports Linux, macOS, Windows and the web, with browser and Node.js execution paths. Platform support follows a rolling window: older platforms may receive best-effort support or be dropped in minor releases. Teams tied to legacy environments should check compatibility before standardizing on it.

Who it's for

Jasmine is a strong fit for JavaScript and TypeScript developers who want browser and Node testing in one framework, particularly when independence from other JavaScript frameworks and customizable runners matter. Its no-server standalone browser option also suits lightweight checks. It is less suitable for teams that need parameterized test cases or depend on long-term support for older platforms.

Pros and cons

• Pro: The core package has no external dependencies and does not depend on other JavaScript frameworks, keeping the framework choice focused.
• Pro: Browser, Node, standalone and remote-grid options cover varied local and CI workflows.
• Pro: Custom runners, reporters, matchers and randomized order let teams shape execution and reporting.
• Con: Parameterized cases are not supported, which limits teams that want to express test variations in that form.
• Con: Rolling platform support can leave older environments on best-effort support or without support after a minor release.
• Con: The unmaintained karma-jasmine adapter depends on jasmine-core 4.x, so newer Jasmine features may not work through it.

Alternatives

JavaScript Testing Frameworks and Unit Testing Frameworks are useful starting points for comparing tools across those categories.

Choose Karma only if its existing setup is important: it is deprecated and receives no new features or general bug fixes, while Jasmine's karma-jasmine adapter is also unmaintained and limited to jasmine-core 4.x.

QUnit is another free, open-source JavaScript testing framework, distributed through CDN, npm and Yarn. Web Test Runner is an alternative for teams looking for browser-focused web development tools and guides.

Cucumber.js is available as an npm development dependency. Pure Test is a free, open-source option under Apache-2.0. Vitest is free and open source, with no plan limits stated.

Testem is a free, MIT-licensed JavaScript test runner. Mocha is a free, open-source JavaScript test framework installed as a development dependency.

Verdict

Choose Jasmine if you want a free, framework-independent way to test JavaScript across browser and Node.js workflows, with runners and reporting you can customize. Look elsewhere if parameterized cases are essential, your platforms need stable long-term support, or your workflow depends on newer features through karma-jasmine.