Added documentation on how to specify the reporter for browser mocha #4026

Lindsay-Needs-Sleep · 2019-09-23T11:22:32Z

Description of the Change

Update documentation to include usage instructions on how to specify the reporter for browser tests.

This was absent, despite hinting that it could be done. It took quite awhile of digging through source to figure out how this could be correctly. This information should be available.

Alternate Designs

Thought about not including the list of possible strings, but decided I should because otherwise people will have to guess on that front as well.

Why should this be in core?

Because it's documentation.

Benefits

Save people time and frustration.

Possible Drawbacks

None.

Applicable issues

Issue #1592

jsf-clabot · 2019-09-23T11:22:34Z

All committers have signed the CLA.

juergba · 2019-09-23T12:39:52Z

I guess the standard way to configure options, is using mocha.setup() as described some lines above:
mocha.setup ( {reporter: 'html'} )

I don't use Mocha in the browser, but I doubt the reporter lists is correct for browser usage.

Lindsay-Needs-Sleep · 2019-09-23T19:58:50Z

Okay!
I'll try that out tomorrow and modify the documentation to match.

I'll try out a couple other reporters and see if they work. All the ones I listed are included in mocha.js. So it would seem that they technically should work (why include broken things). I'll file a bug if they don't.

I haven't dug around too much yet. Do you happen to know if mocha.js is exclusively for the browser? (I guess that is pretty relevant to which reporters are loaded by mocha.js!)

Lindsay-Needs-Sleep · 2019-09-24T23:36:27Z

@juergba You are absolutely right! Thank you for the feedback!

I didn't realize this was how to do it correctly since the documentation on options for the browser is a bit sparse. So I added to the options documentation a bit instead.

I also tested all the available builtin reporters. They all "worked", (aka. none of them caused a failure). Most of the time the output was legible. I removed the list of reporters and put a link instead, (as they all basically correspond directly to the reporters list).

Lindsay-Needs-Sleep · 2019-09-24T23:37:44Z

(Also not sure why the travis-ci build would fail when it is just documentation updates). I ran npm test, it all passed.

coveralls · 2019-09-25T00:07:42Z

Coverage increased (+0.07%) to 92.779% when pulling 2ac64f9 on Lindsay-Needs-Sleep:master into f78e21f on mochajs:master.

docs/index.md

juergba · 2019-10-01T13:04:12Z

I agree that the browser part of our docu is suboptimal. But again I have doubts about your changes.

The option list is not the actual one of the master branch, the Mocha constructor I guess.
Are you sure all these options do work in the browser?

What about the grep, probably also fgrep?

The browser may use the --grep as functionality. Append a query-string to your URL: ?grep=api.

What about color? invert is a CLI option?
Aren't the test files added manually to the browser, so file loading options do work only via CLI?

Lindsay-Needs-Sleep · 2019-10-04T08:40:04Z

@juergba I just took the documentation from the code (lib/mocha.js I believe).

But, good piont. I did not test each option. So I guess it's technically better to have no documentation than have documentation that indicates non-existent/non-working functionality. I have removed the parts I did not personally test.

You were right about color. The documentation in the code was incorrect, it is not "color" but "useColors". I have updated that. And I did just test out useColors out of curiorsity:

useColors: false (reporter: spec)

useColors: true (reporter: spec)

Lindsay-Needs-Sleep · 2019-10-08T03:27:42Z

I have removed the changes to the reporters' names documentation.
That can be addressed in Issue #4054.

This change only includes some minor improvements to the browser documentation.

juergba · 2019-10-10T08:00:37Z

Ok, let's make a last effort and finish this PR.

color / useColors:
the corresponding CLI option is color (with aliases c, colors), therefore the Mocha constructor should also accept an option color (the canonical name, no alias). There have been changes to the Mocha constructor a few weeks ago, in our master branch which is not published yet. Maybe you haven't tested with the master version of ./mocha.js. Anyway I didn't expect color to have an effect in the browser.

Add the options diff and inlineDiffs to your option list, they should also work in browser.

Please also add a comment that not all CLI options are supported in the browser, with a link to the CLI options. For the browser setup the camel-cased option names have to be used, eg. checkLeaks instead of check-leaks.

juergba · 2019-10-10T08:01:18Z

docs/index.md

+```text
+reporter       {string|constructor} -  Reporter** name or constructor.
+ui             {string}             -  Interface name.
+useColors      {boolean}            -  Use color TTY output from reporter?


it should be color

juergba · 2019-10-10T08:01:43Z

docs/index.md

+Some available options:
+
+```text
+reporter       {string|constructor} -  Reporter** name or constructor.


