Optimize factory usage for corpus management show
What does this MR do and why?
This MR replaces create with build_stubbed in ee/spec/views/projects/security/corpus_management/show.html.haml_spec.rb to optimize the factory usage as recommended in our handbook.
This spec is part of the list .rubocop_todo/rspec/factory_bot/avoid_create.yml.
It was verified that database persistence is not needed using the factory doctor command FDOC=1 bin/rspec ee/spec/views/projects/security/corpus_management/show.html.haml_spec.rb.
Factory Usage Optimization Results
Before optimization:
- Factory time: 1.508s (8.26% of total time)
After optimization:
- Factory time: 0.048s (0.31% of total time)
- Factory time reduced by: 1.46s
- Factory time percentage reduced by: 7.95%
- Overall factory usage improvement: 96.8%
Factory Doctor Output
[TEST PROF INFO] FactoryDoctor enabled (event: "sql.active_record", threshold: 0.01)
Run options: include {:focus=>true}
All examples were filtered out; ignoring {:focus=>true}
==> Using precompiled Gitaly binaries from cache
==> Go projects set up in 0.729 seconds...
Test environment set up in 2.080941000021994 seconds
..[TEST PROF INFO] FactoryDoctor report
Total (potentially) bad examples: 2
Total wasted time: 00:01.242
projects/security/corpus_management/show (./ee/spec/views/projects/security/corpus_management/show.html.haml_spec.rb:5) (6 records created, 00:01.242)
renders Vue app root (./ee/spec/views/projects/security/corpus_management/show.html.haml_spec.rb:11) – 3 records created, 00:01.052
passes project's full path (./ee/spec/views/projects/security/corpus_management/show.html.haml_spec.rb:15) – 3 records created, 00:00.190
Finished in 14 seconds (files took 16.01 seconds to load)
2 examples, 0 failures
[TEST PROF INFO] Time spent in factories: 00:01.251 (6.82% of total time)
Factory time after update
[TEST PROF INFO] Time spent in factories: 00:00.048 (0.31% of total time)This MR also adds the missing feature category in this spec.
References
Relates to: #378910.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.