Run database tests when database cleaner changed
What does this MR do and why?
Run database tests when database cleaner changed
This is to avoid the incident gitlab-org/quality/engineering-productivity/master-broken-incidents#1106 (closed) and possibility for breaking master #395718 (closed)
If !113368 (merged) ran migration tests we can catch it in the merge request.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.