cypress: Couldn't determine Mocha version

@wojtek1150 Are you working in a monorepo maybe? I only ask cause I am (with yarn workspaces), and I’m running into the same issue. My current theory is that my issue something to do with…

1. running cypress within a subfolder instead of the project-root. For me, this subfolder has its own package.json and node_modules, in addition to the project root’s at ../node_modules and ../package.json,
2. and cypress (and deps) being hoisted to the project-root ../node_modules.

I haven’t looked at the patched code @sandra-ouadghiri shared, but if the mocha-junit-reporter is using npm/npx to resolve the mocha version then I’m guessing that the reporter can’t find mocha at all: it’s looking in the wrong places with tools that don’t know how to find hoisted workspace packages.

I’ll post a followup with my environment+project details when I’ve got time, probably tomorrow. Or a solution, if I find one for myself. Going to work on this a little tonight.

The problem is we ship mocha as part of the Cypress App binary, which is not installed in node_modules. That only contains the CLI tool, which launches the Cypress app (which includes all the required modules for Cypress, like mocha).

The mocha-junit-reporter tries to do require('mocha') - which looks at your project’s node_modules - which does not contain mocha. It logs a warning - that is here: https://github.com/michaelleeallen/mocha-junit-reporter/blob/4b17772f8da33d580fafa4d124e5c11142a70c1f/index.js#L32.

There isn’t anything we can reasonable do about this warning in the Cypress code base - other than add specific code to silence a specific warning from a third party module, which I don’t think makes much sense.

The warning shouldn’t prevent the reporter from working. The only way to silence this warning when using this reporter would be a PR to the mocha-junit-reporter repository either removing the warning, or adding an option to silence it.

I am going to close this, since there isn’t any actionable work for us to do in Cypress regarding this warning.

@justinmorrow > Indeed, it’s a monorepo, with cypress being under a dedicated folder. So (root/)micro-service-A/package.json and (root/)test-folder/package.json (including the cypress dependencies and the rest).

I also have this issue A mono repo with Cypress on a sub folder, but one package.json under the root

"devDependencies": {
    "cypress": "^8.3.1",
    "junit-report-merger": "^3.0.2",
    "mocha-junit-reporter": "^2.0.0",
    "typescript": "^4.4.2"
  },

cypress.json:

{
    "reporter": "mocha-junit-reporter",
    "reporterOptions": {
        "configFile" : "reporter-config.json"
        },
}

reporter-config.json:

{
    "reporterEnabled": "mocha-junit-reporter",
    "reporterOptions": {
      "testsuitesTitle": true,
      "includePending": true,
      "mochaFile" : "./reports/test-results.[hash].xml"
    }
  }

@jennifer-shehane

Can you provide a reproducible example?

Here is a repo with a reproducible example: https://github.com/jluttrell/cypress-mocha-version-warning-repro

Also producing in 6.3 + “mocha-junit-reporter”: “^2.0.0” (via cypress-multi-reporters in my case, but not sure it matter) Appeared when I added the custom reporter. It looks very very similar to https://github.com/cypress-io/cypress/issues/4602. At that time, @gcirone produced a fix in the reporter. To see if that’s the same root cause/same fix situation or a different bug just leading to the same behaviour.

My config in cypress.json is

"reporter": "cypress-multi-reporters",
"reporterOptions": {
  "reporterEnabled": "mochawesome, mocha-junit-reporter",
  "mochawesomeReporterOptions": {
    "reportDir": "reports/mochawesome-json",
    "overwrite": false,
    "html": true,
    "json": true,
    "quiet": true
  },
  "mochaJunitReporterReporterOptions": {
    "mochaFile": "reports/junit-xml/[hash].xml"
  }
},

package.json

    "cypress": "^6.3.0",
    "cypress-multi-reporters": "^1.4.0",
    "mocha-junit-reporter": "^2.0.0",
    "mochawesome": "^6.2.2",