-
Notifications
You must be signed in to change notification settings - Fork 48
Link configuration for reporter.testId and reporter.issue API's #158
Comments
And againg it is not about wdio-reporter :)
It is in allure docs. See https://docs.qameta.io/allure/#_links |
@BorisOsipov |
@baev can you assist? rigth now reporter just add |
You can create allure.issues.tracker.pattern: https://example.org/issue/%s
allure.tests.management.pattern: https://example.org/tms/%s Or you can use full links directly (providing label This is only applied for results in Allure 1 XML format. In new model we moved pattren resolution logic to adaptor side (it is easier for users to configure and in that case each result file can be processed individually that required for realtime reporting) |
@baev @BorisOsipov |
Yep, I agree. We are already working on new JS integrations https://github.com/allure-framework/allure-js/ |
Hey everybody!
I run into a little problem and I hope you can help me solve it.
FRAMEWORK:
WDIO
MOCHA
CHAI
WDIO-ALLURE-REPORTER
When I'm trying to assign test case ID (via reporter.testId(999)) or issue ID (via reporter.issue(111)) the reporter successfully adds corresponding information to Allure report. But when I click the link it navigates me to Allure server IP. Link looks like the folloing example:
http://10.11.12.123:24240/999 (for reporter.testId(999))
It it very clear for that there should be config property somewhere, intended to regulate this, but I didn't managed to find any information.
Please assist!
The text was updated successfully, but these errors were encountered: