Closed Bug 1024407 Opened 11 years ago Closed 11 years ago

Develop first Semi-auto test for Settings API

Categories

(Firefox OS Graveyard :: Certification Suite, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: gnaneswar.devuni, Assigned: gnaneswar.devuni)

References

Details

Attachments

(1 file)

54 bytes, text/x-github-pull-request
rwood
: review-
Details | Review
Tests the set and get methods of navigator.mozSettings.
Blocks: 1008970
Assignee: nobody → gnaneswar.devuni
Status: UNCONFIRMED → NEW
Ever confirmed: true
Attached file Pointer to github PR
Rob, would like to know your inputs about my note in critic https://critic.hoppipolla.co.uk/r/1831
Attachment #8442047 - Flags: review?(rwood)
Gnaneswar, In regards to vibration and the phone, I checked the code and turns out the gaia phone dialer app itself is checking the settings value to determine if it should call the vibrate API or not. So the setting itself won't disable/enable the vibration; it is up to the gaia app to check the setting and act appropriately. https://github.com/rwood-moz/gaia/blob/master/apps/system/js/dialer_agent.js I'm assuming that the other settings work the same way. In which case any webapi test developed for settings won't require any user intervention / doesn't need to be semi-automated. So for now I would drop this test. Once we decide how we will develop fully-automated webapi tests for the cert suite, then we can revisit this API and develop a test that will just set each available setting and get the value to verify, and be fully automated. I am going to close this bug and mark it as "INVALID" since the semi-auto framework is not required for this particular API test.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Attachment #8442047 - Flags: review?(rwood) → review-
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: