Improve merge requests feature specs
What does this MR do and why?
Describe in detail what your merge request does and why.
Related #375006 (closed)
Before
Finished in 1 minute 39.37 seconds (files took 8 seconds to load)
7 examples, 0 failures
[TEST PROF INFO] Time spent in factories: 00:19.853 (19.82% of total time)
[TEST PROF INFO] Factories usage
Total: 37
Total top-level: 23
Total time: 00:19.853 (out of 01:44.427)
Total uniq factories: 6
total top-level total time time per call top-level time name
8 8 2.4042s 0.3005s 2.4042s merge_request
7 7 17.0331s 2.4333s 17.0331s project
7 0 0.7406s 0.1058s 0.0000s namespace
7 0 0.1058s 0.0151s 0.0000s ci_pipeline
7 7 0.4087s 0.0584s 0.4087s user
1 1 0.0071s 0.0071s 0.0071s license
After
Finished in 1 minute 14.72 seconds (files took 7.24 seconds to load)
7 examples, 0 failures
[TEST PROF INFO] Time spent in factories: 00:03.784 (5.02% of total time)
[TEST PROF INFO] Factories usage
Total: 7
Total top-level: 5
Total time: 00:03.784 (out of 01:19.177)
Total uniq factories: 6
total top-level total time time per call top-level time name
2 2 1.2212s 0.6106s 1.2212s merge_request
1 1 0.0059s 0.0059s 0.0059s license
1 1 2.4892s 2.4892s 2.4892s project
1 0 0.1254s 0.1254s 0.0000s namespace
1 1 0.0682s 0.0682s 0.0682s user
1 0 0.0514s 0.0514s 0.0000s ci_pipeline
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.
-
I have evaluated the MR acceptance checklist for this MR.