rabbitmq-server/deps/rabbitmq_management/selenium
Marcial Rosales 93cee6dede Verify happy-login scenario
With auto-approved scopes
2022-08-30 17:11:18 +01:00
..
bin Verify happy-login scenario 2022-08-30 17:11:18 +01:00
test Verify happy-login scenario 2022-08-30 17:11:18 +01:00
Dockerfile WIP fixing test case happy-login.js using ObjectPages 2022-08-30 17:11:18 +01:00
Makefile Verify happy-login scenario 2022-08-30 17:11:18 +01:00
README.md Testing happy login for oauth 2022-08-30 17:11:17 +01:00
package.json WIP Using PageObject pattern to write tests 2022-08-30 17:11:18 +01:00

README.md

Automated End-to-End testing of the management ui with Selenium

We are using Selenium webdriver to simulate running the management ui in a browser. And Mocha as the testing framework for Javascript.

To run the tests we need:

  • make
  • docker
  • Ruby (needed to install uaac via gem)

Run the tests

To run the tests first we run the following command to launch Selenium for Chrome.

make run-chrome

And then to run the actual tests we run:

make run-tests

How tests are organized

All tests are hanging from the tests folder. We can use subfolders to better organize them. For instance, all Oauth2 related tests are under tests/oauth. And under this folder we have another subfolder, tests/oauth/with-uaa to group all the tests cases which run against UAA as Oauth2 server.

At the moment, there are no smart around discovering all the tests under subfolders. That will come later. For now, the command make run-tests runs just the test cases under oauth/with-uaa. But first, the script setup.sh is invoked which launches a container running RabbitMQ configured with UAA, and another container running UAA configured with a number of users, permissions, and clients.