<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ravanan/e2e-tests/Makefile, branch v0.2.0</title>
<subtitle>High-reproducibility CWL runner powered by Guix</subtitle>
<id>http://git.systemreboot.net/ravanan/atom?h=v0.2.0</id>
<link rel='self' href='http://git.systemreboot.net/ravanan/atom?h=v0.2.0'/>
<link rel='alternate' type='text/html' href='http://git.systemreboot.net/ravanan/'/>
<updated>2025-08-24T17:59:21+00:00</updated>
<entry>
<title>guix: Work with a test suite interned to the store.</title>
<updated>2025-08-24T17:59:21+00:00</updated>
<author>
<name>Arun Isaac</name>
</author>
<published>2025-08-24T16:48:54+00:00</published>
<link rel='alternate' type='text/html' href='http://git.systemreboot.net/ravanan/commit/?id=c2c22bc3a215e2a0d57c976a9aa337df95297ba1'/>
<id>urn:sha1:c2c22bc3a215e2a0d57c976a9aa337df95297ba1</id>
<content type='text'>
Instead of cwl-v1.2-conformance being a script that accepts a path to
the CWL v1.2 conformance test suite, we now work with a CWL v1.2 repo
origin object. This is more declarative, and there is no need for
manual cloning of the cwl-v1.2 git repo on the CI. The CI merely has
to run a script with no arguments. This provides more control here in
the ravanan repo and less configuration on the CI server.

We do likewise for the end-to-end tests. In this case, we work with
files from the ravanan repo, but have to first compile ccwl sources to
CWL workflows.
</content>
</entry>
<entry>
<title>Add end-to-end tests.</title>
<updated>2025-08-24T13:24:11+00:00</updated>
<author>
<name>Arun Isaac</name>
</author>
<published>2025-08-24T11:33:55+00:00</published>
<link rel='alternate' type='text/html' href='http://git.systemreboot.net/ravanan/commit/?id=14845d344ef346029fc58b7c66be6bc43b70a661'/>
<id>urn:sha1:14845d344ef346029fc58b7c66be6bc43b70a661</id>
<content type='text'>
End-to-end tests allow us to test the whole of ravanan. This is a
useful sanity check to ensure that basic workflows remain working.
</content>
</entry>
</feed>
