Increase test coverage for `:fail-fast`?

[vemv]

This will help reliably coming up with a fix for https://github.com/weavejester/eftest/issues/75.

Coverage is extended by:

• providing counterexamples for each test case
• also exercising exception handling, whether it happens in the deftest body, or in fixtures.

[atomist[bot]]

Commit messages of this repository should follow the seven rules of a great Git commit message, as mentioned in the project's contributing guidelines. It looks like there's a few issues with the commit messages in this pull request:

• The commit message should not contain markdown.
• The commit message body has a line over 72 characters.

[vemv]

The commit message should not contain markdown.

Are you on board with this one? Some months ago GH added pretty rendering for markdown in various places of the UI, which invites one to create less ambiguous communication:

[vemv]

(Fat-fingered the close button)

[vemv]

Thanks for the review! It's ready again.

[vemv]

Ready again!

[vemv]

(ping)

[weavejester]

Sorry for the delay. It looks fine - can you squash down your commits?

[atomist[bot]]

Commit messages of this repository should follow the seven rules of a great Git commit message, as mentioned in the project's contributing guidelines. It looks like there's a few issues with the commit messages in this pull request:

• The commit message should not contain markdown.
• The commit message body has a line over 72 characters.

[atomist[bot]]

Commit messages of this repository should follow the seven rules of a great Git commit message, as mentioned in the project's contributing guidelines. It looks like there's a few issues with the commit messages in this pull request:

• The commit message should not contain markdown.

[vemv]

The commit message body has a line over 72 characters.

Satisfied

The commit message should not contain markdown.

Left as-is see https://github.com/weavejester/eftest/pull/85#issuecomment-937713217

[weavejester]

The commit message should not contain markdown.

Are you on board with this one? Some months ago GH added pretty rendering for markdown in various places of the UI, which invites one to create less ambiguous communication:

I'd prefer plaintext, please. Not all git log viewers support markdown. So a better commit message might be:

Increase test coverage for :fail-fast option

Coverage is extended by checking exceptions and the base case when
:fail-fast is false.

You also mention #75 in the commit message, but these tests pass, don't they? How do you see them helping with that issue?