allure-framework / allure-framework/allure-python

How to create a custom Allure step function for sensible data

Ouverte
#481 2 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
task:new feature theme:core
Langage dominant
Python
Étoiles
814
Forks
260
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

#### 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
)

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Commencez par examiner le décorateur de step et le chemin parcouru par ses arguments jusqu’au titre du rapport Allure. Vérifiez le comportement de l’adaptateur pytest décrit dans l’issue et déterminez comment un step personnalisé pourrait omettre ou masquer des valeurs sensibles telles que les mots de passe. La tâche est terminée lorsqu’un step personnalisé peut produire un rapport utile sans exposer son argument sensible.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
python
Domaine
testing
Type d'issue
Fonctionnalité
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.