Skip to content

Testing Strategy for GAE Abstraction [Blocked #76] #77

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.

Sign up for GitHub

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

Jump to bottom
Closed
rt4914 opened this issue Aug 27, 2019 · 0 comments · Fixed by #5806
Closed

Testing Strategy for GAE Abstraction [Blocked #76] #77

rt4914 opened this issue Aug 27, 2019 · 0 comments · Fixed by #5806
Assignees
@BenHenning
Labels
enhancement End user-perceivable enhancements. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. Z-ibt Temporary label for Ben to keep track of issues he's triaged.

Comments

@rt4914
Copy link
Contributor

rt4914 commented Aug 27, 2019

Implement the testing strategy for all the retrofit interfaces.
Fake versions of each retrofit interface will be introduced which can check the corresponding interface. Fakes should be able to check the retrypolicy, XSSI_PREFIX removal and correct deserialisation of response.
This is blocked on #5 , #76
@rt4914 rt4914 added Priority: Important This work item is really important to complete for its milestone, but it can be scoped out. Status: Blocked labels Aug 27, 2019
@rt4914 rt4914 added this to the Prototype milestone Aug 27, 2019
@BenHenning BenHenning changed the title Testing Strategy for GAE Abstraction [Blocked #5, #76] Testing Strategy for GAE Abstraction [Blocked #76] Sep 17, 2019
@BenHenning BenHenning self-assigned this Oct 7, 2019
@BenHenning BenHenning mentioned this issue Dec 6, 2019
Merged
8 tasks
@BenHenning BenHenning added Priority: Essential This work item must be completed for its milestone. and removed Workstream: Misc Infra Priority: Important This work item is really important to complete for its milestone, but it can be scoped out. labels Jun 23, 2020
@BenHenning BenHenning modified the milestones: Alpha, Beta Jul 8, 2020
@Broppia Broppia added issue_type_infrastructure Impact: Low Low perceived user impact (e.g. edge cases). labels Jul 24, 2022
@BenHenning BenHenning added Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Z-ibt Temporary label for Ben to keep track of issues he's triaged. issue_user_developer and removed Impact: Low Low perceived user impact (e.g. edge cases). labels Sep 15, 2022
@BenHenning BenHenning removed this from the Beta milestone Sep 16, 2022
@seanlip seanlip added bug End user-perceivable behaviors which are not desirable. enhancement End user-perceivable enhancements. and removed issue_type_infrastructure bug End user-perceivable behaviors which are not desirable. labels Mar 28, 2023
@adhiamboperes adhiamboperes added Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. and removed Priority: Essential This work item must be completed for its milestone. labels Jul 31, 2023
@BenHenning BenHenning mentioned this issue Apr 5, 2025
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BenHenning BenHenning

Labels
enhancement End user-perceivable enhancements. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. Z-ibt Temporary label for Ben to keep track of issues he's triaged.
Projects
[Team] Core Learner and Mastery flows & UI Frontend - Android
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix #77, part of #59: Revise testability of Retrofit services oppia/oppia-android
5 participants
@rt4914 @seanlip @BenHenning @adhiamboperes @Broppia