Skip to content

Releases: haf/expecto

v4.0.3 – FsCheck bump, correcting docs

19 Feb 15:56
@haf haf
Compare
Choose a tag to compare

v4.0.1 – Bugfix --filter cmd line flag

19 Feb 11:32
@haf haf
Compare
Choose a tag to compare

Filtering tests is now unit-tested and working.

Testing,
Let's me do my resting,
Outside of work,
Because I know the code won't bork.

v4.0.0 – Grouped async and stress tests

17 Feb 11:50
@haf haf
Compare
Choose a tag to compare

Thanks to the great work of @AnthonyLloyd we now support stress tests and grouped async/parallel tests in expecto!

You write your tests like normal, and if you want to enable stress testing, just pass the corresponding flag to your executable.

Use testSequencedGroup to group sequential tests. This means that things which are not sequenced to the group will run in parallel to the group. Docs

More docs in the README.

v3.2.1 – Expect messages improvements

25 Jan 09:10
@haf haf
Compare
Choose a tag to compare

Minor improvements to the Expect assertion messages. Thanks to @isaacabraham for his contribution.

v3.2.0 – Logo, parallel-args bug fix, FsCheck printer, docs

17 Jan 21:20
@haf haf
Compare
Choose a tag to compare

expecto-logo-large

In this release we have a new logo! Rejoice and thanks to @sergey-tihon for his awesome work! This library now also has a nice twitter account @ExpectoIO.

v3.2.0 is a minor bump in version because we have a new feature – support for ptestProperty to make test properties pending, support for passing the standard gen-seed to FsCheck and a brand new FsCheck printer that nicely formats the output from FsCheck as it runs. Many thanks go out to @AnthonyLloyd for adding these improvements.

Version 3.0+ introduced a bug when you turn off parallelism with { config with parallel = false }, causing some test suites to hang and others to crash. This release fixes that bug (#83).

We'd also like some feedback with regards to our plans for supporting stress testing, so if you are on github, do check it out and perhaps give your opinion.

Happy testing!
Henrik

v3.1.0 – TeamCity printers

11 Jan 15:28
@haf haf
Compare
Choose a tag to compare

Expecto now supports TeamCity out of the box. If the test framework is running inside a TeamCity instance, it will notice it and print accordingly.

Thanks to @theimowski for contributing this!

v3.0.2 – Downgrade BenchmarkDotNet

10 Jan 22:54
@haf haf
Compare
Choose a tag to compare

v3.0.1 – bugfix release for FileNotFoundException w/ Cecil

10 Jan 22:54
@haf haf
Compare
Choose a tag to compare

v3.0.0 – Ionide highlighting infra, `testCaseAsync`

09 Jan 13:54
@haf haf
Compare
Choose a tag to compare

The v3 release comes with new bells and whistles – it now supports async tests and has out-of-the box integration with Ionide's test location support. When you write a test in Ionide you can now use Expecto out of the box to run them and run them on code changes! After running them you'll get highlights in the editor to show which failed and which passed. Thanks to @Krzysztof-Cieslak for his contributions!

https://video.twimg.com/tweet_video/C1lBWlYWEAATB53.mp4

Asserting on floats with floatClose

There's also a new Expect.floatClose assertion function that's more robust than floatEquals. We've updated the docs for you, and there's this pull request with the background. Thanks @AnthonyLloyd for your contributions!

Async test support

@AnthonyLloyd Has also contributed a new asynchronous test runner to fix issue #2. You can create async tests with testCaseAsync "name" async {} and they'll be run like they should.

Remember testSequenced

When you run performance tests or use Expect.fasterThan, remember to use the newly added testSequenced function that can tag Test-values (testList, testCase, testCaseAsync) to make your tests robust to run in parallel.

Happy testing!
Henrik

v2.4.1 – Support failing tests if there are focused tests

04 Jan 10:46
@haf haf
Compare
Choose a tag to compare
  • This release provides a runTestsWithArgs function which runs the passed tests and also overrides the passed ExpectoConfig with the command line parameters.
  • Expecto now accepts the command line argument --fail-on-focused-tests, which checks if focused tests exist. This parameter can be set in build scripts and allows CI servers to reject commits that accidentally included focused tests.

If someone has focused a test but not unfocused it before committing, you can now have the CI server go red! ;)