Closed PEZ closed 9 months ago
After the one comment, lgtm
Thanks! Can you have a look again that I got it right? I'm not super savvy with async tests.
We have an deftest-async
macro that maybe should be used...
I changed so that we now use the deftest-async
macro, which ensures we call done
properly also on errors.
This replaces PR:
113
[x] I have read the developer documentation.
[x] This PR corresponds to an issue with a clear problem statement.
[x] This PR contains a test to prevent against future regressions
[x] I have updated the [Unreleased] section of the CHANGELOG.md file with a link to the addressed issue.