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
commented
6 years ago
Type of Change
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.