Redirect SimpleTest queries to a different database

Question

How can I tell SimpleTest to use a different database than the default connection? I want to be able to run the tests against an in memory database while keeping the local data on disk.

UPDATE:

So far the answers I'm getting are on how to set up tmpfs and move mysql data to that folder. That's great and super helpful. However this is missing the specific answer that I am looking for. I'm most interested in how to run SimpleTest against a different connection than the default database connection. You can see above that my question reflected by both the title and the first line of my original submission. I apologize for the confusion caused by my mention of an in memory database, I provided that only as context, but it is not the root of my question.

Answer 1

It's not possible to do this on a storage engine level. You can't install Drupal on top of the HEAP storage engine, there are various missing features, the most obvious one being: "MEMORY tables cannot contain BLOB or TEXT columns." (copied from the link in the comments).

The qa.drupal.org testbot's have the complete MySQL data directory in a tempfs that is stored in memory, which is copied from the real file system during startup and back during shutdown. I don't think that's a doable setup for a development environment because, at least in my case, databases of real sites quickly get too big for something like this (Working on large sites with multiple GB of data). http://drupal.org/node/466972 has some more tipps and scripts for the tempfs thing. Make sure to read the comments.

Not sure what exactly takes 2,5m in your case, I can run a single test in ~10s (Note that every test method is a separate test that runs in a new installation).

I'm quite sure that I've already written quite a list of tipps on how to speed up tests in an answer somewhere but I'm unable to find it. The most important thing is defining $profile = 'testing'; in your test class, that will only install the absolutely required modules for Drupal to run. Speeds up test runs by ~50%. Another way is prefixing your different test methods with anything other than test and having a single public test method that calls all other. Downside is that your tests then run in the same environment and might affect each other. You e.g. can't have hardcoded node id's and things like that.

Another thing is optimizing your mysql configuration, than can speed up tests quite a bit as well, see http://techblog.md-systems.ch/blog/improve-mysql-performance for a start.

To actually override the used database connection, you need to completely overwrite the setUp() method where the connection is created and activated and instead use whatever connection you want, see DrupalWebTestCase::setUp().

Answer 2

I am now running SimpleTests with MySQL on a tmpfs folder, and the execution time went from 27 seconds to 5 seconds. I'll explain how I did it.

• Create a tmpfs folder

  mkdir /var/tmpfs
  mount -t tmpfs -o size=1G tmpfs /var/tmpfs
  chown -R mysql:mysql /var/tmpfs/mysql
  

• Copy your MySQL data into the tmpfs directory

  sudo service mysqld stop
  cp -Rv /var/lib/mysql /var/tmpfs/
  chown -R mysql:mysql /var/tmpfs/mysql
  

• When you want to run some tests, configure my.cnf to use tmpfs.

  #/etc/my.cnf
  [mysqld]
  datadir=/var/tmpfs/mysql
  

• Start mysqld

  sudo service mysqld start
  

The data won't be persistent but it shouldn't be a problem since the website used for testing should not be in a production environment. Anyway you can always switch back to datadir=/var/lib/mysql when you need to save data.

Note that it still worth adding the 'testing' profile to the DrupalTestCase class

protected $profile = 'testing'; 

Indeed, on the same without the above it went up to 12 seconds, instead of 5 seconds.

Answer 3

If you want to perform tests on the current database (usefull to test your specific cases of data migration) you could override DrupalWebTestCase::setUp() and also DrupalWebTestCase::tearDown(). Here some exemple by Trellon.com http://www.trellon.com/content/blog/forcing-simpletest-use-live-database

As for me I use something like this:

abstract class DwCurrentDbBasedTestCase extends DrupalWebTestCase {

  /**
   * Override setUp().
   *
   * Avoid creating a new database and install for testing.
   * We want to use current. Our CI will check project build.
   */
  protected function setUp() {
    global $conf;

    $conf['error_level'] = 2;

    $this->originalFileDirectory = variable_get('file_public_path', 'sites/default/files');
    $this->public_files_directory = $this->originalFileDirectory . '/simpletestFiles';

    // Use the test mail class instead of the default mail handler class.
    variable_set('mail_system', array('default-system' => 'TestingMailSystem'));

    // Simpletest needs this to run any tests
    $this->setup = TRUE;

    // @see drupal_web_test_case.php
    $modules = func_get_args();
    if (isset($modules[0]) && is_array($modules[0])) {
      $modules = $modules[0];
    }
    if ($modules) {
      $new_modules = array();
      foreach ($modules as $module) {
        if (!module_exists($module)) {
          $new_modules[] = $module;
        }
      }
      if (count($new_modules) > 0) {
        $success = module_enable($modules, TRUE);
        $this->assertTrue($success, t('Enabled modules: %modules', array('%modules' => implode(', ', $modules))));
      }
    }
  }

  /**
   * By default this method will remove testing env, avoid this in below code.
   */
  function tearDown() {
    // In case a fatal error occurred that was not in the test process read the
    // log to pick up any fatal errors.
    simpletest_log_read($this->testId, $this->databasePrefix, get_class($this), TRUE);
  } 
}