You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up to #431. We are currently not testing for CSP violations in CI, and instead we require devs to validate that no CSP violations were introduced by running the local dev env during PR review and inspecting the console log. That's asking for trouble.
[Backlog pruning 5/10] We currently check if the CSP changes in infra tests. We don't scan for violations, we do use report-uri.com to monitor CSP issues, but aren't monitoring it very actively. This would be worth doing, but not urgently.
Follow-up to #431. We are currently not testing for CSP violations in CI, and instead we require devs to validate that no CSP violations were introduced by running the local dev env during PR review and inspecting the console log. That's asking for trouble.
Let's wire up base Selenium tests to check for CSP violations. After a bit of reading, it appears it's currently impossible to inspect web console logs with Firefox as a Selenium driver, but with Chrome it may be possible.
The text was updated successfully, but these errors were encountered: