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

Update to nf-test #436

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

adamrtalbot
Copy link
Collaborator

Updates to nf-test which should help clarity

Changes:

  • Move the pipeline test first, to give a gentle introduction
  • Ramp up the complexity throughout the module
  • Add more description of why testing is important

Note I think we could go further, but these are quick and relatively simple changes.

Changes:
 - Moves pipeline level test to the first section, in order to introduce the concept of testing early with a simple example.
 - Moves other tests lower, in order to increase the complexity of the tests as we go.
Copy link

netlify bot commented Nov 5, 2024

Deploy Preview for nextflow-training ready!

Name Link
🔨 Latest commit 7644ebd
🔍 Latest deploy log https://app.netlify.com/sites/nextflow-training/deploys/673535da1df6700008d171d4
😎 Deploy Preview https://deploy-preview-436--nextflow-training.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@kenibrewer
Copy link
Member

@adamrtalbot I like moving the pipeline tests to the beginning. Looks like this needs some updating based on the other changes, though.

@adamrtalbot
Copy link
Collaborator Author

@adamrtalbot I like moving the pipeline tests to the beginning. Looks like this needs some updating based on the other changes, though.

I'm thinking I'm just going to re-write the whole darned thing with a slightly different flow to make it clearer what the purpose of testing really is. We could include things like deliberately breaking a module to demonstrate an error. I've started a planning doc and shared it with you, we can dump a draft here once I've got he major points fleshed out.

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

Successfully merging this pull request may close these issues.

3 participants