jMonkeyEngine / jMonkeyEngine/jmonkeyengine
Proposal: clean up the examples and tests
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 14
Description
As we've been consistently adding tests for issues within the jme3-examples, I realize this might be confusing for newcomers using the examples to learn about the engine.
My proposal is to relocate all tests, including unit tests and assets, into a dedicated jme3-tests module.
What do you think?
Contributor guide
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 inspecting the jme3-examples module and identifying its unit tests and test assets. Review how the proposed jme3-tests module would fit the project structure, then confirm the intended scope with maintainers. Done would mean tests and their assets are relocated without leaving the examples confusing for newcomers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100