Implement GitHub workflow to have a basic test for standalone plugins #639
Labels
Creating standalone plugins
Infrastructure
Issues for the overall performance plugin infrastructure
Performance Lab Plugin
Issue relates to work in the Performance Lab Plugin only
[Type] Enhancement
A suggestion for improvement of an existing feature
Projects
Feature Description
Follow up to #635: As we are publishing certain modules as standalone plugins, it is vital that we ensure the plugins work as expected. This issue's goal is to provide at least a foundation for some automated testing of the individual plugins: It should run the build step from #635 and then load the plugin in e.g. a customized PHPUnit configuration, to just ensure that there is no fatal error when loading the plugin. While this is far from a comprehensive solution, the code itself is already covered by the unit tests on the module, and having this extra check is the most critical and minimum starting point to ensure we don't accidentally use anything from the Performance Lab core in a module that wouldn't work when it's standalone.
This should already be the case per our writing a module guidelines, but having a CI workflow to ensure that will be crucial to ensure we don't let any mistake accidentally slip through.
Requirements
build-plugins
command from Implement CLI command to for a build process to transform modules into standalone plugins #635 and then loads each individual built plugin in a sandboxed PHP environment.push
events totrunk
, not for every pull request, to avoid the overhead of having this on every PR. Running this on everytrunk
push is sufficient to capture failures before they would accidentally get released to end users.push
should be covered by this test, since for unchanged modules it would be redundant and just slow down CI unnecessarily.The text was updated successfully, but these errors were encountered: