-
Notifications
You must be signed in to change notification settings - Fork 24
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
Github workflows: Code coverage for cypress & improvements #955
Draft
olemartinorg
wants to merge
24
commits into
main
Choose a base branch
from
feat/cypress-code-coverage
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…code coverage on cypress.
olemartinorg
added
area/test
related to automated and functional testing
kind/other
Pull requests containing chores/repo structure/other changes
ignore-for-release
Pull requests to be ignored in release notes
labels
Feb 24, 2023
…e items have been created.
…d build (tests don't need build)
…t us the same regardless of how they run. With heavy caching of node_modules etc, we can speed this up.
olemartinorg
changed the title
Cypress: Code coverage
Github workflows: Code coverage for cypress & speed/cost improvements
Feb 24, 2023
…n without also reporting to the dashboard. I'll need to re-implement the split-brain feature. :-(
…egligible cost. Let's build on two more machines!
…aving cache'. Making restore/save explicit to avoid such nonsense.
…en including yarn.lock from dependencies inside node_modules as well.
olemartinorg
changed the title
Github workflows: Code coverage for cypress & speed/cost improvements
Github workflows: Code coverage for cypress & improvements
Feb 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/test
related to automated and functional testing
ignore-for-release
Pull requests to be ignored in release notes
kind/other
Pull requests containing chores/repo structure/other changes
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Work in progress!
Related Issue(s)
Verification/QA
src/layout/layout.d.ts
andlayout.schema.v1.json
, and these are all backwards-compatiblekind/*
label to this PR for proper release notes grouping