I'm submitting a ...
What is the current behavior?
Allure groups suites into sub-suites, which, in case of TestNG, are full class names (with their packages).
What is the expected behavior?
As far as I understand, Allure has an ability to use custom class names with JUnit. In JUnit, classes can be renamed with @DisplayName annotation. In TestNG, there's no such annotation, thus, I'd like to have something like Allure's @Description annotation be applicable to class names. For example,
@Description("Class Name Without Package")
public class TestClass
What is the motivation / use case for changing the behavior?
Some projects have very long package names, which are redundant for reports.
Please tell us about your environment:
| Allure version |
2.8.1 |
| Test framework |
testng@6.8 |
| Allure integration |
allure-testng@2.13.2 |
| Generate report using |
allure-maven@2.10.0 |
Other information
I'm submitting a ...
What is the current behavior?
Allure groups suites into sub-suites, which, in case of TestNG, are full class names (with their packages).
What is the expected behavior?
As far as I understand, Allure has an ability to use custom class names with JUnit. In JUnit, classes can be renamed with
@DisplayNameannotation. In TestNG, there's no such annotation, thus, I'd like to have something like Allure's@Descriptionannotation be applicable to class names. For example,What is the motivation / use case for changing the behavior?
Some projects have very long package names, which are redundant for reports.
Please tell us about your environment:
Other information