- Getting Started with Test Suite
- Studio
- Orchestrator
- Testing robots
- Test Manager
- Change Impact Analysis
- Requirements
- Assigning test cases to requirements
- Linking test cases in Studio to Test Manager
- Unlink automation
- Delete test cases
- Document test cases with Task Capture
- Create test cases
- Importing manual test cases
- Generate tests for requirements
- Cloning test cases
- Exporting test cases
- Automate test cases
- Manual test cases
- Applying filters and views
- Test sets
- Executing tests
- Documents
- Reports
- Export data
- Bulk operations
- Searching with Autopilot
- Troubleshooting
Overview
- Low-code automations use a visual interface with drag-and-drop activities, making it accessible for a broad user base.
- Coded automations allow you to create automations using code, which is ideal for more complex and collaborative projects. These automations use UiPath® services (which are the equivalent of activity packages), APIs (similar to activities), external .NET NuGet packages, and your custom C# classes within Studio.
- Application testing involves test cases and data-driven test cases, along with verification activities from the Testing.Activities package, that allow you to create reliable automated tests.
- RPA testing covers all the specific cases and allows you to execute and manage the tests.
- API Test Automation works through Postman for calls related to testing and to APIs.
Mobile Device Automation offers you a platform for designing and running device automation without physically using the device. The solution works with various device types and connects to device farms and emulators, allowing you to easily record and automate steps taken on a mobile device. The Mobile Device Manager simplifies device interaction, and the available debugging tools help you in creating effective tests.
The structure of Mobile Device Automation consists of the following components:
Mobile device automation component | Description |
---|---|
Mobile Automation Activities (MobileAutomation.Activities) | The specific activities assist you in creating mobile automations by performing tasks like installing and managing apps, retrieving attributes, tapping UI controls, or printing out logs. |
Studio | Studio serves as the environment for creating the automation workflows for mobile devices. |
MDM (Mobile Device Manager) | A tool within Studio that connects to real or emulated devices through Appium. With MDM, you can record and perform actions, manage devices and applications, execute tests, and debug them. MDM supports Android, iOS, and Web for emulators and real devices connected through the cloud, your local network, or USB. |
Studio, along with the mobile automation activities allow you to create effective mobile tests. Meanwhile, the Mobile Device Manager bridges your actions and the devices to ease the process of mobile testing.
SAP Solution Manager integrates with Studio, allowing you to create automated tests that cover both SAP and non-SAP applications. SAP customers can run these test cases, exchange complex test data, and ensure the functionality of the Business Process Change Analyzer with TBOM Recording for automation projects. This integration also provides precise reporting with a consolidated view.
The process flow involves the following steps:
- Test Manager: Performs test executions, collects logs, transfers test data to SAP Solution Manager.
- Orchestrator: Manages the test executions.
- Robot: Executes the tests.