Testability and Shift-Left Testing Questions

I’d treat this like a reproducibility and isolation problem first, not a test-writing problem.

My steps would be:

1. Re-run the exact CI artifact locally if possible: same commit, same build type, same simulator/emulator image, same locale and device size.
2. Collect evidence: logs, screenshots/video, test order, network activity, and whether failures correlate with timing or a specific screen.
3. Narrow the scope: run the failing test alone, then with nearby tests, then in the full suite to see if there is shared state leakage.
4. Check common mobile causes: animations not disabled, missing synchronization, stale app state, async work still running, resource contention, or dependence on previous tests.
5. Fix the root cause by making the test deterministic: better selectors, explicit waits on app state, hermetic test data, reset between tests, and stable test fixtures.

I would only use retries as a temporary shield, not a fix. If a test is still flaky after that, I’d quarantine it short-term, keep the behavior covered elsewhere, and assign ownership until the underlying issue is resolved.

I would split the screen or view model into pure logic and side effects.

First, I’d inject dependencies instead of constructing them: an API client interface, a parser/mapper, and a repository or persistence gateway. The view model should orchestrate state, not know how HTTP or storage works.

A good shape is:

• ViewModel: handles user intent and UI state.
• Use case or service: contains business rules.
• Repository: coordinates remote and local data.
• Data sources: one for API, one for storage.
• Mapper: converts raw DTOs into domain models.

That gives you unit-testable seams. You can test the view model with fake dependencies, verify it emits the right state, and test the repository separately with stubbed API responses or an in-memory store. Parsing should happen in a pure function or mapper, so malformed payload handling can be tested without UI or storage.

This design reduces coupling, makes failures easier to localize, and prevents a single class from becoming impossible to test.

I’d test accessibility at three levels: semantic checks, interaction checks, and real screen-reader verification.

What I can automate:

• Every interactive element has a meaningful label, hint, or content description.
• Focusable elements are exposed in a sensible order.
• Buttons and controls have the right traits and are large enough to tap.
• State changes are announced or at least reflected in accessible text.
• Accessibility scanners can catch obvious issues like missing labels or low-contrast text.

What still needs manual review:

• Whether VoiceOver or TalkBack reads the screen naturally.
• Whether the focus order matches the visual and task flow.
• Whether dynamic updates, modal dialogs, and errors are announced at the right time.
• Whether the feature is usable with only the screen reader, no sighted assistance.

I’d build the automated checks into CI and include accessibility in the definition of done, but I’d still do at least one manual pass on a real device before release. Automation finds regressions; humans catch usability problems.

I avoid arbitrary sleeps because they make tests slow and nondeterministic. Instead, I try to control the source of asynchrony.

Patterns I use:

• Expectations or latches: wait for a specific callback or event, with a timeout only as a safety net.
• Fake clocks or test schedulers: for timers, debounce logic, or reactive streams, I advance virtual time manually instead of waiting in real time.
• Injected executors/dispatchers: run work on a test-controlled thread or immediate executor.
• Async/await or promise testing: await the final state rather than polling.
• For streams, subscribe in the test, emit events explicitly, and assert the sequence.

The key is to make the async dependency injectable so the test controls when work happens. That keeps tests fast, repeatable, and easy to debug. If a test still needs a timeout, I keep it short and use it only to fail fast, not to "solve" synchronization. The best async tests are ones where the test owns time and input, not the app.

I usually separate the problem into two concerns: network I/O and persistence.

For network calls, I prefer a stub or fake server over a pure mock when I want realistic request/response behavior. In iOS that often means abstracting the client behind a protocol and stubbing the transport; in Android/Jest-style tests, I’ll use a fake repository or a local test server. For persistence, an in-memory database or fake store is usually better than mocking every DAO method, because it exercises real reads, writes, and queries.

Trade-offs:

• Mocks: best for verifying interactions, but they can make tests brittle if you over-specify call order.
• Stubs: good for fixed responses and deterministic tests, but they don’t model state changes.
• Fakes: great for higher-confidence tests because they behave like a simplified real dependency, but they take more effort to build.

My rule is: use mocks sparingly for collaboration boundaries, use stubs for simple branching, and use fakes or in-memory implementations when the behavior itself matters. That keeps tests fast, readable, and closer to production behavior.