---
tags: nf-test,infrastructure,plugins
---

# nf-test

## 22-11-10 meeting

Rob, Harshil, @maxulysse, @emiller, Sateesh

## Master Plan

## nf-test adoption

- [ ] Implementation
- [ ] Tests
- [ ] nf-core/modules modules / subworkflows
- [ ] Local modules / subworkflows
- [ ] workflow
- [ ] CI
- [X] Test for changes
- [ ] Level
- [X] Running locally
- [X] Github Actions
- [ ] Structure
- [ ] Standard directory paths for test files (modules/subworkflows/workflows)
- [ ] Documentation
- [ ] Create individual issues where required
- [ ] Add tools to nf-core/tools to automate all of this
- [ ] Add CI tests and general structure to pipeline template

## Questions

- [ ] Can we use "include" aliases in nf-test?

### fetchngs as a proving ground

- [ ] Make milestone
- [ ] Make individual issues for the tests

1. Setup CI PoC ( @emiller )
2. Convert Pipeline tests
3. Add subworkflow tests
4. Test Local modules

### Rolling it out to pipelines

1. Convert Pipeline tests from GitHub actions to nf-test
2. Add Pipeline tests based on changes
a. Split `modules.config` into `modules/*.config`
- [sarek tags](https://github.com/nf-core/sarek/blob/dev/tests/config/pytest_tags.yml)
3. Add local subworkflow tests
4. Add local module tests
---
6. Add lib/ tests
7. Add linting checks(Post March)
- pytest_modules.yml
- Basic tests(check_samplesheet)

#### Locking down modules test-data

- `custom_test_data = "https://raw.githubusercontent.com/nf-core/configs/${params.custom_hash}"
- Default to master
- Pipeline authors can lock down the commit hash

### nf-core/modules

1. Update module template
2. Update CI
3. New modules will use nf-test from here on
4. Convert modules to nf-test as changes roll in
5. Hackathon group in March to covert any modules that haven't been converted