The 3x branch introduces significant UI changes that break existing tests. Cypress would be a better fit for testing the new, more complex UI interactions (i.e. drilling down into sections by clicking instead of hover).

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

justin2pin created an issue. See original summary.

justin2pin changed the visibility of the branch 3547679-tests-in-cypress to hidden.

grgcrlsn321 made their first commit to this issue’s fork.

grgcrlsn321’s picture

Status: Needs work » Needs review

I refactored the tests to run for builder.js, cardinality, and nested-sections to run with cypress when using `npm run cy:open` locally. I attempted to fix the gitlab-ci but it's still failing for cypress. Might be better to create a new issue for that. Going to set this to needs review so someone else can test it out.

grgcrlsn321’s picture

I fixed the tests for gitlab-ci to run correctly. Made changes for eslint to ignore cypress testing. If we need to configure eslint for cypress testing we need a different library specific for Cypress ESLint and then create a different build job.

justin2pin’s picture

Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

justin2pin’s picture

Status: Fixed » Needs work

justin2pin’s picture

Status: Needs work » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.