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

testing: implement full pipeline test with an example datasets #9

Open
9 tasks
sophiamaedler opened this issue Jun 4, 2024 · 2 comments
Open
9 tasks

Comments

@sophiamaedler
Copy link
Collaborator

Whenever a commit is merged, a full test of the entire pipeline should be run to ensure that none of the implemented changes break anything in the current workflow.

Dataset types to test:

  • single timepoint project
  • time course project

Segmentation Workflows to test:

  • WGA segmentation
  • cellpose segmenation
  • nucleus segmentations
  • cytosol segmentations

Segmentation classes:

  • sharded
  • multi-threaded
  • with and without downsampling

The chosen datasets to perform the tests on need to be small enough to be supplied with the repo. The expected results from each run should also be saved and compared with the obtained results. This way any code changes that change obtained results can immediately be flagged and identified.

@mschwoer
Copy link

mschwoer commented Jun 5, 2024

the scope of this test sounds similar to what we did in alphaDIA, so maybe this code here helps: https://github.com/MannLabs/alphadia/tree/main/tests/e2e_tests

@sophiamaedler
Copy link
Collaborator Author

the scope of this test sounds similar to what we did in alphaDIA, so maybe this code here helps: https://github.com/MannLabs/alphadia/tree/main/tests/e2e_tests

indeed this does look helpful. Thanks for sharing! We would try and setup something similar I think.

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

No branches or pull requests

2 participants