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

Check and expand Ci tests #93

Merged
merged 25 commits into from
Oct 16, 2023
Merged

Check and expand Ci tests #93

merged 25 commits into from
Oct 16, 2023

Conversation

tillenglert
Copy link
Collaborator

@tillenglert tillenglert commented Aug 3, 2023

I added some new tests with already existing data and changed some input sample sheets to have the following test:

without NCBI credentials:

  • test_full
  • test_assembly_only
  • test_bins_only
  • test_coassembly
  • test_mouse_allow_all_pep_lengths
  • test_model_information
  • test_mhcflurry
  • test_mhcnuggets_1
  • test_mhcnuggets_2

with NCBI credentials:

  • test
  • test_taxa_only
  • test_mouse
  • test_tiny -> I'm not quite sure if we should keep this test, I would personally delete it, as it doesn't give any more information compared to the other tests (@skrakau)

I also opened a PR on test-datasets (nf-core/test-datasets#982) to add the new sample sheets.

PR checklist

  • This comment contains a description of changes (with reason).
  • If you've fixed a bug or added code that should be tested, add tests!
  • If you've added a new tool - have you followed the pipeline conventions in the contribution docs
  • If necessary, also make a PR on the nf-core/metapep branch on the nf-core/test-datasets repository.
  • Make sure your code lints (nf-core lint).
  • Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
  • Usage Documentation in docs/usage.md is updated.
  • Output Documentation in docs/output.md is updated.
  • CHANGELOG.md is updated.
  • README.md is updated (including new tool citations and authors/contributors).

@github-actions
Copy link

github-actions bot commented Aug 3, 2023

nf-core lint overall result: Failed ❌

Posted for pipeline commit c51f7ad

+| ✅ 151 tests passed       |+
!| ❗   9 tests had warnings |!
-| ❌   5 tests failed       |-

❌ Test failures:

  • files_unchanged - CODE_OF_CONDUCT.md does not match the template
  • files_unchanged - .github/CONTRIBUTING.md does not match the template
  • files_unchanged - .github/workflows/linting.yml does not match the template
  • files_unchanged - lib/NfcoreTemplate.groovy does not match the template
  • multiqc_config - 'assets/multiqc_config.yml' does not contain a matching 'report_comment'.

❗ Test warnings:

  • files_exist - File not found: conf/igenomes.config
  • readme - README contains the placeholder zenodo.XXXXXXX. This should be replaced with the zenodo doi (after the first release).
  • pipeline_todos - TODO string in README.md: Add full-sized test dataset and amend the paragraph below if applicable
  • pipeline_todos - TODO string in README.md: If applicable, make list of people who have also contributed
  • pipeline_todos - TODO string in README.md: Add citation for pipeline after first release. Uncomment lines below and update Zenodo doi and badge at the top of this file.
  • pipeline_todos - TODO string in awsfulltest.yml: You can customise AWS full pipeline tests as required
  • pipeline_todos - TODO string in WorkflowMain.groovy: Add Zenodo DOI for pipeline after first release
  • pipeline_todos - TODO string in usage.md: Add documentation about anything specific to running your pipeline. For general topics, please point to (and add to) the main nf-core website.
  • pipeline_todos - TODO string in output.md: Write this documentation describing your workflow's output

✅ Tests passed:

Run details

  • nf-core/tools version 2.10
  • Run at 2023-10-02 07:23:00

@tillenglert
Copy link
Collaborator Author

@nf-core-bot fix linting

@tillenglert tillenglert marked this pull request as ready for review September 11, 2023 09:25
@@ -71,7 +80,7 @@ jobs:
strategy:
fail-fast: false
matrix:
tests: ["test", "test_mouse", "test_tiny"] # add further test profiles here, will be run in parallel (but only with one nextflow version)
tests: ["test", "test_mouse", "test_tiny", "test_taxa_only"] # add further test profiles here, will be run in parallel (but only with one nextflow version)
Copy link
Member

Choose a reason for hiding this comment

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

Could you change the order here (it was changed in some refactoring in the past), such that the profile test is used in the test above and the others here as additional? would seem more intuitive, or is there still a reason why it is like it is?

Copy link
Member

Choose a reason for hiding this comment

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

doesn't work due to credentials ...

@tillenglert
Copy link
Collaborator Author

I added the versioning directory on test-datasets, so all tests will fail until this is merged.

@tillenglert
Copy link
Collaborator Author

@nf-core-bot fix linting

@tillenglert
Copy link
Collaborator Author

@skrakau linting is still failing due to template update, but it still expects test_bins! I will change it when this PR is merged or would you first change the expected tests for branch protection before merging?

@tillenglert
Copy link
Collaborator Author

@skrakau Maybe different question: Which tests should I make required? All of the new/old ones? :)

@skrakau
Copy link
Member

skrakau commented Oct 11, 2023

would there be a reason for any of the tests to not make them required? Otherwise I would make them required

@skrakau
Copy link
Member

skrakau commented Oct 11, 2023

@skrakau linting is still failing due to template update, but it still expects test_bins! I will change it when this PR is merged or would you first change the expected tests for branch protection before merging?

it's fine to do it afterwards, if you can? Maybe would be easier before

@tillenglert
Copy link
Collaborator Author

would there be a reason for any of the tests to not make them required? Otherwise I would make them required

No not really, okay I will make them required! They should all pass if one makes a PR! :)

Copy link
Member

@skrakau skrakau left a comment

Choose a reason for hiding this comment

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

LGTM!

@tillenglert tillenglert merged commit 2e8e11b into nf-core:dev Oct 16, 2023
@tillenglert tillenglert mentioned this pull request Oct 16, 2023
@tillenglert tillenglert deleted the CI_tests branch October 16, 2023 12:03
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.

3 participants