Closed Bug 935407 Opened 11 years ago Closed 8 years ago

B2G Emulator: Write a marionette test to test card state.

Categories

(Firefox OS Graveyard :: RIL, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:-)

RESOLVED INCOMPLETE
blocking-b2g -

People

(Reporter: allstars.chh, Unassigned)

References

Details

Currently in nsIDOMIccManager.cardState,
we have 

  /**
   * Indicates the state of the device's ICC card.
   *
   * Possible values: null, 'illegal', 'unknown', 'absent', 'pinRequired',
   * 'pukRequired', 'personalizationInProgress', 'networkLocked',
   * 'corporateLocked', 'serviceProviderLocked', 'networkPukRequired',
   * 'corporatePukRequired', 'serviceProviderPukRequired',
   * 'personalizationReady', 'ready'.
   */
  readonly attribute DOMString cardState;


We could send some 'manually written' data to control the SIM Status on the emulator, and write a marionette test to verify the cardState accordingly.
What's so called "manually written data"?
Maybe some pdu could represent the SIM Status,
but you're the expert here welcome to provide suggestions. :)
I guess we won't do it now.
Assignee: gwang → nobody
rild reports SIM status change because it touches some PIN protected SIM file, and then emulator host replies a "+CPIN: ...".  If we're going to implement something that changes SIM status, I'd like to know how should it work on actual devices first.  By now we still treat rild/emulator as some kind of autonomous components that only affected by signals/events from outside world, aka console commands.  And don't get me wrong, not everything is allowed even you want to implement it.  Radio power state is an example, and SIM status is just another because they're either kept as a copy in rild or relevant to the integrity as a whole.

So, like I've already had above, I'd like to know what's happening here, have a discuss in detail before we wasting some time in vain.  "some pdu" sounds like it will ruin the state machine of rild at a very high chance.
Put it in backlog.
blocking-b2g: --- → backlog
See Also: → 1034522
blocking-b2g: backlog → -
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.