Mobile Testing Interview Questions: Offline State, Permissions, and App Lifecycle

A mobile test that passes on a warm foreground app proves little about a user returning after the process was killed, denying a permission, switching networks during a write, or reopening with queued work. Mobile correctness lives at the intersection of durable state, operating-system lifecycle, permission state, and an unreliable network.

This guide prepares you to answer mobile testing interview questions with a diagnostic method, a concrete state trace, and evidence you can defend. It is not a leaked question bank or a claim that every employer uses the same interview format.

Article thesis: Model each transition explicitly: foreground/background, process alive/dead, online/offline, permission granted/denied/revoked, and server result known/unknown. Assert both immediate UI and durable state, then repeat the same action after restoration or retry.

Evidence boundary: Official documentation supports the platform and security mechanics cited below. We did not find a reliable, current corpus of candidate reports that establishes a universal interview sequence for this topic.

To rehearse the same boundary-first reasoning with candidate-reported material, start with Contrast UI vs backend testing; design UI-change test cases; use it as practice evidence, not as a prediction of a specific interview.

Mobile Testing Interview Questions: Quick Answer

Model each transition explicitly: foreground/background, process alive/dead, online/offline, permission granted/denied/revoked, and server result known/unknown. Assert both immediate UI and durable state, then repeat the same action after restoration or retry.

A strong answer begins by drawing the source of truth and the boundary that can fail. It then distinguishes prevention, detection, and recovery; walks one ordinary case and one adversarial case; and names the evidence that would change the diagnosis. Tool names belong after the invariant, not before it.

Start with the five urgent questions

• Which state must survive view recreation and which must survive process death?
• How does the feature behave when permission is denied, revoked, or limited?
• What identity makes an offline write safe to retry?
• How do you test an unknown server result after connectivity drops?
• Which device, OS, locale, and background-policy dimensions are essential?

These questions prevent a polished answer from solving the wrong problem. If the interviewer leaves a value unspecified, state a conservative assumption and show where it enters the design. When the constraint changes, update the affected boundary rather than replacing the whole answer.

Separate documented facts, reports, and inference

Official documentation — Android process lifecycle: Android can kill cached processes; onDestroy() is not guaranteed when the system kills the process.

Official documentation — Android activity testing: Android documents lifecycle tests that move activities through states and recreate them to check data integrity and user experience.

Official documentation — Android Debug Bridge: Android documents pm grant and pm revoke commands that let tests change runtime permission state instead of assuming the installation state.

Candidate reports: No reliable same-cycle set of public reports establishes a standard prompt order, scoring rule, or expected vendor configuration for this general topic. Individual reports can suggest practice areas, but they cannot establish prevalence.

Engineering inference: The diagnostic sequence in this article is designed to make the documented mechanics testable in an interview. It is a preparation framework, not an official rubric.

Draw the diagnostic boundary map

Boundary	Question or state	Defensible response	Failure to expose
Warm foreground	process alive, online, permission granted	basic interaction and rendering	hides restoration defects
Background/resume	activity stopped then resumed	pause/resume resources and freshness	stale screen or duplicate observer
Process death	durable storage remains; memory is gone	recreate navigation and pending work	memory-only state loss
Offline/unknown result	request may be queued or committed remotely	stable operation ID and reconciliation	duplicate write or lost user intent
Permission change	deny, deny permanently, revoke in settings	explain value, degrade, recover	crash or blocked screen

This boundary map is the first article-specific asset. Read it left to right. For every transition, name the initiator, the identity carried with the action, the policy decision, the durable result, and the observation that proves success. When a result is unknown, prefer inspection or reconciliation before repeating a side effect.

Work through a concrete interview scenario

A user creates note op-73 while offline. The app shows a clearly pending note and persists the operation. The process is killed. On restart, the same pending item is restored and uploaded once when connectivity returns. If the connection drops after the server commits but before the response, the client reconciles by operation ID instead of creating a second note.

Narrate the trace in chronological order. Separate facts you have observed from hypotheses you still need to test. A status code, log line, or green dashboard is only one observation; it may not prove the durable business outcome. State what would falsify your current explanation.

The supporting visual is the second article-specific asset. Use it to explain the normal path, the first boundary that can fail, the evidence collected there, and the recovery path. The interviewer should be able to change one condition and see exactly which edge of the diagram changes.

Show a small implementation or review skeleton

on_user_save(note):
  op = durable_outbox.insert(stable_id(), note, state="pending")
  render_pending(op)

on_connectivity_available():
  for op in durable_outbox.pending():
    result = api.put_by_idempotency_key(op.id, op.payload)
    reconcile(op.id, result_or_remote_lookup)

on_process_start(): restore_ui_from_durable_state()

