Ensure specs are under saas context when needed
What does this MR do and why?
Refactoring to ensure spec examples are under :saas
context when required.
This is split into several MRs, to reduce chance of conflict.
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.
Related to #214434 (closed)