Closed shashwatahalder01 closed 1 month ago
The recent updates introduce significant enhancements across various test files, focusing primarily on color palette management, vendor settings, and permissions. Notable changes include new methods for handling CSS styles, improved color customization features, and updated test cases for better coverage. Additionally, the feature map has been revised to reflect these updates and new permissions for different user roles.
Files/Paths | Change Summary |
---|---|
tests/pw/feature-map/feature-map.yml |
Updated feature definitions and permissions for admins, vendors, and customers across various pages. |
tests/pw/pages/basePage.ts |
Added methods getElementCssStyle and getElementPropertyValue for retrieving CSS styles and property values. |
tests/pw/pages/colorsPage.ts |
Introduced methods to manage color palettes, including adding predefined and custom palettes. |
tests/pw/pages/selectors.ts |
Renamed and added selectors related to color palettes and menus. |
tests/pw/pages/settingsPage.ts |
Modified setDokanColorSettings method to accept a paletteName string parameter. |
tests/pw/pages/vendorSettingsPage.ts |
Renamed vendorSettings object to settingsVendor and updated related method calls. |
tests/pw/tests/e2e/colors.spec.ts |
Added end-to-end tests for color scheme customizer feature. |
tests/pw/tests/e2e/followStore.spec.ts |
Updated test description for following a store. |
tests/pw/tests/e2e/settings.spec.ts |
Updated argument for admin.setDokanColorSettings method. |
tests/pw/utils/helpers.ts |
Added functions for color conversion and browser page management. |
tests/pw/utils/interfaces.ts |
Added new interface paletteValues for button and sidebar menu styling properties. |
tests/pw/utils/testData.ts |
Introduced new color palettes and values in the data object. |
In a world of code so bright, Colors dance from day to night. Palettes change with just a click, Admins, vendors, all in sync. With tests that guide and help us see, A vibrant, seamless harmony. 🌈
[!TIP]
New Features and Improvements
## Review Settings Introduced new personality profiles for code reviews. Users can now select between "Chill" and "Assertive" review tones to tailor feedback styles according to their preferences. The "Assertive" profile posts more comments and nitpicks the code more aggressively, while the "Chill" profile is more relaxed and posts fewer comments. ## AST-based Instructions CodeRabbit offers customizing reviews based on the Abstract Syntax Tree (AST) pattern matching. Read more about AST-based instructions in the [documentation](https://docs.coderabbit.ai/guides/review-instructions#ast-based). ## Community-driven AST-based Rules We are kicking off a community-driven initiative to create and share AST-based rules. Users can now contribute their AST-based rules to detect security vulnerabilities, code smells, and anti-patterns. Please see the [ast-grep-essentials](https://github.com/coderabbitai/ast-grep-essentials) repository for more information. ## New Static Analysis Tools We are continually expanding our support for static analysis tools. We have added support for `biome`, `hadolint`, and `ast-grep`. Update the settings in your `.coderabbit.yaml` file or head over to the settings page to enable or disable the tools you want to use. ## Tone Settings Users can now customize CodeRabbit to review code in the style of their favorite characters or personalities. Here are some of our favorite examples: - Mr. T: "You must talk like Mr. T in all your code reviews. I pity the fool who doesn't!" - Pirate: "Arr, matey! Ye must talk like a pirate in all yer code reviews. Yarrr!" - Snarky: "You must be snarky in all your code reviews. Snark, snark, snark!" ## Revamped Settings Page We have redesigned the settings page for a more intuitive layout, enabling users to find and adjust settings quickly. This change was long overdue; it not only improves the user experience but also allows our development team to add more settings in the future with ease. Going forward, the changes to `.coderabbit.yaml` will be reflected in the settings page, and vice versa. ## Miscellaneous - Turn off free summarization: You can switch off free summarization of PRs opened by users not on a paid plan using the `enable_free_tier` setting. - Knowledge-base scope: You can now set the scope of the knowledge base to either the repository (`local`) or the organization (`global`) level using the `knowledge_base` setting. In addition, you can specify Jira project keys and Linear team keys to limit the knowledge base scope for those integrations. - High-level summary placement: You can now customize the location of the high-level summary in the PR description using the `high_level_summary_placeholder` setting (default `@coderabbitai summary`). - Revamped request changes workflow: You can now configure CodeRabbit to auto-approve or request changes on PRs based on the review feedback using the `request_changes_workflow` setting.
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?
All Submissions:
Changes proposed in this Pull Request:
Related Pull Request(s)
Closes
How to test the changes in this Pull Request:
Changelog entry
Title
Detailed Description of the pull request. What was previous behaviour and what will be changed in this PR.
Before Changes
Describe the issue before changes with screenshots(s).
After Changes
Describe the issue after changes with screenshot(s).
Feature Video (optional)
Link of detailed video if this PR is for a feature.
PR Self Review Checklist:
FOR PR REVIEWER ONLY:
Summary by CodeRabbit
New Features
Bug Fixes
Tests
Enhancements