swagger-api / swagger-api/swagger-parser
Unit tests configuration issues (rely on relative path and mix testng and junit)
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 867
- Forks
- 560
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 7
Description
Currently, the unit tests:
- are using relative path to load test resources (could be fixed by using classpath)
- mix testng and a bit of junit (could be fixed by using only testng)
=> on my env, using intellij, some tests fail due to relative path issue and some tests are ignored because we have to choose between testng and junit framework
PR coming.
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
Review the unit-test resource loading and test framework configuration described in the issue; no specific files or tests are named. Run the unit-test suite in IntelliJ to reproduce the relative-path failures and ignored tests, then verify that resources load from the classpath and the tests use one framework consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100