[WPB-8881] Add unit tests for new effect actions#4331
Conversation
a8b9f2d to
458d5e0
Compare
416c464 to
fda4af8
Compare
|
@supersven , is there anything else you'd like me to change, update, or do about it? |
There was a problem hiding this comment.
Have you considered to add a test where the lookup fails? E.g. there is a code, but the key does not match?
There was a problem hiding this comment.
Just added it! I've rebased and pushed.
There was a problem hiding this comment.
Cool, thanks! (The more test code coverage we can add, the better - as long as the task doesn't grow out of bounds, of course 😄 )
There was a problem hiding this comment.
I'm wondering if it wouldn't be useful to also test what happens when the user does not exist. Or, can't this case not happen? 🤔
There was a problem hiding this comment.
Yeah, that can happen. I'd argue it's out of scope for this ticket. Lots of stuff hasn't been tested, and I've added tests for the actions that I introduced in that original PR. Looking up a user in the storage is not an action that was in that PR.
There was a problem hiding this comment.
Ah, I see. Then, I'm approving. 👍
fda4af8 to
bca9dea
Compare
Co-authored-by: Sven Tennie <sven.tennie@wire.com>
bca9dea to
184c598
Compare
This is a follow-up PR to #4316 that adds unit tests for effect actions that were introduced in that PR.
Tracked by https://wearezeta.atlassian.net/browse/WPB-8881
Checklist
changelog.d