Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

No tests found when directory name has `[` or `]` (Component Testing with Next.js)

See original GitHub issue

Current behavior

Hello, I was set up Cypress Component Testing with Next.js plugin. I encountered No tests found. error.

I’m writing exactly the same code for these two files. But different behavior. I investigated below

some/foo.spec.js => works
some/[thing]/foo.spec.js => No tests found
some/[thing/foo.spec.js => No tests found
some/thing]/foo.spec.js => No tests found

[thing] style is used in Next.js pages directory. Is it possible to fix this issue? Thanks

Desired behavior

some/foo.spec.js => works
some/[thing]/foo.spec.js => works
some/[thing/foo.spec.js => works
some/thing]/foo.spec.js => works

Test code to reproduce

It can reproduce minimum Component Testing with Next.js. Just put [ or ] in directory name.

Cypress Version

9.5.1

Other

No response

Issue Analytics

State:
Created 2 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

lmiller1990commented, Mar 11, 2022

I looked into it. It’s only happening with webpack-dev-server, not vite-dev-server. So, this isn’t a Next.js specific thing, but just a webpack-dev-server thing. I will continue looking into this.

0reactions

lmiller1990commented, Mar 18, 2022

Nice, thanks for the confirmation!