76fa325f08
Authelia client uses hash router instead of browser router in order to work with Kubernetes nginx-ingress-controller. This is also better for users having old browsers. This commit is breaking because it requires to change the configuration of the proxy to include the # in the URL of the login portal.
2.2 KiB
Suites
Authelia is a single component in interaction with many others. Consequently, testing the features is not as easy as we might think. In order to solve this problem, Authelia came up with the concept of suite which is a kind of virtual environment for Authelia, it allows to create an environment made of components such as nginx, redis or mongo in which Authelia can run and be tested.
This abstraction allows to prepare an environment for manual testing during development and also to craft and run integration tests.
Start a suite.
Starting a suite called basic is done with the following command:
authelia-scripts suites start basic
It will start the suite and block until you hit ctrl-c to stop the suite.
Run tests of a suite
Run tests of running suite
If a suite is already running, you can simply type:
authelia-scripts suites test
and this will run the tests related to the running suite.
Run tests of non-running suite
However, if no suite is running and you still want to test a particular suite like complete. You can do so with the next command:
authelia-scripts suites test complete
This command will run the tests for the complete suite using the built version of Authelia that should be located in dist.
WARNING: Authelia must be built with authelia-scripts build and possibly
authelia-scripts docker build before running this command.
Run all tests of all suites
Running all tests is easy. Make sure that no suite is already running and run:
authelia-scripts suites test
Run tests in headless mode
In order to run the tests without seeing the windows creating and vanishing, one can run the tests in headless mode with:
authelia-scripts suites test --headless
Create a suite
Creating a suite is as easy as creating a new directory with at least two files:
- environment.ts - It defines the setup and teardown phases when creating the environment. The setup phase is the phase when the required components will be spawned and Authelia will start while the teardown is executed when the suite is destroyed (ctrl-c hit by the user) or the tests are finished.
- test.ts - It defines a set of tests to run against the suite.