> For the complete documentation index, see [llms.txt](https://help.aximo.autify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aximo.autify.com/test-case-creation/test-case-creation-overview.md). # About sessions and cases This article explains the difference between **sessions** and **cases** in Aximo, how to choose between them, and the execution environments and models available at run time. ## Overview Aximo has two units for running tests: **sessions** and **cases**. Use sessions when you want to specify content and run it immediately. Use cases when you want to save and manage reusable test content. ## Sessions In a session, you specify a scenario, start URL, model, and Web, Desktop, mobile, or Multi-Device execution conditions to run one test. Sessions are useful when you want to watch the behavior while checking it or adjust steps while verifying. After execution, check the result, logs, conversation, console output, screenshots, and other information. To reuse the executed content continuously, save it as a case later. ## Cases A case is a unit for saving and managing reusable test cases. When you create one from **New Case**, register the title, scenario, start URL, and other content in an organized state from the beginning. Mobile cases can retain the device and app settings to use, Web cases can retain hostname overrides used during API execution, and Desktop cases can retain the registered device used at run time. When the feature is enabled for your organization, saving a Multi-Device session as a case also preserves that multi-device setup. Manage saved cases in a list and [organize them by directory](/test-case-creation/create-test-case.md#organize-cases-in-directories). Run them individually when needed, enable API triggers to call them from outside Aximo, or add them to plans for batch execution. ## Choosing between sessions and cases * When you want to try something first: use a session. * When you want to organize and manage from the beginning or run the same check repeatedly: use a case. Save content tried in a session later with **Save as a case**. To organize and manage a test from the beginning, create it as a case first so it is easier to add to a plan or connect to an API workflow. ## Execution environments Sessions and cases use different execution targets for browser-based and mobile testing. Check these before starting a test. {% hint style="warning" %} * **Desktop** is available only when BYOD is enabled for the organization and a registered device exists. * Mobile testing is not available in self-hosted environments. {% endhint %} | Execution environment | Sessions | Cases | Execution target | | ---------------------------- | :------: | :---: | ------------------------------------------------------------------------- | | Web environment | ✓ | ✓ | Browser execution environment prepared by Aximo | | Desktop environment | ✓ | ✓ | Browser execution on your own registered device (Windows / macOS / Linux) | | Mobile execution environment | ✓ | ✓ | Selected physical iOS or Android device | ### Choosing between Web and Desktop For browser-based testing, choose whether to run in **Web** or **Desktop**. * **Web**: Runs in a browser execution environment prepared by Aximo. This is the default option when you want an Aximo-managed browser. * **Desktop**: Runs in a browser on your own machine connected to Aximo with the CLI. Use this when you want to test environments that are accessible only through an internal network or applications running locally. You must register the machine in advance. See [Manage registered devices](/settings/registered-devices.md). ### Multi-Device When enabled for your organization, **Multi-Device** lets one scenario coordinate multiple **Web browser** and **Mobile device** targets. You can use it in a new test session, then save that Multi-Device session as a case and run it individually or from a plan later. Registered Desktop devices are not included in this mode. ## Execution limitations Sessions and cases have limitations based on the execution unit and execution environment. | Operation | Handling | | --------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Run on multiple devices at the same time | When it is enabled for the organization, sessions can use **Multi-Device**. If you save a Multi-Device session as a case, you can also run that same setup individually or from a plan. | | Install an app during a session | Upload apps to memories before execution, then select them when starting the session. | | Carry over the state from the previous session | Each session starts from a new environment. | | Target all users, all pages, or all devices | Tests with an unlimited scope are not supported. | | Mock and return API responses | Network-level interception is not supported. | | Run operations that may destroy the execution environment | File deletion, system shutdown, important setting changes, and similar operations cannot be executed. | ## Models Select the model to use for each session or case run. Each model has different characteristics and credit multipliers. | Model | Characteristics | Web credit multiplier per step | Mobile credit multiplier per step | | ----------------------- | ----------------------------- | :----------------------------: | :-------------------------------: | | Claude Haiku | Fastest and most affordable | 0.5x | 1.0x | | Claude Sonnet (default) | Balanced speed and capability | 1.0x | 1.5x | | Kimi K2.5 | Open source powerhouse | 0.5x | 1.0x | | GPT-5.4 | Balanced speed and capability | 1.0x | 1.5x | | GPT-5.4 Mini | Fastest and most affordable | 0.5x | 1.0x | | GPT-5.5 | Most capable OpenAI model | 2.0x | 2.5x | The timing for selecting a model differs between sessions and cases. * **Session**: Select the model when creating a new session. * **Case**: Cases do not save a default model. Select the model in the **Run** modal each time you run the case. The initial value for both is **Claude Sonnet**. {% hint style="info" %} **Kimi K2.5** is available in all organizations. OpenAI GPT models are available only when they are enabled for the organization. Contact your sales representative if you want to enable the GPT models. {% endhint %} ## Further reading * [Check usage and credits](/settings/usage-and-credits.md)