Update test-case requirement from 2.0.2 to 3.0.0

[dependabot[bot]]

Updates the requirements on test-case to permit the latest version.

Release notes

Sourced from test-case's releases.

Test Case - v3.0.0

Overview

This crate provides the #[test_case] procedural macro attribute that generates multiple parametrized tests using one body with different input parameters. A test is generated for each data set passed in the test_case attribute. Under the hood, all test cases that share the same body are grouped into a mod, giving clear and readable test results.

Changes

• Split out test-case-core crate, allowing easier reuse in external crates. By @​evforde

IMPORTANT

Starting with the 3.0 release, we are changing test-case MSRV policy. We no longer can maintain our goal of only bumping MSRV with major SemVer releases partly due to how fast rust landscape changes and partly to how the rest of the rust ecosystem prefers instead not to keep MSRV breakage treated as SemVer breakage, making stricter policies hard to maintain with limited resources we have. The current goal is to support up to 3 of the latest stable releases. We hope that with this change, we'll be able to speed up test-case's maintenance processes and add more features in the coming months.

Changelog

Sourced from test-case's changelog.

3.0.0

[IMPORTANT] Starting with 3.0 release we are changing test-case MSRV policy to support only 3 latest stable releases.

Changes

• Split out functional parts of test-case-macros crate into test-case-core for easy reuse by external libraries

2.2.2

Bugfixes

• Use fully qualified test macro path to avoid conflicts in workspace (#105)

2.2.1

Bugfixes

• Ensure test-case depends on correct version of test-case-macros

2.2.0

New features

• Support ignore["reason"] syntax (#102)

2.1.0

New features

• Support matches_regex complex test-case (requires with-regex feature) (#98)
• Support len, count and empty complex test-cases (#97)

Bug fixes

• Support keyword ignore on void fn (#100)

Improvements

• Move macros to separate subcrate so that test-case can export other things (#96)

2.0.2

Bug fixes

• Covered missing cases in matches X if Y test_case variant (fixes the fact that previous bug fix didn't produce guard code)

2.0.1

Bug fixes

• matches Pattern if condition parses correctly (if condition part wasn't allowed)

2.0.0

New features

• => with |x: T| assert!(x) custom inline test assertions
• => using path::to::fn custom fn test assertions
• ignore|inconclusive can be combined with other keywords (eg.: => ignore matches Ok(_))
• => it|is ... syntax is a built-in (previously required hamcrest2 crate integration)
• Tested items are left in place where they were defined #77
• Simple test cases allow Result<(), _> return types similar to native #[test] macro

Improvements

• Significant code refactoring

... (truncated)

Commits

• aa655a3 Include 'test-case-core' in the version bump
• b093c70 Bump version to 3.0
• 70a962f Separate parsing utils into new test-case-utils crate (#114)
• 5755171 Update test-case msrv policy (#115)
• 29db360 Bump version to v2.2.2
• 2c05a1b Use fully qualified #[test] attribute path (#105)
• c22709f Lock dependency versions in child crates
• 5f5c695 Update tests to latest nightly and stable
• 4cc37f1 Lock once-cell version
• 72d2472 Bump version to 2.2.1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[crjeder]

Update dependencies