[
https://issues.apache.org/jira/browse/MINVOKER-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958355#comment-17958355
]
Olivier Lamy commented on MINVOKER-121:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-invoker-plugin#486|https://github.com/apache/maven-invoker-plugin/issues/486].
> Add @testName@ or @projectName@ to filters for integration-tests
> ----------------------------------------------------------------
>
> Key: MINVOKER-121
> URL: https://issues.apache.org/jira/browse/MINVOKER-121
> Project: Maven Invoker Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Affects Versions: 1.5
> Reporter: Lars Corneliussen
> Priority: Major
>
> It should be as easy as possible to create integration tests. Having
> @testName@ filtered in to the pom and hooks, it would allow me to respect DRY.
> Then the only place, where the testname is stated would be the folder where
> the pom is placed.
> Currently i can already specify -Dinvoker.test=<dir>,<dir>; so the concept is
> already there.
> For Maven-Plugins, my base ITS-pom would the look like this:
> {code:title=src/it/IT001_ZeroConfig/pom.xml}
> <project ... >
> <modelVersion>4.0.0</modelVersion>
> <groupId>@project.groupId@[email protected]@-its</groupId>
> <artifactId>@testName@</artifactId>
> <version>@project.version@</version>
> <packaging>pom</packaging>
> </project>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
