Update tests to use best practices
What does this MR do and why?
Update tests to use best practices
- mock imports appropriately
- remove excessive nextTick
- do not spy on methods and instead track down where the changes are reflected in the UI and verify that instead
- do not override methods
Changelog: changed
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
![]() |
No changes |
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.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #391162 (closed)
Edited by Alexander Turinske