Stryker quits with "TypeError: Cannot read property 'runResult' of undefined"

I’m unable to run stryker on my current project. Error log and config below:

Error log

[2017-08-02 15:54:40.571] [WARN] InputFileResolver - Globbing expression "test/unit/**/*.js" did not result in any files.
[2017-08-02 15:54:40.595] [INFO] InputFileResolver - Found 33 of 33 file(s) to be mutated.
[2017-08-02 15:54:40.597] [INFO] SandboxCoordinator - Starting initial test run. This may take a while.
[2017-08-02 15:54:41.787] [ERROR] Stryker - One or more tests errored in the initial test run:
        TypeError: Cannot read property 'runResult' of undefined
TypeError: Cannot read property 'runResult' of undefined

stryker.conf.js

module.exports = function(config){
  config.set({
    files: [
      'test/unit/**/*.js',
      { pattern: 'src/**/*.js', included: false, mutated: true }
    ],
    testFramework: 'mocha',
    testRunner: 'mocha',
    reporter: ['progress', 'clear-text', 'dots', 'html', 'event-recorder'],
    coverageAnalysis: 'off',
    plugins: ['stryker-mocha-runner', 'stryker-html-reporter']
  });
};

Command I’m running to generate this error:

./node_modules/.bin/babel-node ./node_modules/.bin/stryker run

Note: I’ve had a look in the .stryker-tmp directory, and the ___testHooksForStryker.js file is empty. Assuming this is incorrect?

[simondel]

Hi! We fixed the original error so the issue has been closed. Please upgrade to:

• stryker-api@0.8.0
• stryker-html-reporter@0.7.0
• stryker-mocha-framework@0.4.0
• stryker-mocha-runner@0.7.0
• stryker@0.9.0

[nicojs]

If the error is with the CoverageInstrumenterStream , can it be that you changed the coverageAnalysis setting to something other than 'off'? If coverage instrumentation is 'off' it should not try to instrument for code coverage.

That being said: we we’re not supporting es6 syntax natively yet. A feature request for it can be found here: https://github.com/stryker-mutator/stryker/issues/133. To make it work, we’re starting to migrate to more language agnostic way of working, as can be read in our latest blog article. So it might take some time before we natively support things like the import statement.

For the time being, you can use stryker by first transpiling the code yourself before handing it of to Stryker. First make sure your normal unit tests are passing when ran over the transpiled code though.

Lets keep this issue about the original error message. If you run into anything else, please feel free to update #133 or report new issues when they arise.