Actions
Bug #14097
closed
Only run DatabaseCleaner as 'truncation' on JS tests
Description
Problem:
DatabaseCleaner runs after all integration tests, on truncation mode. However, for tests where we use rack-test instead of poltergeist, this is not necessary and slows down the test suite.
Solution:
Mark the tests that use javascript and only run DatabaseCleaner on truncation mode on these, the rest of them can run in transaction mode (faster).
Updated by The Foreman Bot almost 9 years ago
- Status changed from New to Ready For Testing
- Assignee set to Daniel Lobato Garcia
- Pull request https://github.com/theforeman/foreman/pull/3293 added
Updated by Daniel Lobato Garcia almost 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 26dade0f18bba02430bec08283a47ba039173f37.
Updated by Dominic Cleal almost 9 years ago
- Translation missing: en.field_release set to 136
Updated by Dominic Cleal almost 9 years ago
- Related to Bug #14228: running single test fails due to FileUtils not being required added
Updated by Stephen Benjamin almost 9 years ago
- Related to Bug #14273: Salt integration tets are failing added
Updated by Dominic Cleal over 8 years ago
- Related to Bug #9138: Intermittent HostTest/NIC integration test failures added
Actions