Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing list of executed suites #389

Open
1 of 3 tasks
Ljancek opened this issue Jun 4, 2019 · 14 comments
Open
1 of 3 tasks

Missing list of executed suites #389

Ljancek opened this issue Jun 4, 2019 · 14 comments

Comments

@Ljancek
Copy link

Ljancek commented Jun 4, 2019

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?

Missing of executed tests in SIUTES on Overview page. Suites subtitles show correctly number of items, but missing list of executed suites.
Screenshot 2019-06-04 at 15 17 42

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

  1. Run tests
  2. Generate report

What is the expected behavior?

list of executed suites are displayed

Please tell us about your environment:

Allure version 2.12.1
Test framework [email protected]
Allure adaptor [email protected]
[email protected]

Other information

@Ljancek
Copy link
Author

Ljancek commented Jun 23, 2019

Hi, any update?

@sseliverstov
Copy link
Contributor

@Ljancek what is test-suites in behave?

@Ljancek
Copy link
Author

Ljancek commented Jun 26, 2019

@sseliverstov test-suit in behave is Scenario or Scenario outline

@sseliverstov
Copy link
Contributor

@Ljancek in my opinion

parent suite = path to feature file
suite = feature file
sub suite = scenario/scenario outline

is better.

my motivation is

  1. suites are representation of code layer
  2. avoid duplicating behavior with bdd labels

@Ljancek ?

@Ljancek
Copy link
Author

Ljancek commented Jun 27, 2019

@sseliverstov sounds good

@Ljancek
Copy link
Author

Ljancek commented Jul 13, 2019

Any update?

@Ljancek
Copy link
Author

Ljancek commented Aug 30, 2019

@sseliverstov Something news?

@Ljancek
Copy link
Author

Ljancek commented Feb 11, 2020

Any update? @sseliverstov

@leomenezessz
Copy link

Hi guys i have the exactly same issue, in my case i work with lot of different test teams and every team work with your own language and generate report with allure and then put it all together on the same allure server. For ruby and java the output of allure-results are the same, but in python dont have some keys like "package" and "suites".

In the listener file i change the labels array to add this keys :

test_case.labels.append(Label(name=LabelType.SUITE, value=scenario.feature.name)) test_case.labels.append(Label(name=LabelType.PACKAGE, value=scenario.feature.name))

And in the LabelTypes i add PACKAGE to the constants

This changes reproduces these results :

image

image

I running allure-behave tests locally and everything still working.

Make sense open this pull request ?

@Ljancek
Copy link
Author

Ljancek commented May 18, 2020

Any updates??

@leomenezessz
Copy link

I will open this pull request.

@jmfiaschi
Copy link

Hello ! Someone can unblock this issue ? :)

@leomenezessz
Copy link

@jmfiaschi and @Ljancek I reopened the pull request because previously I deleted the old fix branch.

@TurboCoder13
Copy link

Can this please be merged already?

Testing locally by applying the (literally) minor update as shown in the PR and I can confirm:

The scenarios (aka tests) are grouped under the feature (aka test suite).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants