Stego is primarily designed for developers, QA teams, and product managers who desire to increase the quality of their mobile apps. It can be the best solution for QA and development teams looking for a more convenient and efficient way to handle test process automation. In addition, it is composed of an intuitive design that people can use without programming knowledge, so it is convenient to write test scenarios fast.
Stego supports Android/iOS native, hybrid, and web apps.
Yes. When creating test scenarios in Stego, the actual devices are connected with USB and mirrored at the Stego. Additionally, completed Stego test scenarios can be uploaded to Apptest.ai Cloud to be tested on multiple phones.
No. Stego is a black box testing tool. This means that only the app binaries without the source code are needed. If the app’s binary file does not exist, don’t worry! We provide a handy feature to grab a binary from the app store using Package Name or Bundle ID.
Currently, Stego officially supports two languages, English and Korean. Stego can still be used in other languages, but Stego is not optimized for those languages. Please reach out to us to request for additional language support.
Stego can be installed and used on the following desktop/laptop.
Install Platform: Mac PC (M1 Mac, Intel Mac, Big Sur, Monterey, Xcode 12.1)
Minimum Free Space: 2GB
Other Platform: Coming Soon (Windows, Linux)
Please refer to the Stego installation manual emailed to you. If you have any issues with the installation or have any questions, please contact email@example.com.
The most frequent causes of installation failure are conflicts with the existing Stego version, Xcode version issues, Apple Developer ID-related settings, and other settings problems. As a first step before you consult us, we recommend uninstalling the previously installed Stego and reinstalling it. For additional issues, please contact firstname.lastname@example.org.
No. Stego is using the AI Vision service from apptest.ai, so it must be connected to the internet to fully leverage our solution.
First, check whether your test device is connected to your Mac/PC via a USB cable. If the connection error ever persists from Stego:
1) Quit Stego,
2) Reboot the test device (most important!),
3) Reconnect the USB cable to Mac/PC,
4) Restart Stego and connect the device.
If that doesn’t fix your problem, don’t hesitate to get in touch with email@example.com.
Yes, Stego can be connected and tested concurrently for up to 4 devices. Additionally, using the Apptest.ai Cloud, the Stego scenario can be tested with an unlimited number of devices.
The devices currently supported by Stego are smartphones (iOS, ANDROID). In addition, we plan to support IPTV set-top boxes in the second half of 2022. For other devices, please get in touch with us.
Stego supports all Android devices capable of USB debugging regardless of the country of manufacture.
You can disconnect the device by clicking the [x] button in Stego’s device list. Click the ‘Add’ button from the device screen to connect a new device. If you still have problems despite trying these methods, please get in touch with us at firstname.lastname@example.org.
You can click or scroll with the mouse as if you are using it directly on the screen of a mirrored device. Additionally, other user actions are supported from the toolbar on the right that is activated after connection. For details, refer to ‘Operating the device’ in the manual.
It depends, but it will be blazingly faster than the programming approach. In Stego, test scenario authoring is merely a recording of your simple touch-based gestures on the phone via the mirrored screen. It is enough to select the button/text in the GUI environment and save the corresponding action as Drag-n-Drop. In particular, Stego is an authoring tool, no-code, that is built by mimicking human motions. For authoring a simple test case (i.e, login test), beginners take an average of 10 minutes and experienced users an average of 5 minutes. Please refer to the enclosed user manual for more details on how to write a test scenario.
Yes. In particular, as it is a No-Code-based tool, even beginners can easily write test scenarios quickly.
You can export or import any Stego scenario (.zip format) and share it with other Stego users from your team. For more information, refer to the ‘Export Scenario’ section of the manual.
Stego’s scenario test job can be scheduled at your preference at Apptest.ai Furthermore, by linking your CI/CD with the Apptest.ai via open API, you can set the desired date, number, and device of the scenario created with Stego and receive detailed test reports periodically. For more details, please contact us at email@example.com.
If your Stego test scenario fails, please review the following:
1) Check device connection,
2) Check if Stego is connected to internet so that the Apptest.ai AI function is available,
3) Check if your login in the scenario is handling the triggered condition (i.e, unexpected popup or screen).
If the phenomenon stops after meeting a specific step, additional steps (e.g., if the next screen loading takes a long time, add a Wait action) may be necessary by looking before and after the corresponding step. In this case, please consider adding a conditional step. For other information, please contact us at firstname.lastname@example.org.
Read the user manual and other documents by Apptest.ai thoroughly. If you have any problems while creating scenarios or are unsure of any part, please contact email@example.com.
Stego has implemented a technology for AI to imitate how humans see the app with their own eyes and operate buttons on the app screen instead.
1) With our AI technology, Stego needs to recognize a specific UI, such as a particular button, which we call UIObject,
2) UIObject refers to a specific UIElement created through AI screen analysis,
3) OCR means UIObject in the form of text,
4) OD (Object Detection) is a recommended UIObject selected by AI,
5) finally, Relative means UIObject based on a relative value.
If you need further explanation of our technology, please refer to the user manual or contact us.