Investigate if we can mock a module in VFS and then use it in tests.

Created on 4 April 2025, about 22 hours ago

Problem/Motivation

In the parent issue it was suggested we might be able to mock a module in VFS then use drupal normally to install that module. Since i don't want to block the parent on this, lets investigate here.

```
In other words, what I wish we could do here is mock the module in vfs, then simply say \Drupal::service('module_installer')->install(['mocked_module']), rather than having to do any lower-level work. But if that's impossible for specific reasons, at least right now, then okay! I consider this thread resolved.
```

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

📌 Task

Status

Active

Version

11.0 🔥

Component

other

Created by

🇳🇱Netherlands bbrala Netherlands

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @bbrala
Comment about 19 hours ago →
🇨🇦Canada Charlie ChX Negyesi 🍁Canada
As far as I am aware including from a vfs:// url requires allow_url_include on which is system level setting and is widely considered a security hole so that's probably not a good requirement for running tests.

However, you could include from phar:// and taking over the phar stream wrapper is doable, I linked two issues where Damien and me have did it before, neither made it into core however. But being a little hacky in tests maybe doesn't hurt as much as it would on the hot path.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024