Drupal is a registered trademark of Dries Buytaert
Release: Leaflet 10.4.11 Minor update available for module leaflet (10.4.11). Release: Session Inspector 1.0.8 Minor update available for module session_inspector (1.0.8). Release: Migrate QA 2.0.4 Minor update available for module migrate_qa (2.0.4). Release: CKEditor Description List 3.0.0 Major update available for module ckeditor_descriptionlist (3.0.0). Release: FlowDrop 2.4.0 Minor update available for module flowdrop (2.4.0). Release: JWT Token Refresh 1.0.4 Minor update available for module jwt_token_refresh (1.0.4). Release: ConReg 1.0.0-beta1 First beta version released for module conreg (1.0.0-beta1). Release: AI Image Studio 1.0.0-beta8 New beta version released for module ai_image_studio (1.0.0-beta8). Usage Milestone: Statistics Counter Module statistics_counter crossed 1,000 active installs. Module Revived: Decoupled Router 2.0.7 Module decoupled_router updated after 11 months of inactivity (2.0.7).

Testmode

126 sites No security coverage
View on drupal.org

This module helps ensure accurate testing by filtering out existing content on your site. It allows you to isolate content created specifically for your tests, preventing interference and false positives. When a test is run with a specific tag, the module activates a filter that only displays test-related content to avoid confusion.

Alter existing site content and other configurations when 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).

Development of this module takes place on GitHub: https://github.com/AlexSkrypnyk/testmode

Use case

Running a Behat test on the site with existing content may result in
false positives because of the live content being mixed with test content.

Example: a list of 3 featured articles. When the test creates 3 articles and make
them featured, there may be existing featured articles that will confuse tests
resulting in false positive failure.

How it works

1. When writing Behat tests, all test content items (nodes,
terms, users) follow specific pattern. For example, node titles start with
[TEST] .
2. A machine name of a view, which needs to be tested, is added to
Testmate configuration form.
3. Behat test tagged with @testmode will 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.

Activity

Tracked releases
4
Tracked since
Apr 2026
Latest release
6 days ago
Releases (12 mo)
4 ▲ from 0
Maintenance
Active

Release Timeline

Releases

Version Type Release date
2.7.2 Stable Aug 17, 2026
2.7.1 Stable Jun 13, 2026
2.7.0 Stable Apr 11, 2026
2.6.1 Stable Apr 1, 2026