diff options
| author | Promise Akpan <akpanpromise@hotmail.com> | 2019-08-15 12:06:39 +0100 |
|---|---|---|
| committer | Chris Akritidis <43294513+cakrit@users.noreply.github.com> | 2019-08-15 13:06:39 +0200 |
| commit | f5006d51e8caf9148d393eb68d53dc9fcd28b7b6 (patch) | |
| tree | 03b757236d6b45e46813a4a875c77dc775e5f896 /tests | |
| parent | 69172fd57472df75d877f43de2dcc693c48ab5c0 (diff) | |
Fix Markdown Lint warnings (#6664)
* make remark access all directories
* detailed fix after autofix by remark lint
* cross check autofix for this set of files
* crosscheck more files
* crosschecking and small fixes
* crosscheck autofixed md files
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/README.md | 56 | ||||
| -rw-r--r-- | tests/health_mgmtapi/README.md | 4 |
2 files changed, 31 insertions, 29 deletions
diff --git a/tests/README.md b/tests/README.md index 4ac3f2105a..fe8b8b2036 100644 --- a/tests/README.md +++ b/tests/README.md @@ -1,4 +1,5 @@ # Testing + This readme is a manual on how to get started with unit testing on javascript and nodejs Original author: BrainDoctor (github), July 2017 @@ -24,10 +25,10 @@ Other browsers work too (Chrome, Firefox). However, only the Chromium Browser 59 The commands above leave me with the following versions (July 2017): - - nodejs: v4.2.6 - - npm: 3.5.2 - - chromium-browser: 59.0.3071.109 - - WebStorm (optional): 2017.1.4 +- nodejs: v4.2.6 +- npm: 3.5.2 +- chromium-browser: 59.0.3071.109 +- WebStorm (optional): 2017.1.4 ## Configuration @@ -46,22 +47,24 @@ If you use the JetBrains WebStorm IDE, you can integrate the karma runtime. #### for Karma (Client side testing) Headless Chromium: -1. Run > Edit Configurations -2. "+" > Karma -3. - Name: Karma Headless Chromium - - Configuration file: /path/to/your/netdata/tests/web/karma.conf.js - - Browsers to start: ChromiumHeadless - - Node interpreter: /usr/bin/nodejs (MUST be absolute, NVM works too) - - Karma package: /path/to/your/netdata/node_modules/karma + +1. Run > Edit Configurations +2. "+" > Karma +3. - Name: Karma Headless Chromium + - Configuration file: /path/to/your/netdata/tests/web/karma.conf.js + - Browsers to start: ChromiumHeadless + - Node interpreter: /usr/bin/nodejs (MUST be absolute, NVM works too) + - Karma package: /path/to/your/netdata/node_modules/karma GUI Chromium is similar: -1. Run > Edit Configurations -2. "+" > Karma -3. - Name: Karma Chromium - - Configuration file: /path/to/your/netdata/tests/web/karma.conf.js - - Browsers to start: Chromium - - Node interpreter: /usr/bin/nodejs (MUST be absolute, NVM works too) - - Karma package: /path/to/your/netdata/node_modules/karma + +1. Run > Edit Configurations +2. "+" > Karma +3. - Name: Karma Chromium + - Configuration file: /path/to/your/netdata/tests/web/karma.conf.js + - Browsers to start: Chromium + - Node interpreter: /usr/bin/nodejs (MUST be absolute, NVM works too) + - Karma package: /path/to/your/netdata/node_modules/karma You may add other browsers too (comma separated). With the "Browsers to start" field you can override any settings in karma.conf.js. @@ -69,18 +72,19 @@ Also it is recommended to install WebStorm IDE Extension/Addon to Chrome/Chromiu #### for node.d plugins (nodejs) -1. Run > Edit Configurations -2. "+" > Node.js -3. - Name: Node.d plugins - - Node interpreter: /usr/bin/nodejs (MUST be absolute, NVM works too) - - JavaScript file: node_modules/jasmine-node/bin/jasmine-node - - Application parameters: --captureExceptions tests/node.d +1. Run > Edit Configurations +2. "+" > Node.js +3. - Name: Node.d plugins + - Node interpreter: /usr/bin/nodejs (MUST be absolute, NVM works too) + - JavaScript file: node_modules/jasmine-node/bin/jasmine-node + - Application parameters: --captureExceptions tests/node.d ## Running ### In WebStorm #### Karma + Just run the configured run configurations and they produce nice test trees:  @@ -99,6 +103,7 @@ cd /path/to/your/netdata nodejs ./node_modules/karma/bin/karma start tests/web/karma.conf.js --single-run=true --browsers=ChromiumHeadless ``` + will start the karma server, start chromium in headless mode and exit. If a test fails, it produces even a stack trace: @@ -135,5 +140,4 @@ The karma and node.d runners can be integrated in Travis (AFAIK), but that is ou Note: Karma is for browser-testing. On a build server, no GUI or browser might by available, unless browsers support headless mode. - -[]() +[](<>) diff --git a/tests/health_mgmtapi/README.md b/tests/health_mgmtapi/README.md index 8473b35eab..c74e035364 100644 --- a/tests/health_mgmtapi/README.md +++ b/tests/health_mgmtapi/README.md @@ -7,6 +7,4 @@ The script can be executed with options to prepare the system for the tests, run It depends on the management API being accessible on localhost:19999 and on the responses to the api/v1/alarms?all requests being functional. It also requires read access to the management API key that is usually under `/var/lib/netdata/netdata.api.key` (`@varlibdir_POST@/netdata.api.key`). -[]() - - +[](<>) |