-
Notifications
You must be signed in to change notification settings - Fork 5
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
Comments
Hi @isabelrios , As discussed on Slack there should not be any "Untriaged" test in our Smoke and Sanity test suite.
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.
Please share your thoughts. |
yeah, that makes sense to understand why the numbers are wrong in looker. |
As a possible solution to prevent this error from happening in the future, we could add the |
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.
The text was updated successfully, but these errors were encountered: