Creating autonomous exploratory tests with Ptero is simple and intuitive.
First, the login process is straightforward. After visiting the Ptero website, simply enter your email and password. Once logged in, you can create a team and invite members to collaborate and manage projects together.
The next step is to create a new project by entering details such as the project name, description, and the application to be tested. Then, configure the testing environment in the project settings by selecting the devices, browsers, and operating systems to be tested. Ptero provides cloud-based flexibility and scalability, enabling you to test across various devices and environments anytime, anywhere.
The cloud infrastructure supports fast and reliable testing, providing real-time monitoring and analysis of test results. Ptero enables users to effortlessly create and manage functional tests, automate the testing process, and continuously improve application quality.
Let’s make the most of Ptero’s diverse features and flexibility to perform more effective and reliable tests.
Sign Up #
You can sign up using a social account or a personal email.
① You can sign up with your GitHub or Google account.
② Alternatively, you can sign up directly using your personal email.
If you sign up with an email, you will need to verify it.
Please click the Verify your email in the verification email sent when you click the Sign Up.
Login #
1. Login with Social Accounts #
You can log in using your Github or Google account.
1) Login with Github #
Step 1. Go to the app.apptest.ai/login page.
Step 2. Click the 
above the fields where you enter your ID and password.
Step 3. Log in to Github.
2) Login with Google #
Step 1. Go to the app.apptest.ai/login page.
Step 2. Click the 
above the fields where you enter your ID and password.
Step 3. Log in to Google.
2. Login with Registered ID #
If you signed up using a personal email instead of a social account, you can log in by entering your ID and password.
Step 1. Go to the app.apptest.ai/login page.
Step 2. Enter the ID you used during sign-up.
Step 3. Enter the password you used during sign-up.
Step 4. Click the ‘Login’.
Creating a Team #
Ptero offers two types of teams: Personal Team and Standard Team.
– Personal Team: Automatically created as {Username}’s team based on the logged-in user’s name. This team includes only the logged-in user, and additional users cannot be added.
– Standard Team: Multiple users can join, with roles divided into admin and member for team management.
Step 1. Click the Team Select Menu in the upper right corner and select “Create New Team”.
Step 2. Enter the name of the team you want to create in the ‘Team Name’.
Step 4. Click the ‘Create’.
Team Settings #
To configure detailed team settings, first click the Team Settings button in the left menu bar.
1. Team Info #
- Team Name: Set your team name.
Team names must be unique across the entire service.
Personal teams (in “Username’s Team” format) cannot be renamed, and team name changes are restricted to users with Admin privileges. - Max Test Count: Indicates the maximum number of tests that can run simultaneously.
This value cannot be edited and follows the Concurrency value set in the team’s Billing Manager. - Delete Team: Provides team deletion functionality.
Personal teams cannot be deleted and the delete button is not displayed.
Only users with Admin privileges can delete teams.
Deleting a team removes all associated data (projects, test suites, scenarios, tests, schedules).
2. Members #
- Email Notification : Configure team test result email notifications.
Admin users can configure this for the team, while regular members can only change their own account settings. - Billing Manager : Manages the team’s billing and payment information and can set the Current Test Count.
– Personal Teams: The team owner is automatically assigned as the Billing Manager and cannot be changed.
– Regular Teams: The Billing Manager can be assigned from users with Admin privileges. - Role : Manage user permissions within the team.
– Admin: Teams must have at least one Admin who can invite other members.
– Member: Cannot change team member settings but can modify their own email notification settings. - Member Removal : Remove members from the team.
Only users with Admin privileges can remove members.
In personal teams, the owner cannot be removed.
3. Lables #
Step 1. Click the Labels button in the top menu bar to create labels.
Step 2. Click the + Add Label button in the upper right corner.
Step 3. Enter the desired Label name in Label Name.
Step 4. Click the Add button.
Step 5. Click the 
icon on the Test where you want to apply the label.
Step 6. Click the Label you want to apply from the Label list.
Step 7. Click the Apply button.
4. Alarm Settings #
Step 1. Click the Alarm Settings button in the top menu bar to configure alarms.
Step 2. Click the + Add Alarm button.
Step 3. Click Recipient to select members or teams for error notifications.
Step 4. Click Project to select projects to receive or exclude from error notifications.
Step 5. Click the Activate Execution button to enable or disable error notifications.
Step 6. Click the Apply button.
5. All Schedules #
To view all schedules operating in the team, click the All Schedules button in the top menu bar to access the complete schedule screen.
6. Status Change History #
To check the status value history of tests in progress within the team, click the Status Change History in the top menu bar.
This screen displays records of tests with changed status, including unique test numbers, project names, scenario and Test Suite names, Device/OS, changed Status information, modification date, and the account that made the modification.
Creating a Project #
1. Mobile App #
Step 1. To perform an Mobile App test, click Mobile App from the left menu bar.
Step 2. Click the Create New Project button located on the upper-right side of the Project page.
Step 3. Enter the project name in the Project Name.
Step 4. Enter the App ID (Package Name for Android / Bundle ID for iOS) for the app you wish to test.
Step 5. Click the Create.
2. Browser #
Step 1. To perform a web autonomous test, click Browser from the left menu bar.
Step 3. Click the Create New Project located at the top right of the project page.
Step 4. Enter the project name in the Project Name.
Step 5. Click the Create.
Project Settings #
After creating a project, you can configure it to suit your testing needs.
Once set, the configurations are automatically loaded for future tests, making it easier to start tests.
1. Mobile App #
Test Runs #
Selecting a project opens its Test Runs tab.
1. Run Result Overview #
- Provides test execution data based on records from the past 24 hours, 3 days, and 7 days. The data includes the total number of test runs, success rate, number of passed and failed tests, and average execution time.
2. Recent Test Runs #
- Displays the latest 50 test results.
Test Suites #
A Test Suite is a unit that groups multiple test scenarios for execution.
In the Test Suites tab, you can create and manage test suites. For more details, refer to Creating Mobile App Test.
Schedules
In the Schedules tab, you can create and manage test schedules. For more details, refer to Schedule Settings.
Device #
Set the devices to be used for testing.
By default, all available Android and iOS devices are used.
Paid users can click the Add to choose specific devices for testing.
Once selected, the test will only be conducted on those devices unless you re-enable the Use All Device.
* Free users can only test on one randomly selected device.
The image above shows the devices added by clicking the ADD.
Once the devices for testing are set, you can verify the selected devices by entering the test execution page and clicking DEVICE. Only the configured devices will be displayed.
Settings 탭 #
You can access the Settings tab by clicking Settings,
or the gear icon next to the project name in the project list.
Project settings include four main tabs: Detail, Test Settings, Application and User Defined Failure And Warning Message.
Detail #
Edit the basic project settings.
- PROJECT NAME : Set the name for your project. Names must be unique within your team and can be up to 100 characters long.
- Project Icon : Configure your project icon. You can set it by entering an Icon URL, and the icon will be displayed in the project list.
- Test in Parallel : Determines whether Test Suites within a project run concurrently. This option is enabled by default; if disabled, Test Suites will execute sequentially.
Test Settings
You can modify detailed project settings.
- Test Duration : Set the time limit for tests. Tests automatically terminate after the set duration, which can be configured between 1 and 1440 minutes (24 hours).
- Pre-Test Execution Settings : Configure settings required before test execution.
– Device Language: Set the default language for the device.
– Resigning Application File: Configure whether to resign iOS application files. Default is True. - Test Execution Settings : Configure settings required during test execution.
– Record video for each steps: Enable/disable video recording for each step. Default is True.
– Enable network capture for analysis: Set up network capture functionality. Choose between Chrome devtools (default) or HTTP proxy.
– Enable Lighthouse for performance measuring: Activate Lighthouse functionality for performance measurement.
– Enable Video Optimizer for performance measuring: Activate Video Optimizer functionality for performance measurement.
– Enable JaCoCo code coverage measurement: Activate code coverage measurement for Android applications. - Advanced Settings : Configure advanced options for test execution.
– Store Type: Set the store type for app installation. Defaults are PlayStore for Android and AppStore for iOS. TestFlight is also available for iOS.
– Minimum Device OS Version: Set the minimum OS version required for app execution. Can be configured separately for Android and iOS. Devices are allocated from the Queue based on the specified version requirements.
– Enable Page Load Time Measurement: Configure collection of Time to Interactive (TTI) information. Default is false.
– Clear Application Data: Set whether to clear target application data. Use this to clear data for apps registered in deletion prevention. Default is false.
– Enable Chrome Fetch Domain in HAR Logs: Configure the use of Chrome fetch logs when collecting HAR data. Default is false.
– Monitoring IPs for Network in HAR Logs: Set IP addresses for health checks during testing. Ping commands are sent to configured IPs to log device network connection status.
– Custom Ruleset Alias: Configure aliases for custom rules used in autonomous exploration. Specify aliases within rule files that determine when specific scenarios are executed.
– Allow Exploration for Specific App IDs: Set the list of packages allowed for autonomous exploration. - Environment Variables : Configure Key-Value pairs for new feature development or existing features provided without UI using this functionality.
Application
You can either enter the Package Name (or Bundle ID) of the app you want to test, or upload the APK file (or IPA file) for testing. When starting the test, the system checks if the app with the specified Package Name (or Bundle ID) is installed. If not installed, it will download the app from the Play Store (or App Store) before initiating the test.
For APK files (or IPA files), the test begins after installing the uploaded file. If the same app is already installed on the device, it will be overwritten.
User Defined Failure And Warning Message
e.g. If Apptest.ai is set to detect “Sample” as a Warning, but configured as shown in the image above, it will be detected as an Failed during the test.
2. Browser #
Test Runs #
Selecting a project opens its Test Runs tab.
- Run Result Overview : Provides test execution data based on records from the past 24 hours, 3 days, and 7 days. The data includes the total number of test runs, success rate, number of passed and failed tests, and average execution time.
- Recent Test Runs : Displays the latest 50 test results.
Test Suites #
A Test Suite is a unit that groups multiple test scenarios for execution.
In the Test Suites tab, you can create and manage test suites. For more details, refer to Creating a Web Test.
Settings
Project settings include three main tabs: Detail, Test Settings, and Application.
Detail #
Edit the basic project settings.
- PROJECT NAME : Set the name for your project. Names must be unique within your team and can be up to 100 characters long.
- Project Icon : Configure your project icon. You can set it by entering an Icon URL, and the icon will be displayed in the project list.
- Test in Parallel : Determines whether Test Suites within a project run concurrently. This option is enabled by default; if disabled, Test Suites will execute sequentially.
Test Settings #
- Test Duration (min) : Set the time limit for tests. Tests automatically terminate after the set duration, which can be configured between 1 and 1440 minutes (24 hours).
- Pre-Test Execution Settings : Configure settings required before test execution.
– Locale : Uses the internet network of the selected region. - Test Execution Settings : Configure settings required during test execution.
– Enable network capture for analysis : Set up network capture functionality.
– Enable Lighthouse for performance measuring : Activate Lighthouse functionality for performance measurement.
Application #
Enter the URL to be tested.