Automated Integration Tests for Gerbera Media Server
Read the documentation for details on working with the Gerbera Integration Suite
// Build the docker containers
$ docker-compose -f docker-compose.ui.yml build
// Run the test suite
$ docker-compose -f docker-compose.ui.yml up --abort-on-container-exit
// Build the docker containers
$ docker-compose -f docker-compose.upnp.yml build
// Run the test suite
$ docker-compose -f docker-compose.upnp.yml up --abort-on-container-exit
The
docker-compose.dev.yml
excludes the gerbera-ui container
// Build the docker containers
$ docker-compose -f docker-compose.dev.yml build
// Run the test suite
$ docker-compose -f docker-compose.dev.yml up
You can visit the Gerbera UI via the exposed localhost:
You can run the UI Integration test manually:
/gerbera-ui/$ export HUB_HOST=localhost
/gerbera-ui/$ export HUB_PORT=4444
/gerbera-ui/$ export GERBERA_BASE_URL=http://<gerbera-core-IP-address>:49152
/gerbera-ui/$ export UI_TEST_DATA=default.json
/gerbera-ui/$ export SELENIUM_BROWSER=chrome
/gerbera-ui/$ npm run test
More development details are available in the development documentation
When testing the integration suite is may be necessary to download a different version of the source code.
The docker-compose
system uses the .env
file to inject the GIT commands used to checkout source code.
This allows a developer to point to a forked version of the code, or a specific branch.
- Open the
.env
file at the root of the project - Modify the
CORE_GIT_CMD
variable to change the source code path checkout for the gerbera-core container- Do this when you want to point to new Gerbera Media Server code
- Modify the
INT_GIT_CMD
variable to change the source code path checkout for the gerbera-ui or gerbera-upnp container- Do this when you want to point to new integration test code
NOTE Changing the
git commands
requires a rebuild of the containers.
See gerbera cli script for more details on how to cleanup old containers.