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

how is the count for rows of test data calculated in the serenity report? #2765

Open
sudheer1437 opened this issue Apr 1, 2022 · 4 comments
Labels

Comments

@sudheer1437
Copy link

In the Serenity BDD report, under the overall test results tab, I am able to validate the test cases count but unable to confirm the including xx rows to test data count.

How is this count calculated?
image

@wakaleo
Copy link
Member

wakaleo commented Apr 1, 2022

The rows of test data include rows in scenario outlines or parameterised JUnit tests. See the "Key Statistics" section for more details:
image

@onlybiju
Copy link

onlybiju commented Apr 1, 2022

Hi @wakaleo ,
Is there any way in Summary.txt report if can get the "Number of scenarios"? Currently it doesn't show anywhere in Summary report

Serenity report generated 01-04-2022 03:30:51

Test Cases: 41 (including 82 rows of test data)
Passed: 37
Failed: 2
Failed with errors: 2
Compromised: 0
Pending: 0
Ignored: 0
Skipped: 0

@sudheer1437
Copy link
Author

Got it @wakaleo thank you

@wakaleo
Copy link
Member

wakaleo commented Apr 14, 2022

Hi @wakaleo ,

Is there any way in Summary.txt report if can get the "Number of scenarios"? Currently it doesn't show anywhere in Summary report

Serenity report generated 01-04-2022 03:30:51

Test Cases: 41 (including 82 rows of test data)

Passed: 37

Failed: 2

Failed with errors: 2

Compromised: 0

Pending: 0

Ignored: 0

Skipped: 0

Yes, the easiest way is to update the code to include this info and propose a pull request - the API is fairly self-explanatory.

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

No branches or pull requests

3 participants