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

Add nf-test review guidelines #2414

Closed
wants to merge 11 commits into from
Closed

Conversation

nvnieuwk
Copy link
Contributor

@nvnieuwk nvnieuwk commented Mar 27, 2024

@netlify /docs/contributing/modules

@nvnieuwk nvnieuwk requested a review from a team as a code owner March 27, 2024 08:29
Copy link

netlify bot commented Mar 27, 2024

Deploy Preview for nf-core ready!

Name Link
🔨 Latest commit 933ca83
🔍 Latest deploy log https://app.netlify.com/sites/nf-core/deploys/6603e45fffcf1c0008ee54af
😎 Deploy Preview https://deploy-preview-2414--nf-core.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.


- Check that there are tests for all outputs, including optional ones.
- Check that the `meta.yml` file has correct documentation links and patterns of files.
- Check that the file has correct documentation links and patterns of files.
- Run the tool help and check that important input (usually optional) has not been missed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's quite an overkill imo... are people really doing this? I like more of an organic growth of inputs tbh

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That was already there 😁 do you want me to remove it?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, please.

src/content/docs/contributing/modules.md Outdated Show resolved Hide resolved
src/content/docs/contributing/modules.md Outdated Show resolved Hide resolved
src/content/docs/contributing/modules.md Outdated Show resolved Hide resolved
- [Different assertion types](https://nf-co.re/docs/contributing/tutorials/nf-test_assertions) should be used when a straightforward `process.out` snapshot is not feasible.
- Check that a stub test exists for the module.
- Check that tags for any dependent modules are specified to ensure changes to upstream modules will re-trigger tests for the current module.
- Check that the `assertAll()` function is used and that there is at minimum a success assertion and versions in the snapshot.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should lint for this. could somebody open an issue please?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done #2415

src/content/docs/contributing/modules.md Outdated Show resolved Hide resolved
src/content/docs/contributing/modules.md Outdated Show resolved Hide resolved
src/content/docs/contributing/modules.md Outdated Show resolved Hide resolved
src/content/docs/contributing/modules.md Outdated Show resolved Hide resolved
src/content/docs/contributing/modules.md Outdated Show resolved Hide resolved
nvnieuwk and others added 3 commits March 27, 2024 09:41
Co-authored-by: Matthias Hörtenhuber <mashehu@users.noreply.github.com>
Co-authored-by: Matthias Hörtenhuber <mashehu@users.noreply.github.com>
Co-authored-by: Matthias Hörtenhuber <mashehu@users.noreply.github.com>
nvnieuwk and others added 5 commits March 27, 2024 09:45
Co-authored-by: Matthias Hörtenhuber <mashehu@users.noreply.github.com>
Co-authored-by: Matthias Hörtenhuber <mashehu@users.noreply.github.com>
Co-authored-by: Matthias Hörtenhuber <mashehu@users.noreply.github.com>
Co-authored-by: Matthias Hörtenhuber <mashehu@users.noreply.github.com>
Co-authored-by: Matthias Hörtenhuber <mashehu@users.noreply.github.com>
@nvnieuwk
Copy link
Contributor Author

Thanks for the thorough review @mashehu

@nvnieuwk
Copy link
Contributor Author

Prettier is complaining about the sub-points in the checklist, is there a better way to do this?

Copy link
Member

@jfy133 jfy133 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's there a reason why you are not using my specification version?

The specifications section is what I use for reviewing...

Ach This page is such a mess now..

@mashehu
Copy link
Contributor

mashehu commented Mar 27, 2024

I would also be in favor of putting this on a new page. We could collect all checklists for example similar to the tutorials.

@jfy133
Copy link
Member

jfy133 commented Mar 27, 2024

I would also be in favor of putting this on a new page. We could collect all checklists for example similar to the tutorials.

I'm this close to rage quitting my TODO list and just do it.

That said iirc I thought @robsyme was tasked this before I went on parental leave... I dunno if there was a PR for that?

@nvnieuwk
Copy link
Contributor Author

Oh I didn't know that section existed, my bad 😁

@jfy133
Copy link
Member

jfy133 commented Mar 27, 2024

Ok, you know what, pause this PR. Imma gonna do the restructuring tomorrow once I arrive in the UK (if I don't find an existing PR).

Once it's in maybe can re-do this PR into the section

@nvnieuwk
Copy link
Contributor Author

Okay, sorry for the confusion 😁

@jfy133
Copy link
Member

jfy133 commented Mar 27, 2024

Okay, sorry for the confusion 😁

Not your fault, this has bothered me for almost a year now 😅

@nvnieuwk
Copy link
Contributor Author

I agree it could use some restructuring :p

Copy link
Contributor

@mashehu mashehu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please don't merge this before #2441

@jfy133
Copy link
Member

jfy133 commented Apr 8, 2024

I would suggest @nvnieuwk closes this makes a new PR actually 😬
Most of the content should be added to and rephrased to match: https://nf-co.re/docs/contributing/nfcore_component-specifications/modules (IMO), otherwise general guidance rather than requirements should go with the new condensed page Matthias has writtetn

@nvnieuwk
Copy link
Contributor Author

nvnieuwk commented Apr 9, 2024

Allright, PR on the way!

@nvnieuwk nvnieuwk closed this Apr 9, 2024
@nvnieuwk nvnieuwk deleted the add-nf-test-review-guidelines branch April 9, 2024 13:09
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.

None yet

3 participants