- Issue created by @Ambient.Impact
- last update
about 1 year ago 3 pass - @ambientimpact opened merge request.
- Issue was unassigned.
- Status changed to Needs review
about 1 year ago 7:00am 23 May 2023
As I was writing the test for 📌 Add test to inform us when TargetModuleInstaller is no longer needed (core bug is fixed) Needs review , it became apparent that the default target module would always be present on the file system if a previous test also did something that would get Config Enforce Devel to initialize and write it to disk, and so any subsequent test would always find the module, even when we expect it to raise an exception, such as in the linked issue. This led me down a rabbit hole where I realized we probably need a reusable test trait (or service?) that can generate a randomly named default target module for a test and then remove it once the test has completed.
See above.
Create a test trait or service to automate and abstract this so we can reuse it.
Do the thing.
None probably.
None?
Probably none?
Needs review
1.0
Code