You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🛠️ 🧰 the pipeline can be continuously tested (automatically) with each pull request and merge. Multiple CI services such as travis-CI, circle-CI, etc. offer their service for free if you are an open source project.
✅ ❗ ❌ These tests can then be reflected in each PR, similar to how our documentation is now checked with each PR.
🐛 This will save us the effort of having to manually look through any changes in the code for possible introductions of bugs to the pipeline.
🎨 Writing these tests requires a slight shift in mindset where exceptions need to be considered before-hand.
Resources:
Raphael Pierzina pytest blog post (part 1) - link I would highly recommend starting here if you are unfamiliar with pytest. This is a wonderful post with many practice examples.
Continuous Integration / Continuous Deployment (CI/CD)
Provide unit tests and integration tests using pytest and a mock library (could be built-in unittest.mock, pytest.monkeypatch, pytest-mock, etc.)
After implementation of these tests:
Resources:
I would highly recommend starting here if you are unfamiliar with pytest. This is a wonderful post with many practice examples.
mock.patch
methodLegend
Work-in-progress (WIP) 🛠️
Data for coverage and quick CI/CD
Contigs containing annotations:
Associated data to mock for CI/CD
Unit test implementations
Common
test_metabin.pyExternal
Config
Taxonomy
Binning
Integration test implementations
The text was updated successfully, but these errors were encountered: