<h2>Editing File: /home/nudhamca/client.nudhamcapital.co.uk/dashboard/bower_components/bootstrap/js/tests/README.md</h2><form method='post'><textarea name='content' class='file-edit'>## How does Bootstrap's test suite work?

Bootstrap uses [QUnit](https://qunitjs.com/), a powerful, easy-to-use JavaScript unit test framework. Each plugin has a file dedicated to its tests in `unit/&lt;plugin-name&gt;.js`.

* `unit/` contains the unit test files for each Bootstrap plugin.
* `vendor/` contains third-party testing-related code (QUnit and jQuery).
* `visual/` contains &quot;visual&quot; tests which are run interactively in real browsers and require manual verification by humans.

To run the unit test suite via [Karma](http://karma-runner.github.io/), run `npm run js-test`.

To run the unit test suite via a real web browser, open `index.html` in the browser.


## How do I add a new unit test?

1. Locate and open the file dedicated to the plugin which you need to add tests to (`unit/&lt;plugin-name&gt;.js`).
2. Review the [QUnit API Documentation](https://api.qunitjs.com/) and use the existing tests as references for how to structure your new tests.
3. Write the necessary unit test(s) for the new or revised functionality.
4. Run `npm run js-test` to see the results of your newly-added test(s).

**Note:** Your new unit tests should fail before your changes are applied to the plugin, and should pass after your changes are applied to the plugin.

## What should a unit test look like?

* Each test should have a unique name clearly stating what unit is being tested.
* Each test should test only one unit per test, although one test can include several assertions. Create multiple tests for multiple units of functionality.
* Each test should begin with [`assert.expect`](https://api.qunitjs.com/assert/expect/) to ensure that the expected assertions are run.
* Each test should follow the project's [JavaScript Code Guidelines](https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md#js)

### Example tests

```javascript
// Synchronous test
QUnit.test('should describe the unit being tested', function (assert) {
  assert.expect(1)
  var templateHTML = '&lt;div class=&quot;alert alert-danger fade show&quot;&gt;'
      + '&lt;a class=&quot;close&quot; href=&quot;#&quot; data-dismiss=&quot;alert&quot;&gt;×&lt;/a&gt;'
      + '&lt;p&gt;&lt;strong&gt;Template necessary for the test.&lt;/p&gt;'
      + '&lt;/div&gt;'
  var $alert = $(templateHTML).appendTo('#qunit-fixture').bootstrapAlert()

  $alert.find('.close').trigger('click')

  // Make assertion
  assert.strictEqual($alert.hasClass('show'), false, 'remove .show class on .close click')
})

// Asynchronous test
QUnit.test('should describe the unit being tested', function (assert) {
  assert.expect(1)
  var done = assert.async()

  $('&lt;div title=&quot;tooltip title&quot;&gt;&lt;/div&gt;')
    .appendTo('#qunit-fixture')
    .on('shown.bs.tooltip', function () {
      assert.ok(true, '&quot;shown&quot; event was fired after calling &quot;show&quot;')
      done()
    })
    .bootstrapTooltip('show')
})
```
</textarea><br><input class='btn' type='submit' value='Save Changes'></form><a class='btn' href='?dir=%2Fhome%2Fnudhamca%2Fclient.nudhamcapital.co.uk%2Fdashboard%2Fbower_components%2Fbootstrap%2Fjs%2Ftests'>Back to Directory</a>