B2G/QA/WebAPI Test Plan/WebSMS: Difference between revisions
< B2G | QA | WebAPI Test Plan
Jump to navigation
Jump to search
(→API) |
|||
Line 64: | Line 64: | ||
* <tt>DOMString delivery</tt><br>"sent", "received", or null | * <tt>DOMString delivery</tt><br>"sent", "received", or null | ||
* <tt>jsval read</tt><br>Boolean, can be undefined | * <tt>jsval read</tt><br>Boolean, can be undefined | ||
=== [http://mxr.mozilla.org/mozilla-central/source/dom/sms/interfaces/nsIDOMSmsManager.idl nsIDOMSmsManager] === | |||
==== Methods ==== | |||
* <tt>unsigned short getNumberOfMessagesForText(in DOMString text)</tt> | |||
* <tt>jsval send(in jsval number, in DOMString message)</tt><br>First param can be DOMString (one number) or Array of DOMString (multiple numbers). Returns either SmsRequest or array of SmsRequest accordingly. | |||
* <tt>nsIDOMMozSmsRequest getMessage(in long id)</tt> | |||
* <tt>nsIDOMMozSmsRequest delete(in jsval param)</tt><br>Param can be either message id or SmsMessage | |||
* <tt>nsIDOMMozSmsRequest getMessages(in nsIDOMMozSmsFilter filter, in boolean reverse)</tt> | |||
* <tt>nsIDOMMozSmsRequest markMessageRead(in long id, in boolean aValue)</tt> | |||
==== Events ==== | |||
* <tt>onreceived</tt> | |||
* <tt>onsent</tt> | |||
* <tt>ondelivered</tt> | |||
=== [http://mxr.mozilla.org/mozilla-central/source/nsISomeInterface.idl#1 nsISomeInterface] === | === [http://mxr.mozilla.org/mozilla-central/source/nsISomeInterface.idl#1 nsISomeInterface] === |
Revision as of 00:32, 27 June 2012
B2G WebSMS API Test Plan
Summary
Lead | Geo Mealer (irc: geo) |
Contributors | TBD |
API Description | Send/receive SMS messages as well as manage messages stored on device. |
API Developer | Mounir Lamouri |
API Project Page | WebSMS |
API Tracking Bugs | bug 674725 |
API Status | Mostly done for B2G. |
Scope
A short section should be added here that describes the testing scope of this plan: both what is and is not included, broadly.
Strategy
Explain here how to test the API in question (emulator, device-agnostic CI tests, on-device applications, or a combination).
In the likely case of a combination, discuss how tests will be split between options.
API
Describe the API here. Give a short summary, what the API does, and any considerations or preconditions for using it.
Related Prefs
- dom.sms.enabled
- dom.sms.whitelist
Attributes
- readonly nsIDOMMozSmsManager mozSms
nsIDOMSmsCursor
Attributes
- readonly nsIDOMMozSmsMessage message
Methods
- void continue()
nsIDOMSmsEvent
Attributes
- readonly nsIDOMMozSmsMessage message
nsIDOMSmsFilter
Attributes
- jsval startDate
Date, can return null - jsval endDate
Date, can return null - jsval numbers
Array of DOMString, can return null - DOMString delivery
"sent", "received", or null - jsval read
Boolean, can be undefined
nsIDOMSmsManager
Methods
- unsigned short getNumberOfMessagesForText(in DOMString text)
- jsval send(in jsval number, in DOMString message)
First param can be DOMString (one number) or Array of DOMString (multiple numbers). Returns either SmsRequest or array of SmsRequest accordingly. - nsIDOMMozSmsRequest getMessage(in long id)
- nsIDOMMozSmsRequest delete(in jsval param)
Param can be either message id or SmsMessage - nsIDOMMozSmsRequest getMessages(in nsIDOMMozSmsFilter filter, in boolean reverse)
- nsIDOMMozSmsRequest markMessageRead(in long id, in boolean aValue)
Events
- onreceived
- onsent
- ondelivered
nsISomeInterface
Attributes
- readonly DOMString someAttribute (values can be foo, bar, baz, bam)
Methods
- boolean someMethod(in DOMString param)
- void anotherMethod()
Events
- onsomevent
Tests
Marionette/JS
Test Type 1
- Test 1
- Test 2
Test Type 2
- Test 1
- Test 2
mochitest-plain
Test Type 1
- Test 1
- Test 2
Test Type 2
- Test 1
- Test 2
Test App Design
Describe application functionality here
This page is based on the WebAPI Test Plan Template