Update Rust crate test-case to v3 #12
Open
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
->3
Release Notes
frondeus/test-case (test-case)
v3.3.1
Compare Source
Fixes
v3.3.0
Compare Source
Features
test-matrix
macro (#132)Improvements
proc-macro-error
dependency & improve error messages (#136)v3.2.1
Compare Source
Improvements
syn
dependency to 2.0test-case
selects correct version of it'score
andmacros
subcratesv3.2.0
Compare Source
Features
test_matrix
macro: generates test cases from Cartesian product of possible test function argument values (#128)Improvements
allow
attributes on test functions (#127)v3.1.0
Compare Source
Features
Improvements
v3.0.0
Compare Source
[IMPORTANT] Starting with 3.0 release we are changing
test-case
MSRV policy to support only 3 latest stable releases.Improvements
test-case-macros
crate intotest-case-core
for easy reuse by external librariesv2.2.2
Compare Source
Fixes
test
macro path to avoid conflicts in workspace (#105)v2.2.1
Compare Source
Fixes
test-case
depends on correct version oftest-case-macros
v2.2.0
Compare Source
Features
ignore["reason"]
syntax (#102)v2.1.0
Compare Source
Features
matches_regex
complex test-case (requireswith-regex
feature) (#98)len
,count
andempty
complex test-cases (#97)Fixes
ignore
on void fn (#100)Improvements
v2.0.2
Compare Source
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
Fixes
matches Pattern if condition
parses correctly (if condition
part wasn't allowed)v2.0.0
Compare Source
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
Fixes
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
Fixes
test-case
no longer allows returning values from tested function without=>
pattern (thanks to @tarka)allow_result
featurev1.2.1
Compare Source
Fixes
assert_eq(bool, bool)
expression.v1.2.0
Compare Source
Features
#[test_case::test_case]
(thanks to @tomprince)Improvements
()
expression in test cases withexpected
fragment (thanks to @martinvonz)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 was generated by Mend Renovate. View the repository job log.