Maintenance of [testing] module
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- jupyter-notebook, python
- Domain
- ci-cd, documentation, testing
Research direction
Start by reviewing the existing materials in content/en/modules/testing and the published testing module at school.brainhackmtl.org/modules/testing/. Compare them with Section 2 of the Carpentries Incubator's python-intermediate-development course, then identify what should be replaced or adapted and what upstream contribution may be needed. Done means the module has a clear maintenance plan or updated content aligned with the selected Carpentries materials.
Written by the indexing model from the issue text.
Description
Module to maintain
Website: https://school.brainhackmtl.org/modules/testing/
Code: https://github.com/school-brainhack/school-brainhack.github.io/tree/main/content/en/modules/testing
Work to be done
To ease maintenance, I would suggest that we move towards existing materials for teaching software testing and continuous integration. In particular, I believe that "Section 2 : Ensuring Correctness of Software at Scale" of the Carpentries Incubator: Intermediate Research Software Development course matches well with what is included in the current material.
It would also provide an opportunity for us to contribute upstream to Carpentries lesson development on their repo.
cc @htwangtw, who taught this material in this year's Montreal BHS.
- Dominant language
- Jupyter Notebook
- Stars
- 42
- Forks
- 185
- PR merge metrics
- No merged PRs in 30d
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.
More from school-brainhack/school-brainhack.github.io
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
brainhackschool-2024 maintainence
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
school-brainhack/school-brainhack.github.io#420 · 1 comment · 2 assignees ·
-
school-brainhack/school-brainhack.github.io#409 · 1 assignee ·
-
maintainence
Difficulty 3/5 1-2 days Newbie friendliness 52/100
school-brainhack/school-brainhack.github.io#369 · 2 reactions ·
All issues in school-brainhack/school-brainhack.github.io
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
refactor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug build
Difficulty 1/5 Under an hour Newbie friendliness 91/100
facebookincubator/velox#19194 ·