Create a baseline session

Overview

A baseline session is a completed test session that serves as the source for automated test execution. It captures how an application is exercised on a real device and provides the reference used to create a test case.

A baseline session is required before a test can be run automatically. You can create one from any of the following session types:

Manual sessions
Appium automation sessions
Mixed sessions, which combine manual and automation steps in a single session

What is a baseline session?

A baseline session is a session performed on a real device through the platform.

During the session, the application is exercised as it would be during normal testing, through manual interaction, an Appium script, or a mix of both. These interactions are captured by the platform and later reused to define a test flow.

Once converted into a test case, the baseline session becomes the reference for future test execution. Test cases created from manual sessions can also be used to generate Appium scripts.

Create a baseline from a manual session

Baseline sessions are created from manual sessions by running a session with capture enabled and completing a defined test flow.

1. Start a manual session and enable capture

From the Devices view in the Kobiton platform, select a device and launch a manual session.

Before interacting with the application, select the Play button to enable session capturing mode.

Session capturing mode improves the accuracy of element detection by capturing precise element bounding boxes. Actions performed while capturing is enabled provide the most reliable results for scriptless execution.

If your test requires an application, install or select the app at the start of the session.

Actions performed before capture is enabled are still saved with the session, but may result in reduced element accuracy during automated execution.

2. Perform the test flow

Interact with the application as you would during normal testing.

While capture is enabled, the platform captures supported interactions and associates them with the current application state. These captured interactions form the basis of the baseline session.

Focus on completing a single, intentional test flow from start to finish.

3. End the session and convert it to a test case

When the test flow is complete, exit the manual session by selecting the X icon.

The session then opens in Session Explorer, where it can be converted into a test case. Once converted, the test case is managed through Test Management, where it can be reviewed, edited, and used to create test runs.

To convert a session into a test case or learn more about Test Management, see Test cases.

Create a baseline from an automation or mixed session

To use an Appium automation or mixed session as a baseline:

In your Appium script, set the kobiton:scriptlessCapture capability. Without it, Kobiton captures limited session data.
Run the session to completion. Sessions that are still running cannot be converted.
Convert the session to a test case from Session Explorer, or from Test Management by selecting New Test Case. To find the session in Test Management, search for type:appium or type:mixed.

When a mixed session is converted, the test case keeps the manual and automation steps in the order they were recorded.

For limits on supported apps, unsupported steps, and Appium script generation, see Test Cases from automation and mixed sessions.

What makes a good baseline

Baseline sessions are most reliable when they reflect a clear and stable test flow.

Good baseline sessions typically:

Follow a single, intentional path through the application
Use supported interactions only
Avoid unnecessary navigation or exploratory actions

Baseline quality directly affects how reliably a test can be executed later.

Platform considerations

Baseline sessions are platform-specific.

Separate baseline sessions are required for Android and iOS, even when the application behavior is similar.

Baseline sessions must target a supported application context: a web application (Safari or Chrome), an app installed from the App Repository, or an existing app already available on the device. For automation sessions and the automation steps of mixed sessions, only apps from the App Repository and existing apps are supported.

To create a Test Case that can be replayed, record a baseline session using an app installed from the app repository or an app or browser that can be opened without installation.

Sessions that use only the device home screen or an app installed from a local file or URL cannot produce replayable Test Cases. In a Test Case that includes an app launch, home screen steps are skipped during execution.

See Test Case replay requirements.

Sessions can be converted into test cases even if unsupported actions were captured. Test cases that contain unsupported actions cannot be executed in a test run until those steps are removed and the test case is saved as a new version.