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

Investigate data in report_test_coverage_by_project_prod #27

Open
isabelrios opened this issue Sep 5, 2022 · 3 comments
Open

Investigate data in report_test_coverage_by_project_prod #27

isabelrios opened this issue Sep 5, 2022 · 3 comments

Comments

@isabelrios
Copy link
Collaborator

The graphs for report_test_coverage_by_project_prod view show that there are untriaged tests for Fenix.
Andi raised the flag since running the report on Test Rail there are no untriaged tests for Full Functional or Smoke test suites.

This is the report in Test Rail:
testrail-report-5779.pdf

This is the data from the Data Base:
https://docs.google.com/spreadsheets/d/15sWdruOkRIo9Anhcbk7dvSXkki24XMaZWXeNEMQ37DU/edit?usp=sharing

In yellow I have highlighted the same data we see on Test Rail, but there is more for the same day Smoke test and untriaged, highlighted in green, and those are being sum up, given the incorrect numbers.
We need to understand why those in green appear and why they are added.

@AndiAJ
Copy link

AndiAJ commented Sep 6, 2022

Hi @isabelrios ,

As discussed on Slack there should not be any "Untriaged" test in our Smoke and Sanity test suite.

  • Both the test rail report and the numbers (highlighted in 🟠 ) retrieved from the data base are correct. ✅

image
image

I've made a quick check and I think I've found root cause because of which there are extra values (highlighted in 🟢 ) retrieved from the data base in regards with our smoke test suite.

  • Those numbers look like they are from our "Features" test suite. Test Rail report

image
image

Please share your thoughts.

@isabelrios
Copy link
Collaborator Author

yeah, that makes sense to understand why the numbers are wrong in looker.
In order to fix it, not sure if we can remove the smoke from those tests, or if those are actually part of the smoke test if they should be part of the full functional... not sure about the solution yet...
Please if you don't mind share your ideas as you are more familiar with the tests :)

@isabelrios
Copy link
Collaborator Author

As a possible solution to prevent this error from happening in the future, we could add the testrail_test_suites_id for each project, that's going to identify the Full Functional test suite which is the one we want specific data for now. Unless the test suite is removed and recreated, that ID is not going to change. If that happens, we should know as that's a big change.
Wdyt @AndiAJ @rpappalax ?

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

No branches or pull requests

2 participants