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.

Sign up for GitHub

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

Jump to bottom

feat(modules_testdata_base_path): update guidelines for test data #2474

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
+3 −3
Open

feat(modules_testdata_base_path): update guidelines for test data #2474

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d3dbb07
feat(modules_testdata_base_path): update guidelines for test data
maxulysse Apr 26, 2024
9af2d0d
Apply suggestions from code review
maxulysse Apr 26, 2024
907adc0
Apply suggestions from code review
maxulysse Apr 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/content/docs/contributing/test_data_guidelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,10 +57,10 @@ In contrast, if your module requires many tests, steps, or heavy CPU usage, you

11. The test data pull request requires a review to be merged.

12. Once you've had your pull request merged in into `nf-core/test-datasets`, make another PR into [nf-core/modules](https://github.com/nf-core/modules), to add your file as a new entry to the [`modules/tests/config/test_data.config`](https://github.com/nf-core/modules/blob/master/tests/config/test_data.config).
12. Once you've had your pull request merged in into `nf-core/test-datasets`, you are good to go and you can use refer to the newly uploaded file(s) for your tests. Use `params.modules_testdata_base_path` to point to the test data directory in your module, and append to it the path to the file(s) you need. an example using the `fasta` file from `sarscov2`:
maxulysse marked this conversation as resolved.
Show resolved Hide resolved

- This only applies field-specific collections, `delete_me/` files are excluded from this, and raw github URLs should be used in tests.
- The 'key' for each URL should follow the style of the full file name with extensions but with underscores rather than full-stops e.g. `genome.fa.gz` would become `genome_fa_gz`.
- `file(params.modules_testdata_base_path + 'genomics/sarscov2/genome/genome.fasta', checkIfExists: true)`
maxulysse marked this conversation as resolved.
Show resolved Hide resolved
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- `file(params.modules_testdata_base_path + 'genomics/sarscov2/genome/genome.fasta', checkIfExists: true)`
```groovy
file(params.modules_testdata_base_path + 'genomics/sarscov2/genome/genome.fasta', checkIfExists: true)
```

- Note the file string corresponds to the directory structure of the modules repository.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- Note the file string corresponds to the directory structure of the modules repository.
Note that the file string corresponds to the directory structure of the modules repository.


### Field specific guidance

Expand Down
Loading