Google Git
Sign in
cobalt / cobalt / 08336faa599332e3e3bf29b7ad38ef023018b55e / . / third_party / devtools / node_modules / karma
tree: 5a626c38f0d8efbf8d91e1974eeea988b7447ae8 [path history] [tgz]
  1. bin/
  2. common/
  3. context/
  4. lib/
  5. scripts/
  6. static/
  7. appveyor.yml
  8. CHANGELOG.md
  9. CODE_OF_CONDUCT.md
  10. config.tpl.coffee
  11. config.tpl.js
  12. config.tpl.ls
  13. config.tpl.ts
  14. gruntfile.js
  15. ISSUE_TEMPLATE.md
  16. LICENSE
  17. package.json
  18. PULL_REQUEST_TEMPLATE.md
  19. README.md
  20. requirejs.config.tpl.coffee
  21. requirejs.config.tpl.js
  22. wallaby.js
  23. yarn.lock
third_party/devtools/node_modules/karma/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