Closed
Bug 892099
Opened 11 years ago
Closed 11 years ago
[QA] Need to identify testing required for payments on known OS version, w/ new device
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cgalimidi, Assigned: krupa.mozbugs)
References
Details
We will be coming to market with a new device for - Tricycle - Moss - Seville - Seahorse https://mana.mozilla.org/wiki/display/MARKET/Code+Names+for+Carrier-Region+Launches V1.1, Familiar Regions New Device What testing do we have to schedule and conduct, outside of normal regression testing, to ensure this launch for payments?
Reporter | ||
Comment 1•11 years ago
|
||
Looking to understand, in these regions, what (if anything) we need to do to re-test these regions because of a change in device
Summary: [QA] Need to understand testing required. v1.1, new device → [QA] Need to identify testing required for payments on v1.1, w/ new device
Updated•11 years ago
|
Assignee: nobody → krupa.mozbugs
Priority: -- → P2
Reporter | ||
Comment 2•11 years ago
|
||
FYI - Timeline: in stores in October w/ new device
Updated•11 years ago
|
Version: 1.5 → 1.3
Reporter | ||
Comment 3•11 years ago
|
||
hey there team - looking for an engineering assessment on how a new device could cause bugs in the payments flow. supports our ask for access to new devices for testing. what kind of bugs can arise in payments from simply swapping out hardware on a known OS version? make sense? let me know if not and i'll try to be more clear. i'd rather resolve it in-bug than in-meeting.
Summary: [QA] Need to identify testing required for payments on v1.1, w/ new device → [QA] Need to identify testing required for payments on known OS version, w/ new device
Assignee | ||
Comment 4•11 years ago
|
||
I do not think we need in-depth payments testing for every new device which goes live in existing markets (it won't scale and is for the most part unnecessary) My recommendation is as follows: a) Identify what changes in the platform or device will potentially impact payments and test around those features to ensure that there are no unintended consequences. b) Regression testing for major features. QA people will need a sample test device and appropriate SIM/credit cards to do this testing c) Update testing - Test that updating the phone to a newer version didn't affect the purchased apps/receipts etc d) Ensure that older versions are still handled gracefully. For 1.1 specifically the only changes which would affect Payments are bug 872987 and bug 892068. So, we can test those new features and do the other testing listed above. Let me know if you have any concerns with this approach.
Comment 5•11 years ago
|
||
If there's anything else you need, please let us know.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•