Opened 17 months ago
Closed 16 months ago
#62167 closed enhancement (duplicate)
Stop running WordPress Importer plugin tests in Core
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | |
| Component: | Build/Test Tools | Keywords: | |
| Focuses: | Cc: |
Description
The WordPress Importer tests are currently run for every commit to wordpress-develop. This seems to precede the use of Travis CI for running tests, which happened in 2013 (see [26534]).
As part of implementing develop.svn.wordpress.org (see #24976), it was suggested that the Importer tests should be pulled out of Core and merged into the plugin itself so that they could be managed like any other plugin. This would also eliminate the need to automatically install the plugin when spinning up the local Docker environment.
That has happened to some extent, but a full audit needs to be performed to ensure the tests and any updates in wordpress-develop have made their way over to the wordpress-importer repository on GitHub.
One point of feedback on #24976 was:
I'd want to make sure any importer tests are not neglected, especially in terms of being broken by core changes. We'll probably just want to make sure we hook it up into Travis CI.
The schedule action in GitHub Actions (the replacement for Travis CI) can be used to run the tests at a regular interval. However there is one new consideration:
scheduled workflows are automatically disabled when no repository activity has occurred in 60 days.
Realistically, the plugin does encounter periods of time where the repository is not updated. Care should be taken to ensure the workflows continue to run at the desired interval. The existence of a Dependabot configuration file should be enough to ensure that happens.
For the record: the plugin already has a Dependabot config for the GH Actions part (added recently via PR GH-PR 165).
I'm not sure that'll be enough though. The plugin doesn't have many dependencies and the workflow action runners only need updates on major releases (and moving to commit hashes seems over the top).