Fatal error: test.titlePath is not a function

[cssagogo]

Prerequisites

• Checked that your issue isn't already filed by cross referencing issues with the common mistake label
• Checked next-gen ES issues and syntax problems by using the same environment and/or transpiler configuration without Mocha to ensure it isn't just a feature that actually isn't supported in the environment in question or a bug in your code.
• 'Smoke tested' the code to be tested by running it outside the real test suite to get a better sense of whether the problem is in the code under test, your usage of Mocha, or Mocha itself
• Ensured that there is no discrepancy between the locally and globally installed versions of Mocha. You can find them with:
  node node_modules/.bin/mocha --version(Local) and mocha --version(Global). We recommend avoiding the use of globally installed Mocha.

Description

I have a new project I'm putting together and I'm running 2 very simple unit tests. The test run and the broken test shows as being broken, but it looks like something fails before it can tell me what about it is failing. This is what the output says:

Running "mocha:test2" (mocha) task
Testing: test/index.html

  unitTest.init()
    1) Sample Unit test 1

  unitTest.pdf().init()
    ✓ Sample Unit test 2

  1 passing (1ms)
  1 failing

Fatal error: test.titlePath is not a function

Process finished with exit code 3

I'm running Node v9.0.0 and NPM 5.5.1 on a mac running Sierra.

Steps to Reproduce

1. This is the repo I'm working on: https://github.com/cssagogo/pikadeck
2. Run the test_js grunt task.

Expected behavior: One test pass and one fail with a description of how it failed in the terminal.

Actual behavior: Tests show pass/fail, but hits a fatal error before printing out what was wrong.

Reproduces how often: Always

[dreuxl]

I got that issue on one of my project when I get multiple versions of mocha in the project due to dependencies. By bumping them was able to get rid of that.

codeceptjs/CodeceptJS#741

But then got another issuer with mocha 4 :(

[ScottFreeCode]

@cssagogo Sorry for the late followup -- could you confirm which commits in the repo are affected by the issue? I am having trouble finding one that reproduces it. (Alternatively, double-check that you don't have Mocha installed globally with npm ls -g mocha; if you do, we'd recommend uninstalling it, npm rm -g mocha, as a global version can sometimes cause issues like this, especially used in conjunction with tools like Grunt that work partly globally and partly locally.)

[khiettran]

Any update on this? I got the same issue even I installed Mocha locally.

[ScottFreeCode]

Hi @khiettran,

The only cause of this issue we've found so far is having both a >=4 and <4 version of Mocha installed -- whether one of them is global, or whether one of them is a dependency of one of the project's dependencies. Check npm ls mocha and make sure it only shows one, and npm ls -g mocha should show none at all*. If it's not two different versions of Mocha and you're still running into the issue then I'd be very interested to take a look at a specific example -- the smaller and simpler, the better!

*(At least, avoiding global Mocha is what we recommend -- npm scripts have always had direct access to what's in node_modules/.bin and now npx extends that convenience to direct CLI usage -- but if you really want to have a global copy, you should make sure it's always updated to be the same version as the local one in whichever project you're currently working.)

[khiettran]

@ScottFreeCode Thank you. Update Mocha version in both local and global to be the same and it works.

[JabbyPanda]

I have only local Mocha 4 installed and still can see this error in log.

It is visible only when we have failing unit test

[ScottFreeCode]

Hi @JabbyPanda, do you think you could narrow it down to the minimal amount of code that gets it to happen and post it here? Something I could just copy-paste into an empty project and run Mocha and have the error show up, ideally.

[Spongman]

i'm seeing the same thing when using grunt-mocha

[MiguelCastillo]

I figured I cross reference the issue here. disqus/grunt-mocha#7

[JeffML]

I'm having this problem when running a puppeteer test. This is about as small a test case as I can get:

const chai = require('chai');
chai.should();
const puppeteer = require('puppeteer');

var browser;

describe("UI basic test", function() {
    let page = null;

    before(async () => {
        browser = await puppeteer.launch({
            headless: false,
            // slowMo: 1000
        });
    });

    after(async () => {
        await browser.close();
    })


    it("Load Home Page", async () => {
        page = await browser.newPage();
        //     await page.setViewport({
        //         width: 960,
        //         height: 640,
        //         isLandscape: true
        //     });
        //
        const path = "https://test.mavericklabel.com" //fp('/index.html');
        console.log({
            path
        })
        await page.goto(path);
    })
        .timeout(1200)
});

If I comment out await page.goto(path);, the test passes without error. As far as I can tell, I have not other versions of moch/mochawesome running:
├── chai@4.1.2
├── chai-subset@1.6.0
├── cookieparser@0.1.0
├── eslint@4.18.1
├── lodash@4.17.5
├── mocha@5.0.1
├── mochawesome@3.0.2
├── nano@6.4.2
├── puppeteer@1.1.1
└── superagent@3.8.2

[boneskull]

Thanks, I am also having problems reproducing this issue. The OP's code (at time of the issue submission) doesn't seem to run any tests at all, so I'm unable to use it.

If someone can reproduce this with Mocha by itself--not with grunt-mocha or puppeteer--or if someone can show the problem is not because of how these third-party modules consume Mocha, then I can help further.

It looks like @JabbyPanda may have been in this bucket, but we need more information.

I'm going to close this until we can get a proper MCVE.

[ZaidMomin1]

I recently faced this issue when executing the tests in parallel. The root cause was I had some it and describe blocks associated with .only.

Removing the .only from it and describe blocks resulted in smooth execution of the tests and the error test.titlePath is not a function was no longer encountered.

Mocha Version: 10.2.0