Problem/Motivation

I see/hear about the setup test module, mercury_editor_setup_test, in many videos about Mercury Editor (including this 2024 Stanford WebCamp recording from just a few weeks ago) -- but, it isn't actually available to enable, in the Drupal UI (/admin/modules), or via command line (drush en mercury_editor_setup_test).

As far as I can tell, this sub-module (mercury_editor_setup_test) is in mercury_editor/tests/modules -- so, I definitely don't know for sure, but I imagine this location of the sub-module is why I can't enable it? Probably just needs to be moved to mercury_editor/modules?

Steps to reproduce

Add Mercury editor to your project, i.e. composer require drupal/mercury_editor
In Drupal UI ("Extend"), look for the "Mercury Editor Setup Test" module (I have Module Filter, so I just searched for "mercury")
In a terminal, try to enable mercury_editor_setup_test with drush.

Attached screenshots:
Looking for "Mercury Editor Setup Test" module in Drupal UI (on a site with Module Filter).
Trying to enable (and then trying to find) mercury_editor_setup_test module via command line.

Proposed resolution

Move the sub-module to mercury_editor/modules??

I did this locally (i.e. mv web/modules/contrib/mercury_editor/tests/modules/mercury_editor_setup_test/ web/modules/contrib/mercury_editor/modules/), and after doing that, I was able to enable the module just fine.

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork mercury_editor-3454540

Command icon Show commands

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

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

About issue forks

Comments

alison created an issue. See original summary.

alison’s picture

alison
she/her
commented
Issue summary: View changes

If there's maintainer support for moving this module into mercury_editor/modules, I can submit a MR!

alison opened merge request !53

justin2pin’s picture

justin2pin commented
Status: Active » Closed (works as designed)

Hi @alison - to enable test modules, add (or uncomment) this line in your local settings file (i.e. settings.local.php):

$settings['extension_discovery_scan_tests'] = TRUE;

Let me know if you still run into issues!

alison’s picture

alison
she/her
commented

Oh! Even though it says "test" in the name, it had not occurred to me that this module was meant for testing the module, like for automated tests / debugging -- I thought the intent of this module was more like a demo/example module. I suppose then it would be called Mercury Editor Setup Demo or Mercury Editor Setup Example...

Obviously I'm biased because I didn't know about using test modules like this (to try the module with a demo/starter-setup, not just for automated testing), but, if y'all are going to use this module in how-to presentations, I recommend including an explanation of how to enable the module, or point to documentation about how to enable test modules -- again, I'm biased, but I don't think it's common knowledge among site builders who aren't also contributed module developers.

That said, I get it now, thank you!