Skip to content
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

Run e2e against multiple XMPP server implementations #916

Open
sonnyp opened this issue Aug 24, 2021 · 3 comments
Open

Run e2e against multiple XMPP server implementations #916

sonnyp opened this issue Aug 24, 2021 · 3 comments

Comments

@sonnyp
Copy link
Member

sonnyp commented Aug 24, 2021

Right now we only run integration tests against prosody.

Would be neat to run them against at least openfire, ejabberd and maybe jackal

Priority would be openfire because of #914

Also, openfire is trivial to use

wget https://www.igniterealtime.org/downloadServlet?filename=openfire/openfire_4_6_4.tar.gz
tar -xf openfire_4_6_4.tar.gz
cd openfire
./bin/openfire start
# setup at localhost:9090 - we need to automate his
@guusdk
Copy link
Contributor

guusdk commented Mar 15, 2022

Hey, feel free to ping me about Openfire issues (I'm a core contributor)

To start a pre-provisioned version of Openfire, use ./bin/openfire.sh -demoboot. That will start Openfire using the embedded database, configured to use a domain named example.org, with an administrative account that uses as its credentials admin/admin and two users accounts: john/secret and jane/secret

Likewise, if you can tell me how to run e2e tests, I can see if we can add those to the suite of tests that we run in Openfire's CI.

@sonnyp
Copy link
Member Author

sonnyp commented Mar 15, 2022

@guusdk sweet

e2e tests are fairly specific at the moment. I will make a “public interface” for them and come back to you.

My todo list:

  • env vars for connection parameters (credentials, port, url, ...)
  • add a make target and documentation for running the e2e tests

Aside from that anything else you would need?

@guusdk
Copy link
Contributor

guusdk commented Mar 15, 2022

As with anything Javascript-ish, I need to be explained as if I'm a four-years-old. :)

What probably would be helpful is:

  • how to determine if the tests succeed or fail
  • determine why a particular test failed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants