-
-
Notifications
You must be signed in to change notification settings - Fork 971
Restart Geb VNC Container for each Test in a Spec to get correct recordings #14995
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
test: proof of bug
jdaugherty
reviewed
Aug 20, 2025
Contributor
jdaugherty
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @JonasPammer & Great Work Around!
My only concern is not cleaning up the recordings - can we clean those up unless some setting is set? Otherwise, running grails tests locally will constantly add more recordings.
cbmarcum
reviewed
Aug 21, 2025
grails-geb/src/testFixtures/groovy/grails/plugin/geb/GrailsGebSettings.groovy
Outdated
Show resolved
Hide resolved
Contributor
|
@JonasPammer Thank you for working on this. |
And also, do not use an external url in the test.
Contributor
Author
jdaugherty
reviewed
Aug 24, 2025
The system property `grails.geb.recording.restartRecordingContainerPerTest` was explicitly set to `true` for tests, but this is now the default behavior, so the explicit setting is no longer needed.
Delete all but the two most recent recording directories as part of the build to avoid unnecessary disk usage.
# Conflicts: # grails-geb/src/testFixtures/groovy/grails/plugin/geb/GebRecordingTestListener.groovy # grails-geb/src/testFixtures/groovy/grails/plugin/geb/WebDriverContainerHolder.groovy
9323701 to
19dfb65
Compare
Restore Slf4j logging lost in the merge
matrei
approved these changes
Aug 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Original, Upstream Open Issue: testcontainers/testcontainers-java#3998
The other upstream solution that was suggested, i.e. testcontainers/testcontainers-java#577, seemed way out of bound / too big of a change (that also relies on internals and commands, i.e. volitale to flv.py changes) to hack into here
i also tried a non-reflection attempt, i.e. to manage an own vnc and disable the container's interbound one -- https://gitkraken.dev/link/drafts/3d723754-a136-45c9-bb6f-8cad74600a88?type=patch. but decided to commit this here for comments.
i know reflection code will have a low chance. but at least this also contains a test one could add with Spock-Annotation of "Fails right now".
Edit: Closes #14331