Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[e2e testing] Migrate test-e2e package to use Cypress #6139

Closed
1 task done
jeffchew opened this issue May 20, 2021 · 0 comments
Closed
1 task done

[e2e testing] Migrate test-e2e package to use Cypress #6139

jeffchew opened this issue May 20, 2021 · 0 comments
Assignees
Labels
dev Needs some dev work priority: high
Milestone

Comments

@jeffchew
Copy link
Member

jeffchew commented May 20, 2021

User Story

As a [user role below]:
Carbon for IBM.com developer

I need to:
migrate the test-e2e package from Puppeteer to Cypress

so that I can:
automate e2e testing on multiple browsers, and deploy tests on Browserstack

Additional information

Acceptance criteria

  • Migrate test-e2e to cypress
@jeffchew jeffchew added dev Needs some dev work priority: medium labels May 20, 2021
@jeffchew jeffchew self-assigned this May 20, 2021
@jeffchew jeffchew added this to the Sprint 21-11 milestone May 20, 2021
jeffchew added a commit to jeffchew/carbon-for-ibm-dotcom that referenced this issue May 24, 2021
These are showing flakiness at the moment. We will ultimately replace
with the following stories:

carbon-design-system#6139
carbon-design-system#6142
kodiakhq bot pushed a commit that referenced this issue May 24, 2021
)

### Related Ticket(s)

No related issues

### Description

These are showing flakiness at the moment. We will ultimately replace
with the following stories:

#6139
#6142

### Changelog

**Removed**

- React integration build/bundle tests

<!-- React and Web Component deploy previews are enabled by default. -->
<!-- To enable additional available deploy previews, apply the following -->
<!-- labels for the corresponding package: -->
<!-- *** "package: services": Services -->
<!-- *** "package: utilities": Utilities -->
<!-- *** "package: styles": Carbon Expressive -->
<!-- *** "RTL": React / Web Components (RTL) -->
<!-- *** "feature flag": React / Web Components (experimental) -->
@jeffchew jeffchew modified the milestones: Sprint 21-18, Sprint 21-20 Aug 16, 2021
@jeffchew jeffchew modified the milestones: Sprint 21-20, Sprint 21-18 Sep 9, 2021
kodiakhq bot pushed a commit that referenced this issue Sep 10, 2021
)

### Related Ticket(s)

Refs #6139

### Description

This PR fully moves the existing `test-e2e` package to a dedicated cypress test setup for web components and react storybooks. A few tests have been included for `masthead`, `locale-modal`, and `leadspace`. They are largely focused on snapshot testing, though percy has been disabled for now as rendering of dynamic states are still not supported in percy for web components (see percy/cli#280).

Actual cypress tests can be created now though, and also the current tests uses the built-in cypress screenshot feature:

![image](https://user-images.githubusercontent.com/1641214/132697052-2943ccdf-81c5-450d-999e-c39e557a3d05.png)

And video that shows how the tests are run:

https://user-images.githubusercontent.com/1641214/132697174-a778c055-d3d8-4e01-877d-bd58c2aa7491.mp4

### Changelog

**New**

- Cypress testing for web components and react storybook

**Changed**

- disabled video recording by default to speed up tests

**Removed**

- Removed `test-e2e` package
kodiakhq bot pushed a commit that referenced this issue Sep 10, 2021
…#7117)

### Related Ticket(s)

Refs #6139

### Description

I missed removing this workflow in Github Actions, removed and added the new one to `percy-update-base.yml`.

### Changelog

**Changed**

- Added react e2e percy update
- Removed `test-e2e` workflow in deploy-canary
@jeffchew jeffchew modified the milestones: Sprint 21-19, Sprint 21-18 Sep 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev Needs some dev work priority: high
Projects
None yet
Development

No branches or pull requests

2 participants