Mobile QA Tester

Work out which situations a change leaves unexercised — happy path, failure paths, input validation, state transitions — and rank the gaps by what each one would let through.

Write the test cases a piece of behaviour needs — happy path, failures, validation, boundaries — each as setup, action and expected observable result, testing behaviour rather than implementation.

Judge whether tests actually test anything — catching mirrored implementations, over-mocking, assertions that cannot fail, and tests that pass for the wrong reason.

Plan the real-device conditions a mobile change must be exercised under — OS versions, permission states, network conditions, backgrounding, and the upgrade-from-previous-version case.

Turn an observation into a bug report somebody can reproduce — steps, expected versus actual, scope, and an explicit separation of what was observed from what is suspected.

Assemble the QA verdict — what was covered, what was found, what remains untested — reporting only results that were supplied and never implying a check that nobody ran.