Allure reporter, Gradle and JUnit5

-
Have been playing with JUnit5, Gradle and Allure reporting framework this weekend. A rather "fresh" JUnit5 GA release, some functionality not fully supported in Gradle / IntelliJ, and latest beta from Allure. This sounds so much like me - I want to get it working!

Found lots of configuration samples on web, so won't duplicate info here - most of them are correct. Well, there are some outdated info, especially in Allure config parts, but it's not so difficult to sort out what you need.

The only thing missing in my case was what to look for in configs when your allure-results folder is always generated in PROJECT_ROOT directory instead of PROJECT_ROOT/build. If allure-results is somewhere else - fails allureReport and allureServe. So either you get that folder where it is expected by default configs, or try to reconfigure a lot more. As I'm working with beta - I'd prefer to use as much defaults as possible at the beginning. The only thing which helped - adding this to build.gradle file:

tasks.withType(JavaExec) {
    if (it.name == 'junitPlatformTest') {
        systemProperty 'allure.results.directory', 'build/allure-results'
    }
}

Using Gradle v4+, Allure v2.5.0, Allure-Junit5 v2.0-BETA21.

Now waiting for next Gradle release; according to their plans - config file should become much simpler for JUnit5.

Guess I need to investigate more this situation when I have more time and no other interesting things to do: according to source code Allure is really trying to write results to PROJECT_ROOT/build. Why that code in my case returns only PROJECT_ROOT - yet another interesting question.

Comments

Post a Comment

Popular posts from this blog

Migrate Protractor E2E tests to async / await

-
I'm really tired of long chains of .then() in Protractor E2E tests, especially when loops and checking conditions in loops are needed. Decided I need some motivation so took a look to the future: tried to migrate a small set of tests writing in async / await style. Installed latest Node.js (7.9.0) and Protractor (5.1.1). Here comes the first surprise. "Nothing works" after disabling Selenium promise manager in Protractor config. That's why: https://github.com/angular/protractor/issues/4186 Fortunately, the issue is fixed a few days ago here: https://github.com/angular/jasminewd/pull/87 Apply this fix to my local version of jasminewd and try again. "Everything works!" Well, at least browser opens the page. Lessons learned while rewriting code: Async / await is good! The code becomes much more readable and much more easier to maintain. Try / catch in async / await structures allow better error message handling, which is so important for E2E t...
Read more

Protractor, Jasmine and promises for non-browser functions

-
Image
Since end of October I switched from test automation using Groovy, Geb, Spock and SoapUI to test automation using Protractor, Cucumber and Jasmine. Different apps, different tools, new challenges and new knowledge. The biggest challenge is promises. Lots of samples on the web about promise chaining. The small "problem" - most of those samples are for browser interaction related functions. Well, that's what we are dealing most in e2e tests. But what if those simple functions are not enough, if you need to write some functions of your own which return non-browser related promises? E.g., just to compare some values of complex structure and return "true" or "false"? Or anything else not browser related. If you are new to this kind of testing, here's where "adventures" begin. When you don't know what to google for, it's not so easy to find out you are looking for a thing named "browser control flow". What it is about? Wel...
Read more