JavaScript Gherkin HTML Shell CoffeeScript TypeScript LiveScript
Clone or download
Permalink
Failed to load latest commit information.
bin feat: remove `karma` binary in favor of karma-cli Nov 16, 2013
client feat(config): Add config option for browser socket timeout (#3102) Aug 13, 2018
common refactor: unify style of functions declarations Jun 14, 2018
context refactor: unify style of functions declarations Jun 14, 2018
docs feat(config): Add config option for browser socket timeout (#3102) Aug 13, 2018
lib fix(init): Support ChromeHeadless in `validateBrowser` (#3110) Aug 13, 2018
logo chore: add logo Jan 6, 2014
scripts chore(ci): pass expected path to validate-commit-msg Jul 10, 2017
static fix(debug-runner): support asynchronous tests in the debug runner Aug 25, 2017
tasks refactor: unify style of functions declarations Jun 14, 2018
test chore(deps): update mime -> 2.3.1 (#3107) Aug 9, 2018
.codeclimate.yml chore: Add .codeclimate.yml Jun 23, 2015
.eslintignore refactor(server): refactor bundleResource in lib/server.js (#3029) Jun 8, 2018
.eslintrc refactor: update eslint configuration (#3020) May 29, 2018
.gitattributes chore: do not change pdf files line endings Jul 16, 2013
.gitignore refactor(server): refactor bundleResource in lib/server.js (#3029) Jun 8, 2018
.mailmap chore: update @mgol's name in .mailmap Oct 25, 2017
.npmignore Revert "refactor(server): move compile step to first run" Feb 23, 2018
.travis.yml chore(ci): drop node 9 from travis tests (#3100) Aug 5, 2018
CHANGELOG.md docs(readme): update BREAKING CHANGES in CHANGELOG (#3109) Aug 10, 2018
CODE_OF_CONDUCT.md chore: Add code of conduct May 15, 2015
CONTRIBUTING.md docs(contributing): fix markdown syntax (broken link) Sep 13, 2016
ISSUE_TEMPLATE.md docs(gh): fix typos Aug 22, 2016
LICENSE chore(license): update year Jun 29, 2016
README.md docs(readme): update downloads badge to point to graph of downloads Mar 15, 2018
appveyor.yml chore: remove support for node 4, update log4js (#3082) Jul 25, 2018
config.tpl.coffee refactor(formatters): refactor formatters.js May 5, 2018
config.tpl.js refactor(formatters): refactor formatters.js May 5, 2018
config.tpl.ls refactor(formatters): refactor formatters.js May 5, 2018
config.tpl.ts refactor(formatters): refactor formatters.js May 5, 2018
credentials switch saucelabs credentials from voijta to karmarunnerbot Oct 12, 2015
gruntfile.js feat(grunt): run check_clean before starting release. (#2978) Apr 23, 2018
package.json chore: release v3.0.0 Aug 9, 2018
requirejs.config.tpl.coffee fix(init): Make the requirejs config template normalize paths Jun 18, 2015
requirejs.config.tpl.js refactor: Upgrade to eslint@2 Feb 18, 2016
thesis.pdf chore: add my thesis Jul 16, 2013
wallaby.js fix(deps): remove babel-core and babel call in wallaby. (#3044) Jun 20, 2018
yarn.lock chore(deps): update yarn.lock May 4, 2018

README.md

Karma

js-standard-style npm version npm downloads

Build Status Build Status Code Climate PRs Welcome Dependency Status devDependency Status

A simple tool that allows you to execute JavaScript code in multiple real browsers.

The main purpose of Karma is to make your test-driven development easy, fast, and fun.

Help and Support

For questions and support please use the mailing list or Gitter. The issue tracker is for bug reports and feature discussions only.

When should I use Karma?

  • You want to test code in real browsers.
  • You want to test code in multiple browsers (desktop, mobile, tablets, etc.).
  • You want to execute your tests locally during development.
  • You want to execute your tests on a continuous integration server.
  • You want to execute your tests on every save.
  • You love your terminal.
  • You don't want your (testing) life to suck.
  • You want to use Istanbul to automagically generate coverage reports.
  • You want to use RequireJS for your source files.

But I still want to use _insert testing library_

Karma is not a testing framework, nor an assertion library. Karma just launches an HTTP server, and generates the test runner HTML file you probably already know from your favourite testing framework. So for testing purposes you can use pretty much anything you like. There are already plugins for most of the common testing frameworks:

If you can't find an adapter for your favourite framework, don't worry and write your own. It's not that hard and we are here to help.

Which Browsers can I use?

All the major browsers are supported, if you want to know more see the browsers page.

Troubleshooting

See FAQ.

I want to use it. Where do I sign?

You don't need to sign anything but here are some resources to help you to get started...

Obligatory Screencast.

Every serious project has a screencast, so here is ours. Just click here and let the show begin.

Installation.

See installation.

Using it.

See configuration.

This is so great. I want to help.

Please, see contributing.

Why did you create this?

Throughout the development of AngularJS, we've been using JSTD for testing. I really think that JSTD is a great idea. Unfortunately, we had many problems with JSTD, so we decided to write our own test runner based on the same idea. We wanted a simple tool just for executing JavaScript tests that is both stable and fast. That's why we use the awesome Socket.io library and Node.js.

My boss wants a license. So where is it?

MIT License