Component Tests Can't Run When Cypress Is In a Different Project Folder

[peterkrieg]

Current behavior

I have a cypress project where we have the cypress config in a different folder, so that we run cypress open --project spec/e2e. This has always worked fine with the traditional cypress e2e tests.

I tried out the component tests and encountered a bug where the cypress test runner doesn't seem able to execute the test. (screenshot below). The webpack compiles successfully, the tests are shown correctly, but clicking on a test results in the console error below 👇

If I move the cypress config to the root folder, as is the more common case with cypress examples/docs, everything works fine. It appears to be a path resolution error.

Desired behavior

Able to run component tests inside of a different project folder.

Test code to reproduce

Minimal Repo to observe, with additional instructions in the readme: https://github.com/peterkrieg/cypress-bug-repro

Thank you for looking at this! Cypress component testing looks awesome and I can't wait to try it some more.

Versions

Cypress: 7.1.0
@cypress/webpack-dev-server: 1.1.3

[lmiller1990]

Thanks for reporting this. I am investigating. I reproduced the issue in here and will make a fix in the same PR.

[cypress-bot]

The code for this is done in cypress-io/cypress#16056, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[jennifer-shehane]

Released in 7.2.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v7.2.0, please open a new issue.