Update from voxpupuli modulesync_config #13
Annotations
5 errors
|
spec/support/acceptance/cmdline.rb#L4
RSpec/BeforeAfterAll: Beware of using `before(:context)` as it may cause state to leak between tests. If you are using `rspec-rails`, and `use_transactional_fixtures` is enabled, then records created in `before(:context)` are not automatically rolled back. (https://rspec.rubystyle.guide/#avoid-hooks-with-context-scope, https://www.rubydoc.info/gems/rubocop-rspec/RuboCop/Cop/RSpec/BeforeAfterAll)
|
|
spec/support/acceptance/cmdline.rb#L10
RSpec/BeforeAfterAll: Beware of using `after(:context)` as it may cause state to leak between tests. If you are using `rspec-rails`, and `use_transactional_fixtures` is enabled, then records created in `after(:context)` are not automatically rolled back. (https://rspec.rubystyle.guide/#avoid-hooks-with-context-scope, https://www.rubydoc.info/gems/rubocop-rspec/RuboCop/Cop/RSpec/BeforeAfterAll)
|
|
spec/support/acceptance/config.rb#L4
RSpec/BeforeAfterAll: Beware of using `before(:context)` as it may cause state to leak between tests. If you are using `rspec-rails`, and `use_transactional_fixtures` is enabled, then records created in `before(:context)` are not automatically rolled back. (https://rspec.rubystyle.guide/#avoid-hooks-with-context-scope, https://www.rubydoc.info/gems/rubocop-rspec/RuboCop/Cop/RSpec/BeforeAfterAll)
|
|
spec/support/acceptance/config.rb#L8
RSpec/BeforeAfterAll: Beware of using `after(:context)` as it may cause state to leak between tests. If you are using `rspec-rails`, and `use_transactional_fixtures` is enabled, then records created in `after(:context)` are not automatically rolled back. (https://rspec.rubystyle.guide/#avoid-hooks-with-context-scope, https://www.rubydoc.info/gems/rubocop-rspec/RuboCop/Cop/RSpec/BeforeAfterAll)
|
|
|
This job failed
Loading