bootlint/test
Chris Rebert 4ca3c1bba3 Merge pull request #194 from twbs/fix-163
warn about outdated versions of Bootstrap
2014-12-16 15:30:25 -08:00
..
fixtures Merge pull request #194 from twbs/fix-163 2014-12-16 15:30:25 -08:00
lib Bump jQuery to v2.1.1 in tests. 2014-09-25 11:57:49 +03:00
README.md Fixes #106 2014-10-06 20:03:24 -07:00
bootlint_test.js Merge pull request #194 from twbs/fix-163 2014-12-16 15:30:25 -08:00
location_index_test.js update ESLint config and update JS style accordingly 2014-12-15 15:51:29 -08:00
www-test.sh don't leak a server process in the test script 2014-11-03 20:01:08 -08:00

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?

  1. Copy the /test/fixtures/doctype/html5-normal.html test case to a new file.
  2. Add the HTML of your new testcase into the new file.
  3. For each lint message you expect Bootlint to emit, add an <li> under the <ol id="bootlint"> in the file, and add a data-lint attribute to the <li> with the lint message string as the value (see existing tests for examples).
  4. 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.)
  5. Run grunt test to see the results of your newly-added test.