Project

General

Profile

Actions

Bug #14097

closed

Only run DatabaseCleaner as 'truncation' on JS tests

Added by Daniel Lobato Garcia about 8 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Tests
Target version:
Difficulty:
easy
Triaged:
Fixed in Releases:
Found in Releases:

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).


Related issues 3 (0 open3 closed)

Related to Foreman - Bug #14228: running single test fails due to FileUtils not being requiredClosedOri Rabin03/16/2016Actions
Related to Salt - Bug #14273: Salt integration tets are failingClosedStephen Benjamin03/18/2016Actions
Related to Foreman - Bug #9138: Intermittent HostTest/NIC integration test failuresDuplicateTomáš Strachota01/28/2015Actions
Actions #1

Updated by The Foreman Bot about 8 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
Actions #2

Updated by Daniel Lobato Garcia about 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #3

Updated by Dominic Cleal about 8 years ago

  • translation missing: en.field_release set to 136
Actions #4

Updated by Dominic Cleal about 8 years ago

  • Related to Bug #14228: running single test fails due to FileUtils not being required added
Actions #5

Updated by Stephen Benjamin about 8 years ago

  • Related to Bug #14273: Salt integration tets are failing added
Actions #6

Updated by Dominic Cleal about 8 years ago

  • Related to Bug #9138: Intermittent HostTest/NIC integration test failures added
Actions

Also available in: Atom PDF