Skip to content

Commit cb06704

Browse files
committed
reversed stance on testing. totally agree testing should use solid jshint rules
1 parent 0dd7261 commit cb06704

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2010,9 +2010,9 @@ Unit testing helps maintain clean code, as such I included some of my recommenda
20102010
20112011
*Why?*: Tests are code. JSHint can help identify code quality issues that may cause the test to work improperly.
20122012
2013-
- **Alleviate JSHint Rules on Tests**: Relax the rules on your test code.
2013+
- **Alleviate Globals for JSHint Rules on Tests**: Relax the rules on your test code to allow for common globals such as `describe` and `expect`.
20142014
2015-
*Why?*: Your tests won't be run by your end users and do not require as strenuous of code quality rules. Global variables, for example, can be relaxed by including this in your test specs.
2015+
*Why?*: Your tests are code and require the same attention and code quality rules as all of your production code. However, global variables used by the testing framework, for example, can be relaxed by including this in your test specs.
20162016
20172017
```javascript
20182018
/*global sinon, describe, it, afterEach, beforeEach, expect, inject */

0 commit comments

Comments
 (0)