Test Cases That Play Well with Mobile Automation

Autotests for mobile applications often suffer from flakiness, long execution times, and weak reproducibility. Another common issue is the gap between automated tests and manual scenarios: some checks are lost because QA engineers consider them “covered by automation” and stop performing them manually. This leads to missed bugs. A frequent mistake is designing test cases for automation in the same way as for manual testing: long scenarios, numerous checks bundled together, and a mix of layout, logic, and UX.

In this talk, we will explore what makes a test case suitable for automation:

  • how to make it atomic without being excessively fragmented;

  • how to take the architecture of a mobile application into account when designing tests;

  • and how to map a feature onto the levels of the testing pyramid in practice.

By the end, you will take away a checklist on “how to write automation-friendly test cases” and a visual map linking mobile application architecture to the testing pyramid.


Comments ({{Comments.length}})
  • {{comment.AuthorFullName}}
    {{comment.AuthorInfo}}
    {{ comment.DateCreated | date: 'dd.MM.yyyy' }}

To leave a feedback you need to

or
Chat with us, we are online!