зеркало из https://github.com/twbs/bootlint.git
cff261c4ca | ||
---|---|---|
.. | ||
fixtures | ||
lib | ||
README.md | ||
bootlint_test.js | ||
location_index_test.js | ||
www-test.sh |
README.md
How does Bootlint's test suite work?
/test/fixtures/
contains the HTML test case files./test/lib/
contains third-party testing-related code for the browser environment (jQuery and QUnit)
To test usage in a Node.js environment, Nodeunit tests are defined in /test/bootlint_test.js
, and can be run via the nodeunit
Grunt task.
To test usage in a browser environment, we use QUnit along with some additional automation in /test/fixtures/generic-qunit.js
. Basically, when PhantonJS runs each test case webpage, we automatically Bootlint the page and then assert that the list of lint messages equals the data-lint
attributes of the <li>
s under the <ol id="bootlint">
within the page. The qunit
Grunt task runs these tests in PhantonJS.
How do I add a new test?
- Copy the
/test/fixtures/doctype/html5-normal.html
test case to a new file. - Add the HTML of your new testcase into the new file.
- For each lint message you expect Bootlint to emit, add an
<li>
under the<ol id="bootlint">
in the file, and add adata-lint
attribute to the<li>
with the lint message string as the value (see existing tests for examples). - In
/test/bootlint_test.js
, add a corresponding Nodeunit test that uses your new test case file. (Yes, this involves duplicating the expected lint messages.) - Run
grunt test
to see the results of your newly-added test.