-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat(tests): add e2e tests for widgets #8735
Conversation
Cool! |
@syuilo No clue 😕 Before the final push, that case worked...so I assume that it's something timeout-related mainly and we might need to adjust something here so that it consistently works. Here's the last action run on my fork before I made the PR, and there it passed fine! This also might be an issue with the |
👍🏻👍🏻👍🏻 |
What
This PR adds 22 end-to-end test cases for adding all widgets to the widget sidebar.
3 basic tests:
Edit widgets
button is presentEdit widgets
has been pressed (Edit mode)19 tests for all current widgets
Why
After the recent merge of the widget refactoring/lint issues a lot of regressions happened. Testing if widgets are present after being added at least makes sure that they are not breaking the application completely.
Additional info (optional)
mk-widget-edit/select/add
classes to mark up the elements that are used to add widgetsmkw-*
classes to the widgets that had them missingmkw-{widgetName}
is present after being added