Skip to content

Fix suppress cross-db modification checks in feature specs

What does this MR do and why?

Previously this was only disabling at the Thread.current level which does not work correctly for features (capybara) specs because puma runs in a different thread so it does not actually suppress the analyzer for puma.

We still need to keep the Thread.current approach to suppressing as this is how we suppress cross-db modification checking in production.

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.

Merge request reports

Loading