GEMScienceTools / GEMScienceTools/hamlet
better validation of test config
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Need to do a bit more validation of test config. For example, a config made by a user had the max mag and min mag switched, and this wasn't reported as an error.
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
Start by locating the validation entry point for the test configuration and trace how minimum and maximum magnitude values are checked. Done means a configuration with max magnitude lower than min magnitude is detected and reported as an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100