Addressed issue #593 - Link TestResult to JUnit platform TestIdentifier

[naresha]

Context

Checklist

• Sign Allure CLA
• Provide unit tests

[baev]

We can't use uniqueId as testCaseId as it will break parameterised tests: uniqueId is differ for different parameters but testCaseId should be the same no matter what parameter values are provided.

So far Allure has:

• testCaseId (same for the same test cases, used in Allure TestOps to determinate test cases). If not specified, md5(fullName) is used.
• historyId (aka historyKey): used for determinate retries within a test run. In case of same historyId results are merged, and only the last one is shown. If not specified, calculated as md5(testCaseId, parameterValues, environment)

[naresha]

Thanks for sharing the details of testCaseId.
Do you have any suggestions on alternative ways to pass unique id?

[baev]

simply put it into labels, you can pick any key you like, for example JUNIT5_UNIQUE_ID

[naresha]

Thanks for your suggestion.

[baev]

@naresha thanks!