appium+gradle+serenity+junit4: part of test suites doesn't run after adding allure-reporting #1447
Unanswered
arhanechka
asked this question in
Bug Reports
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
we have a test framework, written with appium+gradle+serenity+junit4. As a more convenient reporting we added allure.
Th dependencies we used:
buildscript {
}
apply plugin: 'io.qameta.allure'
allure {
version = '2.14.0'
autoconfigure = true
aspectjweaver = true
allureJavaVersion = '2.14.0'
}
dependencies {
implementation 'org.projectlombok:lombok:1.18.18'
compile localGroovy()
compile "net.serenity-bdd:serenity-core:$serenity_version"
compile "net.serenity-bdd:serenity-junit:$serenity_version"
compile("net.serenity-bdd:serenity-rest-assured:$serenity_version")
compile 'org.slf4j:slf4j-simple:1.8.0-beta4'
compile 'org.codehaus.groovy:groovy-all:2.3.10'
compile 'junit:junit:4.12'
compile 'org.assertj:assertj-core:3.1.0'
implementation('org.aspectj:aspectjweaver:1.8.10')
implementation group: 'io.qameta.allure', name: 'allure-junit4', version: '2.14.0'
implementation group: 'com.github.automatedowl', name: 'allure-environment-writer', version: '1.0.0'
}
after adding allure last suites don't start. It's mostly 92 tests from 150 (the stable number) It's random, sometimes we have a full result, sometimes it's cut to 92 tests. The same thing is when we start a custom set (with tag) - it;s cut to 50 from 82.
Do you have any suggestion what it could be and how to fix it?
Beta Was this translation helpful? Give feedback.
All reactions