Add e2e tests for Drag-and-Drop in the inserter#44631
Conversation
|
Size Change: +1 B (0%) Total Size: 1.28 MB
ℹ️ View Unchanged
|
d8ad8df to
e325500
Compare
9ac2232 to
91bfe4a
Compare
17275e8 to
bb5f0d3
Compare
test/e2e/playwright.config.ts
Outdated
There was a problem hiding this comment.
This is kinda unfortunate for linux developers. I'll try to raise an issue upstream. Maybe we should consider only running chromium tests when developing locally?
There was a problem hiding this comment.
Opened an issue here: microsoft/playwright#18013.
|
Would be good to get CI passing in this PR. I think the problem causing them to fail has been solved in |
8f638a4 to
2fbbbc8
Compare
|
Nice job working through the kinks in getting the cross-browser testing in place @kevin940726 👌 Everything tests well for me, changes make sense, and CI is passing. I'm inclined to approve this PR but think it might be better to get the official green light from someone with more expertise in this area. |
talldan
left a comment
There was a problem hiding this comment.
Nice work, looks good to me!
c1ad83c to
ecb0a43
Compare
What?
Close #31356. Add drag-and-drop e2e tests for the global inserter.
This PR also tries to add cross-browser testing with firefox and webkit, powered by Playwright.
Why?
Because more tests = better! It will also make a potential refactor of the drag-and-drop feature easier to implement.
How?
By default, e2e tests are only run in chromium. We can enable testing in firefox and webkit by appending the
@firefoxor@webkittag to the test title. The tag also works intest.describeand will apply to all the nested tests. We can append-firefox,-webkit, or-chromiumto individually disable testing in some browsers.Testing Instructions
CI should pass.