-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Make tree items more actionable and add AppAction for expanding the object tree #5997
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5997 +/- ##
==========================================
- Coverage 54.70% 54.41% -0.29%
==========================================
Files 607 607
Lines 25959 25943 -16
Branches 2349 2350 +1
==========================================
- Hits 14200 14118 -82
- Misses 11098 11164 +66
Partials 661 661
*This pull request uses carry forward flags. Click here to find out more.
Continue to review full report at Codecov.
|
Blocked temporarily. Waiting to upgrade to the version with this fix in it: microsoft/playwright#18920 Now also waiting for this fix to drop: microsoft/playwright#18976 (v1.28.2 or v1.29.x) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
What happens when there are two trees on the page (create modal)? Does the secondary tree expand in the same way?
- The purpose of this is so that Playwright can perform actionability checks on the tree items. This will make operations involving expanding tree items much easier to perform in e2e.
- Use dynamic aria-label for different tree implementations - Get rid of CSS ids which are only for testing - Update percy tree scope selector
Updated the appAction to be able to take a tree selector so we can use this against both trees. Also updated trees to use |
… for expanding the object tree * style: add `visibility` to tree expand triangles - The purpose of this is so that Playwright can perform actionability checks on the tree items. This will make operations involving expanding tree items much easier to perform in e2e. * feat(e2e): Add AppAction to expand the entire tree * fix: wait for loading indicator * test: add test for `expandEntireTree` * test: update `expandEntireTree` and tree selectors - Use dynamic aria-label for different tree implementations - Get rid of CSS ids which are only for testing - Update percy tree scope selector * chore(lint): remove unused variable * refactor(e2e): update tree locators Co-authored-by: John Hill <[email protected]>
… for expanding the object tree (#6200) * style: add `visibility` to tree expand triangles - The purpose of this is so that Playwright can perform actionability checks on the tree items. This will make operations involving expanding tree items much easier to perform in e2e. * feat(e2e): Add AppAction to expand the entire tree * fix: wait for loading indicator * test: add test for `expandEntireTree` * test: update `expandEntireTree` and tree selectors - Use dynamic aria-label for different tree implementations - Get rid of CSS ids which are only for testing - Update percy tree scope selector * chore(lint): remove unused variable * refactor(e2e): update tree locators Co-authored-by: John Hill <[email protected]> Co-authored-by: John Hill <[email protected]>
Closes #5994
Describe your changes:
visibility
css attributes to the.c-disclosure-triangle
on the object tree, so that we can better locate expandable tree items within Playwright.All Submissions:
Author Checklist
Reviewer Checklist