Inserted images
Chris committed
Jul 17, 2017 at 18:15 UTC
00d0aad3c23e871eaf83749b3a01585ab7c70a72
1 file changed
+14
-3
tests/README.md
+14
-3
@@ -86,8 +86,15 @@ I haven't figured out yet how to switch to newer 2.6 versions. So it may contain
86
87
## In WebStorm
88
89
+### Karma
90
Just run the configured run configurations and they produce nice test trees:
91
92
+
93
+
94
+### node.js
95
+
96
+Debugging is awesome too!
97
+
98
99
## From CLI
100
@@ -101,7 +108,7 @@ nodejs ./node_modules/karma/bin/karma start tests/web/karma.conf.js --single-run
108
will start the karma server, start chromium in headless mode and exit.
109
110
If a test fails, it produces even a stack trace:
104
-
111
+
112
113
### Node.d plugins
114
@@ -112,7 +119,7 @@ nodejs node_modules/jasmine-node/bin/jasmine-node --captureExceptions tests/node
119
```
120
121
will run the tests in `tests/node.d` and produce a stacktrace too on error:
115
-
122
+
123
124
## Coverage
125
@@ -120,6 +127,10 @@ will run the tests in `tests/node.d` and produce a stacktrace too on error:
127
128
A nice HTML is produced from Karma which shows which code paths were executed. It is located somewhere in `/path/to/your/netdata/coverage/`
129
130
+
131
+and
132
+
133
+
134
### Node.d
135
136
Apparently, jasmine-node can produce a junit report with the `--junitreport` flag. But that output was not very useful. Maybe it's configurable?
@@ -128,4 +139,4 @@ Apparently, jasmine-node can produce a junit report with the `--junitreport` fla
139
140
The karma and node.d runners can be integrated in Travis (AFAIK), but that is outside my ability.
141
131
-Note: Karma is for browser-testing. On a build server, no GUI or browser might by available, unless browsers support headless mode.
\ No newline at end of file
142
+Note: Karma is for browser-testing. On a build server, no GUI or browser might by available, unless browsers support headless mode.