10 releases (4 breaking)

0.4.1 Apr 8, 2019
0.4.0 Apr 8, 2019
0.3.0 Nov 24, 2018
0.2.4 Aug 18, 2018
0.0.0 Jul 21, 2018

#11 in #unit-test

Download history 7/week @ 2021-07-01 25/week @ 2021-07-08 100/week @ 2021-07-15 339/week @ 2021-07-22 427/week @ 2021-07-29 432/week @ 2021-08-05 537/week @ 2021-08-12 468/week @ 2021-08-19 196/week @ 2021-08-26 499/week @ 2021-09-02 462/week @ 2021-09-09 480/week @ 2021-09-16 472/week @ 2021-09-23 474/week @ 2021-09-30 725/week @ 2021-10-07 993/week @ 2021-10-14

113 downloads per month
Used in radix_fmt

Apache-2.0

100KB
2K SLoC

Latest Version Documentation Lines of Code

fluid is a library to write human readable tests.

This crate is in alpha state. It is fully usable, but one can (rightfully) think that there are incomplete or missing features. The maintainer would be very happy if he was given some feedback, issues, pull requests, etc.


fluid is a crate to make the tests more readable and easier to write, mainly inspired by xUnit. It is still in an unstable state. Be adviced that in future alphas — let alone in the release — it could/will be very different.

Wiki

Detailed information is in the wiki.

Goals

The current goals are to provide:

  • ☑ Easily readable tests: they should be read like english sentences.
  • ☑ Nice and understandable error messages.
  • ☐ The most possible useful assertions for common cases: numbers, Iterators, Options, Results, etc.
  • ☐ A full test framework that launches the tests, displays the failures, etc. Since this feature is not stabilized, it will be gated in the nightly compiler.

Non-goals:

  • Run the tests fast: under the hood, there are some code generation at compile-time, especially for the #[theory] and/or #[session] tests. This will never be as fast as the standard tests.

Known bugs/limitations

  • The stringification of the left element is not perfect when the procedural macros are used. That is because there is no way to render the token as they were written by the user (as far as I know).
  • Hygiene issue. For now, every span is located at the macro call site. That means that the tests report a failure at the #[fact], #[theory] or #[session] line.

Changelog

See the dedicated file.

Roadmap

See the dedicated file.

Dependencies

~2.5MB
~54K SLoC