diff options
| author | Bardi Harborow <bardi@bardiharborow.com> | 2016-10-03 19:55:59 +0300 |
|---|---|---|
| committer | Mark Otto <markd.otto@gmail.com> | 2016-10-03 19:55:59 +0300 |
| commit | 2e69dfa8c1679238579ef6f5ec85deb755e4fb6d (patch) | |
| tree | 57ac7cd1aeef5d78895f7a631155ce746fc0c43b /js/tests/README.md | |
| parent | db533c2e8d950647ff5e884083bf2d72063ed4b0 (diff) | |
Fix broken/redirected links, moving to HTTPS where possible. (#20557)
Diffstat (limited to 'js/tests/README.md')
| -rw-r--r-- | js/tests/README.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/js/tests/README.md b/js/tests/README.md index 6cdb41059b..b2d505723b 100644 --- a/js/tests/README.md +++ b/js/tests/README.md @@ -1,6 +1,6 @@ ## How does Bootstrap's test suite work? -Bootstrap uses [QUnit](http://api.qunitjs.com/), a powerful, easy-to-use JavaScript unit test framework. Each plugin has a file dedicated to its tests in `unit/<plugin-name>.js`. +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/<plugin-name>.js`. * `unit/` contains the unit test files for each Bootstrap plugin. * `vendor/` contains third-party testing-related code (QUnit and jQuery). @@ -14,7 +14,7 @@ To run the unit test suite via a real web browser, open `index.html` in the brow ## 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/<plugin-name>.js`). -2. Review the [QUnit API Documentation](http://api.qunitjs.com/) and use the existing tests as references for how to structure your new tests. +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 `grunt test-js` to see the results of your newly-added test(s). @@ -24,7 +24,7 @@ To run the unit test suite via a real web browser, open `index.html` in the brow * 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`](http://api.qunitjs.com/expect/) to ensure that the expected assertions are run. +* Each test should begin with [`assert.expect`](https://api.qunitjs.com/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 |