allure-framework / allure-python

Allure integrations for Python test frameworks
https://allurereport.org/
Apache License 2.0
727 stars 237 forks source link

Package view for behave tests - The class label isn't displayed in the tree #789

Open harmin-parra opened 10 months ago

harmin-parra commented 10 months ago

[//]: # ( . Note: for support questions, please use Stackoverflow or Gitter. . This repository's issues are reserved for feature requests and bug reports. . . In case of any problems with Allure Jenkins plugin please use the following repository . to create an issue: https://github.com/jenkinsci/allure-plugin/issues . . Make sure you have a clear name for your issue. The name should start with a capital . letter and no dot is required in the end of the sentence. An example of good issue names: . . - The report is broken in IE11 . - Add an ability to disable default plugins . - Support emoji in test descriptions )

I'm submitting a ...

What is the current behavior?

The documentation says that it is posible to personalize the package, class and method of Behave tests in the Package view. https://allurereport.org/docs/behave/

The class label isn't displayed in the report.

image

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

Execute:

@allure.label.package:cucumber
Feature: Calculator

  @allure.label.testClass:Calculator
  @allure.label.testMethod:add()
  Scenario Outline: Addition
    Given I have a calculator
    When I add "<x>" and "<y>"
    Then the calculator returns "<sum>"

    Examples:
      |  x  |  y | sum |
      |  1  |  1 |  2  |
      |  2  |  1 |  3  |
      |  2  |  7 |  9  |

Generate the rapport

Open the Package view

Result: The class Calculator is not displayed in the tree

The actual tree is:

- cucumber
   - #3 add
   - #2 add
   - #1 add

What is the expected behavior?

The class Calculator is displayed in the tree

The expected tree is:

- cucumber
   - Calculator
      - #3 add
      - #2 add
      - #1 add

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

Please tell us about your environment:

Other information

[//]: # ( . e.g. detailed explanation, stacktraces, related issues, suggestions . how to fix, links for us to have more context, eg. Stackoverflow, Gitter etc )