Open amitasil opened 4 years ago
@wakaleo Scenario Details are not getting recorded in Test report. Not sure if its related to cucumber5 upgrade. using gradle build tool with Cucumber5 latest
serenityCoreVersion = '2.2.9' serenityCucumberVersion = '2.2.5' serenityRestAssuredVersion = '2.2.10' junitVersion = '4.12'
Was working for cucumber4 though
It says that no scenarios were executed. Most likely your step definition classes are not compatible with Cucumber 5
@wakaleo above is not my screenshot, I just used the existing issue to report mine.
Please refer the screens here
Scenario details are not getting captured in report
With Cucumber 4 they were getting captured like this:
Am I missing anything ?
Hi, @mayank-kapoor @wakaleo
I'm starting a new gradle project and I'm facing this same problem.
This is my build.gradle file:
defaultTasks 'clean', 'test', 'aggregate', 'reports'
group 'com.mm.e2e'
version '1.0.0'
buildscript {
repositories {
mavenLocal()
jcenter()
}
dependencies {
classpath group: 'net.serenity-bdd', name: 'serenity-gradle-plugin', version: serenityCoreVersion
classpath group: 'net.serenity-bdd', name: 'serenity-single-page-report', version: serenityCoreVersion
}
}
apply plugin: 'java'
sourceCompatibility = JavaVersion.VERSION_1_8
targetCompatibility = JavaVersion.VERSION_1_8
compileJava.options.encoding = 'UTF-8'
compileTestJava.options.encoding = 'UTF-8'
apply plugin: 'net.serenity-bdd.aggregator'
repositories {
mavenLocal()
jcenter()
}
dependencies {
// JUnit
testCompile group: 'junit', name: 'junit', version: junitVersion
// Serenity Framework
testCompile group: 'net.serenity-bdd', name: 'serenity-core', version: serenityCoreVersion
testCompile group: 'net.serenity-bdd', name: 'serenity-screenplay', version: serenityCoreVersion
testCompile group: 'net.serenity-bdd', name: 'serenity-screenplay-webdriver', version: serenityCoreVersion
testCompile group: 'net.serenity-bdd', name: 'serenity-ensure', version: serenityCoreVersion
testCompile group: 'net.serenity-bdd', name: 'serenity-cucumber6', version: serenityCucumberVersion
// QA Integration
testCompile group: 'com.mm.qa', name: 'integration', version: qaIntegrationVersion
// Annotation Processor
testCompile group: 'org.projectlombok', name: 'lombok', version: lombokVersion
testAnnotationProcessor group: 'org.projectlombok', name: 'lombok', version: lombokVersion
// Logs
compile group: 'org.slf4j', name: 'slf4j-simple', version: slf4jVersion
}
test {
outputs.upToDateWhen { false }
testLogging.showStandardStreams = true
systemProperties System.getProperties()
finalizedBy aggregate
ignoreFailures = true
}
serenity {
reports = ["single-page-html"]
}
aggregate { dependsOn test }
checkOutcomes { dependsOn aggregate }
This is my gradle.properties file:
# System properties
systemProp.file.encoding = utf-8
# Dependencies Versions
junitVersion = 4.13.1
serenityCoreVersion = 2.3.8
serenityCucumberVersion = 2.3.6
qaIntegrationVersion = 3.0.0
lombokVersion = 1.18.16
slf4jVersion = 2.0.0-alpha1
I randomly get this problem, and then create a new feature file, copy paste the test into the new feature file and run from there, and the report works fine.
@wakaleo could this be some sort of caching issue? or something is not getting properly cleared before generating the new report?
My project started with the serenity-cucumber-starter, I am on
Total tests executed in Jenkins build: 116
serenity-maven-plugin:2.1.8:aggregate (serenity-reports)
maven-failsafe-plugin:2.22.2:verify