Update Rust crate test-case to v2 - autoclosed #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1
->2
Release Notes
frondeus/test-case
v2.2.2
Compare Source
Bugfixes
test
macro path to avoid conflicts in workspace (#105)v2.2.1
Compare Source
Bugfixes
test-case
depends on correct version oftest-case-macros
v2.2.0
Compare Source
New features
ignore["reason"]
syntax (#102)v2.1.0
Compare Source
New features
matches_regex
complex test-case (requireswith-regex
feature) (#98)len
,count
andempty
complex test-cases (#97)Bug fixes
ignore
on void fn (#100)Improvements
v2.0.2
Compare Source
Bug fixes
matches X if Y
test_case variant (fixes the fact that previous bug fix didn't produce guard code)v2.0.1
Compare Source
Bug fixes
matches Pattern if condition
parses correctly (if condition
part wasn't allowed)v2.0.0
Compare Source
New features
=> with |x: T| assert!(x)
custom inline test assertions=> using path::to::fn
custom fn test assertionsignore|inconclusive
can be combined with other keywords (eg.:=> ignore matches Ok(_)
)=> it|is ...
syntax is a built-in (previously requiredhamcrest2
crate integration)Result<(), _>
return types similar to native#[test]
macroImprovements
Breaking changes
inconclusive
within test description string - it will no longer act like modifier keywordhamcrest2
integrationallow_result
featurev1.2.3
Compare Source
panics
andinconclusive
were not allowed ontest_cases
returning a valuetest_case
would allow to return a type when only single attribute was usedv1.2.2
Compare Source
test-case
no longer allows returning values from tested function without=>
pattern (thanks to @tarka)allow_result
featurev1.2.1
Compare Source
assert_eq(bool, bool)
expression.v1.2.0
Compare Source
New features
#[test_case::test_case]
(thanks to @tomprince)Improvements
()
expression in test cases withexpected
fragment (thanks to @martinvonz)v1.1.0
Compare Source
New features
hamcrest2
assertions with test caseasync
via tokio or similartest-case
with other testing frameworks,given at least one
#[test_case]
attribute appears before mentioned framework in testing functionDeprecation
inconclusive
inside test case name will not be supported starting2.0.0
v1.0.1
: TestCase - v1.0.1Compare Source
Legacy release supporting MSRV < 1.39, including syn::export fix
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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.