Follow-up from "Show when the last update to seats usage data was in the Billing page"
The following discussion from !42763 (merged) should be addressed:
-
@a_luna started a discussion: (+1 comment) @splattael from your comment, it seemed like adding more than a happy path spec would be a bit overkill here
🙃 but please let me know if you consider adding other case(s) would be valuable👀 🙌🏼
@splattael said in !42763 (comment 417925178):
Thanks for adding the spec
🙇 It looks good!Non-blocking I'd love to see a spec which cover the
nil
branch (if the job is not found) because self-managed instances might have persistent Redis.Personally, I am huge fan of Mutation Testing (e.g. https://github.com/mbj/mutant) which probably would have caught this missing spec
😅 I think we could follow-up on this.