allure-framework / allure-framework/allure2

Double '/' in URL when navigate to history result

Open
#1,762 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
5.5k
Forks
782
Avg merge
2d 33m
Merged PRs (30d)
16

Description

**Describe the bug**
Occures in TeamCity

**To Reproduce**
Steps to reproduce the behavior:
1. for TC configuration run open tab Allure Reports
2. Select any test
3. Open tab History for this test
4. Click on any history result for this test

**Expected behavior**
Web page opens and I can see history result

**Actual result**
The URL contains extra '/' before repository part. For example:
https://teamcity.mycompany.com//repository/download/AndroidVK_AndroidAutoTests_UiTestsStableRegressOnAvd/9260311:id/allure-report.zip!/allure-report/index.html?branch=develop/#testresult/eb3ac8ea616d60ea

If I remove this extra '/' everythig is working

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Environment (please complete the following information):**
Android kotlin autotests use following dependencies:
io.qameta.allure:allure-kotlin-commons:2.4.0
io.qameta.allure:allure-kotlin-junit4:2.4.0
io.qameta.allure:allure-kotlin-model:2.4.0
io.qameta.allure:allure-kotlin-android:2.4.0

| Allure version | 2.4.0 |
| --- | --- |
| Test framework | junit@4.13.2 |
| Allure adaptor | allure-kotlin-junit4@2.4.0 |
| Generate report using | Report is formed on TeamCity Enterprise 2022.04 (build 108502) |

Contributor guide

Open the contributing guide

Research direction

Reproduce the history-result navigation in TeamCity using the described Allure Kotlin setup, then trace where the history result URL is assembled. Done means the generated URL contains only one slash before the repository path and opens the history result without manual editing.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.