Open
Bug 1057916
Opened 10 years ago
Updated 2 years ago
breakdown: Add FxA authentication tests
Categories
(Firefox :: Sync, defect, P3)
Firefox
Sync
Tracking
()
NEW
People
(Reporter: markh, Unassigned)
Details
We have no testing infrastructure in place for FxA authentication tests with sync. This is becoming a relatively serious risk - manual testing of all edge-cases is hard and the code is complex - any change we make to browserid_identity.js risks breaking sync in subtle edge-cases. The main reason is that we don't have tests is that we don't have implementations of the various servers in-tree that we can use. We can *probably* get away with mocked servers, but this isn't clear, and even if it was, would be non-trivial - so I'm marking this as a breakdown bug to get some idea of what is involved.
Flags: firefox-backlog+
Updated•10 years ago
|
Flags: qe-verify?
Comment 1•10 years ago
|
||
Related: we recently added some functional tests (primarily for regression testing sync login) for about:accounts in our FxA server. We ran into some roadblocks that make these less effective than they could be, e.g., when you log out of sync all our custom prefs set at the beginning of the test get reset.
Comment 2•10 years ago
|
||
Link to the tests mentioned above: https://github.com/mozilla/fxa-content-server/pull/1576
Updated•10 years ago
|
Points: --- → 5
Flags: qe-verify? → qe-verify-
Summary: [breakdown] Add FxA authentication tests → breakdown: Add FxA authentication tests
Updated•9 years ago
|
Priority: -- → P2
Updated•8 years ago
|
Priority: P2 → P3
Assignee | ||
Updated•6 years ago
|
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•