please remove those **

juergba · 2019-10-10T08:02:41Z

lib/mocha.js

 * @param {Object} [options.reporterOption] - Reporter settings object.
 * @param {number} [options.retries] - Number of times to retry failed tests.
 * @param {number} [options.slow] - Slow threshold value.
 * @param {number|string} [options.timeout] - Timeout threshold value.
 * @param {string} [options.ui] - Interface name.
+ * @param {boolean} [options.useColors] - Use color TTY output from reporter?


it should be color

Lindsay-Needs-Sleep · 2019-10-10T21:58:14Z

@juergba Sure, I can go through those changes in a couple days. (I just have some very urgent work deadlines that I need to finish first. T.T)

Lindsay-Needs-Sleep · 2019-10-12T00:32:16Z

I added diff and inlineDiffs. I tried them out as well. Nothing broke (after my changes). But I didn't see anything different. What are they supposed to do?

Lindsay-Needs-Sleep · 2019-10-12T00:44:37Z

Also, changing the options to use color instead of useColors caused this[opt](opts[opt]); to break:

    mocha.setup = function(opts) {
      if (typeof opts === 'string') {
        opts = {ui: opts};
      }
      for (var opt in opts) {
        if (opts.hasOwnProperty(opt)) {
          this[opt](opts[opt]);
        }
      }
      return this;
    };

So I also changed:

