From time to time security issues are discovered (ex. T133700) in new code. I suggest we have some unit tests/jenkins jobs checking some edits with oversighted content to see it really stays oversighted.
Description
Description
Related Objects
Related Objects
Event Timeline
Comment Actions
This sounds like a good idea for a browser test - add some suppressed content to the database, and then access the page through different endpoints to ensure it's not leaked somehow.
Comment Actions
I'm available for pairing and/or review if somebody wants to create a Selenium/browser test for this.