CHANGELOG.md

Changelog

3.3.1

Fixes

• Avoid emitting additional misleading error messages by proc-macro2-diagnostics (#138)

3.3.0

Features

• Allow comments in test-matrix macro (#132)

Improvements

• Drop proc-macro-error dependency & improve error messages (#136)

3.2.1

Improvements

• Update syn dependency to 2.0
• Ensure that test-case selects correct version of it's core and macros subcrates

3.2.0

Features

• Add test_matrix macro: generates test cases from Cartesian product of possible test function argument values (#128)

Improvements

• Retain allow attributes on test functions (#127)

3.1.0

Features

• Copy attribute span to generated test functions so that IDEs recognize them properly as individual tests

Improvements

• Added LICENSE file to child crates

3.0.0

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

Improvements

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

2.2.2

Fixes

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

2.2.1

Fixes

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

2.2.0

Features

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

2.1.0

Features

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

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

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

Fixes

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

2.0.0

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

Fixes

• 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

Fixes

• 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

Fixes

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

V1.2.0

Features

• Allow usage of fully qualified attribute #[test_case::test_case] (thanks to @tomprince)

Improvements

• Stopped code from emmiting unneded () expression in test cases with expected fragment (thanks to @martinvonz)

V1.1.0

Features

• Added support for using hamcrest2 assertions with test case
• Enabled support of async via tokio or similar
• Enabled attribute passthrough for test cases - it means that you can combine test-case with other testing frameworks, given at least one #[test_case] attribute appears before mentioned framework in testing function

Deprecation

• inconclusive inside test case name will not be supported starting 2.0.0

V1.0.0

Features

• Added support for three new keywords: panics, matches and inconclusive which can be applied after => token.

  matches gives possibility to test patterns, like:

  #[test_case("foo" => matches Some(("foo", _)))]

  panics gives should_panic(expected="...") for one test_case:

  #[test_case(true  => panics "Panic error message" ; "This should panic")]
  #[test_case(false => None                         ; "But this should return None")]

  inconclusive ignores one specific test case.- thanks to @luke_biel

  #[test_case("42")]
  #[test_case("XX" ; "inconclusive - parsing letters temporarily doesn't work, but it's ok")]
  #[test_case("na" => inconclusive ())]

Major improvements

• Added extra unit tests - thanks to @luke-biel
• Replace parented_test_case with parsing test_case directly from args - thanks to @luke-biel
• Added keeping trailing underscores in names - thanks to @rzumer

Minor improvements

• Moved lazy-static dependency to dev-dependencies
• Fixed README - thanks to @luke-biel and @drwilco

Upgraded dependencies

• Upgraded insta to 0.12.0

v0.3.3

Fixes

• Fixed "inconclusive" feature with different cases.

v0.3.2

Fixes

• Added support for impl Trait - it worked in v2.x crate.

Minor improvements

• Added extra test cases

Upgraded dependencies

• Upgraded version_check to v0.9.1

v0.3.1

Minor improvements:

• Refreshed readme
• Added CI for stable version of Rust. - thanks to @macisamuele
• Limited crate to Rust 1.29+ - thanks to @macisamuele

Upgraded dependencies:

• Upgraded syn, quote and proc-macro-2 to v1
• Upgraded lazy-static to 1.4.0
• Upgraded insta to 0.11.0

v0.3.0

Breaking changes

• Crate has new maintainer: Wojciech Polak ✋ 🎉

• Crate has new name, as test-case-derive had no meaning for derive part.

• Delimiter for test case description is ; instead of ::.

  Reason: :: is valid part of expression and rustc treats const variable as path

New features

• Proper error propagation 🎉 When there is for example a typo in function body, rustc can now show location of it instead of test_case location.
• Internally for tests crate uses cargo insta for snapshot testing
• Attribute is now compatible all other attributes like #[should_panic]