Mocha.prototype.useColors = function(colors) {

to:

Mocha.prototype.color = function(colors) {

I had do similar changes for diff and inlineDiffs.

This caused these tests to fail:

1) Mocha
       constructor
         "before each" hook for "should not attempt to set timeout":
     TypeError: Cannot stub non-existent own property useInlineDiffs
      at Sandbox.stub (node_modules\sinon\lib\sinon\sandbox.js:308:19)
      at Context.<anonymous> (test\unit\mocha.spec.js:23:15)
      at callFn (lib\runnable.js:386:21)
      at Hook.Runnable.run (lib\runnable.js:373:7)
      at next (lib\runner.js:384:10)
      at Immediate.<anonymous> (lib\runner.js:421:5)

  2) Mocha
       #hideDiff()
         should set the diff option to false when param equals true:
     TypeError: mocha.hideDiff is not a function
      at Context.<anonymous> (test\unit\mocha.spec.js:230:13)
      at callFn (lib\runnable.js:386:21)
      at Test.Runnable.run (lib\runnable.js:373:7)
      at Runner.runTest (lib\runner.js:534:10)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:652:12
      at next (lib\runner.js:443:14)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:453:7
      at next (lib\runner.js:362:14)
      at Immediate.<anonymous> (lib\runner.js:421:5)

  3) Mocha
       #hideDiff()
         should set the diff option to true when param equals false:
     TypeError: mocha.hideDiff is not a function
      at Context.<anonymous> (test\unit\mocha.spec.js:236:13)
      at callFn (lib\runnable.js:386:21)
      at Test.Runnable.run (lib\runnable.js:373:7)
      at Runner.runTest (lib\runner.js:534:10)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:652:12
      at next (lib\runner.js:443:14)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:453:7
      at next (lib\runner.js:362:14)
      at Immediate.<anonymous> (lib\runner.js:421:5)

  4) Mocha
       #hideDiff()
         should set the diff option to true when the param is undefined:
     TypeError: mocha.hideDiff is not a function
      at Context.<anonymous> (test\unit\mocha.spec.js:242:13)
      at callFn (lib\runnable.js:386:21)
      at Test.Runnable.run (lib\runnable.js:373:7)
      at Runner.runTest (lib\runner.js:534:10)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:652:12
      at next (lib\runner.js:443:14)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:453:7
      at next (lib\runner.js:362:14)
      at Immediate.<anonymous> (lib\runner.js:421:5)

  5) Mocha
       #hideDiff()
         should be chainable:
     TypeError: mocha.hideDiff is not a function
      at Context.<anonymous> (test\unit\mocha.spec.js:248:20)
      at callFn (lib\runnable.js:386:21)
      at Test.Runnable.run (lib\runnable.js:373:7)
      at Runner.runTest (lib\runner.js:534:10)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:652:12
      at next (lib\runner.js:443:14)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:453:7
      at next (lib\runner.js:362:14)
      at Immediate.<anonymous> (lib\runner.js:421:5)

  6) Mocha
       #useColors()
         should set the color option to true:
     TypeError: mocha.useColors is not a function
      at Context.<anonymous> (test\unit\mocha.spec.js:358:13)
      at callFn (lib\runnable.js:386:21)
      at Test.Runnable.run (lib\runnable.js:373:7)
      at Runner.runTest (lib\runner.js:534:10)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:652:12
      at next (lib\runner.js:443:14)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:453:7
      at next (lib\runner.js:362:14)
      at Immediate.<anonymous> (lib\runner.js:421:5)

  7) Mocha
       #useColors()
         should not create the color property:
     TypeError: mocha.useColors is not a function
      at Context.<anonymous> (test\unit\mocha.spec.js:364:13)
      at callFn (lib\runnable.js:386:21)
      at Test.Runnable.run (lib\runnable.js:373:7)
      at Runner.runTest (lib\runner.js:534:10)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:652:12
      at next (lib\runner.js:443:14)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:453:7
      at next (lib\runner.js:362:14)
      at Immediate.<anonymous> (lib\runner.js:421:5)

  8) Mocha
       #useColors()
         should be chainable:
     TypeError: mocha.useColors is not a function
      at Context.<anonymous> (test\unit\mocha.spec.js:370:20)
      at callFn (lib\runnable.js:386:21)
      at Test.Runnable.run (lib\runnable.js:373:7)
      at Runner.runTest (lib\runner.js:534:10)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:652:12
      at next (lib\runner.js:443:14)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:453:7
      at next (lib\runner.js:362:14)
      at Immediate.<anonymous> (lib\runner.js:421:5)

  9) Mocha
       #useInlineDiffs()
         should set the inlineDiffs option to true when param equals true:
     TypeError: mocha.useInlineDiffs is not a function
      at Context.<anonymous> (test\unit\mocha.spec.js:377:13)
      at callFn (lib\runnable.js:386:21)
      at Test.Runnable.run (lib\runnable.js:373:7)
      at Runner.runTest (lib\runner.js:534:10)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:652:12
      at next (lib\runner.js:443:14)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:453:7
      at next (lib\runner.js:362:14)
      at Immediate.<anonymous> (lib\runner.js:421:5)

  10) Mocha
       #useInlineDiffs()
         should set the inlineDiffs option to false when param equals false:
     TypeError: mocha.useInlineDiffs is not a function
      at Context.<anonymous> (test\unit\mocha.spec.js:383:13)
      at callFn (lib\runnable.js:386:21)
      at Test.Runnable.run (lib\runnable.js:373:7)
      at Runner.runTest (lib\runner.js:534:10)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:652:12
      at next (lib\runner.js:443:14)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:453:7
      at next (lib\runner.js:362:14)
      at Immediate.<anonymous> (lib\runner.js:421:5)

  11) Mocha
       #useInlineDiffs()
         should set the inlineDiffs option to false when the param is undefined:
     TypeError: mocha.useInlineDiffs is not a function
      at Context.<anonymous> (test\unit\mocha.spec.js:389:13)
      at callFn (lib\runnable.js:386:21)
      at Test.Runnable.run (lib\runnable.js:373:7)
      at Runner.runTest (lib\runner.js:534:10)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:652:12
      at next (lib\runner.js:443:14)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:453:7
      at next (lib\runner.js:362:14)
      at Immediate.<anonymous> (lib\runner.js:421:5)

  12) Mocha
       #useInlineDiffs()
         should be chainable:
     TypeError: mocha.useInlineDiffs is not a function
      at Context.<anonymous> (test\unit\mocha.spec.js:395:20)
      at callFn (lib\runnable.js:386:21)
      at Test.Runnable.run (lib\runnable.js:373:7)
      at Runner.runTest (lib\runner.js:534:10)
      at S:\Projects\MiloProductions\00 Old and reference Repos\mocha\lib\runner.js:652:12
      at next (lib\runner.js:443:14)

So should I leave the prototype functions alone, and then be modifying the Mocha.setup function to not use this[opt](opts[opt]); and instead manually call the corresponding function for each option?

This seems way beyond the scope of my pull request intent. I just wanted to let people know how to use custom reporters in the browser. T.T

This problem also probably extends to many of the options. Could we create a new issue specifically for dealing with all the browser options? (Finding out which ones actually do things, have proper names, etc)

…in browser. You can pass the constructor function of your custom reporter in options and mocha will use it.

juergba · 2019-10-12T07:20:36Z

Yes, I'm sorry. Lets squash this PR down to the absolute minimum, the reporter setup thing, and then finish it.
I will have a look at the error messages.

juergba · 2019-10-12T10:10:35Z

I just have tested most of the builtin reporters, the only one which works in the browser on my laptop (Chrome/Windows10) is "HTML". All the others don't output anything.
You commented earlier that all builtin reporters were producing an output. Can you explain?
When I misspell the reporter (eg. "SPEC"), then the default reporter ("html") is used.
Otherwise with correct spelling "spec" there is no output at all.

