Add basic test coverage [#3610673]

Problem/Motivation

No test coverage

Steps to reproduce

Check gitlab CI pipeline

Proposed resolution

Add test coverage to ensure reliability of the module

Remaining tasks

User interface changes

N/A

API changes

N/A

Data model changes

N/A

Issue fork suppress_logs-3610673

Show commands

Start within a Git clone of the project using the version control instructions.

Add & fetch this issue fork’s repository

Or, if you do not have SSH keys set up on git.drupalcode.org:

Add & fetch this issue fork’s repository

3610673-add-test-coverage changes, plain diff MR !5
Check out this branch for the first time

Check out existing branch, if you already have it locally

About issue forks

Comments

Comment #1

13 July 2026 at 15:56

scott_euser created an issue. See original summary.

Comment #2

13 July 2026 at 15:57

scott_euser opened merge request !5

Comment #3

scott_euser commented 13 July 2026 at 16:24

Assigned:	scott_euser	» Unassigned
Status:	Active	» Needs review

Added some basic test coverage which unfortunately led me to needing to fix two issues (could be raised separately but the tests here help prove the issues);

The info.yml pointed to a non-existent settings form route. Updated to point to the one in your routing yaml file.
The set_error_handler completely overrode Drupal's one suppressing logs well beyond what is scoped in the settings form, this allows your targeted one to still exist and let Drupal then handle the rest still (where some will be the suppressed by the null handler)

On (2) its probably better if that's an opt-in via the settings form as the module leads you to believe nothing is suppressed until you decide what to suppress, but actually that set_error_handler is already suppressing as soon as the module is enabled.