The skeleton is deliberately compact. In an interview, explain the behavior around it: parsing, identity, timeouts, concurrency, cancellation, cleanup, authorization, observability, and version-sensitive assumptions. Production code also needs framework-specific error handling and tests; the point here is to expose the control decisions.

A useful code-review question is, “What fact makes the next transition safe?” If the answer is only that the previous call returned, add a durable check. If an action can repeat, define whether repetition resumes the same operation, creates a new attempt, or creates a new business effect.

Diagnose four misleading answers

Tempting answer	Why it fails	Better response
Test airplane mode only	Airplane mode is one network state	Cover loss, latency, captive path, and unknown result
Rotate to simulate process death	Configuration recreation may retain process memory	Use platform process-death/restoration tests
Grant permission in setup forever	Revocation and limited grants are missed	Exercise deny, revoke, rationale, and recovery
Retry a POST with a new identity	Unknown results create duplicates	Persist a stable operation identity

For each misleading answer, reproduce the smallest counterexample, name the violated invariant, apply one narrow repair, and rerun the same case. Changing several layers at once may make the symptom disappear without proving which change fixed it.

Design the test matrix before naming tools

Use at least four classes of tests:

1. Normal path: the smallest valid input reaches the intended durable result.
2. Boundary path: an empty, maximum, ambiguous, stale, or repeated input exercises the contract edge.
3. Failure path: inject one timeout, dependency failure, process interruption, policy denial, or capacity limit.
4. Recovery path: prove the system reaches a known state without guessing whether an earlier effect occurred.

Keep fixtures deterministic. Record versions, configuration, time, identity, and the injected fault. Assert both the immediate response and the later durable state. A test that observes only the UI or only the log can miss a duplicated, lost, or unauthorized effect.

Measure what the answer promises

• pending outbox age and retry distribution
• duplicate and reconciliation outcomes
• restoration success after process death
• permission-denial and recovery paths
• crashes, ANRs, battery/network use, and sync latency by OS/device cohort

Avoid unsupported percentage improvements. State the workload, baseline, window, sample size, and measurement point. Separate averages from tail behavior and application failures from experiment or infrastructure failures. A dashboard should make a bad hypothesis easier to reject, not merely make the system look active.

Use this answer structure in the interview

1. Restate the requirement and define the source of truth.
2. Name one invariant that must survive every transition.
3. Draw the trust, process, network, or data boundaries.
4. Walk a concrete example with identities and state changes.
5. Inject one failure and distinguish known from unknown outcomes.
6. Recover through verification, reconciliation, rollback, or bounded retry.
7. Name measurements, tests, and the trade-off your design chooses.

This structure keeps the answer adaptable. When the interviewer adds scale, security, concurrency, or availability constraints, place the new fact on the diagram and revise the relevant mechanism. Memorizing a product checklist is less useful than showing which assumption each control protects.

Common follow-up questions

What makes an answer senior-level?

Senior answers make ownership and uncertainty explicit. They identify the authoritative state, protect tenant or user boundaries, define what happens after an unknown result, and propose evidence that could disprove the design. Extra components do not substitute for these decisions.

Should I memorize every vendor setting?

Memorize the state model and a few diagnostic examples. Treat version-sensitive settings as facts to verify against current documentation. In the interview, explain how you would inspect the live configuration rather than inventing a default.

How should I use candidate reports?

Use a report as one person’s account of a prompt or process. Record the date, role, location, and source when available. Do not turn one report into a universal employer rule or a frequency claim. For these general technical topics, official mechanics and reproducible reasoning carry more weight.

What should I do when the outcome of an action is unknown?

Do not repeat a side effect blindly. Inspect durable state using a stable operation identity, reconcile the intended result, and retry only when the operation is idempotent or the business rule defines safe repetition.

How much detail should I include?

Go deep on the boundary that determines correctness. Give one normal trace, one failure trace, one recovery trace, and the measurements that validate them. Mention alternative tools only when they change a stated trade-off.

Final preparation checklist

• Define identity, lifetime, ownership, and source of truth.
• Separate documented fact, candidate report, and engineering inference.
• State the invariant before the product or tool name.
• Trace normal, boundary, failure, and recovery behavior.
• Treat unknown results differently from confirmed failures.
• Protect authorization and tenant scope at every boundary.
• Record version-sensitive assumptions and current sources.
• Measure the promised outcome and its failure surface.
• Keep fixtures deterministic and verify durable state.
• Finish with one explicit trade-off and one falsifiable test.

Sources and Further Reading

• Android process lifecycle
• Android activity testing
• Android permissions testing

Research note: Sources were checked on 2026-09-13. Official documents support the cited mechanics. Candidate-report evidence does not establish a universal interview format for this topic.