Test graphical user interfaces
by Harald Pehl
I would like to start a discussion on how to test graphical user interfaces
related to WildFly.
There's a demand to test the client side of OpenID Connect. Other use cases
are integration tests in the Quickstarts [1] and smoke tests in the WildFly
test suite [2]. There has already been some discussion about this topic in
the chat [3].
We should find a common approach used for these use cases. There are several
different approaches:
1. Use Arquillian Drone and Graphene, Selenium and a WebDriver backed by
HtmlUnit. This approach is currently used in [2].
2. Use Arquillian Drone and Graphene, Selenium and a remote WebDriver provided
by Testcontainers [4].
3. Use HtmlUnit only
The list is not meant to be complete. Please let me know if you have any
suggestions for other methods or tools that could help us with our testing
needs.
One thing to keep in mind is that the final approach has to work also in a
closed CI environment without downloading resources from external
sources/repositories.
[1] https://issues.redhat.com/browse/WFLY-20129
[2] https://issues.redhat.com/browse/WFLY-20322
[3] https://wildfly.zulipchat.com/#narrow/channel/174184-wildfly-developers/t...
[4] https://java.testcontainers.org/modules/webdriver_containers/
--
Harald Pehl
3 months, 1 week
Move WildFly container image to github.com/wildfly organization
by Jeff Mesnil
Hi,
Some weeks ago, I opened an issue to move our docker/container image to the wildfly organization in GitHub (instead of the current jboss-dockerfiles organization).
This transfer of project would have no user impact (images will continue to be published on quay.io/wildfly/wildfly registry) but will simplify the maintenance of the project (with maintainers that are already in the wildfly organization).
It will also simplify the integration of the image documentation on docs.wildfly.org.
It will have a little impact on the GitHub actions quota but this is a low activity project with few PRs opened at any given time.
One thing that will have to change is the name of the project (wildfly is already taken by WildFly :) The suggestion with the most votes is github.com/widfly/wildfly-container <http://github.com/widfly/wildfly-container>. Again, this has no user impact on the name of the images published in Quay <http://quay.io/>.
I’m planning to do this move in a few weeks but I want to make sure that any questions/concerns can be addressed before we push the transfer button.
If you have any feedback, please reply to the issue[1].
Thanks,
Jeff
[1] https://github.com/jboss-dockerfiles/wildfly/issues/234
--
Jeff Mesnil
Engineer @ Red Hat
http://jmesnil.net/
3 months, 3 weeks
WildFly Calendary Proposal
by Jason Lee
I have a PR open that is a first step in creating a calendar of
WildFly-related events: https://github.com/wildfly/wildfly.org/pull/439
Brian does a great job of emailing the WF dev schedule to this list, but,
for me, it tends to get buried and lost. What I'd love to be able to do is
subscribe to a .ics and have events show up on my calendar. This is a step
toward that. What would be nice is to take that one step further and make
it available in a human-friendly form on wildfly.org as well.
All that said, I would love feedback on the idea itself, the contents of
the calendar, etc. to see if this would be useful to more than just myself.
Additionally, I know we have various community efforts going on at the
moment, so if this overlaps with any of that, I'm happy to roll this into
those efforts.
Jason Lee
Principal Software Engineer
Red Hat JBoss EAP
4 months
