ALLURE DOCKER SERVICE
[!IMPORTANT]
ANNOUNCEMENT
We are developing a new open-source version designed to resolve known issues and introduce significant enhancements related to UI, functionality, and data processing. While this transition will take time, we are prioritizing development to get a build ready for our testers as soon as possible.
Table of contents
- FEATURES
- USAGE
- Generate Allure Results
- ALLURE DOCKER SERVICE
- PORT 4040 Deprecated
- Known Issues
- Opening & Refreshing Report
- New User Interface
- Deploy using Kubernetes
- Extra options
- Allure API
- Send results through API
- Customize Executors Configuration
- API Response Less Verbose
- Switching version
- Switching port
- Updating seconds to check Allure Results
- Keep History and Trends
- Override User Container
- Start in DEV Mode
- Enable TLS
- Enable Security
- Multi-instance Setup
- Add Custom URL Prefix
- Optimize Storage
- Export Native Full Report
- Customize Emailable Report
- Allure Customized Plugins
- Allure Options
- SUPPORT
- DOCKER GENERATION (Usage for developers)
FEATURES
Allure Framework provides you good looking reports for automation testing. For using this tool is required to install a server. You could have this server running on Jenkins or if you want to see reports locally, you need to run some commands on your machine. This work results tedious, at least for me :)
For that reason, this docker container allows you to see up to date reports simply mounting your allure-results directory (for a Single Project) or your projects directory (for Multiple Projects). Every time appears new results (generated for your tests), Allure Docker Service will detect those changes and it will generate a new report automatically (optional: send results / generate report through API), what you will see refreshing your browser.
- Useful for developers who wants to run tests locally and want to see what were the problems during regressions.
- Useful for the team to check the tests status for every project.
Docker Hub
- Repository: frankescobar/allure-docker-service
Docker Versions
Docker container versions are based on binary Allure 2 releases
Image Variants
Allure Docker Service supports architectures amd64, arm32v7 and arm64v8.
The following table shows the variation of provided images.
| Base Image | Arch | OS |
|---|---|---|
| amd64/eclipse-temurin:11-jre-noble | amd64 | ubuntu |
| arm32v7/eclipse-temurin:11-jre-noble | armv7 | ubuntu |
| arm64/eclipse-temurin:11-jre-noble | arm64 | ubuntu |
The following table shows the provided Manifest Lists.
| Tag | allure-docker-service Base Image |
|---|---|
| latest, 2.44.0 | frankescobar/allure-docker-service:2.44.0-amd64 |
| frankescobar/allure-docker-service:2.44.0-armv7 | |
| frankescobar/allure-docker-service:2.44.0-arm64 |
USAGE
Generate Allure Results
First at all it's important to be clear. This container only generates reports based on results. You have to generate allure results according to the technology what are you using.
Reference: https://github.com/fescobar/allure-docker-service-examples
We have some examples projects:
- allure-docker-java-testng-example
- allure-docker-java-junit4-example
- allure-docker-java-cucumber-jvm-example
- allure-docker-nodejs-cucumber-example
- allure-docker-nodejs-typescript-cucumber-example
- allure-docker-nodejs-typescript-mocha-example
- allure-docker-python-behave-example
- allure-docker-python-pytest-example
- AllureDockerCSharpExample
- AllureDockerCSharpSpecFlow3Example
In this case we are going to generate results using the java project allure-docker-java-testng-example of this repository.
Go to directory allure-docker-java-testng-example via command line:
cd allure

