Consider adding configuration in reporter declaration

[pascalduez]

hi,

We can already use the plugin from a jest.config.js as such:

reporters: [
  'default',
  'jest-html-reporter',
]

But we need to create a jesthtmlreporter.config.json.

Desired (fits other reporters config api):

reporters: [
  'default',
  [
    'jest-html-reporter',
    {
      executionMode: 'reporter',
      pageTitle: '...',
      outputPath: '...',
    },
  ],
],

[Hargne]

This is a pretty neat idea. Will try to look into it ASAP.

[jpicton]

I'll upvote this idea. Took me a while to understand why the reporters options format wasn't working for this package. It's a bit messy having to spread Jest-related configuration around in multiple files/directories.

[Hargne]

Hi,

I am currently working on this feature as I believed it to be a nice improvement of the plugin.
A small dilemma has appeared however in which I would like to get some inputs on in order to solve it as smoothly as possible:

As the plugin is designed at the moment, it expects to be run as a testResultsProcessor by default - meaning that it will read the config from jesthtmlreporter.config.json.
Running the plugin as a Custom Reporter is priority 2, meaning that you have to actively define inside jesthtmlreporter.config.json that you want it to be run as such. This would eventually mean that you would have to create a jesthtmlreporter.config.json-file in either case.

The reason the execution mode needs to be defined is because of how Jest requires different exports depending on these modes.

If we were to swap the priority order (Custom Reporter being default, and testResultsProcessor needing configuration), it would break the plugin for all users who haven't defined executionMode in jesthtmlreporter.config.json, and it would also mean that we would somewhat deviate from the pattern of keeping configurations separate (as discussed in this issue #20)

What are your thoughts on this matter?

[jpicton]

Can you do something similar to what they’ve done with jest-junit (which can also be used in both ways)? See https://github.com/jest-community/jest-junit/blob/master/index.js

[pascalduez]

@Hargne Thanks for the explanation!
Actually the point of this request is being able to dismiss the jesthtmlreporter.config.json and having all the jest related configurations in one file. Mostly because it's easier to maintain across several packages.

[Hargne]

@pascalduez @jpicton could you take a look at the PR regarding this (#44) and see if this solves this issue for you?

Thanks!

[jpicton]

Cheers @Hargne, the changes look like they're exactly what I was after.

[Hargne]

Added in #44

[pascalduez]

@Hargne Works like a charm, thanks a bunch!