Testability and Shift-Left Testing Questions

I’d make the standards explicit, automated, and incremental.

First, I’d agree as a team on a small set of rules that actually matter: things like no unchecked force unwraps, no obvious thread-safety hazards, no dead code, and no new lint violations in touched files. Then I’d encode as much as possible in tooling so reviewers aren’t the enforcement mechanism.

Practically, that means:

• fast local lint and formatter hooks,
• static-analysis checks in CI,
• a clear severity policy: block on correctness issues, warn on style issues,
• and a review checklist that focuses humans on architecture, naming, and risky trade-offs.

I’d also avoid creating a bottleneck by ratcheting gradually. Don’t fail the whole codebase on legacy warnings; prevent new debt from entering and chip away at old debt over time. If a rule is too noisy, tune or remove it. That keeps trust high.

The goal is consistency and bug prevention, not gatekeeping. Good standards should make reviews shorter, not longer.

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’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.

Unit tests, integration tests, and end-to-end tests each protect a different risk.

• Unit tests: verify one class or function in isolation. They are fast, precise, and best for business rules, edge cases, and pure logic.
• Integration tests: verify that components work together, like a repository talking to a database or a view model calling a service. They catch wiring and contract issues.
• End-to-end tests: simulate the user journey through the app UI. They are slower, but they protect the most important flows from a real-user perspective.

If I were starting a feature from scratch, I’d put most logic in unit-testable code, add integration tests at the boundaries that are likely to break, and reserve end-to-end tests for critical paths like sign-in, checkout, or data submission. That gives good coverage without making the suite too slow or brittle.

My rule is simple: test the behavior at the lowest layer that can prove it correctly, and only go higher when the user experience itself is the thing at risk.

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.