Continuing to adopt the new framework, this time focusing on coverage for ReactionHasBeenAdded and ReactionHasBeenRemoved.
As part of these changes, I abandoned the previous optimization to skip setting up the test framework from main_test.go until the first test that uses it. There is a significant downside to doing so for the first test: all logs from the setup are incorrectly associated with that test, making it harder to trace what happened. Since we're migrating everything anyway, it doesn't seem necessary to keep the optimization unto itself.
Summary
Continuing to adopt the new framework, this time focusing on coverage for
ReactionHasBeenAddedandReactionHasBeenRemoved.As part of these changes, I abandoned the previous optimization to skip setting up the test framework from
main_test.gountil the first test that uses it. There is a significant downside to doing so for the first test: all logs from the setup are incorrectly associated with that test, making it harder to trace what happened. Since we're migrating everything anyway, it doesn't seem necessary to keep the optimization unto itself.Ticket Link
None.