first use - Githubissues

Jean-Baptiste-Lasselle commented 3 years ago

HEre below how to :

install allure (one executable, with folders with plugins in)
generate an allure report, from a folder containing all the test results (so the tests results can go into an s3 bucket)
generate 3 different allure reports, for the same project, in a fixed folder path for each report
open one of the 3 existing allure reports

jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ # ./allure-2.13.9/bin/allure generate ./jbl-allure-results/ -o
jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ mkdir -p jbl/project1/report1
jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ mkdir -p jbl/project1/report2
jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ mkdir -p jbl/project1/report3
jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ ./allure-2.13.9/bin/allure generate ./jbl-allure-results/ -o jbl/project1/report1
Report successfully generated to jbl/project1/report1
jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ ./allure-2.13.9/bin/allure generate ./jbl-allure-results/ -o jbl/project1/report2
Report successfully generated to jbl/project1/report2
jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ ./allure-2.13.9/bin/allure generate ./jbl-allure-results/ -o jbl/project1/report3
Report successfully generated to jbl/project1/report3
jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ ./allure-2.13.9/bin/allure open jbl/project1/report3 jbl
jbl/                jbl-allure-results/
jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ ./allure-2.13.9/bin/allure open jbl/project1/report3 jbl/project1/report2
Only one main argument is allowed
jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ ./allure-2.13.9/bin/allure open jbl/project1/report3
Starting web server...
2021-04-16 17:19:47.093:INFO::main: Logging initialized @270ms to org.eclipse.jetty.util.log.StdErrLog
Server started at <http://127.0.1.1:34265/>. Press <Ctrl+C> to exit
^Cjibl@poste-devops-jbl-16gbram:~/someops/qamteio
jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ # wget https://github.com/allure-framework/allure2/releases/download/2.13.9/allure-2.13.9.zip
jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ # unzip allure-2.13.9.zip
jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ tree jbl/
jbl/
└── project1
    ├── report1
    │   ├── app.js
    │   ├── data
    │   │   ├── attachments
    │   │   ├── behaviors.csv
    │   │   ├── behaviors.json
    │   │   ├── categories.csv
    │   │   ├── categories.json
    │   │   ├── packages.json
    │   │   ├── suites.csv
    │   │   ├── suites.json
    │   │   ├── test-cases
    │   │   └── timeline.json
    │   ├── export
    │   │   ├── influxDbData.txt
    │   │   ├── mail.html
    │   │   └── prometheusData.txt
    │   ├── favicon.ico
    │   ├── history
    │   │   ├── categories-trend.json
    │   │   ├── duration-trend.json
    │   │   ├── history.json
    │   │   ├── history-trend.json
    │   │   └── retry-trend.json
    │   ├── index.html
    │   ├── plugins
    │   │   ├── behaviors
    │   │   │   └── index.js
    │   │   ├── jira
    │   │   ├── junit
    │   │   ├── packages
    │   │   │   └── index.js
    │   │   ├── screen-diff
    │   │   │   ├── index.js
    │   │   │   └── styles.css
    │   │   ├── trx
    │   │   ├── xctest
    │   │   ├── xray
    │   │   └── xunit-xml
    │   ├── styles.css
    │   └── widgets
    │       ├── behaviors.json
    │       ├── categories.json
    │       ├── categories-trend.json
    │       ├── duration.json
    │       ├── duration-trend.json
    │       ├── environment.json
    │       ├── executors.json
    │       ├── history-trend.json
    │       ├── launch.json
    │       ├── retry-trend.json
    │       ├── severity.json
    │       ├── status-chart.json
    │       ├── suites.json
    │       └── summary.json
    ├── report2
    │   ├── app.js
    │   ├── data
    │   │   ├── attachments
    │   │   ├── behaviors.csv
    │   │   ├── behaviors.json
    │   │   ├── categories.csv
    │   │   ├── categories.json
    │   │   ├── packages.json
    │   │   ├── suites.csv
    │   │   ├── suites.json
    │   │   ├── test-cases
    │   │   └── timeline.json
    │   ├── export
    │   │   ├── influxDbData.txt
    │   │   ├── mail.html
    │   │   └── prometheusData.txt
    │   ├── favicon.ico
    │   ├── history
    │   │   ├── categories-trend.json
    │   │   ├── duration-trend.json
    │   │   ├── history.json
    │   │   ├── history-trend.json
    │   │   └── retry-trend.json
    │   ├── index.html
    │   ├── plugins
    │   │   ├── behaviors
    │   │   │   └── index.js
    │   │   ├── jira
    │   │   ├── junit
    │   │   ├── packages
    │   │   │   └── index.js
    │   │   ├── screen-diff
    │   │   │   ├── index.js
    │   │   │   └── styles.css
    │   │   ├── trx
    │   │   ├── xctest
    │   │   ├── xray
    │   │   └── xunit-xml
    │   ├── styles.css
    │   └── widgets
    │       ├── behaviors.json
    │       ├── categories.json
    │       ├── categories-trend.json
    │       ├── duration.json
    │       ├── duration-trend.json
    │       ├── environment.json
    │       ├── executors.json
    │       ├── history-trend.json
    │       ├── launch.json
    │       ├── retry-trend.json
    │       ├── severity.json
    │       ├── status-chart.json
    │       ├── suites.json
    │       └── summary.json
    └── report3
        ├── app.js
        ├── data
        │   ├── attachments
        │   ├── behaviors.csv
        │   ├── behaviors.json
        │   ├── categories.csv
        │   ├── categories.json
        │   ├── packages.json
        │   ├── suites.csv
        │   ├── suites.json
        │   ├── test-cases
        │   └── timeline.json
        ├── export
        │   ├── influxDbData.txt
        │   ├── mail.html
        │   └── prometheusData.txt
        ├── favicon.ico
        ├── history
        │   ├── categories-trend.json
        │   ├── duration-trend.json
        │   ├── history.json
        │   ├── history-trend.json
        │   └── retry-trend.json
        ├── index.html
        ├── plugins
        │   ├── behaviors
        │   │   └── index.js
        │   ├── jira
        │   ├── junit
        │   ├── packages
        │   │   └── index.js
        │   ├── screen-diff
        │   │   ├── index.js
        │   │   └── styles.css
        │   ├── trx
        │   ├── xctest
        │   ├── xray
        │   └── xunit-xml
        ├── styles.css
        └── widgets
            ├── behaviors.json
            ├── categories.json
            ├── categories-trend.json
            ├── duration.json
            ├── duration-trend.json
            ├── environment.json
            ├── executors.json
            ├── history-trend.json
            ├── launch.json
            ├── retry-trend.json
            ├── severity.json
            ├── status-chart.json
            ├── suites.json
            └── summary.json

