Public analysis · Mattermost
One PR. A constraint gap behind 9,856 production panics in a 32k-star platform.
TestMojo examined a public pull request to show how requirements can be mapped to test evidence. This is a public analysis, not a claim about the current state of Mattermost.
7
Requirements extracted
5
Verified gaps
14%
Coverage before
86%
Coverage after
Requirement-to-test traceability
Every row begins with the behavior that should hold.
R1Database rejects NULL username on insertGap
R2Database rejects empty-string username on insertGap
R3Migration backfills existing NULL or empty usernamesGap
R4Application validation still rejects invalid usernamesCovered
R5Plugin and webhook user creation respects the constraintPartial
R6Profile image generation handles valid usernamesGap
R7Migration rollback removes the constraint cleanlyGap
What this analysis shows
Missing protection is not automatically a bug. The point is to identify which paths are unknown, write targeted tests and make review evidence visible.
Read the public source change on GitHub before drawing conclusions about the live project.
Start with a real pull request
Bring a pull request from your own codebase.
Bring one real change. We’ll help you find the evidence worth reviewing.