allure-framework / allure-framework/allure2
@Severity seems not take effect.
- Dominant language
- HTML
- Stars
- 5.5k
- Forks
- 782
- Avg merge
- 2d 33m
- Merged PRs (30d)
- 16
Description
**Describe the bug**
@Severity seems not take effect.
**To Reproduce**
Steps to reproduce the behavior:
1. code
@Test
@DisplayName("xxx")
@Description("yyy")
@Link("zzz")
@Issue("123321")
@Severity(SeverityLevel.MINOR)
public void testCase(){...}
2. pom
```
1.8.10
org.apache.maven.plugins
maven-compiler-plugin
8
8
org.apache.maven.plugins
maven-surefire-plugin
2.20
false
-javaagent:"${settings.localRepository}/org/aspectj/aspectjweaver/${aspectj.version}/aspectjweaver-${aspectj.version}.jar"
listener
io.qameta.allure.junit4.AllureJunit4
org.aspectj
aspectjweaver
${aspectj.version}
```
4. mvn clean test
5. allure serve allure-results
**Expected behavior**

**Screenshots**
Severity seems not take effect
**Environment (please complete the following information):**
| Allure version | 2.17.2 |
| junit | 4.13.1 |
| allure-junit4 | 2.19.0 |
**Additional context**
Add any other context about the problem here.
Contributor guide
Research direction
Start with the Java reproducer and the Maven Surefire configuration using AllureJunit4, then run `mvn clean test` and `allure serve allure-results` as described. Compare the generated report with the `@Severity(SeverityLevel.MINOR)` annotation; done means the report reflects the specified severity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100