Use explicit rule names to avoid flaky specs
What does this MR do and why?
Use explicit rule names to avoid flaky specs
-
Test was flaky when relying on default(implicit) factory naming and sometimes sequence counters didn't match anymore.
Changelog: fixed EE: true
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.