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

test: Set up E2E tests #53

Closed
pahund opened this issue May 4, 2021 · 0 comments · Fixed by #54
Closed

test: Set up E2E tests #53

pahund opened this issue May 4, 2021 · 0 comments · Fixed by #54
Labels
test Something needs to be tested

Comments

@pahund
Copy link

pahund commented May 4, 2021

Complex functionality like lazy loading, asynchronous config loading or config switching should be tested through end-to-end tests.

A promising setup: Storybook combined with Cypress.

Run the E2E tests with Travis.

Measure code coverage with Istanbul, as explained in the Travis docs.

Combine the coverage data with the coverage data from the Jest unit tests and send the combined data to Coveralls.

As a first spike, set up a test that just renders a plain old GCP ad.

@pahund pahund added the test Something needs to be tested label May 4, 2021
@pahund pahund linked a pull request May 5, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test Something needs to be tested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant