In this update, Dogu's major version has been changed! With this update, we have addressed the issue of specifying the app version in routines, improving convenience. We have also introduced the ability to apply and configure licensing (pricing) policies in self-hosted environments. Take a closer look!👀
✨ Run routine with latest app
In the previous v1.11.0 update, we introduced support for Routine with mobile app and games. Routine was structured as follows at that time.
name: app_test
on:
workflow_dispatch:
jobs:
test-android:
runs-on:
group:
- android
appVersion:
android: 1.0.0
record: true
steps:
- name: run test
uses: dogu-actions/run-test
with:
checkout: true
environment: python
command: |
pip install -r requirements.txt
pytest app/test_android.py --capture=no -x
cwd: app/python/pytest
This involves locating and installing an app with version 1.0.0 on all devices with the android tag and executing a test script while performing routines. You can run routines and view the results. So far, everything seems fine!
However, when integrating routines with CI, there is a slight inconvenience. Why is that? It's because the routine mentioned above always runs an app with version 1.0.0. During the process of uploading the app built in the CI workflow, the app version can dynamically change. Therefore, Dogu defines the latest app based on the app build version and specifies the app package name in routines, allowing you to run the latest app with that package name! Awesome!😎
The above routine can be replaced with the following:
name: app_test
on:
workflow_dispatch:
jobs:
test-android:
runs-on:
group:
- android
appPackageName:
android: com.dogu.sample
record: true
steps:
- name: run test
uses: dogu-actions/run-test
with:
checkout: true
environment: python
command: |
pip install -r requirements.txt
pytest app/test_android.py --capture=no -x
cwd: app/python/pytest
In this routine, it locates the app among the uploaded apps with the package name com.dogu.sample and selects the one with the highest build version to execute.
Furthermore, you can also see which app is the latest one in the project app list from the console!
✨ License policy and configuration for self-hosted
The reason for the change in Dogu's major version is as follows. Our team members engaged in extensive discussions and deliberations regarding the Dogu's direction and business model, considering various valuable insights. Initially, decisions were made after converging on several key points.
Firstly, in the self-hosted environment, there will be differences in functionality between the Community Edition and the Professional Edition. These differences will encompass the number of devices and runners available, routine CI integration, and additional support features such as technical support.
For detailed information about the Professional Edition or inquiries regarding experiencing it, please visit the Pricing page below.
As a result of this, we have introduced the concept of a root user in the self-hosted environment. When you first run in the self-hosted mode, you can now sign up with a root account and configure license.
In self-hosted Dogu, if you are a root user, you will find the "Admin settings" menu in the top header - Profile menu. Clicking on that menu will take you to a page where you can set up your license.
There are a few things to set up to register your license in a self-hosted environment, visit our guide!
In the cloud environment, it appears that there will be different pricing plans prepared in a different way. We will provide further guidance on this through future updates.
✨ Browser screen records in routine result report
One of the most helpful things you can find in your test results report is a video recording of your test screen. If a test fails, you can intuitively see why it failed. This feature was previously only available for mobile apps and games, but this update brings it to the web!
Browser records in routine result report
✨ Host device with runner
In Dogu, a host machine can also be used as a device. In this case, the host device is special and can have multiple Runners. You'll use these Runners when you run web tests on the host device, and you'll use one Runner for one browser.
Runners can now be changed in the Runner settings menu. Just enter how many browser runners you want to use!
Host device with runners
Now, when you run the web test using the host device, the usage state of each runner will change. If you run the test on the Chrome, Safari, and Firefox browsers at the same time, runners 1 through 3 will change to the running state.
Wrapped up
In this update, we've improved usability by using package names instead of app versions in routines, provided browser recordings in web test results reports for richer results. Furthermore, we bumped up the major version to self-hosted with licensing. We're offering a free trial on self-hosted, so give it a try!
If you have any questions or need assistance, feel free to reach out via email at contact@dogutech.io, or consider joining our Dogu Slack Community where you'll find a warm welcome and support. We're always here to help!
Happy Testing!
Top comments (0)