juergba · 2019-10-13T17:46:39Z

The cat was meant as a picture, I was hoping you as english native would translate this into some smooth words ... meaning: you can use those CLI reporters in the browser, but they are not made/supported for that purpose.

I will finish this PR tomorrow with maybe:

It is possible to use built-in reporters as well, but their employment in browsers is neither recommended nor supported.

Thanks!

You can pass the constructor function of your custom reporter in options and mocha will use it.

juergba

@Lindsay-Needs-Sleep thank you!
I also run npm start docs which updated some automatically created docu parts.

Lindsay-Needs-Sleep · 2019-10-14T10:32:59Z

The cat was meant as a picture, I was hoping you as english native would translate this into some smooth words ... meaning: you can use those CLI reporters in the browser, but they are not made/supported for that purpose.

Haha, sorry! I liked it, it made me laugh, and it definitely got the point across. (But, I guess it was a bit extreme. :p) (I wouldn’t have guessed that english is not your first language!)

Thank you for finishing this pull request though! :)

You can pass the constructor function of your custom reporter in options and mocha will use it. # Conflicts: # docs/index.md

Lindsay-Needs-Sleep force-pushed the master branch 4 times, most recently from 67686eb to 5bfbdb4 Compare September 24, 2019 23:18

Lindsay-Needs-Sleep mentioned this pull request Sep 24, 2019

JSON Stream documentation #4027

Closed

4 tasks

Lindsay-Needs-Sleep force-pushed the master branch from 5bfbdb4 to 1b7d714 Compare September 24, 2019 23:53

outsideris reviewed Sep 30, 2019

View reviewed changes

docs/index.md Outdated Show resolved Hide resolved

Lindsay-Needs-Sleep force-pushed the master branch from 8a01b3d to ff6b64f Compare October 4, 2019 08:36

Lindsay-Needs-Sleep force-pushed the master branch from ff6b64f to 455505e Compare October 8, 2019 03:24

Lindsay-Needs-Sleep mentioned this pull request Oct 8, 2019

(documentation) Inconsistent formatting of reporter names #4054

Closed

juergba added area: browser browser-specific area: documentation anything involving docs or mochajs.org semver-major implementation requires increase of "major" version number; "breaking changes" labels Oct 10, 2019

juergba reviewed Oct 10, 2019

View reviewed changes

Lindsay-Needs-Sleep force-pushed the master branch from a5c5b24 to 40bbaaa Compare October 13, 2019 16:46

Issue mochajs#1592 Improve reporter documentation for mocha in browser.

2ac64f9

You can pass the constructor function of your custom reporter in options and mocha will use it.

juergba force-pushed the master branch from 40bbaaa to 2ac64f9 Compare October 14, 2019 06:50

juergba approved these changes Oct 14, 2019

View reviewed changes

juergba merged commit 3a0ef50 into mochajs:master Oct 14, 2019

juergba added this to the next milestone Oct 14, 2019

boneskull added the semver-patch implementation requires increase of "patch" version number; "bug fixes" label Oct 14, 2019

juergba mentioned this pull request Oct 16, 2019

Mocha constructor: improve browser setup #4070

Merged

juergba modified the milestones: 6.2.1, 6.2.2 Oct 18, 2019

boneskull pushed a commit that referenced this pull request Oct 18, 2019

