mozilla-mobile / mozilla-mobile/testops-dashboard
Investigate data in report_test_coverage_by_project_prod
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 7
- Avg merge
- 24m
- Merged PRs (30d)
- 2
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the TestRail report with the highlighted rows in the database spreadsheet for report_test_coverage_by_project_prod. Trace how the green Smoke-suite rows enter the report and are summed with the yellow rows. Done means the source of the extra untriaged tests is identified and the report numbers match the expected TestRail data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100