Skip to content
This repository has been archived by the owner on Aug 5, 2021. It is now read-only.

Add support for E2E Testing #36

Open
1 of 6 tasks
thescientist13 opened this issue Jun 1, 2018 · 1 comment
Open
1 of 6 tasks

Add support for E2E Testing #36

thescientist13 opened this issue Jun 1, 2018 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested testing
Milestone

Comments

@thescientist13
Copy link
Member

Type of Change

  • New Feature Request
  • Documentation
  • Future Spec
  • Improvement / Suggestion
  • Bug
  • Other (please clarify below)

Summary

Description

Not just for the sake of E2E testing, but also to validate our browserlist preferences / recommendations.

Use Case

E2E Testing is a valuable part of any modern CI / CD based release management strategy. In addition, being able to validate that everything will work according to an expected browser support matrix (maybe using something like Saucelabs?).

Code Sample

N / A

Pros / Cons

Would be valuable from a documentation / code sample perspective and from a best practices perspective. Only consideration is that E2E testing can be fragile, and support for Web Component APIs may or may not be mature / stable. Discovery / spiking will likely be needed for this task.

@thescientist13 thescientist13 added enhancement New feature or request question Further information is requested labels Jun 1, 2018
@thescientist13 thescientist13 added this to the Beta milestone Jun 1, 2018
@thescientist13
Copy link
Member Author

https://www.cypress.io/

@thescientist13 thescientist13 added testing help wanted Extra attention is needed labels Aug 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested testing
Projects
None yet
Development

No branches or pull requests

1 participant