Search Results

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

Unit tests must have the following namespace: Drupal\Tests\dev_module\Unit. For complicated reasons, they also don't show up in the right group but they are all in the PHPUnit group. To run your uni …

StringTranslationTrait also has a setStringTranslation() method so you can inject a string translation mock for exactly that purpose.

See https://www.drupal.org/phpunit for better documentation. There are 4 test base classes: UnitTestBase, pure unit tests where everything but your code has to be mocked and only supports classes K …

Simpletest automatically captures sent mails during a test and allows you to fetch them using $this->drupalGetMails() in the test class. I did something like this recently in tests I wrote for the Si …

You can't mock static calls directly. A relatively easy way to fix this is what core uses in quite some places to mock functions that haven't been converted to objects/services yet. You create a meth …

You can't create and save entities in a unit test. That's what kernel tests are for. You will also need to install the necessary entity schema then, make sure the necessary modules are enabled. One w …

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

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 …

In regards to the testing pyramid, that is the ideal scenario, but it's not always feasible. I also think that it is makes more sense in a scenario where you built and control the whole system. …

Wrap it in a !function_exists() See core/tests/Drupal/Tests/Core/Render/Element/MachineNameTest.php for example: <?php namespace Drupal\Core\Render\Element; if (!function_exists('t')) { functio …

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

Use testing and then create only what you need in the test. That's the main thing to speed up your tests. They are still rather slow, but that should help. …

See https://www.drupal.org/docs/8/testing/types-of-tests-in-drupal-8 for documentation of different types of tests in Drupal 8 and when they should be used. …