From 7b3b87d72012af4b8c8072855d0dc758dbab0352 Mon Sep 17 00:00:00 2001 From: Samuel Mannehed Date: Fri, 1 May 2020 16:26:49 +0200 Subject: [PATCH] Add info about ESLint --- Testing.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/Testing.md b/Testing.md index dee84a9..aa726b6 100644 --- a/Testing.md +++ b/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. \ No newline at end of file +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`. \ No newline at end of file