When we spin up a CI matrix, the installer version is available for all jobs in the matrix. I think it's only needed for behat, though? My understanding is it's needed to spin up a functional ss app that can be run in the browser.
The phpunit tests don't need a fully functional app to run, and should pass just with the dev-dependencies defined in composer.json.
Another thing to consider
- We may not need installer at all - we can probably use
recipe-core which would be even better, because then only the dependencies we absolutely need for running a given module's tests will be included.
- Some behat tests may assume modules are installed, e.g. admin may have behat tests that assume cms is installed. We should move those tests to the appropriate modules, and create fixtures as needed instead of relying on entirely unnecessary dependencies.
Acceptance criteria
When we spin up a CI matrix, the installer version is available for all jobs in the matrix. I think it's only needed for behat, though? My understanding is it's needed to spin up a functional ss app that can be run in the browser.
The phpunit tests don't need a fully functional app to run, and should pass just with the dev-dependencies defined in composer.json.
Another thing to consider
recipe-corewhich would be even better, because then only the dependencies we absolutely need for running a given module's tests will be included.Acceptance criteria