Refactor DefaultTargetModuleTest to use/test DefaultTargetModuleSetUpTrait and TargetModuleCollection::ensureDefaultTargetModuleIsSet() parameters

Created on 23 May 2023, about 1 year ago

Problem/Motivation

This is a follow up to ✨ Make it possible to set default target module machine name and path before creating Needs review and πŸ“Œ Add test trait to create randomly named, non-conflicting default target modules Needs review to refactor/adapt DefaultTargetModuleTest to make use of both the new parameters added to TargetModuleCollection::ensureDefaultTargetModuleIsSet() and the new test trait to avoid naming collisions with any existing default target module.

Steps to reproduce

Look, I'm tired and it's late and you're smart enough.

Proposed resolution

I'll make a fork and merge request hang tight.

Remaining tasks

Do the thing.

User interface changes

None.

API changes

None.

Data model changes

None.

πŸ“Œ Task
Status

Needs review

Version

1.0

Component

Code

Created by

πŸ‡¨πŸ‡¦Canada Ambient.Impact Toronto

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.69.0 2024