Add notebook automated testing
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the discussion in pull request 32 and the dependency and data prerequisites tracked in issues 25 and 22. Define how the notebooks should run at website build time or in CI, then verify that automated runs use documented dependencies and a suitably small dataset while remaining reproducible.
Written by the indexing model from the issue text.
Description
As noted in https://github.com/leap-stc/ClimSim/pull/32#issuecomment-1684436061, we currently do not run the notebooks automatically, either at website build time or as part of our CI testing. We should do that eventually to ensure reproducibility, but it will require, at minimum:
- Resolving https://github.com/leap-stc/ClimSim/issues/25 to ensure we know what dependencies are required for each notebook
- Having a smaller subset of data available, as we don't want to pull a large amount of data on every automated run. I believe this will be resolved as part of https://github.com/leap-stc/ClimSim/issues/22.
- Dominant language
- Jupyter Notebook
- Stars
- 164
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from leap-stc/ClimSim
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
All issues in leap-stc/ClimSim
Similar issues
-
bug: ARCHITECTURE.md states three different workflow counts (88 / 69 / 69) and no test pins themOpenarea:docs area:workflow bug documentation priority:later
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Ikalus1988/MisakaNet#4357 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
smswithoutborders/RelaySMS-Publisher#227 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 Under an hour Newbie friendliness 70/100
aiqadam/qadam-flow#1003 ·
Maintainers usually reply within 1 day
-
blocked-needs-validation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
projectcapsule/capsule#2265 ·
Maintainers usually reply within 1 day
-
bug new
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
redhat-cop/infra.aap_configuration#1484 ·
Maintainers usually reply within 2 days