Property support for test cases

[dennisgrck]

This PR adds optional support for properties on a test case level as discussed in #183. This allows developers & testers to include additional metadata and properties that are then displayed by various CI and testing tools. It uses the exact format as already supported by many tools. Summary of this PR:

• Fully backwards compatible: if no properties are specified, nothing is output (no need for additional options)
• It uses the same API style as the existing this.test.attachments and this.test.consoleOutputs APIs
• It uses the standard <property> format as used for <testsuite>, and works the same as other frameworks with test case property support (such as Pytest and Playwright)
• This is intentionally a small code change only so it is easy to review and merge
• I've tested this with various other tools to make sure it works well in various scenarios

[anna-mkrtchyan-vertex]

This is exactly what is needed to import Cypress Junit XML reports to Xray and map Cypress test cases to existing Xray test cases. As Xray documentation suggests we need to have 'test_key' property on testcase element in our XML report. It can be easily done by using the functionality included in this PR.

Any news on when can we expect to have this merged?

[debo07]

@clayreimann Is there any way this can be reviewed and merged to the repo? I am also stuck with the same issue which is mentioned by @anna-mkrtchyan-vertex, where I want to import Cypress Junit XML reports to Xray and map Cypress test cases to existing Xray test cases.
Thanks in advance!

[debo07]

I tried this patch for my cypress tests, it didn't work for me. Maybe some tweaks will be required.

However when I tried the patch from #153, it worked out pretty well for me.
If you are a cypress users, you can try this out.

[clayreimann]

@dennisgrck Sorry for the long delay on this. Could you rebase this PR on master (and/or allow edits from collaborators so I can do it)?

[cheuk0324]

is there update on this PR? Thanks

[nmazzon]

news about this PR ? Thanks

[Andarist]

@dennisgrck do u plan to continue working on this? if not I could pull those commits into my fork, rebase it, and do whatever would be necessary to move forward with this

[ivanbesida-sage]

@clayreimann @michaelleeallen could you push that PR forward? Maybe create with same cahnges by your own. I am one of the interested person to have it in merged.

@dennisgrck maybe you can do that?

@dennisgrck Sorry for the long delay on this. Could you rebase this PR on master (and/or allow edits from collaborators so I can do it)?

[N1kbes]

Raised duplicate with edit access to have that code merged #211