Closed
Bug 970263
Opened 10 years ago
Closed 10 years ago
B2G NFC: Enable NFC when running NFC marionette tests
Categories
(Firefox OS Graveyard :: NFC, defect)
Tracking
(feature-b2g:2.0, tracking-b2g:backlog)
RESOLVED
FIXED
1.4 S6 (25apr)
People
(Reporter: allstars.chh, Assigned: allstars.chh)
References
Details
(Whiteboard: [p=8])
Attachments
(1 file, 1 obsolete file)
4.18 KB,
patch
|
allstars.chh
:
review+
|
Details | Diff | Splinter Review |
Right now if the screen is off or locked, NFC daemon will enter lower power mode(Disable discovery). So when running marionette test for NFC, we should also unlock the lockScreen and keeps screen always on.
Assignee | ||
Comment 2•10 years ago
|
||
Also see the assertion from https://bugzilla.mozilla.org/show_bug.cgi?id=976478#c0
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → allstars.chh
Comment 3•10 years ago
|
||
Hi Yoshi, I was debugging this problem today. A change to the settings value 'nfc.enabled' should be observed by nfc_manager.js near line 144. When doing the test steps by hand, I see the event twice, once during boot, and a second time when I enable NFC in the Settings app. But when I run the test case, I only see this event at the beginning; not during the test itself. Any ideas?
Flags: needinfo?(allstars.chh)
Assignee | ||
Comment 4•10 years ago
|
||
I also know this and is checking this too. It seems before the marionette starts, some Gaia app (communication) has been killed, and the system app is also gone, so nfc_manager cannot observe the settings change event from head.js. One thing I also found that is System app is running on b2g process, so the process shouldn't be killed, however it is gone.
Flags: needinfo?(allstars.chh)
Updated•10 years ago
|
Blocks: b2g-NFC-2.0
Updated•10 years ago
|
Assignee | ||
Updated•10 years ago
|
Summary: B2G NFC: Unlock screen when running marionette test → B2G NFC: Enable NFC when running NFC marionette tests
Assignee | ||
Updated•10 years ago
|
Whiteboard: [p=8]
Target Milestone: --- → 1.4 S6 (25apr)
Assignee | ||
Comment 6•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Attachment #8405270 -
Flags: review?(dlee)
Updated•10 years ago
|
blocking-b2g: --- → backlog
Comment 7•10 years ago
|
||
Comment on attachment 8405270 [details] [diff] [review] Patch. Review of attachment 8405270 [details] [diff] [review]: ----------------------------------------------------------------- If we will not use setting in test cases maybe we could remove SpecialPowers.pushPermissions( [{'type': 'settings', 'allow': true, 'context': document}], runTests);
Attachment #8405270 -
Flags: review?(dlee) → review+
Assignee | ||
Comment 8•10 years ago
|
||
remove settings permission.
Attachment #8405270 -
Attachment is obsolete: true
Attachment #8406724 -
Flags: review+
Assignee | ||
Comment 9•10 years ago
|
||
https://hg.mozilla.org/integration/b2g-inbound/rev/220f343d80c2
Status: NEW → ASSIGNED
Comment 10•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/220f343d80c2
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
feature-b2g: --- → 2.0
Updated•10 years ago
|
Flags: in-moztrap-
Updated•9 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•