You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently you cannot check the stdout/stderr of a process unless it is explicitly captured as a channel.
It would be useful if nf-test could expose the content of the relevant .command.* file at e.g. process.command_out so that they can be tested without needing to be explicitly checked.
It should be possible to read and inject this information in a similar method to the way thew nextflow top level stdout is injected to e.g. pipeline.stdout
The text was updated successfully, but these errors were encountered:
Currently you cannot check the stdout/stderr of a process unless it is explicitly captured as a channel.
It would be useful if
nf-test
could expose the content of the relevant.command.*
file at e.g.process.command_out
so that they can be tested without needing to be explicitly checked.It should be possible to read and inject this information in a similar method to the way thew nextflow top level stdout is injected to e.g.
pipeline.stdout
The text was updated successfully, but these errors were encountered: