allure-framework / allure-framework/allure-python

use loguru's stderr or stdout cant generate log in allure report

Aperta
#820 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Python
Stelle
814
Fork
260
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

[//]: # (
. Note: for support questions, please use Stackoverflow or Gitter**.
. This repository's issues are reserved for feature requests and bug reports.
.
. In case of any problems with Allure Jenkins plugin** please use the following repository
. to create an issue: https://github.com/jenkinsci/allure-plugin/issues
.
. Make sure you have a clear name for your issue. The name should start with a capital
. letter and no dot is required in the end of the sentence. An example of good issue names:
.
. - The report is broken in IE11
. - Add an ability to disable default plugins
. - Support emoji in test descriptions
)

#### I'm submitting a ...
- [ ] bug report

#### What is the current behavior?
i use loguru to generate log in api testing, but allure cant capture log by loguru code
so i search solution for this problem, and i use stderr instead of stdout, but problem cant solve
BUT logging can generate log in allure report, the search result say it use stderr to output log!

#### If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

#### What is the expected behavior?
allure can capture the loguru log in testing

#### What is the motivation / use case for changing the behavior?

#### Please tell us about your environment:

- Allure version: 2.25.0
- Test framework: pytest 8.1.1
- Allure adaptor: allure-pytest 2.13.5

#### Other information

[//]: # (
. e.g. detailed explanation, stacktraces, related issues, suggestions
. how to fix, links for us to have more context, eg. Stackoverflow, Gitter etc
)

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Inizia riproducendo il caso di generazione del report con loguru sotto pytest usando allure-pytest 2.13.5 e Allure 2.25.0, confrontando stdout, stderr e il logging standard. L'issue non indica file né fornisce una demo minima, quindi isola innanzitutto il test fallimentare più piccolo; il lavoro è completato quando l'output di loguru appare nel report Allure generato.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
python
Ambito
testing
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.