guix: Work with a test suite interned to the store. HEAD main

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.

1 files changed, 5 insertions, 5 deletions

diff --git a/HACKING.md b/HACKING.md
index 7bb6691..e456242 100644
--- a/HACKING.md
+++ b/HACKING.md
@@ -7,12 +7,12 @@ guix shell -L .guix -Df manifest.scm
 
 # Run end-to-end tests
 
-ravanan comes with a suite of end-to-end tests under `e2e-tests`. To run them, first compile the required CWL workflows from the ccwl sources.
+ravanan comes with a suite of end-to-end tests under `e2e-tests`. End-to-end tests require a running Guix daemon. To run them, create and change into a new empty directory.
 ```
-make -C e2e-tests
+mkdir rundir
+cd rundir
 ```
-Then, run cwltest like so:
+Then, build and run the tests.
 ```
-make -C e2e-tests check
+$(guix build -L ../.guix -e '(@ (cwl-conformance) e2e-tests)')
 ```
-End-to-end tests require a running Guix daemon.