Closed Bug 1068183 Opened 10 years ago Closed 10 years ago

[UAT] Go/No-Go on Firefox Accounts Payments UX & PRD (24-Sep, 2014)

Categories

(Tracking Graveyard :: Marketplace, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cgalimidi, Unassigned)

References

Details

User Story

User Acceptance Testing : Firefox Accounts Payments Flow

Testing Steps:  
- Review the test environment ( https://marketplace-dev.allizom.org/ ) against your requirements (as below)
- List bugs / omissions in a detailed comment below
- Please recommend if changes should be fixed now (P1 / P2 - potentially delay launch) or can wait until post launch (14-Oct)
- Please provide your "GO" or "No-Go" recommendation based on your items outstanding


Bialer / Maggs
- PRD : https://docs.google.com/a/mozilla.com/document/d/1fDSzifD6_BUH0aOOPR1byZwexHpmS4qGReXGmWQzPGw/edit 
- User Stories: https://bugzilla.mozilla.org/showdependencytree.cgi?id=1017239&hide_resolved=1 


Ryan / John G : 
- Please ensure Marketplace has implemented Firefox Accounts correctly in the payments flow
- Check design details and UX

Attachments

(1 file)

No description provided.
User Story: (updated)
Summary: [UAT] Go/No-Go on Firefox Accounts Payments → [UAT] Go/No-Go on Firefox Accounts Payments UX & PRD (24-Sep, 2014)
Everything looks good on my end, ready to rock.
Attached image marketplace-account-settings.png (deleted) —
This field in Account Settings is read-only and should not be user-selectable. Also when the user selects the text all the way to the left, the page goes back to the Marketplace homepage.
I don't see the toast notification that should appear when the user logs in.
When I click a verification link in the email that has already been clicked, instead of our "account verified" message again, the user gets: /fxa-authorize?error=3005 which shows the Marketplace progress indicator endlessly.
Already Fixed on FXA: - position of FX Logo - lack of space btwn 'Forgot password?'/'Create an account' Link
Needs fixing on FXA: Popup has a fixed height w/no overflow, legal copy should have internal overflow so it is all accessible https://www.dropbox.com/s/y2r4oyyruypkxtl/Screen%20Shot%202014-09-24%20at%205.46.44%20PM.png?dl=0 Will be fixed by: https://github.com/mozilla/fxa-content-server/issues/1701
David B - Please confirm that the build for Firefox Accounts / Payments is working according to the PRD. Please call out any issues (or bugs filed) and specifically note if they are P1s (showstoppers) or if they can be addressed after launch. :-)
Flags: needinfo?(dbialer)
Maureen - Please confirm that the build for Firefox Accounts / Payments is working according to the UX / Design specs. Please call out any issues (or bugs filed) and specifically note if they are P1s (showstoppers) or if they can be addressed after launch. Thanks muchly!
Flags: needinfo?(mhanratty)
(In reply to Ryan Feeley from comment #4) > When I click a verification link in the email that has already been clicked, > instead of our "account verified" message again, the user gets: > /fxa-authorize?error=3005 which shows the Marketplace progress indicator > endlessly. This is related to what's happening here in bug 1072267. Here's my discussion on how it can be addressed: https://bugzilla.mozilla.org/show_bug.cgi?id=1072267#c5
Hey there Ryan - have the issues you noted above been resolved? do you have any new issues to log? https://bugzilla.mozilla.org/show_bug.cgi?id=1068183#c2 This field in Account Settings should be read-only https://bugzilla.mozilla.org/show_bug.cgi?id=1068183#c3 need toast notification on login https://bugzilla.mozilla.org/show_bug.cgi?id=1068183#c4 Marketplace progress indicator showing endlessly Note (Maureen no longer here)
Flags: needinfo?(mhanratty) → needinfo?(rfeeley)
NO - Field is still selectable. YES - Toast notification appear. YES - indicator does not show endlessly
Flags: needinfo?(rfeeley)
Hey there Ryan and David Bialer - Does the current build satisfy the product requirements and ux specs? Do you have any concerns / bugs we need to take on for after go-live, as part of a cleanup / stabilization activity?
Flags: needinfo?(rfeeley)
Flags: needinfo?(dbialer)
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(rfeeley)
Resolution: --- → FIXED
Product: Tracking → Tracking Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: