Add UI-tests for forceAuthentication

RESOLVED WONTFIX

Status

defect
P3
normal
RESOLVED WONTFIX
6 years ago
Last year

People

(Reporter: ferjm, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [fxa4fxos2.0])

No description provided.
Assignee: nobody → ferjmoreno
Component: Identity → Gaia::UI Tests
Product: Core → Firefox OS
Depends on: 970438
Depends on: 929917
No longer depends on: 970438
Assignee: ferjmoreno → nobody
Fernando any updates on this? Can we help with anything?
Flags: needinfo?(ferjmoreno)
I will take this one.
Assignee: nobody → spenrose
Flags: needinfo?(ferjmoreno)
Priority: -- → P3
Whiteboard: [fxa4fxos2.0]
Sam any updates on this? Can we help with anything?
Flags: needinfo?(spenrose)
(In reply to Florin Strugariu [:Bebe] from comment #3)
> Sam any updates on this? Can we help with anything?

No updates; it's been languishing at P3. The work is this:

1) In gaia/dev_apps/uitest/tests_html/API/fxa.html, add a "Refresh Authentication" button and some number widget that can have a value of 0 and a value greater than 0, say 5 or 10.

2) In gaia/dev_apps/uitest/js/API/fxa.js:_bindEvents(), add a handler for the new button that reads the number widget value into some var gracePeriod and fires:

  navigator.mozId.request({refreshAuthentication: gracePeriod, oncancel: function(){<code here>}})

3) Bonus: Write marionette tests that call:
  i. Invoke the button with the value set to 0, and check the "correct password->onlogin()" and "cancel->oncancel() fires" cases.
  ii. Before N seconds have passed, reinvoke the button with gracePeriod of N and verify that onlogin() fires.
  iii. Continue waiting until N seconds have passed, and reinvoke the button, and check the "correct password" and "cancel" cases per i.
Flags: needinfo?(spenrose)
Oh, one more thing: Richard Pappalardo may have done some of this work.
QA Whiteboard: [fxosqa-auto-backlog+]
Assignee: spenrose → nobody
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.