Search Results

The only thing that I'm aware of is that for contributed modules, you can enable automated testing of commits and patches in the issue queue, see http://drupal.org/node/689990. …

Drupal 7 comes with a Testing module, and for Drupal 6 you can download http://drupal.org/project/simpletest. …

While setting the user_register variable works by automatically logging you in, if you want to test the default mail confirmation, you can inspect the mail as described over in your other question: Ho …

This behavior is correct. SimpleTest sets up a new site environment for every test case, using a table name prefix. You probably forgot to install your module by overriding the setUp() method. Once y …

You can create a test module and place hidden = TRUE in the .info file. This will hide the module in the user interface but you can still enable it in your setUp() method. See http://drupalcode.org/ …

All tests are run on every patch that is posted on drupal.org, fully automated. Nothing is commited unless all tests are passing (It happens that something is commited that breaks the tests (for examp …

My guess is that you're not including the phpunit.xml.dist file, which sits in the core folder. Either run tests from there (./vendor/bin/phpunit ../modules/your_module) or specify that file with -c. …

file like this: files[]=yourmodule.test Then, let it rebuild by submitting the modules page or use the "Clear information" (or similar, not sure about the exact label right now) at the bottom of the Testing …

Inside the test method? No idea what in $GLOBALS['user'] is, but you certainly can't rely on it. You are never "logged in" in that context, you are only logged in when doing requests with drupalGet() …

Use the testing profile by adding a protected $profile = 'testing'; to your test class. …

There is a base image field test class in image.module, which has a uploadNodeImage() method. You can either re-use that by extending from that class or steal the code there. See testStyleReplacment( …

Permissions would be my first guess. Enable debug output in the Simpletest settings and then check if your module is installed and you have permissions to visit that page.

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%. …

It is sometimes more complicated to set up, but has the advantage that you are testing much more of your actual code and integration. … Testing all possible cases, error handling/conditions and so on. …

I don't understand why you need libraries module for swiftmailer? Swiftmailer dependencies in 8.x-1.x are installed using composer (manager). Which is something that the testbot currently simply does …