trabajo-afectivo/spec/support/db_strategies.rb

RSpec.configure do |config|

  config.around(:each, db_strategy: :reset) do |example|
    self.use_transactional_tests = false
    example.run
    Rake::Task['zammad:db:reset'].reenable
    Rake::Task['zammad:db:reset'].invoke
  end
end
Added db_strategy (:truncaction) meta helper to switch to DB cleanup via truncation (from transaction) for single examples. We choose to stick to Rails/RSpec transactional cleanup over DatabaseCleaner transaction strategy because of performance reasons. Rails default performs between 30 and 50% better. 2018-10-02 14:25:04 +00:00			`RSpec.configure do \|config\|`

Switched over to DB reset strategy in tests and removed DatabaseCleaner because it can't guarantee a clean DB state for all test scenarios. 2018-10-18 12:20:51 +00:00			`config.around(:each, db_strategy: :reset) do \|example\|`
Added db_strategy (:truncaction) meta helper to switch to DB cleanup via truncation (from transaction) for single examples. We choose to stick to Rails/RSpec transactional cleanup over DatabaseCleaner transaction strategy because of performance reasons. Rails default performs between 30 and 50% better. 2018-10-02 14:25:04 +00:00			`self.use_transactional_tests = false`
			`example.run`
Switched over to DB reset strategy in tests and removed DatabaseCleaner because it can't guarantee a clean DB state for all test scenarios. 2018-10-18 12:20:51 +00:00			`Rake::Task['zammad:db:reset'].reenable`
			`Rake::Task['zammad:db:reset'].invoke`
Added db_strategy (:truncaction) meta helper to switch to DB cleanup via truncation (from transaction) for single examples. We choose to stick to Rails/RSpec transactional cleanup over DatabaseCleaner transaction strategy because of performance reasons. Rails default performs between 30 and 50% better. 2018-10-02 14:25:04 +00:00			`end`
			`end`