Create test cases for existing subsystems
Open
Nobody has claimed this yet.
code quality
just do it
lang: c++
- Dominant language
- Python
- Stars
- 14.4k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
Because reasons we should add more tests to the code.
Substems with test coverage:
- Pathfinding
- Jobmanager
- Terrain blending
- Coordinate system
- Asset manager
- Logger
For the missing ones, please create some creative tests.
An example how that could look like can be seen in libopenage/datastructure/.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
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
Review the existing test patterns in libopenage/datastructure/ first. Then locate the Terrain blending, Asset manager, and Logger subsystems and identify their current test entry points. Done means each listed missing subsystem has meaningful test cases covering its existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100