71672dfa6a
This replaces the use of fake_application_settings with
`::ApplicationSetting.build`_from_defaults. The reason is that
`fake_application_settings` doesn't have the custom accessors that
`ApplicationSetting` has, e.g. `#commit_email_hostname`, thus this
can lead to unexpected `nil` values which comes from the database
column instead of `.default_commit_email_hostname` returned by
`ApplicationSetting#commit_email_hostname`.
Using `::ApplicationSetting.build_from_defaults` should be safe as it
doesn't try to `INSERT` a DB record, in contrary to
`::ApplicationSetting.create_from_defaults` which we used to use, and
which created issues that the introduction of
`fake_application_settings` tried to resolve (
|
||
---|---|---|
.. | ||
api | ||
backup | ||
banzai | ||
bitbucket | ||
bitbucket_server | ||
constraints | ||
container_registry | ||
gitaly | ||
gitlab | ||
google_api | ||
json_web_token | ||
mattermost | ||
microsoft_teams | ||
object_storage | ||
omni_auth/strategies | ||
quality | ||
rspec_flaky | ||
system_check | ||
after_commit_queue_spec.rb | ||
event_filter_spec.rb | ||
expand_variables_spec.rb | ||
extracts_path_spec.rb | ||
feature_spec.rb | ||
file_size_validator_spec.rb | ||
forever_spec.rb | ||
gitlab_spec.rb | ||
milestone_array_spec.rb | ||
system_check_spec.rb | ||
uploaded_file_spec.rb |