We don't currently have a rapid way to test a workflow. I think that having a null workflow that reproduces the order, input and output files of the tasks would be helpful for rapid testing.
Ideally we would have a quick way to make sure that a workflow would run end to end without having to wait for any kbmod processing. i.e. just a way to test the workflow part, not the science part.
This could be something simple like a config parameter like dry-run: true that will be used by the tasks to not call any of the actual code, but instead, read input files and write empty output files.
We don't currently have a rapid way to test a workflow. I think that having a null workflow that reproduces the order, input and output files of the tasks would be helpful for rapid testing.
Ideally we would have a quick way to make sure that a workflow would run end to end without having to wait for any kbmod processing. i.e. just a way to test the workflow part, not the science part.