Implement Public API for Component Testing Onboarding

[lmiller1990]

What would you like?

Based on the work done in the technical brief: #24991 (Cypress team only), implement the proposed public API.

Documentation: (public post 12.7 release): https://docs.cypress.io/guides/component-testing/third-party-definitions

Why is this needed?

No response

Other

No response

[baus]

Please add your planning poker estimate with Zenhub @astone123

[baus]

Please add your planning poker estimate with Zenhub @lmiller1990

[baus]

Please add your planning poker estimate with Zenhub @marktnoonan

[baus]

Please add your planning poker estimate with Zenhub @mike-plummer

[baus]

Please add your planning poker estimate with Zenhub @warrensplayer

[baus]

Please add your planning poker estimate with Zenhub @ZachJW34

[astone123]

@lmiller1990 Does this include reworking the existing adapters to use the API?

[lmiller1990]

Yeah it does - this single ticket will manage all the work, I don't think it's too large for a single PR. Reworking them should not be much work - the actual API/format isn't changing for internal adapters. Most of the work will be around grabbing a third party one (via cypress-ct-*) exposing the right exports, and integrating it to the workflow.

I wonder if we should stop naming things WIZARD and install call them something more generic. WIZARD is an internal implementation detail. Worth doing if it's not much work as part of this PR.

[lmiller1990]

Splitting this in to two tickets:

1. Define API for third party CT in Launchpad #25680
2. Rework internal code for CT Launchpad to support public API #25681

[lmiller1990]

I'm removing this from the sprint in favor or the above two tickets. I split the points here between the two tickets.

[cypress-bot]

Released in 12.7.0.

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