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

No reports are generated when using latest Allure version (2.16.1) #82

Open
1 of 3 tasks
serzhshakur opened this issue Nov 9, 2021 · 3 comments
Open
1 of 3 tasks

Comments

@serzhshakur
Copy link

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?

No reports are generated when using latest Allure version (2.16.1)

allure_gradle_bug

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

This can be easily observed using this project
Do

git checkout allure-2.16.1
./gradlew clean runTestsOne
./gradlew allureAggregateServe  

Click the link provided by allureAggregateServe in the output - no report is served.
The report is successfully generated when using Allure version 2.14.0 and below (check the same project on master branch).

What is the expected behavior?

Report should be properly generated and viewed while served.

Please tell us about your environment:

Allure version 2.16.1
Test framework junit 5
Allure adaptor [email protected]
Generate report using [email protected]
@baev
Copy link
Member

baev commented Dec 21, 2021

ok, the issue is that you setting allure commandline version (using version.set(allureVersion)), but not updating allure-java version (allureJavaVersion.set(allureVersion)).

So the following will work:

allure {
    version.set(allureVersion)
    adapter {
        allureJavaVersion.set(allureVersion)
        frameworks {
            junit5
        }
    }
}

since we are using the same version for allure-java and allure report itself it probably makes sense to fix it and make so users only set a single property by default.

@vlsi
Copy link
Contributor

vlsi commented Sep 14, 2022

@baev , is allureJava adapter always released together with allure-commandline?
If that is the case, we could use allureJavaVersion.convention(allure.version) so allureJavaVersion is using allure.version by default.

WDYT?

At the same time, we should probably bump the defaults for allure.version, apsectjVersion, etc.

@vlsi
Copy link
Contributor

vlsi commented Sep 14, 2022

I believe the issue is fixed in #99

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

No branches or pull requests

3 participants