allure-framework / allure-framework/allure-python

How to create a custom Allure step function for sensible data

Abierto
#481 2 comentarios 0 reacciones 0 asignados Ver en GitHub
task:new feature theme:core
Lenguaje dominante
Python
Estrellas
814
Forks
260
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

#### I'm submitting a ...
- [ ] bug report
- [x] feature request
- [ ] support request => Please do not submit support request here, see note at the top of this template.

#### What is the current behavior?
With a step decorator like this:
![imagen](https://user-images.githubusercontent.com/26765591/77885990-59624880-7268-11ea-9bd6-96906efd1518.png)

Which takes an element (a text box) and enters the value in it. In the step function I display the value that I want to enter No matter what I enter on the step title, the report always shows the info that was passed as arguments to the function.

My report looks like the following image:
![imagen](https://user-images.githubusercontent.com/26765591/77886155-a34b2e80-7268-11ea-9c12-bef4e7382fdf.png)

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

#### What is the expected behavior?
Thus, the "value" argument will always be displayed and that is something that I cannot have on certain projects. I could either use with not showing the value at all or to change it to something like '*****'. Is there anyway to make a custom step function that solves my problem?.

#### What is the motivation / use case for changing the behavior?
I am currently working on a Testing Automation team, using Python and Allure to make reports of all the test cases that we run. Sometimes we deal with sensible data (e.g: passwords) that I can't show directly on the reports due to data protection policies.

#### Please tell us about your environment:

- Allure version: 2.13.0
- Test framework: pytest@3.6.1
- Allure adaptor: pytest-allure-adaptor@1.7.10

#### Other information

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

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza revisando el decorador de step y el recorrido desde sus argumentos hasta el título del informe de Allure. Comprueba el comportamiento del adaptador de pytest descrito en el issue y determina cómo un step personalizado podría omitir o enmascarar valores sensibles, como las contraseñas. Se considera terminado cuando un step personalizado puede generar un informe útil sin exponer su argumento sensible.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
python
Área
testing
Tipo de issue
Nueva funcionalidad
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.