Search Results

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 …

Since those tests are grouped by namespace/directory, you can just pass the respective path to phpunit, simply add tests/src/Unit to your existing path.

There is no standard test feature to assert a logged message. The simplest approach is to just install dblog in your test and then inspect the watchdog table for the expected record. Alternatively, …

Sure, all you need to do is provide a path/file to phpunit and it will be limited to that. vendor/bin/phpunit -c core modules/custom

The Schema file is: https://github.com/aneek/rate_limiter/blob/develop/config/install/rate_limiter.settings.yml No, that is not the schema file, that is the config file for which you need to crea …

No, you should not. An assertion message is basically on the same level as a code comment, you're not translating that either. We used to do that in core, also because it was all Simpletest then and …

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

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

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

BrowserTestBase do not run against your installation, they do a new installation and then run against that. There is no content, no modules, pretty much nothing there by default, everything you need …

edit: This might be my issue. Yes. The error happens during test discovery, first it has to find all tests and then limit it based on the group. The easiest workaround is simply to specifiy you …

Yes you should do that. Module install is not really a problem as all plugins are invalidated then anyway, but entities can also be changed in the UI. See \Drupal\block_content\Entity\BlockContent:: …

As commented, you were missing the save call in the test. That means that the change is only in the runtime object returned by getEditable() and since get() and getEditable() do not share the static …

As discussed in IRC, pretty sure your problem is $this->drupalPlaceBlock('my_context_aware_block'); which doesn't configure the necessary context mapping. That's not visible in the UI if you only have …

A kernel tests actually installs Drupal (in-memory only, but still), that means it runs thounsands and thousands of lines of code. You can't really do anything to change that, xdebug (I guess you use …