Simone Leo

@mr-c no changes. To double check, I've redone everything from scratch, here is the log: ```console [simleo@neuron:tmp]$ git clone [email protected]:RenskeW/cwlprov-provenance.git Cloning into 'cwlprov-provenance'... remote: Enumerating objects: 960, done. remote: Counting...

Hi everyone. I published a first 0.1.0 release of `repo2rocrate` (that's the name of the package and of the command line tool, I should rename the repository accordingly) to PyPI...

> * Metadata spec: https://github.com/crs4/life_monitor/wiki/Test-Metadata-Draft-Spec That's the old version of the specs, still there for reference. Can you please delete that bullet? Sorry for the confusion.

Thanks for opening this @ewels. Adding some more info. Yes, [Life Monitor](https://github.com/crs4/life_monitor) is a workflow monitoring and testing service under development as part of [EOSC-Life](https://www.eosc-life.eu). Part of the work is...

> I'm not sure that we need direct integration into Nextflow here No, that's also not the case for Planemo / Galaxy, as you wrote above.

I've taken a look at pytest-workflow. One problem I see is that it allows arbitrary code execution via the `command` field, with security implications for the "running tests according to...

On the other hand, I guess Nextflow allows arbitrary code execution in the first place, which calls for some form of isolation in the running environment. One difference is that...

> @simleo - we've been talking with @johanneskoester about collaborating on a set of data that could be used for automated testing: a set of minimal inputs (eg. fastq, bam,...

We have a use case for this in biotracks, see https://github.com/CellMigStandOrg/biotracks/issues/9

```python diagram = crate.add_file("diagram.png", properties={"@type": ["File", "ImageObject"]}) ```