Improve reporter documentation for mocha in browser. (#4026)

cebddf2

You can pass the constructor function of your custom reporter in options and mocha will use it. # Conflicts: # docs/index.md

boneskull added the landed-on-v6.2.x cherry-picked on v6.2.x branch from master label Oct 18, 2019

This was referenced Oct 27, 2019

[Snyk] Upgrade mocha from 6.2.1 to 6.2.2 jamesleesaunders/d3-x3d#119

Closed

[Snyk] Upgrade mocha from 2.5.3 to 6.2.2 ajesse11x/kompose#5

Open

[Snyk] Upgrade mocha from 6.2.0 to 6.2.2 Niweera/googledict#5

Open

snyk-bot mentioned this pull request Nov 25, 2019

[Snyk] Upgrade mocha from 2.4.5 to 6.2.2 ajesse11x/cypress#12

Open

snyk-bot mentioned this pull request Apr 9, 2020

[Snyk] Upgrade mocha from 6.0.2 to 6.2.2 civilizador/ticket-master#4

Open

snyk-bot mentioned this pull request Apr 17, 2020

[Snyk] Upgrade mocha from 6.2.2 to 6.2.3 WealthWizardsEngineering/instance-terminator#17

Closed

This was referenced May 21, 2024

[Snyk] Upgrade mocha from 6.2.2 to 6.2.3 82ndAirborneDiv/Azure-Network-Security#5

Open

[Snyk] Upgrade mocha from 6.2.2 to 6.2.3 82ndAirborneDiv/Azure-Security-Center#5

Open

leonmonson mentioned this pull request Jul 27, 2024

[Snyk] Upgrade mocha from 6.2.2 to 6.2.3 leonmonson/practice-for-week-02-scope-problems-without-context#2

Open

satoshinakamoto007 mentioned this pull request Sep 8, 2024

[Snyk] Upgrade: , , , , bitcore-lib, bitcore-lib-cash, bitcore-lib-doge, bitcore-lib-ltc, chai, ethers, mocha, ripple-binary-codec, ripple-lib, ts-node, tslint, typescript, web3 satoshinakamoto007/bitcore#1118

Open

satoshinakamoto007 mentioned this pull request Nov 8, 2024

[Snyk] Upgrade mocha from 6.1.4 to 6.2.3 satoshinakamoto007/bitcore#1214

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Added documentation on how to specify the reporter for browser mocha #4026

Added documentation on how to specify the reporter for browser mocha #4026

Lindsay-Needs-Sleep commented Sep 23, 2019 •

edited

Loading

jsf-clabot commented Sep 23, 2019 •

edited

Loading

juergba commented Sep 23, 2019

Lindsay-Needs-Sleep commented Sep 23, 2019

Lindsay-Needs-Sleep commented Sep 24, 2019

Lindsay-Needs-Sleep commented Sep 24, 2019

coveralls commented Sep 25, 2019 •

edited

Loading

juergba commented Oct 1, 2019

Lindsay-Needs-Sleep commented Oct 4, 2019

Lindsay-Needs-Sleep commented Oct 8, 2019 •

edited

Loading

juergba commented Oct 10, 2019 •

edited

Loading

juergba Oct 10, 2019

juergba Oct 10, 2019

juergba Oct 10, 2019

Lindsay-Needs-Sleep commented Oct 10, 2019

Lindsay-Needs-Sleep commented Oct 12, 2019

Lindsay-Needs-Sleep commented Oct 12, 2019 •

edited

Loading

juergba commented Oct 12, 2019

juergba commented Oct 12, 2019

juergba commented Oct 13, 2019

juergba left a comment

Lindsay-Needs-Sleep commented Oct 14, 2019

Added documentation on how to specify the reporter for browser mocha #4026

Added documentation on how to specify the reporter for browser mocha #4026

Conversation

Lindsay-Needs-Sleep commented Sep 23, 2019 • edited Loading

Description of the Change

Alternate Designs

Why should this be in core?

Benefits

Possible Drawbacks

Applicable issues

jsf-clabot commented Sep 23, 2019 • edited Loading

juergba commented Sep 23, 2019

Lindsay-Needs-Sleep commented Sep 23, 2019

Lindsay-Needs-Sleep commented Sep 24, 2019

Lindsay-Needs-Sleep commented Sep 24, 2019

coveralls commented Sep 25, 2019 • edited Loading

juergba commented Oct 1, 2019

Lindsay-Needs-Sleep commented Oct 4, 2019

Lindsay-Needs-Sleep commented Oct 8, 2019 • edited Loading

juergba commented Oct 10, 2019 • edited Loading

juergba Oct 10, 2019

Choose a reason for hiding this comment

juergba Oct 10, 2019

Choose a reason for hiding this comment

juergba Oct 10, 2019

Choose a reason for hiding this comment

Lindsay-Needs-Sleep commented Oct 10, 2019

Lindsay-Needs-Sleep commented Oct 12, 2019

Lindsay-Needs-Sleep commented Oct 12, 2019 • edited Loading

juergba commented Oct 12, 2019

juergba commented Oct 12, 2019

juergba commented Oct 13, 2019

juergba left a comment

Choose a reason for hiding this comment

Lindsay-Needs-Sleep commented Oct 14, 2019

Lindsay-Needs-Sleep commented Sep 23, 2019 •

edited

Loading

jsf-clabot commented Sep 23, 2019 •

edited

Loading

coveralls commented Sep 25, 2019 •

edited

Loading

Lindsay-Needs-Sleep commented Oct 8, 2019 •

edited

Loading

juergba commented Oct 10, 2019 •

edited

Loading

Lindsay-Needs-Sleep commented Oct 12, 2019 •

edited

Loading