Question: (playwright-qase-reporter) - Set step data and expected result via reporter

[RichWattieCera]

Hi, is it possible to set data values and the expected result for steps via code, and then during a test run, updates the test in Qase via the reporter?

[gibiw]

@RichWattieCera Hello! The reporter doesn't support this functionality.

[RichWattieCera]

Thanks for responding. Could this be a possible feature request or is it something that's already been discussed?

[gibiw]

You are the first to request this functionality. Can you describe your case in more detail? What problem do you want to solve?

[RichWattieCera]

I like the fact that I can essentially have my playwright code as a source of truth. So that if the application under test changes, I need to update a test and I only have to do that in one place. Then once running the tests it will update the test steps in Qase. Rather than me having to go and update that manually as well.

Use Case...
I have manually set "Data" and/or "Expected Result" values for test steps in Qase.
I have Qase automation configured so that the report updates my test steps.
These properties get deleted when the test runs.
I now have to add that data back into Qase.
It would be handy to be able to set these properties in the code for each/any test step.

[ZeylanEmir]

I want to inform you that the above thoughts of the authors are true, in qasefor playwright or cypress or any other testing framework it would be useful to have a function similar to the function in python: where you can write qase.step(1, "passed") or something similar that would indicate that this particular step has been passed or not Since it is inconvenient for many manual testers to read the test results, where either the first 1-2 steps are marked as "passed" and the rest are either "skipped" or "unmarked", and this causes certain inconveniences.