Closed shashwatahalder01 closed 1 month ago
The updates involve various refinements and additions across multiple test files, including adjustments to selectors, introduction of new methods for handling vendor verification settings, enhancements to API endpoint tests, and updates to test descriptions for clarity and consistency. These changes aim to improve functionality, maintainability, and coverage of the testing framework.
Files | Change Summary |
---|---|
tests/pw/pages/selectors.ts |
Added and removed selectors, updated existing ones, and introduced new methods for various elements. |
tests/pw/pages/settingsPage.ts |
Added a method setDokanVendorVerificationSettings in the SettingsPage class for handling Dokan vendor verification settings. |
tests/pw/tests/api/vendorVerification.spec.ts |
Introduced tests for vendor verification API endpoints covering methods like getting, creating, updating, and deleting verifications. |
tests/pw/tests/e2e/_coverage.teardown.spec.ts |
Adjusted access to a JSON object by fixing optional chaining syntax for reading the tests property. |
tests/pw/tests/e2e/admin.spec.ts |
Added checks for DOKAN_PRO environment variable and skipped a test based on the value of DOKAN_PRO . |
tests/pw/tests/e2e/privacyPolicy.spec.ts |
Updated a test description by removing a comment and adjusting the test function signature slightly. |
tests/pw/tests/e2e/settings.spec.ts |
Added a test for setting Dokan vendor verification settings in the Settings test suite (skipped as feature is not merged yet). |
tests/pw/tests/e2e/stores.spec.ts |
Updated test descriptions for admin actions related to vendors in an e-commerce scenario for clarity and consistency. |
tests/pw/utils/schemas.ts |
Modified various schema definitions including socialSchema , paypalSchema , paymentSchema , linksSchema , and added new schemas. |
tests/pw/utils/testData.ts |
Updated test data entries including file paths, URLs, and added new fields like vendorVerification with subfields. |
🐇 In the realm of code, where changes abound, A rabbit dances to the testing sound, New methods, tests, and schemas aligned, Ensuring our code is refined. With each update, the framework grows, Stronger, better, as the rabbit knows. 🌟
[!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
Refactor
goto
method for better performance.Chores
printWidth
setting in the configuration file for better code formatting.