[core] Use describeTreeView for type-ahead tests
#12811
Merged
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
flaviendelangle
added
core
flaviendelangle
changed the title
describeTreeView for type-ahead tests
9 tasks
flaviendelangle
force-pushed
the
type-ahead-test
branch
2 times, most recently
from
952b8da
to
6e72b9a
Compare
|
Deploy preview: https://deploy-preview-12811--material-ui-x.netlify.app/ |
flaviendelangle
force-pushed
the
type-ahead-test
branch
from
6e72b9a
to
38b36c9
Compare
github-actions
bot
added
the
PR: out-of-date
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
github-actions
bot
removed
the
PR: out-of-date
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.
Part of #12433
Blocked by #12698
I'm splitting the migration of this plugin's tests because it's basically half of the tests of the tree view 馃槅
I am splitting the test file into 1 describe per entry of the big
switchinuseTreeViewKeyboardNavigation, that way it's easy to know where a test should live. I'll see how many tests don't fit well in one of these blocks.