Improve commit_presenter_spec tests
What does this MR do and why?
Describe in detail what your merge request does and why.
Related #374505 (closed)
Before
Finished in 36.87 seconds (files took 9.09 seconds to load)
12 examples, 0 failures
[TEST PROF INFO] Time spent in factories: 00:28.058 (74.8% of total time)
[TEST PROF INFO] Factories usage
Total: 45
Total top-level: 33
Total time: 00:28.058 (out of 00:42.212)
Total uniq factories: 5
total top-level total time time per call top-level time name
12 12 27.0874s 2.2573s 27.0874s project
12 0 1.1104s 0.0925s 0.0000s namespace
12 12 0.7882s 0.0657s 0.7882s user
8 8 0.1750s 0.0219s 0.1750s ci_pipeline
1 1 0.0083s 0.0083s 0.0083s license
After
Finished in 10.58 seconds (files took 12.02 seconds to load)
12 examples, 0 failures
[TEST PROF INFO] Time spent in factories: 00:02.765 (24.82% of total time)
[TEST PROF INFO] Factories usage
Total: 11
Total top-level: 10
Total time: 00:02.765 (out of 00:16.682)
Total uniq factories: 4
total top-level total time time per call top-level time name
8 8 0.1436s 0.0180s 0.1436s ci_pipeline
1 1 0.0066s 0.0066s 0.0066s license
1 1 2.6147s 2.6147s 2.6147s project
1 0 0.1526s 0.1526s 0.0000s namespace
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.
Edited by Alina Mihaila