-
Notifications
You must be signed in to change notification settings - Fork 249
fix: update docs on nf-test #3306
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for nf-core-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for nf-core-main-site ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
then { | ||
assertAll( | ||
{ assert process.success }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can do as @SPPearce suggested and put the assert process.success before the assertAll?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, this would be nice.
In the end do we even need the assertAll
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not so sure about that either
any updates here @famosab? |
I'm going to ping @LouisLeNezet here and hope that he is willing to do some work on the docs ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is some comments, where things could be further standardized.
This would help to uniformize the modules repository 😉
sites/docs/src/content/docs/tutorials/tests_and_test_data/nf-test_writing_tests.md
Outdated
Show resolved
Hide resolved
sites/docs/src/content/docs/tutorials/tests_and_test_data/nf-test_writing_tests.md
Show resolved
Hide resolved
then { | ||
assertAll( | ||
{ assert process.success }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, this would be nice.
In the end do we even need the assertAll
?
sites/docs/src/content/docs/tutorials/tests_and_test_data/nf-test_writing_tests.md
Outdated
Show resolved
Hide resolved
sites/docs/src/content/docs/tutorials/tests_and_test_data/nf-test_writing_tests.md
Outdated
Show resolved
Hide resolved
sites/docs/src/content/docs/tutorials/tests_and_test_data/nf-test_writing_tests.md
Outdated
Show resolved
Hide resolved
sites/docs/src/content/docs/tutorials/tests_and_test_data/nf-test_writing_tests.md
Show resolved
Hide resolved
sites/docs/src/content/docs/tutorials/tests_and_test_data/nf-test_writing_tests.md
Show resolved
Hide resolved
Co-authored-by: Louis Le Nézet <58640615+LouisLeNezet@users.noreply.github.com>
…est_writing_tests.md Co-authored-by: Louis Le Nézet <58640615+LouisLeNezet@users.noreply.github.com>
process { | ||
""" | ||
input[0] = Channel.fromList([ | ||
tuple([ id:'test1', single_end:false ], // meta map |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use tuple(
or [
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tend to remove everything even the Channel statetement
@netlify /docs/tutorials/tests_and_test_data/nf-test_writing_tests