search

allure-framework / allure2

Allure Report is a flexible, lightweight multi-language test reporting tool. It provides clear graphical reports and allows everyone involved in the development process to extract the maximum of information from the everyday testing process
https://allurereport.org/
Apache License 2.0
4.08k stars 703 forks source link

Permalink testcases/{testName} #837

Open Fanch- opened 6 years ago

Fanch- commented 6 years ago

I'm submitting a ...

What is the current behavior?

Permalinks for allure dashboard are currently formed like this (ids) : https://demo.qameta.io/allure/#suites/bd5db97a62d5115f1a4b09738ac3c2b1/64cfd40c8b6df023/

What is the expected behavior?

Could it be possible to display it with full name instead ? https://demo.qameta.io/allure/#suites/AlwaysPassingTest/testFour

What is the motivation / use case for changing the behavior?

Same behaviour as junit jenkins plugin. Like that we could also use lastJob link and it's easier to send link in a clever way to other people.

Please tell us about your environment:

Allure version 2.2.0
Test framework junit@4.12
Generate report using allure-plugin
baev commented 6 years ago

The problem is that parameterised tests and test retries has the same full name. Also this solution is difficult to implement for nested groups (For example for TestNG we have suite > test > test class > test method grouping, so routing would be /#suites/TestNG suite/TestNg test/com.example.TestClass/testMethod)