Bump test-case from 1.2.0 to 2.0.2

[dependabot[bot]]

Bumps test-case from 1.2.0 to 2.0.2.

Release notes

Sourced from test-case's releases.

TestCase - v2.0.2

Bug fixes

• Fixed the fact that match X if Y didn't produce correct guard code which resulted in false positives.

Full Changelog: https://github.com/frondeus/test-case/compare/v2.0.1...v2.0.2

TestCase - v2.0.1

Bug fixes:

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

Full Changelog: https://github.com/frondeus/test-case/compare/v2.0.0...v2.0.1

TestCase - v2.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.

What's changed

New features

• => with |x: T| assert!(x) custom inline test assertions
• => using path::to::fn custom fn test assertions
• ignore and inconclusive can be combined with other keywords
• => it|is ... syntax is a built-in (previously required hamcrest2 crate integration)
• Simple test cases support returning Result<(), _> as #[test] attribute does #50

Improvements

• Code refactoring
• Test function is kept in its original scope so it can be reused for non-test related code #77
• Improved test case name selection

Breaking changes

• Deprecation of inconclusive within test description string - it will no longer act like modifier keyword
• Removal of hamcrest2 integration (it and is are kept, complex assertions now have different syntax)

---

Custom inline test assertions

Now it is possible to pass the closure which will assert the test case.

#[test_case(1.0 => with |v: f64| assert!(v.is_infinite()))]
#[test_case(0.0 => with |v: f64| assert!(v.is_nan()))]
fn divide_by_zero_f64_with_lambda(input: f64) -> f64 {
    input / 0.0f64
}

... (truncated)

Changelog

Sourced from test-case's changelog.

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
• Improved test case name selection

Breaking changes

• Deprecation of inconclusive within test description string - it will no longer act like modifier keyword
• Deprecation of hamcrest2 integration
• Deprecation of allow_result feature

V1.2.3

• Fix regression where panics and inconclusive were not allowed on test_cases returning a value
• Fix case where test_case would allow to return a type when only single attribute was used

V1.2.2

• test-case no longer allows returning values from tested function without => pattern (thanks to @​tarka)
  • Behaviour can be reenabled via allow_result feature

V1.2.1

• Disabled clippy warning when test-case was generating assert_eq(bool, bool) expression.

Commits

• 2853497 Release version to 2.0.2
• ff59e5e Add extra tests to ; fix not working cases; cleanup scripts
• 75bd091 Fix matches Pattern if condition test case
• 6301fbd Improve readme & changelog. Publish version 2.0.0.
• 1c43651 Update README. Move most of technical documentation to our wiki.
• 26e0fc4 Omit line with full path to hash-encoded dir
• c7ca456 Revert echo's in publish.sh
• 4b139fe Bump version to 2.0.0-rc3.
• c7a098c Tweak test_case handling (#88)
• f4edb1d Update README to mention rc2
• 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]]

Superseded by #264.