-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap: 2.0.0 and beyond #74
Labels
next release
Issues that are meant to release with next minor/major release
Comments
Merged
Closing in favor of project |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a tracking issue for
test_case
roadmap beyond1.x
.Features are waiting to be implemented or are being currently implemented.
2.0.0
is coming with major codebase rewrite, thus it will be released asrc
first to test stability and portability from1.x
versions.# 2.0.0removal ofinconclusive
within description (currently deprecated)removal ofhamcrest_assertions
in favor of custom solutionis
andit
modifiers have to be first class citizens #75#[test_case(args => with |x: T| assert!(...))]
for inline custom assertions Add possibility to replaceassert_eq!
with custom assertion #31#[test_case(args => using $path)]
for custom assertion reuse Add possibility to replaceassert_eq!
with custom assertion #31leave tested fn item in place where it's written Leave annotated item outside test module #77default#[test_case]
with no return type matching supportResult<(), E> where E: Error
similar to#[test]
macro Result::Err is not interpreted as a failure #50beyond
test_cases
via#[test_case_handler($path)]
attribute Allow replacement of test-case assertion on per-fn scale #83#[test_case(args as function_name)]
,#[test_case(args => result as function_name)]
and#[test_case(args => result ; "description" as function_name)]
Bad custom test names should not fail silently #72with |val| {body}
can skip type annotation on closure #95research needed
with |val: T| -> bool {body}
is allowed withoutassertion
within bodytest_case
block Access test case name from test case body #37test_case
could look aftercustom_test_frameworks
are stabilized: https://github.com/luke-biel/interrogateThe text was updated successfully, but these errors were encountered: