Description
Subject
guides - references - configuration
Description
In this issue, it is reported that passing --spec to Cypress when attempting to run a spec does not appear to run that spec if it exists outside of the cypress/e2e folder. It is pretty difficult for a user to debug this, as the cause is that such specs do not match the default specPattern. Since that spec pattern is not present explicitly, and our error message does not refer to it, it seems likely users will find their way to this "Test files not found when using spec parameter". Let's document this potential reason that Cypress will find a spec here.
I'm making a separate issue in the Cypress app repo to improve the error message, which will likely include use an onlink to refer to this part of the documentation as well.