Continuous integration testing
The key words “MUST”, “MUST NOT”, “SHOULD”, etc. are to be interpreted as described in RFC 2119.
Pipelines MUST have automated continuous integration testing running using GitHub Actions.
There MUST also be CI tests using AWS (test and test_full).
There MUST be a config profile called test that SHOULD be as comprehensive as possible - that is, it SHOULD run as much of the pipeline as possible.
It SHOULD use as tiny a test data set as possible (even if the output that it creates is meaningless).
- Get started
- Running
- Overview
- Advanced topics
- Configuration
- Reference genomes
- Running pipelines offline
- Developing
- Overview
- Containers
- Documentation
- Institutional profiles
- Migration guides
- Testing
- Contributing
- Overview
- Components
- Contribution types
- Contributor's list
- Deprecating modules
- Documentation
- Existing pipelines
- New pipelines
- Project proposals
- Reviewing pull requests
- nf-core bot
- Review checklists
- Reviewing pipeline releases
- Specifications
- Community
- Advisories
- Governance
- Terminology
- nf-core/tools
- API
- CLI
- Installation
- Test datasets
- TUI