E2E: Enable E2E v2 in CI #5952
Open
E2E: Enable E2E v2 in CI #5952
+4,963
−10,993
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
This was referenced Oct 20, 2024
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
RXminuS
force-pushed
the
ci-enable-e2e-v2/windows-tweaks-1
branch
from
276e91f
to
71004fb
Compare
RXminuS
force-pushed
the
rnauta/ci-enable-e2e-v2/enable-gh-ci
branch
from
7c9f76a
to
f935409
Compare
E2E Test - Summary
Details
Failed testse2e › e2e/features/command-edit.test.ts › edit command › can change edit ranges |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Before E2Ev2 tests were not running as part of CI as to not introduce unnecessary warnings/errors whilst they still received some polish. Now that E2Ev2 tests have stabalized (and all remaining E2E tests have a upcoming migration PR) they are stable enough to run in CI.
Now we move all the current E2E tests to legacy (we might need to update the Required Merge Action Names) and enable E2Ev2 tests in CI.
Once all remaining tests have migrated (upcoming PR) we can make this new CI step required for merging.
Test plan