Here are answers to some common questions.

1. General Information

Q. Who should use Apptest.ai Service and why?

Apptest.ai is ideal for any individual or company engaged in software or mobile app development. In today’s dynamic and device-diverse market, mobile app testing can be particularly challenging.


Our platform provides a robust test automation solution tailored to meet these challenges, featuring the test automation cloud (Ptero) and test scenario authoring tool (Stego).


Ptero is comprised of a powerful AI-based test engine, a visualization dashboard, and access to a diverse range of real devices in our device farm.


By leveraging both Ptero and Stego, developers can significantly increase test coverage and streamline the app testing process, effectively reducing the time to market and elevating product quality.

Q. Does Apptest.ai Service support devices other than smartphones?

Yes, Apptest.ai Service supports a variety of devices including smartphones (iOS and Android), and IPTV set-top boxes (Android).

Q. Which types of applications can Apptest.ai test?

Apptest.ai supports a wide range of applications, including Android and iOS native apps, hybrid apps, and web-based applications.

Q. Does Apptest.ai use simulators or emulators for testing?

No, Apptest.ai performs UI-based blackbox testing using real devices in our device farm.

Q. How do I upload an app binary file for testing?

Yes, you can directly upload your IPA or APK file for testing to Ptero.

Alternatively, if your app is available on the Apple App Store or Google Play Store, you can simply provide the Bundle ID or package name. We will then download the app to the test device for testing.

Q. What languages does Apptest.ai Service support?

Apptest.ai Service officially supports English and Korean. While it can be used in other languages, it is not optimized for them.

If you require support for additional languages, please contact us for support.

2. Ptero: Test Automation Cloud

Q. What is Ptero (Test Automation Cloud)?

Ptero is an integrated test automation cloud consisting of a Web Client, Test Engine, AI Engine, and Device Farm.


Users can schedule test sessions and manage results in one place, obtaining visualized insights through customizable dashboards.


In a cloud-based system, autonomous exploratory and scenario testing using AI technology can be performed, providing a more efficient and automated testing environment.

Q. How long does Apptest.ai store my test results and related files?

Apptest.ai stores test results, screenshots, and related logs on our servers for a default retention period of up to three months. You also have the option to manually delete your files and results at any time.

Q. Does Apptest.ai clean up devices after testing?

Yes, after each test session is completed, Apptest.ai ensures that all devices are cleaned up, which includes restoring them to their default settings and uninstalling your app from the test devices.

Q. Does Apptest.ai modify my app for testing?

No, Apptest.ai does not modify your app in any way during the testing process.

Q. How can I schedule a test?

You can schedule test jobs at your convenience using Ptero web client.
For detailed instructions on setting this up, please refer to the manual here.


Additionally, by integrating your CI/CD system with Ptero through our Open API,
You can specify the timing, frequency, and devices for the scenario authored in Stego and receive detailed test results on a regular basis.

Q. What information is included in an Apptest.ai test result?

Apptest.ai delivers comprehensive test results via our web client. This includes a test summary, step-by-step screenshots, device logs showcasing CPU/memory usage and network performance, and an activity map.

Q. Do Apptest.ai test results include device logs?

Yes, Apptest.ai test results provide device logs for both Android and iOS platforms, helping you diagnose issues and improve app performance.

3. Stego: Test Scenario Authoring Tool

3.1 General Information
Q. What is Stego and what are its benefits?

Stego is Apptest.ai’s test scenario authoring tool, developed using state-of-the-art AI technology. Its simple drag-and-drop operation makes it exceptionally easy to use. One of its key benefits is that it requires no coding experience; users can author scenarios simply by interacting with UI flows on the mirrored test device.

Q. What are the system requirements for installing Stego?

Stego is compatible with Mac and Windows platforms. (Stego is not supported on Linux OS)


OS : Monterey or higher (iOS 17 device requires Sonoma.)
Processor : Apple silicon / Intel i5 or higher
Memory : 4GB RAM or higher


OS : Windows 10 or higher
Processor : Intel i5 / AMD FX Series or higher
Memory : 4GB RAM or higher

Q. How do I install Stego?

You can download Stego by clicking this link and follow detailed installation manual here. If you have any questions, please contact us at stego.support@apptest.ai.

Q. What should I do if Stego fails to install on my PC or Mac?

Installation failures often arise from version conflicts.
You can try uninstalling any previously installed versions of Stego and Xcode (for Mac only) and then try reinstalling.


