-
Notifications
You must be signed in to change notification settings - Fork 521
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix part of #5343: Enable Code Coverage Analysis for many to one test…
… target files (#5459) <!-- READ ME FIRST: Please fill in the explanation section below and check off every point from the Essential Checklist! --> ## Explanation <!-- - Explain what your PR does. If this PR fixes an existing bug, please include - "Fixes #bugnum:" in the explanation so that GitHub can auto-close the issue - when this PR is merged. --> Fixes part of #5343 ### Project [PR 2.1 of Project 4.1] ### Changes Made - Enabling code coverage analysis for many-to-one relationship test target files by aggregating the coverage reports of each related test target into a single report using the `calculateAggregateCoverageReport()` function. - Using the calculated aggregated coverage report to generate Markdown and HTML files. - Properly re-implemented the asynchronous flow as previous implementation though has async calls was still handling it sequentially as targets are provided one by one and made to wait until the coverage report is generated and the previous one is returned back. **Working test asynchronous flow screenshot** With static test targets provided: 2ac7b04 ![image](https://github.com/oppia/oppia-android/assets/122200035/295cfd9d-7c3a-4784-ba51-a1e8241dccbd) **Low impact changes:** Not related to the current PR implementation but added few fixes along with it, - Restyled the HTML report slightly since the previous version appeared somewhat vague and empty 😶🌫️. - Renamed sample test name from `TwoSum` to `AddNums`, felt more appropriate and clear. ### Note I couldn't find any actual working app module file with both shared and local tests to fully test this. Instead, I mocked the behavior with a sample coverage report and tested it with test cases, assuming that both tests for the same source file would have identical **line_number**, **lines_hit**, and **lines_found** data. ___ ### Screenshot of current HTML report ![Screenshot (1460)](https://github.com/oppia/oppia-android/assets/122200035/922a6228-1685-4463-8d64-6d162d5d1e59) **Responsive layouts** ![zero contributions (48)](https://github.com/oppia/oppia-android/assets/122200035/626e08eb-eeec-446b-b54c-46dd6aa5eaf8) ## Essential Checklist <!-- Please tick the relevant boxes by putting an "x" in them. --> - [x] The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".) - [x] Any changes to [scripts/assets](https://github.com/oppia/oppia-android/tree/develop/scripts/assets) files have their rationale included in the PR explanation. - [x] The PR follows the [style guide](https://github.com/oppia/oppia-android/wiki/Coding-style-guide). - [x] The PR does not contain any unnecessary code changes from Android Studio ([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#undo-unnecessary-changes)). - [x] The PR is made from a branch that's **not** called "develop" and is up-to-date with "develop". - [x] The PR is **assigned** to the appropriate reviewers ([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section)). ## For UI-specific PRs only <!-- Delete these section if this PR does not include UI-related changes. --> If your PR includes UI-related changes, then: - Add screenshots for portrait/landscape for both a tablet & phone of the before & after UI changes - For the screenshots above, include both English and pseudo-localized (RTL) screenshots (see [RTL guide](https://github.com/oppia/oppia-android/wiki/RTL-Guidelines)) - Add a video showing the full UX flow with a screen reader enabled (see [accessibility guide](https://github.com/oppia/oppia-android/wiki/Accessibility-A11y-Guide)) - For PRs introducing new UI elements or color changes, both light and dark mode screenshots must be included - Add a screenshot demonstrating that you ran affected Espresso tests locally & that they're passing
- Loading branch information
Showing
9 changed files
with
624 additions
and
240 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.