Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Annotation Description, "useJavaDoc=true" do not working #778

Closed
2 tasks
dm-test opened this issue Apr 13, 2018 · 1 comment · Fixed by allure-framework/allure-java#261
Closed
2 tasks

Comments

@dm-test
Copy link

dm-test commented Apr 13, 2018

I'm submitting a ...

  • [*] bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

The "use Java Doc=true" parameter does not work correctly. In allure-junit 4, allure-unit 5 adapters annotation with such parameter is ignored (javaDoc text is not displayed in html-report), in allure-testng adapter problems with javaDoc with Russian text (encoding!)

Please tell us about your environment:

Allure version 2.6.0
Test framework testng@6.14.2
Allure adaptor allure-testng@2.6.0
Generate report using allure-maven@2.9
Allure version 2.6.0
Test framework junit@4.12
Allure adaptor allure-junit4@2.6.0
Generate report using allure-maven@2.9
Allure version 2.6.0
Test framework junit-jupiter-engine@5.1.0
Allure adaptor allure-junit5@2.6.0
Generate report using allure-maven@2.9
@dm-test dm-test changed the title Annotation Description, "@useJavaDoc=true" do not working Annotation Description, "useJavaDoc=true" do not working Apr 13, 2018
@occupant23
Copy link

I use the same versions for jUnit as mentioned above and found that the annotation is not working at all at the moment. While the data of other annotations is visible in the JSON file the Description annotation in not included within the file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants