No command-line output since 4.1.3

[thegecko]

Hi,

Our build system automatically updated to 4.1.4 (semver FTW!) but it looks like some of our reporters are no longer running.

This worked in 4.1.2, but not on 4.1.3. There is no longer any command line output although the chrome runner is running. Config file as follows:

{
    "environments": [
        "node",
        "chrome"
    ],
    "node": {
        "suites": "lib/_tests/**/*.js"
    },
    "browser": {
        "suites": "bundles/_tests/**/*.js"
    },
    "coverage": [
        "lib/**/*.js",
        "!lib/_api/**",
        "!lib/_tests/**"
    ],
    "reporters+": [
        {
            "name": "jsoncoverage",
            "options": {
                "filename": "unit_coverage.json",
                "directory": "coverage"
            }
        },
        {
            "name": "junit",
            "options": {
                "filename": "junit.xml"
            }
        }
    ]
}
``

[jason0x43]

It looks like the recent updates to make configuration merging more consistent are causing the default 'runner' reporter to be removed in bin/intern.

A temporary fix is to explicitly add the 'runner' reporter to your config.

[jason0x43]

Need more integration tests, it seems...

[thegecko]

Ack, I'll pin 4.1.2 for now :)

[jason0x43]

This is being tracked in #970