Closed gimmyhehe closed 2 weeks ago
The pull request introduces modifications to various Playwright test files, primarily focusing on the validation of SVG icons within action menus, dropdowns, and other UI components. Key changes include updates to assertions related to SVG path attributes and visibility checks, enhancing the accuracy of the tests. The overall structure of the tests remains largely unchanged, with adjustments made to specific checks and expected values.
File Path | Change Summary |
---|---|
examples/sites/demos/pc/app/action-menu/basic-usage.spec.ts |
Updated test to verify visibility of .tiny-dropdown__trigger .tiny-svg instead of SVG path attribute. |
examples/sites/demos/pc/app/action-menu/card-mode.spec.ts |
Changed assertion from counting circle elements to validating 'd' attribute of the first path element in SVG. |
examples/sites/demos/pc/app/action-menu/icon.spec.ts |
Adjusted index from nth(2) to nth(1) in one test case, affecting visibility expectations for SVG icons. |
examples/sites/demos/pc/app/button-group/show-more.spec.ts |
Replaced original regex for SVG path of "more" button with a new pattern for validation. |
examples/sites/demos/pc/app/date-picker/clear.spec.ts |
Updated expected SVG path attributes to use regex for matching instead of static strings. |
examples/sites/demos/pc/app/dropdown/basic-usage.spec.ts |
Removed assertion checking for specific SVG path attribute, simplifying the test. |
e2e-test
, bug
In the garden where icons play,
Tests now dance in a new ballet.
With paths that twist and turn just right,
Our dropdowns bloom, a lovely sight!
So hop along, let’s celebrate,
For every change, we elevate! 🐇✨
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
[e2e-test-warn] The component to be tested is missing.
The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".
Please make sure you've read our contributing guide
PR
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information
Summary by CodeRabbit
These changes enhance the reliability of the testing process, ensuring that the UI components behave as expected.