For detailed guidance, please refer to the manual here.
If you need further assistance, please contact us at stego.support@apptest.ai.

Q. Can Stego be used offline?

No, Stego requires an internet connection to function properly as it utilizes the AI Engine from our Test Automation Cloud (Ptero).

Q. What types of apps does Stego support?

Stego supports test scenario authoring for Android and iOS native apps, hybrid apps, and web applications.

Q. Does Stego use real devices for authoring test scenarios?

Yes, real devices are used for authoring test scenarios.

Q. Is the app source code required to use Stego?

No, Stego is a black box testing scenario authoring tool and does not require any source codes.

3.2 Test Device
Q. What should I do if Stego does not recognize a connected device?

First, verify that your test device is properly connected to your Mac or PC via a USB cable.


Then, perform the following steps:

1. Quit Stego.
2. Disconnect the USB cable from your Mac or PC.
3. Reboot the test device—this step is essential.
4. Reconnect the USB cable to your Mac or PC.
5. Restart Stego and attempt to connect the device again.
6. If the above steps do not resolve the issue, please reboot the Mac or PC where Stego is installed and repeat steps 4-5.


For detailed instructions, please refer to the manual here.

If these steps do not resolve the issue, please contact us at stego.support@apptest.ai.

Q. Can a single scenario be tested on different device types/models or OS?

Yes, you can author a test scenario with up to four devices concurrently.
This ensures efficient and comprehensive testing across multiple devices within a single scenario.
Once the scenarios authored with Stego are uploaded to Ptero, they can be scheduled to be tested on multiple devices in parallel.

Q. I want to disconnect the device and connect to a new one. What should I do?

To switch devices in Stego, start by disconnecting the current device; simply click the [x] button in Stego’s device list.
Then, click the ‘Add’ button on the device screen to connect a new device.


For detailed instructions, please refer to the manual here.
If you encounter any issues during this process, please contact us at stego.support@apptest.ai for support.

Q. Can I control the connected device through mirrored screen?

You can control the mirrored device screen using your mouse to click or scroll,
just as you would directly on the device itself.


Additionally, Stego provides various user actions through a toolbar on the right side of the mirrored screen, which becomes available once the device is connected.


For more detailed instructions on how to control the device, please refer to the manual here.

3.3 Test Scenario
Q. How long does it take to author a test scenario in Stego?

Simple test scenarios can be authored within minutes, such as searching for a specific app and starting it.
Because Stego is a no-code authoring tool designed to replicate human actions on touchscreens, it significantly simplifies the creation of test scenarios.

Q. Can someone with no prior programming experience author a test scenario?

Absolutely! Stego is a no-code tool that utilizes a simple drag-n-drop interface, which means there is almost no learning curve.
Even beginners can easily author test scenarios from day one.

Q. How can I share my test scenario with my team?

You can share your test scenario by utilizing downloading and uploading features.
This functionality transfers test scenarios from one account to the other.


For step-by-step instructions on how to use these features, please refer to the manual here.

Q. What should I do if my test scenario fails?

Here are some tips on how to troubleshoot:

1. Ensure that the device is properly connected.
2. Verify that Stego is connected to the internet, as it relies on the Ptero AI Engine for vision-based screen analysis.


For more troubleshooting tips, please refer to the manual here.

Q. What is a shared scenario and how do I use it?

Shared Scenario serve as building blocks for constructing test scenarios.
They allow you to create simple actions that can be reused in different scenarios.

E.g. login scenario – this captures all the actions associated with logging into a page.


Steps for creating a shared scenario:
1. Use the scenario editor to create the scenario.
2. Save the test scenario file.
3. Drag and drop the saved scenario file to Shared Scenario section.


Steps for using Shared scenario:
1. Open the scenario editor and add a new step.
2. Select “Shared Scenario” from the “Action” dropdown menu.
3. Drag and drop the shared scenario into the designated step.

Q. Can you explain what do UIObject, OCR, OD, and Relative mean?

Here’s a breakdown of these terms as used in Stego:

1. UIObject
This term refers to a specific user interface element, such as a button, that the AI Engine recognizes through its screen analysis. It represents a distinct element on the screen.


2. OCR (Optical Character Recognition)
This process enables the AI Engine to recognize text-based UIObjects, allowing interactions with text elements on the screen.


