Module test coverage
Open
Nobody has claimed this yet.
regulatory
- Dominant language
- Python
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Until we get coverage supported by nf-test (https://github.com/askimed/nf-test/issues/11), let's simply compare the number of main.nf to the number of main.nf.test
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing module-counting or statistics entry point and any tests covering module discovery. Compare the number of main.nf files with main.nf.test files, using the nf-test coverage limitation in issue 11 as context; done means the comparison is reported for the repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100