Cypress doesn't find tests when custom webpack config uses code-splitting

[oswaldofreitas]

Version

3.0.5

Reproduction link

https://github.com/vuejs/vue-cli

Node and OS info

Node 10.11.0 / npm 6.4.1 / macOS Mojave 10.14

Steps to reproduce

1. create a new project via vue create and add cypress as e2e test tool
2. add a new vue.config.js file with the following content:

module.exports = {
  configureWebpack: {
    optimization: {
      runtimeChunk: {
        name: 'manifest',
      }
    }
  }
}

What is expected?

tests ran fine on npm run test:e2e

What is actually happening?

A "No tests found in your file" message is shown in Cypress and no tests are executed

---

I'm not sure if it's a vue cli or cypress issue, so I opened this issue too in cypress repo

[LinusBorg]

Please see my comment in the cypress issue you linked.

We think the issue with with the cypress webpack preprocessor. A workaround should look like this:

module.exports = {
  configureWebpack: () => {
    return {
      optimization: {
        runtimeChunk: process.env.CYPRESS_ENV ? undefined : {
          name: 'manifest',
        }
      }
    }
  }
}

We'll see how the problem in the cypress repository develops and will determine how to deal with this in our own repo accordingly.

[leeuwd]

I'm having the same/comparable issue. Still working on it. See cypress-io/cypress#2608

[oswaldofreitas]

sorry for dumb question, but how do I get process.env.CYPRESS_ENV different than undefined?

I just added console.log(process.env.CYPRESS_ENV) to my vue.config.js and ran npm run test:e2e and it logged undefined

[oswaldofreitas]

hm, I think CYPRESS_ENV is true after vue.config.js is read, tried your workaround and worked! Thank you @LinusBorg

[LinusBorg]

I opened an issue in the cypress-webpack-preprocessor reporsitory as I think the problem should be solved there.

cypress-io/cypress-webpack-preprocessor#31

[haoqunjiang]

Now that we've removed webpack preprocessor from default cypress config (#2904), there's no remaining actionable item in vue cli, so I'm closing this issue.