Files
cypress/system-tests/projects/migration-component-testing-customized/README.md
T
Cesar 3103442b92 fix: migration ui differences (#20134)
Co-authored-by: Lachlan Miller <lachlan.miller.1990@outlook.com>
Co-authored-by: Barthélémy Ledoux <bart@cypress.io>
2022-02-14 14:00:48 -07:00

1.1 KiB

Migration Component Testing Customized

A component tesing project without e2e. We ask the users to migrate their specs manually.

The following migration steps will be used during this migration:

Steps:

  • automatic file rename
  • manual file rename
  • rename support
  • update config file
  • setup component testing

Automatic Migration

Not used.

Manual Files

Since the user has a custom componentFolder and testFiles pattern, we won't ask them to migrate away. We only do this if they are using the defaults.

Rename supportFile

Not used. supportFile: false is set. We woudl normally put this in your e2e.supportFile key. We assume a top level supportFile is used for E2E testing. Since this project does not have E2E configured, we just skip this step.

Update Config

The expected output is in expected-cypress.config.js.

Setup Component Testing

Users are required to reconfigure component testing, since the API is changing so much (we now use a devServer key in the config to start their dev server, etc).