Skip to content

Conversation

@fi3ework
Copy link
Member

bump Rstest to 0.8.0.

@fi3ework fi3ework marked this pull request as ready for review January 21, 2026 11:41
@fi3ework fi3ework enabled auto-merge (squash) January 21, 2026 11:41
@gemini-code-assist
Copy link

Summary of Changes

Hello @fi3ework, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on upgrading the Rstest testing framework to its latest 0.8.0 version across various modules within the project. This ensures that the project benefits from the newest features, performance improvements, and bug fixes provided by the updated framework and its associated packages. The update also streamlines test execution commands and standardizes browser testing configurations.

Highlights

  • Dependency Updates: The @rstest/core package has been updated from version 0.7.9 to 0.8.0 across multiple package.json files. Several related @rstest/* packages, such as @rstest/adapter-rsbuild, @rstest/browser, @rstest/browser-react, @rstest/coverage-istanbul, and @rstest/adapter-rslib, have also been bumped to their respective 0.8.0 or 0.2.0 versions.
  • Script Command Changes: The test script in rstest/browser-rsbuild-react/package.json and rstest/browser-rsbuild-vanilla/package.json has been simplified from rstest run to rstest. Additionally, a new test:watch script has been added to these files, allowing for continuous testing with the --watch flag.
  • Browser Test Configuration: The rstest.config.ts files for browser-based tests (rstest/browser-rsbuild-react/rstest.config.ts and rstest/browser-rsbuild-vanilla/rstest.config.ts) now explicitly define provider: 'playwright' within their browser configuration, ensuring Playwright is used for browser testing.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly bumps Rstest to version 0.8.0 and updates the necessary configurations and scripts. The changes look good. I've made one suggestion to improve consistency in dependency versioning. Additionally, I noticed you've updated the test script from rstest run to rstest in some packages. To maintain consistency across the monorepo, it would be beneficial to apply this change to other packages that still use the rstest run command.

"@rsbuild/core": "^1.7.2",
"@rsbuild/plugin-react": "^1.4.3",
"@rstest/core": "0.7.9",
"@rstest/core": "0.8.0",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For consistency with the other packages in this monorepo, consider using a caret ^ for this dependency's version. This allows for non-breaking patch and minor updates automatically. Most other package.json files in this project use a caret version for @rstest/core.

Suggested change
"@rstest/core": "0.8.0",
"@rstest/core": "^0.8.0",

@fi3ework fi3ework merged commit 546a8d7 into rstackjs:main Jan 21, 2026
1 check passed
@fi3ework fi3ework deleted the rstest080 branch January 21, 2026 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant