apache / apache/maven-dependency-plugin

[MDEP-770] Integration test can not be run in parallel

Open
#1,274 1 comment 0 reactions 0 assignees View on GitHub
priority:minor
Dominant language
Java
Stars
175
Forks
196
Avg merge
19h 30m
Merged PRs (30d)
5

Description

**[Slawomir Jaranowski](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=slawekjaranowski)** opened **[MDEP-770](https://issues.apache.org/jira/browse/MDEP-770?redirect=false)** and commented

Those test:

```java
src/it/projects/get-artifact
src/it/projects/get-artifact-maven-plugin
src/it/projects/get-artifact-no-transitive
src/it/projects/get-gav
src/it/projects/analyze-testDependencyWithNonTestScope
```

operate on the same tests artifacts.

During test prepare artifacts are deleted from local repository and after test execute - assertion checks if artifact was downloaded ...

---

**Issue Links:**
- [MDEP-767](https://issues.apache.org/jira/browse/MDEP-767) Unique names of IT test artifacts

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by inspecting the five integration-test projects under src/it/projects: get-artifact, get-artifact-maven-plugin, get-artifact-no-transitive, get-gav, and analyze-testDependencyWithNonTestScope. Run these integration tests in parallel and observe the shared local-repository artifacts during preparation and execution. Done means the tests can run concurrently without interfering with each other or failing artifact-download assertions.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.