GitHub/noVNC
1
0
Fork 0
mirror of https://github.com/novnc/noVNC.git synced 2026-06-08 21:34:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add info about ESLint

Samuel Mannehed
2020-05-01 16:26:49 +02:00
parent e25362a5dc
commit 7b3b87d720
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
Testing.md

@@ -25,4 +25,9 @@ The automatic tests require the Node Package Manager. On RPM systems, run `sudo
Writing Tests
=============
New tests should be written using the [Mocha](http://visionmedia.github.io/mocha/) test platform and the [Chai](http://chaijs.com/) assertion library. You do not need to do anything special to use these libraries in your tests. The tests should be placed in the `tests` directory, and should follow the naming convention of `test.whatever_it_is_you_are_testing.js`. There are several example tests to get you started.
New tests should be written using the [Mocha](http://visionmedia.github.io/mocha/) test platform and the [Chai](http://chaijs.com/) assertion library. You do not need to do anything special to use these libraries in your tests. The tests should be placed in the `tests` directory, and should follow the naming convention of `test.whatever_it_is_you_are_testing.js`. There are several example tests to get you started.
Linter
======
We use ESLint to analyze the JavaScript code to flag for style errors. The rules are specified in `.eslintrc`. All new code must pass the linter. To start the lint check run `npm run lint`.