Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow capture and assertion of .command.{err,out,log} #209

Open
awgymer opened this issue Apr 16, 2024 · 0 comments
Open

Allow capture and assertion of .command.{err,out,log} #209

awgymer opened this issue Apr 16, 2024 · 0 comments

Comments

@awgymer
Copy link

awgymer commented Apr 16, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant