LifeMonitor is a service to support the sustainability and reusability of published computational workflows.
The collapse  over time of the software and services on which computational workflows depend is destructive to their reusability, and to the reproducibility of work for which they were used; this phenomenon can be caused by an API change that is not backwards compatible, a regression in a tool whose version was not pinned, a change in URL of an external resource, etc. Frequent testing is crucial to the preservation of workflow health, allowing to expose problems when they arise and providing a machine-actionable way to verify changes to the workflow structure. LifeMonitor aims to facilitate the maintenance of computational workflows, supporting their reusability over time, with a strong focus on testing and test monitoring.
The project’s main goals are to:
If you just want to play around or get familiar with the API, use the dev instance of LifeMonitor (note that the dev instance could be wiped out at any time with no warning).
Once installed, the LifeMonitor app can be configured to:
See the page describing the LifeMonitor GitHub app for more detailed information on what it does and how it can be configured.
If you don’t want to install the GitHub app, you can still use LifeMonitor’s test monitoring and periodic test execution features. Follow the instructions on configuring test monitoring.
If you still don’t have tests for your workflow or you haven’t created an automated testing pipeline, see our page on general workflow testing tips.
Here is our planned development road map.
LifeMonitor is being developed as part of the EOSC-Life project
 K. Hinsen, Dealing with software collapse. Computing in Science & Engineering 21 (3), 104-108 (2019).