In #38, it was proposed to run the test suite on a regular schedule (e.g., once a week) in order to detect issues related to the release of new versions of the package dependencies (see #39 for an example).
This is particularly relevant for this package, as it is expected that the time between future PRs will be quite long (several months if not longer) and test failures could potentially go undetected for a long time.
Running the tests on a weekly cron schedule is as simple as adding the following lines to the GitHub Action:
on:
schedule:
- cron: '0 0 * * 0'
However, one should be aware of who receives notifications of failed cron jobs as discussed here:
Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead. If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.
An alternative solution would be to send an email to one or more specific people, however, this would require specifying the username/password of the email to send from, which seems like a hassle (e.g., in case of password changes).
Thus, my suggestion is simply to add the cron schedule to the existing test workflow file. This will then only notify me of any cron job failures, but I think that is sufficient and certainly better than the current solution (no regular testing).
In #38, it was proposed to run the test suite on a regular schedule (e.g., once a week) in order to detect issues related to the release of new versions of the package dependencies (see #39 for an example).
This is particularly relevant for this package, as it is expected that the time between future PRs will be quite long (several months if not longer) and test failures could potentially go undetected for a long time.
Running the tests on a weekly cron schedule is as simple as adding the following lines to the GitHub Action:
However, one should be aware of who receives notifications of failed cron jobs as discussed here:
An alternative solution would be to send an email to one or more specific people, however, this would require specifying the username/password of the email to send from, which seems like a hassle (e.g., in case of password changes).
Thus, my suggestion is simply to add the cron schedule to the existing test workflow file. This will then only notify me of any cron job failures, but I think that is sufficient and certainly better than the current solution (no regular testing).
@kanderso-nrel what do you think?