bartvds / mocha-unfunk-reporter Goto Github PK

For longer texts it could be nice to skip leading/trailing identical parts that clutter the view.

Use gruntfile-gtx to get rid of repeating elements.

Do not left-trim the stack-trace:

For example: when using for Q.longStackSupport promises the From previous event:-line should be on different indent level then the at's:

         at Function.assert.jsonOf (index.js:105:40)
         From previous event:
         at Context.<anonymous> (API.ts:101:7)

Should be doable without colors with a multi-line format:

Hello        world today
||||||-------|||||++++++
Hello lovely world

Would be nice to have a list of active filters, both in code as well as in the documentation.

For clarity

Hi,

I am adding mocha to the index.html page. and include test scripts to that page..
and use mocha or mocha-phantomjs to run the test by giving index.html as input.

Can you please let me know how to include your reporter in this kind of setup.

I added the unfunk.js to the html page --- complained about requirejs
Added requireJS to the htmlpage -- error : Module name "jsesc" has not been loaded yet for context: _. Use require([])
jsesc is in the nodemodules folder.

Girish

you currently have

grit://github.com/Bartvds/mocha-unfunk-reporter.git (git)

use the http address

https://github.com/Bartvds/mocha-unfunk-reporter.git

Setting options through process.env['mocha-unfunk-<option_name>'] is very unpractical, since environment variables in bash can only contain letters, numbers and underscores. Dashes are not allowed.

I would change it to MOCHA_UNFUNK_STYLE for example.

Seriously, it is a huge mess out there.

Consider dropping support for everything that is not on the level with Chai.

Or write a use-activated compatibility layer that can restore some of the dmaaged assertion errors.

Chai, Proclaim, Must, Expect, Should, CommonJS/Node.

Use grunt-run-grunt to process and verify the console output.

And ministyle of course.

AssertionErrors from Chai looks good but output from commonjs standard assert's and modules like proclaim need some tuning.

The message / stack code is ugly hacked copy from base reporter, needs a clean rewrite.

Keep console from exploding when comparing long strings.

Update grunt-mocha note (as my fix is merged)

Update screenshots (with string/objects diff demo)

Bail is for easy debugging. Why clutter the view?

$ mocha --reporter mocha-unfunk-reporter --reporter-options foo=bar

constructor will get args runner and options object, which contains a reporterOptions hash.

constructor(runner, options) {
    console.log(options.reporterOptions);
}

// => { foo: 'bar' }

Will start working on implementing this, but wanted to track it here. 👍

Filter from both sides in.

Separately configurable because 'top' is important for debugging custom assertion stuff.

Careful with promises and other odd constructs (chai-as-promised / mocha-as-promised)

Hey Gang

Is there a method for integrating this reporter with Karma?

Use the demo test and local browser: seems to work nicely. How?

Maybe same thing will work on Node.js too, would be nice.

Seems doable to highlight lines in the stack trace.

Add a submodule or config mode for compacter display of passing tests.

Similar to the default 'Dot' reporter

Per-char gives less usable results, like this dangling 'e':

  My Message: actual-value: expected 'test/fixtures/non-existing.txt'
  ||||||||||||-----------|---||||||||||||||||||||||||||||||||||||||||
  My Message:            e   xpected 'test/fixtures/non-existing.txt'