Skip to content

Possible async issues with tests #15

@solsson

Description

@solsson

The jest suite passes with #14, but I'm getting the following warnings:

Jest did not exit one second after the test run has completed.
This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with --detectOpenHandles to troubleshoot this issue.

Jest has detected the following 1 open handle potentially keeping Jest from exiting:
● ZLIB

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions