bonigarcia/mastering-junit5

junit5-allure fixes

sskorol opened this issue · 4 comments

sskorol commented

Currently allure-gradle doesn't support junit5 (see allure-framework/allure-gradle#17). However, junit5-allure module still requires some configuration tweaks. Will create a PR for that.

bonigarcia commented

Cool, thank you!

bonigarcia commented

Thanks to PR #2 now the allure report is stored where expected, but unfortunately the command gradlew allureReport seems not be working yet. In Linux I get this:

$ ./gradlew allureReport

> Configure project :
Gradle now uses separate output directories for each JVM language, but this build assumes a single directory for all classes from a source set. This behaviour has been deprecated and is scheduled to be removed in Gradle 5.0


FAILURE: Build failed with an exception.

* What went wrong:
Task 'allureReport' not found in root project 'junit5-allure'.

* Try:
Run gradlew tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

* Get more help at https://help.gradle.org

BUILD FAILED in 0s
sskorol commented

@bonigarcia allureReport is allure-plugin's task. As plugin doesn't support junit5 yet, I've temporary removed it from build.gradle.

See #2 description. There's a link on allure-commandline installation. You can install it via brew, scoop or whatever, and then use allure script directly instead of plugin.

That's why I've mentioned allure serve build/allure-results command in PR. You don't need gradle or maven to run allure-commandline directly.

bonigarcia commented

Understood. Thank you very much for your help!

  • 👍1