3. OD (Object Detection)
This process involves the AI Engine scanning the screen to detect UI elements like buttons or text fields that users can interact with through gestures.


4. Relative
This term is used when a UIObject is defined by its position relative to other UI elements, rather than by its absolute position on the screen.


For a more detailed explanation of these technologies and how they are implemented in Stego, please refer to the manual here.

4. Autonomous Exploratory Test

Q. What is Autonomous Exploratory Test?

Autonomous exploratory testing is a UI based and non-functional black-box testing method performed entirely by AI without human intervention.


This approach allows the AI Testbot to autonomously navigate and explore the application, aiming to discover errors related to app stability, such as forced terminations or error messages.


This testing eliminates the need for development resources during the initial setup and ensures zero maintenance overhead, even when the application or service environment is updated.


The AI not only tests the application continuously to achieve 100% test coverage but also can automatically generate test cases based on the outcomes of its autonomous exploration, thereby enhancing overall testing efficiency.

Q. Are the Google Play Store and Apple App Store accessible on your test devices?

Yes, each iPhone in our device farm comes equipped with the App Store,
and all Android devices have the Google Play Store installed, allowing for comprehensive app testing.

Q. Is there a default account logged in on Android and iOS devices?

Yes, each device in our device farm is logged in with a default account.

Q. Can I simulate interactions with external apps or devices during my app testing?

Currently, our platform does not support the integration of external devices or apps during autonomous exploratory testing.
However, if you have specific test scenarios that involve external interactions, you can use Stego, to author and execute these test scenarios.

Q. Can I install and test multiple apps simultaneously for cross-app functionality?

No, our standard setup permits the installation of only one app at a time for autonomous exploratory testing.
However, using Stego, you can author and execute scenarios that involve testing multiple apps simultaneously.

Q. Can I test my app with specific location settings?

Currently, our product does not support location simulation for testing specific GPS coordinates.

Q. Is it possible to conduct localization tests by changing the device language?

Yes, our platform supports testing in both English and Korean.
If you need to test in additional languages, please contact us for support.

Q. How quickly does testing begin?

Tests are immediately placed in the queue and typically start within a few minutes, depending on the availability of the test device.

Q. What is the maximum duration for an app testing session?

Currently, each app testing session is limited to 30 minutes.
If you require a longer duration for testing, please contact us for support.

Q. My app serves ads. Will they be displayed on your devices? Would there be any issues with my ad provider?

Ads in your app will be displayed during testing on our devices.


During autonomous exploratory testing, our AI test bot is programmed to interact with an ad once and then proceed to explore other areas of the app.
This approach is intended to prevent the occurrence of ad abuse conditions.


The handling of ads in test scenarios depends on how they are authored, so care should be taken when designing these tests to ensure compliance with ad provider policies.

5. Device Farm

Q. What is Device Farm?

A device farm is a cloud-based platform or service that provides access to a large variety of physical mobile devices for testing purposes.


It allows developers and testers to remotely access real devices over the internet to run tests, debug applications, and ensure compatibility across different devices, operating systems, and screen sizes.


Device farms typically offer features such as automated testing, manual testing, debugging tools, and device management capabilities.


This helps streamline the testing process, improve test coverage, and ensure the quality of mobile applications before they are released to users.

Q. What types of devices does Apptest.ai use for testing?

Apptest.ai performs testing on real devices, supporting both iOS and Android platforms.
Our device farm features a wide range of models, including Apple iPhones and Samsung Galaxy devices.
If you need testing on a device not currently available in our device farm, please contact us for support.

Q. Are there pre-installed apps on devices in the Apptest.ai device farm?

Yes, devices in our device farm come with a number of apps that are pre-installed by the device manufacturer or carrier.

Q. How do devices in the Apptest.ai device farm connect to the internet?

All devices in our device farm are connected to the internet over Wi-Fi.

Q. Is it possible to test using different carrier connections?

Currently, all our test devices connect to the internet via Wi-Fi.
If you need to test using a carrier SIM to simulate different network conditions, please contact us for support.

Q. Can your test devices make phone calls or send SMS/MMS messages?

Our devices in the device farm are not equipped with carrier SIMs, therefore, they cannot make phone calls or send SMS/MMS messages.

If your testing requirements include these capabilities, please contact us for support.

Q. Is the camera function available on your test devices?

Yes, you can utilize both the front and rear-facing cameras on the devices in our device farm.

6. Miscellaneous