allure-framework / allure-framework/allure-java

Add property to support the restriction for the Steps length in the report

Aperta
#490 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Java
Stelle
376
Fork
240
Merge medio
1g 7h
PR unite (30g)
45

Descrizione

#### I'm submitting a ...
- [x] feature request

Add a property to support the restriction for the Steps length in the report, for example,
`allure.max.title.length' as was in Allure 1.

#### What is the current behavior?
Property `allure.max.title.length` is ignored.

#### What is the expected behavior?
When `allure.max.title.length=1000` is added in `allure.property` file, the logged steps in the Allure report should be cut after 1000 symbols.

#### What is the motivation / use case for changing the behavior?
Sometimes, very big values are passed to methods annotated with @Step annotation, and there is no obvious way to restrict the number of characters to be printed in the report.
For example, if 'allure-assertj' is used, and the JSON objects to be compared are large, there is no way to restrict how they are displayed in the report.
On the following sample screenshot there are more than 2000 characters:
![image](https://user-images.githubusercontent.com/13782827/98965363-a272be80-2512-11eb-9b9f-e2a0bf8c691e.png)
and this is just about 1/3 of the whole JSON object. And all its characters are displayed in the step.

#### Additional information
The issue was discussed here https://github.com/allure-framework/allure2/issues/1150

| Allure version | 2.13.5 |
| --- | --- |
| Test framework | testng@6.9.10 |
| Allure integration | allure-testng@2.13.5 |
| Generate report using | allure-maven@2.9 |

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Inizia individuando come vengono gestiti la proprietà allure.max.title.length e i valori di @Step quando vengono generati i passaggi del report. Implementa il limite richiesto in modo che il testo del passaggio registrato venga troncato al numero configurato di caratteri, quindi verifica che un valore come 1000 modifichi l'output del report generato.

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

Valutazione

Stack tecnologico
java
Ambito
testing-qa
Tipo di issue
Funzionalità
Difficoltà
3/5
Tempo stimato
1-2 giorni
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
45/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.