Show a better error message during cypress run when CT/E2E has not been configured.

[sync-by-unito]

Summary

CT testing is not configured, but there is a cypress.config.js file configured for E2E.

When running cypress run --ct   I'm seeing no supportFile found. Should I expect a message like not configured, not tests to run  to align with open-mode's not configured verbiage?

!Screen Shot 2022-05-17 at 2.39.15 PM.png|width=942,height=247!

https://cypressio.slack.com/archives/C02MW5QBD4K/p1652816461805149

Acceptance Criteria

• Show a better error message in the case of running cypress run --component when CT testing has never been setup that instructs users to run cypress open to configure their CT tests.

┆Issue is synchronized with this Jira Task by Unito
┆Attachments: Screen Shot 2022-05-17 at 2.39.15 PM.png | Screen Shot 2022-05-19 at 3.27.11 PM.png | Screen Shot 2022-06-02 at 12.20.51 PM.png
┆author: Emily Rohrbough
┆epic: CT Post Unification Release
┆friendlyId: UNIFY-1766
┆priority: Medium
┆sprint: Fast Follows 1
┆taskType: Task

[sync-by-unito]

➤ Jennifer Shehane commented:

The is also the same message that display if you don’t have E2E configured.

Via Bill Glesias

!Screen Shot 2022-05-19 at 3.27.11 PM.png|width=1845,height=945!

[sync-by-unito]

➤ Brian Mann commented:

Yeah the CLI logic spreadsheet documents the correct behavior. We’re missing a check higher up in the process and should validate it’s been configured prior to trying to open the testing type and thus subsequently failing

[brian-mann]

yes you need to have both e2e + component configured. It should always throw when trying to run them when they are not configured.

...and yes this error message is just completely wrong… the problem isn't that the error needs to be improved, its that we need to ADD the error state for what happens when you try to run a mode that isn’t configured

[sync-by-unito]

➤ Alejandro Estrada commented:

Should this throw an error as well if e2e is not configured? currently, you can run e2e tests without any extra configuration on the cypress.config.js file, the only need is that the supportFile exists (the default one) so, should we throw on e2e as well or only on component?

!Screen Shot 2022-06-02 at 12.20.51 PM.png|width=1228,height=823!

[sync-by-unito]

➤ Brian Mann commented:

yes you need to have both e2e + component configured. It should always throw when trying to run them when they are not configured.

[sync-by-unito]

➤ Brian Mann commented:

and yes this error message is just completely wrong… the problem isn't that the error needs to be improved, its that we need to ADD the error state for what happens when you try to run a mode that isn’t configured

[cypress-bot]

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

[cypress-bot]

Released in 10.1.0.

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