Kobiton 4.13.3S release notes

Test Suites: Previously, test cases had to be run one by one. Now, you can organize your test cases into suites and initiate a test run to test a set of test cases across multiple devices.

Test Cases: Creating a test case is now more intuitive. Use the Convert to Test Case option instead of Automated Test Case option in Session Explorer, or create a new test case directly from the Test Case List by searching for a session. We’ve also introduced a new Test Case Details screen, enhancing your control over test cases. Here, you can delete or remediate test steps, create different versions of a test case, or clone an existing test case.

Test Runs: Gain complete oversight of your testing efforts with our new test runs interface. View a comprehensive list of all your test runs, initiate new Test Runs, and access detailed, actionable insights from your Test Run results - all designed to streamline your testing process.

All users can create, view, and manage test cases and test suites.

Only users with Scriptless in their subscription can initiate test runs.

Only users with Appium Script Generation in their subscription can generate Appium Scripts.

The team assignment of test cases, test suites, and test runs is inherited from the baseline session from which they are created.

If the baseline session is created at the organization level, then test cases, test suites, and test runs created from it can only be accessed by users with the ADMIN predefined role who have selected the organization level from the team menu.

If the baseline session is created at the team level, then test cases, test suites, and test runs created from it can only be accessed by users assigned to that team who have selected that team from the team menu.

Clear indications of the unsupported actions are displayed in test steps.

All steps containing unsupported actions must be removed from a test case before test runs can be triggered.

Launching Test Runs: test runs can be launched via:

Testing Capabilities: With the Beta release, only crash and accessibility validations are available. We are actively developing performance, text/color, and visual validations. Data-driven testing is not supported in the Beta, but will be added in a future release.

Test Run Statuses:

Search and filters:

Blocker Remediations: When a Blocker is encountered for a Touch action during a test run, you can now remediate the step where the Blocker happened or review and remediate in a previous step. The submitted remediation will apply to subsequent reruns from the same test case and on the same device model.

Create Test Case from Appium script: We do not currently support creating a Test Case from an Appium script using scriptless:enable with this Beta version. We will reintroduce that feature in an upcoming release.