Skip to content

Conversation

@mxr576
Copy link
Collaborator

@mxr576 mxr576 commented Nov 11, 2025

Added a step to show Chrome logs on test failure.

This may help with debugging random test failures such as

image https://github.com/ddev/ddev-selenium-standalone-chrome/actions/runs/19259853228/attempts/1


- name: Show Chrome logs when tests fails
shell: bash
# if: ${{ failure() }}
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uncomment before merge.

@rfay
Copy link
Member

rfay commented Nov 11, 2025

Thank you!

@mxr576
Copy link
Collaborator Author

mxr576 commented Nov 11, 2025

Okay, so as I expected this is not going to be a simple copy-paste due to the nature of how addon tests works. Will get back this PR later.

Added a step to show Chrome logs on test failure.
@mxr576 mxr576 force-pushed the mxr576-patch-1 branch 2 times, most recently from b712794 to c1731c6 Compare November 12, 2025 13:21
@mxr576 mxr576 marked this pull request as ready for review November 12, 2025 13:22
@mxr576
Copy link
Collaborator Author

mxr576 commented Nov 12, 2025

I had issues with setting up BATS on my local for running tests - different story, but I have proof that the following solution would work in the PR.

Here is an intentionally failed build and selenium-chrome logs at end.

https://github.com/ddev/ddev-selenium-standalone-chrome/actions/runs/19298600040/job/55186748888

@rfay
Copy link
Member

rfay commented Nov 12, 2025

Bats is not hard. Happy to help you install it.

@mxr576 mxr576 merged commit 72be48d into main Nov 12, 2025
4 checks passed
@mxr576 mxr576 deleted the mxr576-patch-1 branch November 12, 2025 16:33
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

Successfully merging this pull request may close these issues.

3 participants