52 directories, 114 files

and to serve all the allure reports, of all projects, at the same time :

jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ sudo npm i -g serve
[sudo] password for jibl: 

added 78 packages, and audited 79 packages in 11s

1 package is looking for funding
  run `npm fund` for details

found 0 vulnerabilities
npm notice 
npm notice New minor version of npm available! 7.7.4 -> 7.10.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v7.10.0
npm notice Run npm install -g npm@7.10.0 to update!
npm notice 
jbl@poste-devops-jbl-16gbram:~/someops/qamteio$ serve jbl
jbl/                jbl-allure-results/ 
jibl@poste-devops-jbl-16gbram:~/someops/qamteio$ serve jbl/

   ┌───────────────────────────────────────────────────┐
   │                                                   │
   │   Serving!                                        │
   │                                                   │
   │   - Local:            http://localhost:5000       │
   │   - On Your Network:  http://192.168.1.103:5000   │
   │                                                   │
   │   Copied local address to clipboard!              │
   │                                                   │
   └───────────────────────────────────────────────────┘

So on the one hand, allure executable generates the reports, they are sync to an S3, and in one container, the serve http server serves all the folders (jsut see how to customize the design of the page displaying folders =>

Jean-Baptiste-Lasselle commented 3 years ago

https://github.com/fescobar/allure-docker-service-ui

https://github.com/fescobar/allure-docker-service-examples

https://github.com/fescobar/allure-docker-service

Jean-Baptiste-Lasselle commented 3 years ago

https://github.com/pharindoko/json-serverless => case remplacer aws api gateway par gravitee

Jean-Baptiste-Lasselle commented 3 years ago

https://github.com/Ebazhanov/cypress-allure2-report-example

Jean-Baptiste-Lasselle commented 3 years ago

https://github.com/google/dana

Jean-Baptiste-Lasselle commented 3 years ago

allure selenoid poc https://www.youtube.com/watch?v=8wcu9Osbcag

Jean-Baptiste-Lasselle commented 3 years ago

https://github.com/MicrosoftDX/Vorlonjs

Jean-Baptiste-Lasselle commented 3 years ago

https://www.youtube.com/watch?v=JY3_cBdjFws

https://github.com/romsper/qa-automation-base

https://medium.com/swlh/feed-prometheus-with-locust-performance-tests-as-a-metrics-source-d8d2bfec918c

https://grafana.com/blog/2018/11/29/pro-tips-using-grafana-in-quality-assurance/

Prometheus exprorters

https://github.com/hudeldudel/postman-exporter

maybe an Allure Prometheus exporter on the allure small app that generates the reprts...? no too much data into one report ?

https://github.com/dmeiners88/sonarqube-prometheus-exporter

https://github.com/andreidan/prometheus-gatling-exporter

thing is it is more like :

sending tests results to a storage, label them witth infos :
- gtit commit id of the tested source code, git branch name, pull request number, git repo URL
- datetime of the test execution (start datetime, end datetime)
- name and version of the product (if it is apim, then the product is made fom severa git repos, so it's not just one) so to identify the product, one could identi with the git commit id from the gitops git repo....and the version of the product is just a data inferd from that gti commit id...

allure still useful for cypress tests...

Jean-Baptiste-Lasselle commented 3 years ago

https://www.youtube.com/watch?v=JY3_cBdjFws

Jean-Baptiste-Lasselle commented 3 years ago

https://restqa.io/#/ : not enpough at all for gravitee top level metrics dashboard, but this project can become a friend of Gravitee

Jean-Baptiste-Lasselle commented 3 years ago

quick try on https://github.com/kiwitcms/Kiwi :

seems they have years of existence (experience ?)
bad here : there's a docker compose, and as soon as you start it, there's an issue about setting the fully qualified domain name...
entreprise offer is just a joke : https://kiwitcms.org/features/
quick look at the feature it's just really too narrow : eg they give features on a per test frameworks basis like test anything protocol , robot framework etc... and there the list is so narrow https://kiwitcms.org/features/
they have lived for more than ten years and given where they are today we cannot expect any big evolution in th enear future.
conclusion : byebye

Jean-Baptiste-Lasselle / allure-test-reporting

first use #1

Prometheus exprorters