Skip to content

Conversation

@pablothedude
Copy link
Contributor

This needs discussion on how this can be added to devconf so the functional tests in GW can run fully automated.

Do we for example need a dedicated image on ghcr.io/openconext/openconext-basecontainers so this could be easily pulled on a per project basis?

@pablothedude
Copy link
Contributor Author

pablothedude commented Mar 3, 2025

@baszoetekouw @pmeulen can I add this as-is or should this be moved to the containers repo, or a separate Dockerfile in this project?

This is needed for functional tests in for example GW to test multiple and simultaneous flows in a browser.

Copy link
Member

@pmeulen pmeulen left a comment

Choose a reason for hiding this comment

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

Looks fine to me. This change is limited to the "smoketest" profile, so the container won't be there when starting the stepup devconf environment normally.

@pmeulen pmeulen merged commit c465717 into main May 6, 2025
2 checks passed
@pablothedude pablothedude deleted the feature/add-crome-browser-test-container branch May 6, 2025 13:11
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