For now, the implementation of CI/CD in the testing workflow for the mobile app team is limited to the CI phase. The CD process itself is still separate.
At a considerable level, this concept still combines with traditional execution. This means you need to download the latest build for Android and iOS in AppTester, and then run it with a Jenkins pipeline. After that, the whole process will run automatically. Currently, the automation test only runs on Android and has covered around +70 test scenarios (mixing tests for widget, functionality and data), and the entire automation test suite takes about ~20 minutes (depending on API response and device stability).
The idea was: how do we enforce all pipelines to run automatically?
Basically, the process will change: every time developers do a build, it triggers Jenkins to automatically run the pipeline, which then triggers our test agents to execute automation tests. When finished (either passed or failed), it sends the report to a DingTalk group and combines with manual testing. When finished, it is released as a new version.