This Drupal module is designed to modify existing site content and configurations while running tests.
This is a module to support testing, so it is not expected to be used in production (although, it adheres to Drupal coding standards and has good test coverage).
composer require drupal/testmode
Running a Behat test on the site with existing content may result in false-positives because of the live content being mixed with the test content.
Example: list of 3 featured articles. When the test creates 3 articles and makes them featured, there may be existing featured articles that will confuse tests resulting in a false-positive failure.
- When writing Behat tests, all test content items (nodes,
terms, users) follow specific pattern. For example, node titles start with
[TEST]. - A machine name of a view, which needs to be tested, is added to Testmode configuration form.
- Behat test tagged with
@testmodewill put the site in test mode that will filter-out all items in the view that do not fit the pattern, leaving only content items created by the test.
Releases in GitHub are automatically pushed to http://drupal.org/project/testmode by CI.
https://www.drupal.org/project/issues/testmode
Provided that you have PHP installed locally, you can develop an extension using the provided scripts.
Run .devtools/buid.sh (or ahoy build
if Ahoy is installed) to start inbuilt PHP
server locally and run the same commands as in CI, plus installing a site and
your extension automatically.
Run tools individually (or ahoy lint to run all tools
if Ahoy is installed) to lint your code
according to
the Drupal coding standards.
cd build
vendor/bin/phpcs
vendor/bin/phpstan
vendor/bin/rector --clear-cache --dry-run
vendor/bin/phpmd . text phpmd.xml
vendor/bin/twig-cs-fixer
- PHPCS config:
phpcs.xml - PHPStan config:
phpstan.neon - PHPMD config:
phpmd.xml - Rector config:
rector.php - Twig CS Fixer config:
.twig-cs-fixer.php - Patches can be applied to the dependencies: add a patch to the
patchessection ofcomposer.json. Local patches will be sourced from thepatchesdirectory.
Run tests individually with cd build && ./vendor/bin/phpunit (or ahoy test
if Ahoy is installed) to run all test for
your extension.
To browse the contents of created SQLite database
(located at /tmp/site_[EXTENSION_NAME].sqlite),
use DB Browser for SQLite.
