Skip to content

karma-runner/karma-qunit

master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
lib
 
 
src
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

karma-qunit

npm version Build Status js-standard-style npm downloads

Adapter for the QUnit testing framework.

Installation

The easiest way is to keep karma-qunit as a devDependency in your package.json by running

npm install karma-qunit --save-dev

Configuration

Add qunit in the frameworks array in your karma.conf.js file. Then, in the plugins array, add karma-qunit. The following code shows the default configuration:

// karma.conf.js
module.exports = function (config) {
  config.set({
    frameworks: ['qunit'],
    plugins: ['karma-qunit'],
    files: [
      '*.js'
    ]
  })
}

You can also pass options for QUnit.config (documented here) as such:

/// karma.conf.js
module.exports = function (config) {
  config.set({
    frameworks: ['qunit'],
    plugins: ['karma-qunit'],
    files: [
      '*.js'
    ],

    // client configuration
    client: {
      clearContext: false,
      qunit: {
        showUI: true,
        testTimeout: 5000
      }
    }
  })
}

Note: showUI: true needs the clearContext: false option to display correctly in non-debug mode.


For more information on Karma see the homepage. If you're using karma-qunit to test Ember.js, you might find Karma's Ember guide helpful.