Optimize factory usage for lfs file lock entity

What does this MR do and why?

This MR replaces create with build_stubbed in spec/serializers/lfs_file_lock_entity_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 spec/serializers/lfs_file_lock_entity_spec.rb.

Factory Usage Optimization Results

Before optimization:

  • Factory time: 1.798s (8.54% of total time)

After optimization:

  • Factory time: 0.046s (0.25% of total time)

🚀 Improvement:

  • Factory time reduced by: 1.752s
  • Factory time percentage reduced by: 8.29%
  • Overall factory usage improvement: 97.4%

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

Test environment set up in 1.3756130000110716 seconds
..[TEST PROF INFO] FactoryDoctor report

Total (potentially) bad examples: 2
Total wasted time: 00:01.540

LfsFileLockEntity (./spec/serializers/lfs_file_lock_entity_spec.rb:5) (12 records created, 00:01.540)
  exposes basic attrs of the lock (./spec/serializers/lfs_file_lock_entity_spec.rb:13)  6 records created, 00:01.281
  exposes the owner info (./spec/serializers/lfs_file_lock_entity_spec.rb:17)  6 records created, 00:00.258




Finished in 15.63 seconds (files took 16.12 seconds to load)
2 examples, 0 failures

[TEST PROF INFO] Time spent in factories: 00:01.547 (7.57% of total time)

Factory time before the update

[TEST PROF INFO] Time spent in factories: 00:01.798 (8.54% of total time)

Factory time after update

[TEST PROF INFO] Time spent in factories: 00:00.046 (0.25% 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.

Merge request reports

Loading