apache / apache/maven-surefire
[SUREFIRE-1789] inclusion using fully qualified class name is not respected
- Dominant language
- Java
- Stars
- 461
- Forks
- 588
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 19
Description
**[Mark Lehky](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mlehky)** opened **[SUREFIRE-1789](https://issues.apache.org/jira/browse/SUREFIRE-1789?redirect=false)** and commented
I am trying to use `include` configuration using fully qualified class name, as described [here](https://maven.apache.org/surefire/maven-failsafe-plugin/examples/inclusion-exclusion.html#Fully_qualified_class_name).
I have the following hierarchy in my test folder (showing only relevant parts):
```
src/test/java
+ features.feature_a
+- SomeStory.java
+ ignore.features.under_construction
+- AnotherStory.java
```
My pom configuration is:
```xml
org.apache.maven.plugins
maven-failsafe-plugin
${surefire.plugin.version}
features.*.*Story
integration-test
verify
```
When I execute `mvn verify` both of the above Stories are run.
I am expecting that only "SomeStory" will be run. The other test "AnotherStory", is not in the package "features.*".
---
**Affects:** 2.22.2
Contributor guide
Research direction
Start by reproducing the issue with mvn verify and the shown maven-failsafe-plugin configuration, using the features.feature_a and ignore.features.under_construction test packages. Compare the inclusion behavior with the Fully qualified class name documentation; done means only SomeStory.java runs and AnotherStory.java is excluded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100