Skip to content
This repository has been archived by the owner on Sep 24, 2024. It is now read-only.

loftyduck/karma

Folders and files

NameName
Last commit message
Last commit date

Latest commit

a85cfd6 · May 14, 2024
Nov 16, 2013
Aug 22, 2017
Mar 10, 2017
Mar 21, 2017
Sep 6, 2017
Jun 26, 2017
Jan 6, 2014
Jul 10, 2017
Aug 25, 2017
Jun 7, 2015
Oct 25, 2017
Mar 31, 2017
Jun 23, 2015
Jun 8, 2015
Feb 18, 2016
Jul 16, 2013
Mar 19, 2017
Oct 25, 2017
Nov 16, 2016
Sep 6, 2017
May 6, 2017
May 15, 2015
Sep 13, 2016
Aug 22, 2016
Jun 29, 2016
Mar 15, 2017
Jul 24, 2017
Dec 17, 2015
Dec 17, 2015
Dec 17, 2015
Jul 2, 2016
Oct 12, 2015
Jul 19, 2017
May 14, 2024
Jun 18, 2015
Feb 18, 2016
Jul 16, 2013
Jun 26, 2016

Repository files navigation

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

About

Spectacular Test Runner for JavaScript

Resources

License

Code of conduct

Stars

Watchers

Forks

Packages

No packages published

Languages

  • JavaScript 91.6%
  • Gherkin 5.0%
  • HTML 1.8%
  • Shell 0.5%
  • CoffeeScript 0.5%
  • TypeScript 0.3%
  • LiveScript 0.3%