Hi Rebecca,

Harald Pehl was asking about this as well -- see https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/thread/VYLHKAFFMMXFYHC4GDVU463IAY7NHBVH/#CYVW5OQPI5ZXRSBLSMIJHB7WJVOUEBZU.

It looks like the consensus is HtmlUnit is what we should be using for this kind of testing in the main WildFly code base, and should be the default choice across WF projects. Of course there can be exceptions for cases like HAL that might need really in depth stuff.

So +1 to your using it for your elytron-oidc-client testing.

Best regards,
Brian

On Thu, Mar 13, 2025 at 2:47 AM Scott Marlow <smarlow@redhat.com> wrote:
Rebecca, Thanks for mentioning this!


https://htmlunit.sourceforge.io/ looks interesting to read for anyone looking for more info.

Pasting a little more:
"
HtmlUnit is a "GUI-Less browser for Java programs". It models HTML documents and provides an API that allows you to invoke pages, fill out forms, click links, etc... just like you do in your "normal" browser.
It has fairly good JavaScript support (which is constantly improving) and is able to work even with quite complex AJAX libraries, simulating Chrome, Firefox or Edge depending on the configuration used.
It is typically used for testing purposes or to retrieve information from websites.

HtmlUnit is not a generic unit testing framework. It is specifically a way to simulate a browser for testing purposes and is intended to be used within another testing framework such as JUnit or TestNG. Refer to the document "Getting Started with HtmlUnit" for an introduction.
"

Interesting project!

Scott

On Tue, Mar 11, 2025, 9:38 AM Rebecca Searls <rsearls@redhat.com> wrote:
I used htmlunit only in adding several elytron-oidc-client integration tests.  It was sufficient for elytron's simple UI testing needs.

Elytron (project) uses htmlunit in its unit testing, so there's some
consistency there with this api.
_______________________________________________
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message/F2FRAZEQ6YZ4J75PEVMFIMRXSMGKUWRV/
_______________________________________________
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message/YOZZ2NJKG3JZZC3UDHVS2GBXEL43PTTZ/


--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His