aidancrilly / aidancrilly/NeSST
feature requests: tests and pytest in the CI
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 13
- Forks
- 2
- Avg merge
- 18m
- Merged PRs (30d)
- 3
Description
It would be really nice to add a few unit tests, regression tests, integration tests. Perhaps pytest and a standard tests folder is a nice option to go with. Then it can be connected to the CI
Happy to make some minimal unit tests for the energy part of the code
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.
Research direction
No files, existing tests, or CI configuration are named. Start by inspecting the energy-related code and the repository's current CI setup, then define a standard tests folder and determine what unit, regression, and integration coverage is appropriate. Done means the tests run with pytest and are connected to CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100