Skip to content
This repository was archived by the owner on Jul 7, 2025. It is now read-only.
This repository was archived by the owner on Jul 7, 2025. It is now read-only.

Document before and after behavior #112

@schneems

Description

@schneems

First of all I love your project. Thank you for your work. I hit a bit of an issue with some of my expectations of this library and was wondering if we can clarify what should be expected to happen with different before and after blocks with this gem.

Here's my raw issue heroku/hatchet#110. In the issue we're basically running a test in the background via a thread, and then joining the threads in anafter task. It looks like when a test fails due to an after task that it does not get re-run. Is that correct? Can we document the behavior? Would it be easy/possible to re-run the whole test that fails in this way?

I'm happy to send you a doc PR, but I want to make sure I understand the desired behavior here first.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions