Skip to main content
QA Studio provides a web-based interface for defining and managing your mobile test cases. You can build tests step by step, organize them with folders and tags, reuse common flows across tests, and track stability over time.

​
Defining test cases

Each test case consists of step-by-step instructions that describe the actions and assertions to perform. Steps are written in natural language, making them easy to read and maintain without deep technical knowledge. You can also reference other test cases within the steps of a test case. This lets you build modular, reusable flows (like login or onboarding) and include them as steps in multiple tests without duplicating definitions. See Reusable test steps for details.

​
Tags

Test cases can be freely tagged to support flexible grouping and filtering. Tags are useful for organizing tests by priority, feature area, or team ownership. Common examples include:
  • smoke, critical, regression for test priority
  • checkout, login, onboarding for feature areas
  • team-mobile, team-payments for team ownership
Tags can also be used to trigger specific subsets of tests in CI. See Tags for more.

​
Folders

A folder system is available to organize test cases into a structure that fits your project. Folders can represent features, modules, platforms, or any other grouping that makes sense for your team. See Folders for details.

​
Dependency chains

Test cases can be chained sequentially so that one test depends on the completion of another. This is useful when tests share preconditions or need to run in a specific order. See Dependency chains for details.

​
Run history

The test overview provides a clear run history for each test case, showing pass/fail trends over time. This makes it easy to identify which tests are stable and which are currently flaky, so you can prioritize fixes where they matter most. See Run history for more.