-
Notifications
You must be signed in to change notification settings - Fork 523
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
[Feature Request]: Create means for verifying Fragment Arguments #5485
Comments
Ho @adhiamboperes , can i work on this ? |
Hi, sure, please look into it and let us know your proposed solution.
…On Sat, Aug 17, 2024, 08:41 Subhajit Mallick ***@***.***> wrote:
Ho @adhiamboperes <https://github.com/adhiamboperes> , can i work on this
?
—
Reply to this email directly, view it on GitHub
<#5485 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOGXANFS4L3FQWNLEB4RYL3ZR3O77AVCNFSM6AAAAABMQAN5M6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUGYZTONRZGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sure. |
Hi @adhiamboperes , please check my approach and share your views on it.
|
Hi @subhajitxyz, the approach does look good. For the implementation, please opt to create a PR with only a small subset of packages at once, rather than all the fragment tests in one PR. For example, we have about 30 packages, so we could do this in 3 different PRs for ease of review. |
Ok, fine. |
Hi @adhiamboperes , So ,I have changed my approach little bit . try to recreate the scenario instead of activity. please check it and share your views. Here is my new approach.
|
<!-- READ ME FIRST: Please fill in the explanation section below and check off every point from the Essential Checklist! --> ## Explanation Fixes #5485 Added test for 10 fragments arguments and saveInstanceState. ## 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: ...".) - [ ] 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 --------- Co-authored-by: Mr. 17 <[email protected]>
Is your feature request related to a problem? Please describe.
We use Espresso
Intents.Intended
to verify activity intent params, but we also need to test the fragment arguments and saved state bundles for correcteness, and to prevent bugs during development.Describe the solution you'd like
// TODO
Describe alternatives you've considered
// TODO
Additional context
No response
The text was updated successfully, but these errors were encountered: