not able to see the step-by-step console log locally with 4.0.14 version

[jerrin89]

What happened?

When I upgraded to the latest version of Serenity (4.0.14), I am not able to see the step-by-step console log locally when a step actually fails (I intentionally used the wrong element locator in one step to make it fail). The log is not detecting the failure, and it shows that all steps passed.

What did you expect to happen?

w

Serenity BDD version

buildscript {
repositories {
mavenLocal()
mavenCentral()
maven {
url "https://plugins.gradle.org/m2/"
}
}
dependencies {
classpath "net.serenity-bdd:serenity-gradle-plugin:4.0.1"
classpath "net.serenity-bdd:serenity-single-page-report:4.0.1"
}
}

apply plugin: 'java'
apply plugin: 'eclipse'
apply plugin: 'idea'
apply plugin: "net.serenity-bdd.serenity-gradle-plugin"
//apply plugin: 'net.serenity-bdd.aggregator'
//apply from: "$rootDir/gradle/libraries.gradle"

configurations {
nexusCompile
}

ext {
slf4jVersion = '2.0.9'
serenityCoreVersion = '4.0.1'
serenityCucumberVersion = '4.0.1'
serenityRestAssuredVersion = '4.0.1'
junitVersion = '4.13.1'
assertJVersion = '3.8.0'
logbackVersion = '1.4.11'
bonigarcia ='5.4.1'

// serenityJiraVersion = '1.12.0'

sql2oVersion = '1.6.0'
mssqlJdbcVersion = '9.4.0.jre11'
lombokVersion = '1.18.28'

jacksonJsrVersion = '2.12.5'
jsonSchemaValidatorVersion = '4.1.0'
ucaseApiCommonsVersion = "0.5.55"
jsonVersion = '20201115'
hikariCpVersion = '5.0.0'

rabbitMQClientversion = '5.10.0'
springKafkaVersion = '2.8.2'

}

dependencies {
testImplementation "ch.qos.logback:logback-classic:${logbackVersion}",
"io.github.bonigarcia:webdrivermanager:${bonigarcia}",
"org.springframework.kafka:spring-kafka:${springKafkaVersion}",
"org.springframework.kafka:spring-kafka-test:${springKafkaVersion}",
"net.serenity-bdd:serenity-core:${serenityCoreVersion}",
"net.serenity-bdd:serenity-cucumber:${serenityCucumberVersion}",
"net.serenity-bdd:serenity-screenplay:${serenityCoreVersion}",
"net.serenity-bdd:serenity-screenplay-webdriver:${serenityCoreVersion}",
"net.serenity-bdd:serenity-ensure:${serenityCoreVersion}",
"net.serenity-bdd:serenity-rest-assured:${serenityRestAssuredVersion}",
"junit:junit:${junitVersion}",
"org.assertj:assertj-core:${assertJVersion}",
"org.json:json:${jsonVersion}",
"com.rabbitmq:amqp-client:${rabbitMQClientversion}",
"io.rest-assured:json-schema-validator:${jsonSchemaValidatorVersion}",
"com.fasterxml.jackson.datatype:jackson-datatype-jsr310:${jacksonJsrVersion}",
"org.slf4j:slf4j-api:$slf4jVersion",
"org.sql2o:sql2o:${sql2oVersion}",
"com.microsoft.sqlserver:mssql-jdbc:${mssqlJdbcVersion}",
"org.projectlombok:lombok:${lombokVersion}",
"com.fasterxml.jackson.module:jackson-module-jsonSchema:2.9.0",
"com.zaxxer:HikariCP:${hikariCpVersion}",
"com.unilink.ucase:api-commons:${ucaseApiCommonsVersion}",
"com.unilink.ucase.api-commons-models:authorisation-service-model:latest"
// "com.unilink.ucase.api-commons-models:party-event-service-model:0.0.16",
// "net.serenity-bdd:serenity-jira-plugin:${serenityJiraVersion}" ,

testAnnotationProcessor "org.projectlombok:lombok:${lombokVersion}"

}

JDK version

w

Execution environment

w

How to reproduce the bug.

w

How can we make it happen?

Work on this myself and propose a PR (with Serenity BDD team guidance)