How to run test locally in a reproducible way?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 75
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
I am sorry, but I have no experience with Maven and I am having headaches in getting locally the same results that I get on the CI.
For example, at this time on my machine when running `mvn test` from `tool-testuite` I get errors I do not get on the CI.
What I am doing is to run:
```
mvn clean install -e -U -Dmaven.test.skip=true
cd tool-testsuite
mvn test
```
Am I missing something?
I think that other potential contributors could come from a Gradle background and be running into surprising challenges when dealing with Maven
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 reproducing the reported `mvn clean install -e -U -Dmaven.test.skip=true` and `mvn test` commands in `tool-testsuite`, then compare them with the CI setup. Document the Maven steps that produce reproducible local results and explain what successful completion should look like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100