Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

WebdriverIO Version

8.20.0

Node.js Version

v18.13.0

Mode

WDIO Testrunner

Which capabilities are you using?

No response

What happened?

I updated from a pretty old setup
"@wdio/allure-reporter": "^7.16.10",
"webdriverio": "^7.20.5"
which used aoutdated xml format for allure results

up to
"webdriverio": "^8.20.0",
"@wdio/allure-reporter": "^8.20.0",
which produces json results

with the update test ops lost ability to assign test results to test-cases.
I found out that allure testOps unlike allure report uses different unique ID to assign cases
testCaseId - test ops, historyId - report
https://allurereport.org/docs/how-it-works/test-result-file/#historyid-string - both can be found in docs here

adding testCaseId to the result.json file manually before upload to testOps solves the problem

What is your expected behavior?

allure report should have both historyId and testCaseId which can be generated at the same time, since they use pretty much the same structure.

testCaseId = md5(fullName, sort(names(parameters)) // see https://help.qameta.io/support/solutions/articles/101000480600-cooking-the-allureid

which is exactly how historyId is generated now
https://github.com/webdriverio/webdriverio/blob/main/packages/wdio-allure-reporter/src/utils.ts#L189

How to reproduce the bug.

upload these files to testOps
noTestCaseId-result.json
withTestCaseId-result.json
second file has historyId added as testCase Id
"testCaseId":"f6edc25502e8c60dcadb37f34b9efc73", "historyId":"f6edc25502e8c60dcadb37f34b9efc73"

Relevant log output

nothing to share here

Code of Conduct

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues