Karma
karma-runner.github.io
- Free plan
- Windows
- macOS
- Linux
- Web
- iPhone and iPad
- Android
- Self-hosted
What Karma is
Karma is a JavaScript test runner that starts a web server, connects browsers, runs tests, and reports results to developers. It can watch configured files and rerun tests after changes. Plugins connect frameworks such as Jasmine, Mocha, and QUnit, along with preprocessors, reporters, and browser launchers. Documented launchers include Chrome, Firefox, Safari, PhantomJS, JSDOM, Opera, Internet Explorer, SauceLabs, and BrowserStack. A browser on another device on the same network, including a phone or tablet, can be captured by opening the Karma server URL. Karma runs on Node.js and is distributed as an npm package; the installation guide recommends installing it locally in a project. The documentation includes integration guides for Travis CI, Jenkins, and Semaphore CI. The project describes Karma as suited to local, multi-browser, save-triggered, and continuous-integration test runs, primarily for low-level unit testing. It is free MIT-licensed software, but deprecated: it does not accept new features or general bug fixes. Critical security fixes will continue until 12 months after Angular CLI's Web Test Runner support is marked stable.
Who it suits
Karma may suit developers who want to run JavaScript tests locally across browsers, rerun them on file changes, or use them in continuous integration. Its stated focus is low-level unit testing.
Good to know, and what to watch
- Runs tests in configured real browsers
- Reruns tests when watched files change
- Plugins connect multiple testing frameworks
- Free under the MIT license
- Deprecated and accepting no new features
- General bug fixes are not accepted
- Designed primarily for low-level unit testing
Plans
Every plan and priceKarma
Free plan
Getting started
- Open the Karma website and installation documentation
- Install Node.js for the project
- Install Karma locally as an npm package
- Add plugins for the testing framework, launcher, reporter, or preprocessor you need
- Configure browsers and test files
- Run Karma locally or connect it to a CI server
Limits to check
The free MIT-licensed plan is deprecated and receives no new features or general bug fixes. Critical security fixes continue only during the stated support period.
The Club's review
Overview
Karma is a Node.js JavaScript test runner that executes tests in connected browsers and reports the results. It best suits teams maintaining projects that already rely on browser-based unit testing, particularly where local reruns or CI runs are part of the workflow. Its browser and plugin support are useful, but deprecated status makes it a poor default for new projects.
Key features
Browser-based testing
Karma starts a web server, connects configured browsers, runs tests, and displays results. Documented launchers span Chrome, Firefox, Safari, PhantomJS, JSDOM, Opera, Internet Explorer, SauceLabs, and BrowserStack. That range can help teams check behavior across browser environments, though each option depends on the launcher and environment configured for the project. A browser on another device, such as a phone or tablet on the same network, can also be captured by visiting the Karma server URL.
Reruns and extensions
Karma watches configured files and reruns tests after a change, supporting a quick edit-and-check cycle. Plugins provide preprocessors, reporters, browser launchers, and framework adapters; documented adapters include Jasmine, Mocha, and QUnit. This modularity suits projects with specific testing needs, but teams must choose and maintain the components they use.
Local development and CI
Distributed as an npm package, Karma runs on Node.js, and its installation guide recommends installing it locally in a project. Documentation includes integration guides for Travis CI, Jenkins, and Semaphore CI. Karma supports component testing, coverage reporting, and parallel execution. Its stated scope is primarily low-level unit testing; the project recommends Protractor for high-level testing.
Maintenance constraint
Karma is deprecated and no longer accepts new features or general bug fixes. Critical security issues will still be triaged and fixed until 12 months after Angular CLI's Web Test Runner support is marked stable. That limited security commitment does not replace ongoing maintenance, so new adopters should weigh the risk of depending on software whose routine development has stopped.
Pricing
Karma is free and open source under the MIT license. Its Karma plan costs nothing, with no paid tier to unlock its browser, plugin, or testing capabilities. The practical trade-off is maintenance, not a subscription: users accept a deprecated project with no new features or general bug fixes.
Platforms
Karma runs on Node.js and is distributed through npm. It supports Linux, macOS, and Windows, as well as web, Android, iOS, and self-hosted environments. Actual browser execution depends on the launchers and environments configured for the project.
Who it's for
Karma is a reasonable fit for developers maintaining an existing Karma setup or needing local, multi-browser unit tests that rerun on save and can run in CI. Its plugin and launcher model gives those teams room to fit the runner to an established workflow. It is not a strong choice for teams starting a project that need continuing feature work and general bug fixes. It is also not positioned for high-level testing, for which the project recommends Protractor.
Pros and cons
Pros
- Runs tests in multiple browser environments: documented launchers include major browsers, emulated environments, and services such as SauceLabs and BrowserStack.
- Fits local and CI workflows: file watching reruns tests on changes, and integration guides cover Travis CI, Jenkins, and Semaphore CI.
- Extensible without a paid plan: framework adapters and other components are plugins, while the software is MIT-licensed and free.
Cons
- Deprecated: there will be no new features or general bug fixes, a significant concern for teams adopting it for long-lived projects.
- Primarily for low-level unit tests: it is not the project's recommendation for high-level testing.
- Configuration shapes browser coverage: launcher availability depends on the setup and environment a project maintains.
Alternatives
Consider Web Test Runner if you want a free option positioned around modern web development and browser-focused tools. Vitest is another free option, with no plan limits stated. Choose Rstest if a free, MIT-licensed JavaScript/TypeScript testing framework fits your needs. Mocha is a free open-source JavaScript test framework installed as a development dependency. Jest is a free alternative with no paid plans or usage limits stated on its official pages. Poku may suit projects seeking a free, MIT-licensed option with Node.js, Bun, and Deno support. For other choices, see JavaScript Testing Frameworks. Japa and Pure Test are also free alternatives.
Verdict
Karma makes sense chiefly for teams that need to keep an existing browser-based unit-testing workflow running: it combines multi-browser execution, file-change reruns, and CI guidance without a license cost. For a new project, its deprecated status is the decisive drawback; choose another runner if ongoing features and general bug fixes matter.
The verdict
Karma provides browser-based JavaScript test runs and plugin support, but its deprecated status is an important constraint. Teams considering it should account for the end of feature and general bug-fix work.
Questions people ask
How much does Karma cost?
Karma is free: its listed plan is free under the MIT license.
Which systems does Karma support?
The listing includes Android, iOS, Linux, macOS, self-hosted, web, and Windows. Karma itself runs on Node.js.
Which testing frameworks work with Karma?
Plugins are available for Jasmine, Mocha, QUnit, and other testing frameworks.
Can Karma run tests on another device?
Yes. A browser on another device on the same network can be captured by visiting the Karma server URL.
Is Karma still maintained?
Karma is deprecated and does not accept new features or general bug fixes. Critical security issues are covered during the stated support period.
What the maker publishes
- Automatic reruns
- Karma watches configured files and reruns tests when a file changes. source
- Browser launchers
- Documented launchers include Chrome, Firefox, Safari, PhantomJS, JSDOM, Opera, Internet Explorer, SauceLabs, and BrowserStack. source
- CI integrations
- The documentation provides integration guides for Travis CI, Jenkins, and Semaphore CI. source
- How it works
- Karma starts a web server, connects browsers, runs tests in them, and displays their results. source
- Installation
- Karma runs on Node.js, is distributed as an npm package, and the installation guide recommends installing it locally in the project. source
- License
- Karma is released under the MIT license. source
- Maintenance status
- Karma is deprecated and is not accepting new features or general bug fixes; critical security issues will still be triaged and fixed during the stated support period. source
- Manual device capture
- A browser on another device, including a phone or tablet on the same network, can be captured by visiting the Karma server URL. source
- Plugin model
- Preprocessors, reporters, browser launchers, and framework adapters are plugins that can be installed from npm or written for Karma. source
- Purpose
- Karma runs JavaScript tests in multiple real browsers and reports results to developers. source
- Security support period
- The repository says critical security fixes will continue until 12 months after Angular CLI's Web Test Runner support is marked stable. source
- Support
- The project directs questions to its mailing list or Gitter and says the issue tracker is for bug reports and feature discussions. source
- Testing frameworks
- Plugins are available for Jasmine, Mocha, QUnit, and other testing frameworks. source
- Testing scope
- The FAQ says Karma was primarily designed for low-level unit testing and recommends Protractor for high-level testing. source
- Who it is for
- The project describes Karma as useful for developers who want to run tests locally, in multiple browsers, on each save, or on a continuous integration server. source
Checked against the maker's pages on 29 Sept 2026.