Skip to content

Add tests #6

@arcanis

Description

@arcanis

Because of reentrance & whatnot, the code flow might be a bit hard to follow sometimes, and I would feel more confident if we had tests to validate that the behaviour doesn't break (or at least, that it breaks because bugs are being fixed).

A few things to test:

  • A regular action should dispatch a single notification
  • Two regular actions should dispatch two different notifications
  • An empty batched action should dispatch no notification
  • A batched action should dispatch a single notification
  • A batched action emitted from within a saga should dispatch a single notification
  • A batched action asynchronously emitted from within a saga should dispatch a single notification
  • Two actions asynchronously emitted from within a saga should dispatch two different notifications

I still have to think about a good reentrant test.

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