How to create a custom Allure step function for sensible data

[CarlosHernandezP]

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:

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:

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: [email protected]
• Allure adaptor: [email protected]

Other information

[ric79]

Hello, I use in my tests the Ansible way. All passwords are encrypted in my inventory in SHA256 with decode_pass.

Before starting the tests, just set an environment var (decode_pass).

During tests, the functions receive the encrypted vars and then they use os.environ["decode_pass"] in order to decrypt.

[CarlosHernandezP]

Even thought I did not use @ric79 specific answer it did give me the idea to use the cryptography library.

I created a new function for the sensible data that encrypts the strings and then, inside this new function I call the one I shared on the screenshot. This results in the following report:

Which solves my privacy issues. Thank you @ric79