Preprocessor unittests
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
Desired capability or behavior.
There are currently no tests to ensure the preprocessor is functioning as intended
Suggested implementation.
Since the preprocessor does possibly hundreds of different things, this could be quite large. At a minimum we can have separate test files for each preprocessor (propulsion, crew & payload, etc.) that runs through as few test cases as reasonable to check all the different rules. AI may be able to automate some of this, especially if given a framework to start with first.
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
Begin by locating the preprocessor modules for propulsion, crew, and payload, then inspect how the existing test suite is organized. Done means separate tests exercise the different preprocessors and cover their relevant rules, but the issue does not define a bounded initial scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100