Skip to content
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

After v3.6.12 test report do not list the feature file having a failed scenario. #3179

Closed
sandeepraina-lenze opened this issue Jul 7, 2023 · 1 comment

Comments

@sandeepraina-lenze
Copy link

Hello,

I am facing an issue with the test reports where the feature file is completely delinked from the report and not at all displayed in the list is the feature is marked as failed. This used to work till v3.6.12 and since then it looks to be broken. Sharing the screen-shots to show the difference.

When v3.6.12 is used:
image

When v3.6.15 or higher version is used:
image

Clearly a difference in how the reports are getting displayed is visible with the given screen shots.

There is no difference in the Serenity.conf and sharing the same for reference.

serenity {
  take.screenshots = FOR_EACH_ACTION
 # tag.failures = "true"
 # linked.tags = "issue"
 # requirements.types = "theme,epic,story"

  project.name = "${reporttitle}"
  compress.filenames = false



  report {
    accessibility = true
    #show.releases = true
    #show.manual.tests = true

    exclude.tags="startrecording,staging,reset,stoprecording,notdeployed,debug,singlebrowser"
  }

  #reports.show.step.details = true
  hide.empty.requirements = true
  full.page.screenshot.strategy = true
}

#
# Report config
#
environments {
  with_screenshots {
    serenity {
      take.screenshots = BEFORE_AND_AFTER_EACH_STEP
    }
  }
}

shutterbug {
    capturestrategy = FULL
    betweenScrollTimeout = 100
    useDevicePixelRatio = true
} 

Please help me to understand am I missing any property update or required configuration change.

@sandeepraina-lenze
Copy link
Author

I can confirm that latest Serenity version 4.0.29 works perfectly fine and resolves the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant