Update Rust crate rstest to 0.26.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
rstest	dependencies	minor	0.12.0 → 0.26.0
rstest	dev-dependencies	minor	0.12.0 → 0.26.0

---

Release Notes

la10736/rstest (rstest)

v0.26.1

Compare Source

Fixed

• Docs

v0.26.0

Compare Source

Changed

• The #[files(...)] attribute now ignores matched directory paths by default.
  See #​306 thanks to @​Obito-git.

Add

• Introduced the #[dirs] attribute, which can be used with #[files(...)] to explicitly include directory paths.
  See #​306 thanks to @​Obito-git.
• The CI now runs builds and tests on Windows, as well.
• #[test_attr] to define test attribute explicit and also enable the use of
  #[macro_rules_attribute::apply(<macro>)]: naw also smol works. See
  #​303
  #​311
  #​315
  thanks to @​coriolinus.

Fixed

• Removed unsued trait and impl spotted out on 1.89.0-nightly
• Add missed tests about ignore attribute's args in rstest expansion.
  See #​313
• The #[files(...)] attribute now works reliably on Windows.
• Now global attributes can go everywhere in the list also where case is used

v0.25.0

Compare Source

Changed

• Append generated test macro so next test macros are aware of it
  (see #​291 thanks to @​kezhuw).

Add

• Added a #[mode = ...] attribute to be used with the #[files(...)] attribute to change the way
  the files get passed to the test.
  (see #​295 thanks to @​lucascool12)

v0.24.0

Compare Source

Changed

• MSRV to 1.70.0 (see #​284 thanks to @​rnbguy)

Add

• #![no_std] support: now you can use rstest also in no_std lib
  (see #​282 thanks to @​rnbguy)
• #[context] to have test function name and other useful thighs on
  the tip of your fingers (see #​177)

v0.23.0

Compare Source

Add

• You can now use environment variables in #[files] with an optional default value (see #​277).
• You can now set a base_dir for #[files] with the $[base_dir = "..."] attribute (see #​277).

v0.22.0

Compare Source

Changed

• Now it's possible destructuring input values both for cases, values and fixtures. See #​231 for details

Add

• Implemented #[ignore] attribute to ignore test parameters during fixtures resolution/injection. See #​228 for details

Fixed

• Lot of typo in code

v0.21.0

Compare Source

Changed

• Add feature crate-name enabled by default to opt-in crate rename
  support. See #​258

v0.20.0

Compare Source

Add

• Implemented #[by_ref] attribute to take get a local lifetime for test arguments.
  See #​241 for more details. Thanks to
  @​narpfel for suggesting it and useful discussions.
• Support for import rstest with another name. See #​221

Fixed

• Don't remove Lifetimes from test function if any. See #​230
  #​241 for more details.
• PathBuf does no longer need to be
  in scope when using #[files] (see #​242)
• #[from(now::accept::also::path::for::fixture)] See #​246
  for more details

v0.19.0

Compare Source

Changed

• Defined rust-version for each crate (see #​227)

Fixed

• #[once] fixtures now require the returned type to be
  Sync to prevent UB
  when tests are executed in parallel. (see #​235
  for more details)

• #[future(awt)] and #[awt] now properly handle mutable (mut) parameters by treating futures as immutable and
  treating the awaited rebinding as mutable.

v0.18.2

Compare Source

Changed

• Now #[files] accept also parent folders (see #​205
  for more details).

v0.18.1

Compare Source

Fixed

• Wrong doc test
• Docs

v0.18.0

Compare Source

Add

• Add support for RSTEST_TIMEOUT environment variable to define a max timeout
  for each function (see #​190 for details).
  Thanks to @​aviramha for idea and PR
• #[files("glob path")] attribute to generate tests based on files that
  satisfy the given glob path (see #​163 for details).

Changed

• Switch to syn 2.0 and edition 2021 : minimal Rust version now is 1.56.0
  both for rstest and rstest_reuse (see #​187)

Fixed

• Fixed wired behavior on extraction #[awt] function attrs (See
  #​189)

v0.17.0

Compare Source

Add

• Add #[awt] and #[future(awt)] to .await future input

Fixed

• Fixed wrong message when timeout tests panic before timeout expire (See #​171)

v0.16.0

Compare Source

Changed

• Show TEST START banner only when trace some argument: See #​158 for details.
• Add values to test name: See #​160 for details.

Fixed

• Updated test fixtures to 1.64.0 compiler's error messages.

v0.15.0

Compare Source

Fixed

• Timeout not compile if one of its test arguments il not a copy
  type [see #​154]

v0.14.0

Compare Source

Changed

• Feature gated async timeout via async-timeout feature [see #​148]

Fixed

• Removed async-std build dependency [see #​148]

v0.13.0

Compare Source

Add

• #[timeout(duration)] test implementation for both sync and async tests (See #​136)

Changed

• Split rstest in separated crates for macro and libs (See #​32)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.