testem version changed in [email protected] without updating grunt-testem version

[jblack10101]

I've got a project that uses [email protected]. Recently, my grunt tasks that use Testem started failing for seemingly no reason. I spent a lot of time troubleshooting the issue, and I found that some of my node packages' transitive dependencies changed without the main packages updating their version numbers.

When my builds were working, [email protected] depended [email protected]. When my builds started failing, [email protected] now depends on [email protected].

So in the future, please reference an exact version number in your package.json, and update your node module's version number when your dependency versions update. Thanks

[jblack10101]

Well, I'm going to just start using shrinkwrap, so disregard my request above.

But I think I found the issue: My tests are hanging when I define an output.coverage option to use with grunt-istanbul. It worked with [email protected] was pulling in [email protected], and now fails when it pulls in [email protected].

Here's a snippet of my grunt config:

grunt.initConfig({
    ...
    testem: {
        options: {
            launch_in_ci: ["Chrome"],
            output: {
                coverage: 'tmp/coverage/from_browsers/'
            },
            routes: {
                "/build": "instrumented/build"
            },
            force: false,
            port: testemPort
        },
        main: {
            src: [
                ...             
            ],
        },
        ...
    },
    ...
});

If I remove the testem.options.output object, it works with the latest version of testem, otherwise it hangs.

[yvanavermaet]

I created a ticket for this issue about an hour ago. In my opinion this is an issue with testem, not with grunt-testem or gulp-testem (in my case): https://github.com/airportyh/testem/issues/500

[sideroad]

denk> thanks for creating the ticket.

jblack> sorry for inconvinient...

I hope that testem community will resolve this issue.

[yvanavermaet]

@sideroad @jblack10101 A quick fix was added to the testem-multi module (which is used by the grunt-testem module). testem-multi module will use 0.6.24 (instead of 0.6.39), which doesn't have this issue. So re-install the node modules.