Skip to content

Use let_it_be in related_issues_spec.rb

Alina Mihaila requested to merge am-use-let-it-be-related-issues-specs into master

What does this MR do and why?

Describe in detail what your merge request does and why.

Related #375006 (closed) Before

Finished in 3 minutes 36.3 seconds (files took 26.58 seconds to load)
28 examples, 0 failures

[TEST PROF INFO] Time spent in factories: 00:14.641 (6.26% of total time)
[TEST PROF INFO] Factories usage

 Total: 222
 Total top-level: 132
 Total time: 00:14.641 (out of 03:58.741)
 Total uniq factories: 7

   total   top-level     total time      time per call      top-level time               name

      49          49        1.8597s            0.0380s             1.8597s              issue
      49           0        0.3570s            0.0073s             0.0000s     work_item_type
      41          41       10.9139s            0.2662s            10.9139s project_empty_repo
      41           0        3.1389s            0.0766s             0.0000s          namespace
      25          25        1.7460s            0.0698s             1.7460s               user
      16          16        0.1075s            0.0067s             0.1075s         issue_link
       1           1        0.0143s            0.0143s             0.0143s            license

After

Finished in 2 minutes 25.7 seconds (files took 9.67 seconds to load)
28 examples, 0 failures

[TEST PROF INFO] Time spent in factories: 00:02.181 (1.49% of total time)
[TEST PROF INFO] Factories usage

 Total: 52
 Total top-level: 35
 Total time: 00:02.181 (out of 02:31.323)
 Total uniq factories: 7

   total   top-level     total time      time per call      top-level time               name

      16          16        0.0907s            0.0057s             0.0907s         issue_link
      11          11        0.4420s            0.0402s             0.4420s              issue
      11           0        0.0619s            0.0056s             0.0000s     work_item_type
       6           6        1.4610s            0.2435s             1.4610s project_empty_repo
       6           0        0.3026s            0.0504s             0.0000s          namespace
       1           1        0.0086s            0.0086s             0.0086s            license
       1           1        0.1794s            0.1794s             0.1794s               user

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.

Edited by Alina Mihaila

Merge request reports