-
-
Notifications
You must be signed in to change notification settings - Fork 513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The log is not detecting the failure (locally)after upgrading to serenityCoreVersion = '4.0.1' #3252
Comments
Can you provide a sample project to reproduce the issue? |
@wakaleo File bddLogger = new File(projectDir, "failed-tests.log") // Default to false if not provided buildscript { apply plugin: 'java' configurations { ext { // serenityJiraVersion = '1.12.0'
} dependencies {
} test {
} gradle.startParameter.continueOnFailure = true tasks.withType(Test) {
} serenity { |
|
@wakaleo the above are the confiqs is there anything you can do with out the sample project?? |
If you can provide a sample project that reproduces the issue, someone might be able to pick it up and take a look. If you cannot do that and need project-specific support, we can do that as part of the commercial support packages (https://www.serenity-dojo.com/serenity-bdd-enterprise-support). |
When I upgraded to the latest version (4.0.1) of Serenity, 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.
Below are the config
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'
The text was updated successfully, but these errors were encountered: