自动化测试时运行在uni-app Android模拟器时报错

自动化测试时运行在uni-app Android模拟器时报错

产品分类

uniapp/App

PC开发环境操作系统

Windows

PC开发环境操作系统版本号

23H2(0S内郚版本22631.4169)

HBuilderX类型

正式

HBuilderX版本号

4.61

手机系统

Android

手机系统版本号

Android 12

手机厂商

模拟器

手机机型

mumu模拟器

页面类型

vue

vue版本

vue3

打包方式

云端

项目创建方式

HBuilderX

示例代码：

// uni-app自动化测试教程: uni-app自动化测试教程: https://uniapp.dcloud.net.cn/worktile/auto/hbuilderx-extension/  

describe('test title', () => {  

    let page;  
    beforeAll(async () => {  
        page = await program.currentPage();  
        await page.waitFor(3000);  
    });  

    it('check page title', async () => {  
        const el = await page.$('.title');  
        const titleText = await el.text();  
        expect(titleText).toEqual('Hello');  
    });  

});

操作步骤：

点击初始uniapp自动测试环境，开启模拟器，点击自动化测试并选择Android环境，运行报错，测试不通过，使用adb连接模拟器，再次运行，报另一个错误但测试不会结束

预期结果：

测试正常进行

实际结果：

运行报错

bug描述：

在Android模拟器运行测试的时候报FailError: Failure: ‘device not found’，已经配置了Android模拟器端口号

13:49:15.021 [demo:android-127.0...] 项目 demo，开始运行 android 测试  
13:49:15.021 [demo:android-127.0...] 提示：如果Android测试设备没有正常运行提示，请检查手机跟电脑IP是否处于同一网段...  
13:49:16.690 [demo:android-127.0...] app-plus/launcher/android.ts init start  
13:49:16.690 [demo:android-127.0...] app-plus/launcher/android.ts init before adb.createClient  
13:49:16.690 [demo:android-127.0...] app-plus/launcher/android.ts init after adb.createClient  
13:49:16.702 [demo:android-127.0...] app-plus/launcher/android.ts init after debugClient init this.tool.version  
13:49:16.705 [demo:android-127.0...] app-plus/launcher/android.ts init before echo ${$EXTERNAL_STORAGE}  
13:49:16.728 [demo:android-127.0...] FAIL pages/index/index.test.js  
13:49:16.728 [demo:android-127.0...]   
13:49:16.728 [demo:android-127.0...] ● Test suite failed to run  
13:49:16.728 [demo:android-127.0...]   
13:49:16.728 [demo:android-127.0...]   
13:49:16.728 [demo:android-127.0...] FailError: Failure: 'device not found'  
13:49:16.728 [demo:android-127.0...]   
13:49:16.728 [demo:android-127.0...] at ../../../HBuilderX.4.08.2024040127/HBuilderX/plugins/hbuilderx-for-uniapp-test-lib/node_modules/adbkit/lib/adb/parser.js:183:29  
13:49:16.728 [demo:android-127.0...] at tryCatcher (../../../HBuilderX.4.08.2024040127/HBuilderX/plugins/hbuilderx-for-uniapp-test-lib/node_modules/bluebird/js/main/util.js:26:23)  
13:49:16.728 [demo:android-127.0...] at Promise._settlePromiseFromHandler (../../../HBuilderX.4.08.2024040127/HBuilderX/plugins/hbuilderx-for-uniapp-test-lib/node_modules/bluebird/js/main/promise.js:503:31)  
13:49:16.729 [demo:android-127.0...] at Promise._settlePromiseAt (../../../HBuilderX.4.08.2024040127/HBuilderX/plugins/hbuilderx-for-uniapp-test-lib/node_modules/bluebird/js/main/promise.js:577:18)  
13:49:16.729 [demo:android-127.0...] at Async._drainQueue (../../../HBuilderX.4.08.2024040127/HBuilderX/plugins/hbuilderx-for-uniapp-test-lib/node_modules/bluebird/js/main/async.js:128:12)  
13:49:16.729 [demo:android-127.0...] at Async._drainQueues (../../../HBuilderX.4.08.2024040127/HBuilderX/plugins/hbuilderx-for-uniapp-test-lib/node_modules/bluebird/js/main/async.js:133:10)  
13:49:16.729 [demo:android-127.0...] at Immediate.Async.drainQueues [as _onImmediate] (../../../HBuilderX.4.08.2024040127/HBuilderX/plugins/hbuilderx-for-uniapp-test-lib/node_modules/bluebird/js/main/async.js:15:14)  
13:49:16.729 [demo:android-127.0...]   
13:49:16.737 [demo:android-127.0...] Test Suites: 1 failed, 1 total  
13:49:16.737 [demo:android-127.0...] Tests:       0 total  
13:49:16.737 [demo:android-127.0...] Snapshots:   0 total  
13:49:16.737 [demo:android-127.0...] Time:        0.478 s  
13:49:16.737 [demo:android-127.0...] Ran all test suites.  
13:49:19.736 [demo:android-127.0...] Test results written to: ..\..\..\demo\android\127.0.0.1-202504141349.json  
13:49:19.744 [demo:android-127.0...] Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?  
13:49:19.757 [demo:android-127.0...] 测试运行结束。  

用adb连接了模拟器后还是会报device not found，但报错信息不一样了