Skip to content

2 SubSuite defined while using dynamic definition (pytest) #586

@Shionigami

Description

@Shionigami

I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

I want to use allure to generate report, and especially write some data into the report dynamically.
We already did implementation for data like: feature, title, description, ... and it is working fine.
But, in the case of sub_suite, if it is NOT defined in the pytest script, with @allure.sub_suite('value1'), then it will add to the report a new subsuite, automatically with the name of the class.
Then, when I add the subsuite with allure.dynamic.sub_suite('value1'), I have in the same report:

  • {"name": "subSuite", "value": "className"}
  • {"name": "subSuite", "value": "value1"}

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

  • Do not define any subsuite in the pytest script. eg: @allure.sub_suite('value1')
  • While generating the allure report dynamically, use the function: allure.dynamic.sub_suite('value1')

What is the expected behavior?

Only 1 entry should be available in the allure report:
{"name": "subSuite", "value": "value1"}

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

Get data from a configuration file or document and define the data based on those files, dynamically.

Please tell us about your environment:

  • Allure version: 2.13.6
  • Test framework: pytest@5.0.1
  • Allure adaptor: allure-pytest@2.8.40

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions