You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: readme.markdown
+4-5
Original file line number
Diff line number
Diff line change
@@ -217,6 +217,10 @@ Create a subtest with a new test handle `st` from `cb(st)` inside the current
217
217
test `t`. `cb(st)` will only fire when `t` finishes. Additional tests queued up
218
218
after `t` will not be run until all subtests finish.
219
219
220
+
## t.comment(message)
221
+
222
+
Print a message without breaking the tap output. (Useful when using e.g. `tap-colorize` where output is buffered & `console.log` will print in incorrect order vis-a-vis tap output.)
223
+
220
224
## var htest = test.createHarness()
221
225
222
226
Create a new test harness instance, which is a function like `test()`, but with
@@ -226,11 +230,6 @@ By default the TAP output goes to `console.log()`. You can pipe the output to
226
230
someplace else if you `htest.createStream().pipe()` to a destination stream on
227
231
the first tick.
228
232
229
-
230
-
## test.comment(message)
231
-
232
-
Print a message without breaking the tap output. (Useful when using e.g. `tap-colorize` where output is buffered & `console.log` will print in incorrect order vis-a-vis tap output.)
233
-
234
233
## test.only(name, cb)
235
234
236
235
Like `test(name, cb)` except if you use `.only` this is the only test case
0 commit comments