在 Android 上运行测试失败时不断收到错误消息
Posted
技术标签:
【中文标题】在 Android 上运行测试失败时不断收到错误消息【英文标题】:Keep getting an error when a test fails running tests on Android 【发布时间】:2020-07-08 14:00:00 【问题描述】:说明
免责声明:这也作为wix/Detox repo 的问题发布在github here 上,因此您可以更好地查看那里的图像。
在 android 模拟器上运行测试时,如果其中一个失败,则在测试报告的末尾会显示如下错误消息:
detox[8530] ERROR: [cli.js] Error: Command failed: node_modules/.bin/jest --config e2e/config.json '--testNamePattern=^((?!:ios:).)*$' --maxWorkers 1 "e2e"
如果所有测试都通过,则不会出现此消息,如以下屏幕截图链接所示: detox-success
您可以在下面查看测试失败时终端中显示的最后一部分:
Check device logs for full details!
13 |
14 | it("should have welcome screen", async () =>
> 15 | await expect(element(by.id("WelcomeScreen"))).toBeVisible()
| ^
16 | )
17 |
18 | // it("should go to next screen after tap", async () =>
at Client.execute (../node_modules/detox/src/client/Client.js:92:28)
at InvocationManager.execute (../node_modules/detox/src/invoke.js:11:39)
at MatcherAssertionInteraction.execute (../node_modules/detox/src/android/expect.js:128:35)
at ExpectElement.toBeVisible (../node_modules/detox/src/android/expect.js:275:112)
at _callee3$ (firstTest.spec.js:15:51)
at tryCatch (../node_modules/regenerator-runtime/runtime.js:45:40)
at Generator.invoke [as _invoke] (../node_modules/regenerator-runtime/runtime.js:271:22)
at Generator.prototype.<computed> [as next] (../node_modules/regenerator-runtime/runtime.js:97:21)
at tryCatch (../node_modules/regenerator-runtime/runtime.js:45:40)
at invoke (../node_modules/regenerator-runtime/runtime.js:135:20)
at ../node_modules/regenerator-runtime/runtime.js:170:11
at callInvokeWithMethodAndArg (../node_modules/regenerator-runtime/runtime.js:169:16)
at AsyncIterator.enqueue (../node_modules/regenerator-runtime/runtime.js:192:13)
at AsyncIterator.prototype.<computed> [as next] (../node_modules/regenerator-runtime/runtime.js:97:21)
at Object.exports.async (../node_modules/regenerator-runtime/runtime.js:216:14)
detox[9947] INFO: at e2e/login-screen-tests/login-screen.spec.js:99:9
detox[9947] INFO: at e2e/login-screen-tests/login-screen.spec.js:100:9
detox[9947] INFO: [DetoxServer.js] server listening on localhost:36337...
PASS e2e/login-screen-tests/login-screen.spec.js (18.825s)
Test Suites: 1 failed, 1 passed, 2 total
Tests: 1 failed, 2 passed, 3 total
Snapshots: 0 total
Time: 36.553s
Ran all test suites matching /e2e/i with tests matching "^((?!:ios:).)*$".
detox[9939] ERROR: [cli.js] Error: Command failed: node_modules/.bin/jest --config e2e/config.json '--testNamePattern=^((?!:ios:).)*$' --maxWorkers 1 "e2e"
您还可以在链接的屏幕截图中看到完整的报告(我缩小了一点以适应屏幕): detox-error
在下面的链接中,我展示了使用detox test -c android.emu.debug --loglevel trace
运行时的最后一部分:
detox-error2
我做错了什么?有人可以帮我找出问题所在吗?
复制
[X] 我已经在最新的 Detox 版本中测试过这个问题,它仍然可以重现
package.json
"name": "rmb-rn",
"version": "0.5.0",
"private": true,
"scripts":
"android": "react-native run-android",
"ios": "react-native run-ios",
"start": "react-native start",
"test": "jest",
"lint": "eslint index.js app --fix --ext .js,.ts,.tsx",
"test:e2e": "detox test -c ios.sim.debug",
"build:e2e": "detox build -c ios.sim.debug",
"ci:test:e2e": "detox test -c ios.sim.release -l verbose --cleanup",
"ci:build:e2e": "detox build -c ios.sim.release",
"compile": "tsc --noEmit -p . --pretty",
"format": "npm-run-all format:*",
"format:js": "prettier --write .,**/*.js",
"format:json": "prettier --write .,**/*.json",
"format:md": "prettier --write .,**/*.md",
"format:ts": "prettier --write .,**/*.ts,tsx",
"hack:types-react-navigation": "rimraf node_modules/@types/react-navigation/node_modules/@types",
"hack:types-react-native": "rimraf node_modules/@types/react-native/node_modules/@types",
"hack:types-react-test-renderer": "rimraf node_modules/@types/react-test-renderer/node_modules/@types",
"patch": "patch-package",
"postinstall": "node ./bin/postInstall",
"prepare": "npm-run-all patch hack:*",
"storybook": "(adb reverse tcp:7007 tcp:7007 || true) && start-storybook -p 7007",
"build-storybook": "build-storybook -c .storybook -o .out",
"adb": "adb reverse tcp:9090 tcp:9090 && adb reverse tcp:3000 tcp:3000 && adb reverse tcp:9001 tcp:9001 && adb reverse tcp:8081 tcp:8081"
,
"dependencies":
"@react-native-community/async-storage": "^1.5.1",
"@react-native-community/datetimepicker": "^2.2.2",
"@react-native-community/masked-view": "^0.1.7",
"@storybook/addon-actions": "^6.0.0-alpha.2",
"@storybook/addon-links": "^6.0.0-alpha.2",
"@storybook/addons": "^6.0.0-alpha.2",
"@storybook/react": "^6.0.0-alpha.2",
"@types/node": "^13.5.3",
"animated": "^0.2.2",
"apisauce": "1.1.1",
"babel-loader": "^8.0.6",
"i18n-js": "^3.0.11",
"lodash.throttle": "4.1.1",
"mobx": "5.15.0",
"mobx-react-lite": "^1.4.1",
"mobx-state-tree": "^3.14.1",
"moment": "^2.24.0",
"native-base": "^2.13.8",
"ramda": "0.26.1",
"react": "16.12.0",
"react-dom": "^16.12.0",
"react-native": "0.61.5",
"react-native-action-sheet": "^2.2.0",
"react-native-camera": "^3.19.1",
"react-native-contacts": "^5.0.7",
"react-native-device-info": "^5.5.3",
"react-native-gesture-handler": "^1.5.0",
"react-native-keyboard-listener": "^1.1.0",
"react-native-keychain": "4.0.1",
"react-native-localize": "^1.0.0",
"react-native-reanimated": "^1.4.0",
"react-native-safe-area-context": "^0.7.3",
"react-native-screens": "^2.0.0-alpha.6",
"react-native-snap-carousel": "^3.8.4",
"react-native-splash-screen": "3.2.0",
"react-native-uuid": "^1.4.9",
"react-native-vector-icons": "^6.6.0",
"react-navigation": "4.2.2",
"react-navigation-drawer": "^2.3.3",
"react-navigation-stack": "2.2.3",
"react-navigation-tabs": "^2.6.0",
"reactotron-mst": "^3.1.1",
"reactotron-react-native": "^4.0.0-beta.1",
"validate.js": "0.13.1"
,
"devDependencies":
"@babel/core": "^7.7.4",
"@babel/plugin-proposal-decorators": "^7.0.0",
"@babel/plugin-proposal-optional-catch-binding": "^7.0.0",
"@babel/runtime": "^7.7.4",
"@emotion/core": "^10.0.15",
"@storybook/addon-storyshots": "6.0.0-alpha.2",
"@storybook/react-native": "^5.3.9",
"@storybook/react-native-server": "^5.3.9",
"@types/jest": "25.1.4",
"@types/ramda": "0.26.36",
"@types/react": "16.9.13",
"@types/react-native": "0.60.23",
"@types/react-navigation": "3.4.0",
"@types/react-test-renderer": "16.9.1",
"@typescript-eslint/eslint-plugin": "2.9.0",
"@typescript-eslint/parser": "2.9.0",
"babel-jest": "^25.2.3",
"detox": "^16.0.1",
"emotion-theming": "^10.0.14",
"eslint": "^6.6.0",
"eslint-config-prettier": "^6.0.0",
"eslint-config-standard": "14.1.0",
"eslint-plugin-import": "^2.15.0",
"eslint-plugin-node": "10.0.0",
"eslint-plugin-promise": "^4.0.1",
"eslint-plugin-react": "^7.12.4",
"eslint-plugin-react-native": "^3.6.0",
"eslint-plugin-standard": "^4.0.0",
"ignite-bowser": "^4.11.3",
"jest": "^25.2.3",
"jetifier": "^1.6.1",
"metro-react-native-babel-preset": "^0.57.0",
"npm-run-all": "4.1.5",
"patch-package": "6.2.0",
"postinstall-prepare": "1.0.1",
"prettier": "1.19.1",
"react-devtools-core": "4.2.1",
"react-native-dotenv": "^0.2.0",
"react-powerplug": "1.0.0",
"react-test-renderer": "16.12.0",
"rimraf": "3.0.0",
"solidarity": "2.3.1",
"typescript": "3.7.2"
,
"jest":
"preset": "react-native",
"setupFiles": [
"<rootDir>/node_modules/react-native/jest/setup.js",
"<rootDir>/test/setup.ts"
],
"testPathIgnorePatterns": [
"/node_modules/",
"/e2e"
],
"transformIgnorePatterns": [
"node_modules/(?!(jest-)?react-native|react-native|react-navigation|@react-navigation|@storybook|@react-native-community)"
]
,
"detox":
"test-runner": "jest",
"configurations":
"ios.sim.debug":
"binaryPath": "ios/build/Build/Products/Debug-iphonesimulator/rmbRn.app",
"build": "xcodebuild -workspace ios/rmbRn.xcworkspace -scheme rmbRn -configuration Debug -sdk iphonesimulator -derivedDataPath ios/build -UseModernBuildSystem=NO",
"type": "ios.simulator",
"name": "iPhone 8"
,
"ios.sim.release":
"binaryPath": "ios/build/Build/Products/Release-iphonesimulator/rmbRn.app",
"build": "xcodebuild -workspace ios/rmbRn.xcworkspace -scheme rmbRn -configuration Release -sdk iphonesimulator -derivedDataPath ios/build -UseModernBuildSystem=NO",
"type": "ios.simulator",
"name": "iPhone 8"
,
"android.emu.debug":
"binaryPath": "android/app/build/outputs/apk/debug/app-debug.apk",
"build": "cd android && ./gradlew assembleDebug assembleAndroidTest -DtestBuildType=debug && cd ..",
"type": "android.emulator",
"device":
"avdName": "Nexus_4_API_28"
,
"android.emu.debug-real-device":
"binaryPath": "android/app/build/outputs/apk/debug/app-debug.apk",
"build": "cd android && ./gradlew assembleDebug assembleAndroidTest -DtestBuildType=debug && cd ..",
"type": "android.attached",
"name": "ce50806d386d"
,
"android.emu.release":
"binaryPath": "android/app/build/outputs/apk/release/app-release.apk",
"build": "cd android && ./gradlew assembleRelease assembleAndroidTest -DtestBuildType=release && cd ..",
"type": "android.emulator",
"device":
"avdName": "Nexus_4_API_28"
e2e 文件夹如下:
1) init.js
const detox = require("detox")
const config = require("../package.json").detox
const adapter = require("detox/runners/jest/adapter")
jest.setTimeout(120000)
jasmine.getEnv().addReporter(adapter)
beforeAll(async () =>
await detox.init(config)
)
beforeEach(async () =>
await adapter.beforeEach()
)
afterAll(async () =>
await adapter.afterAll()
await detox.cleanup()
)
2) config.json
"setupFilesAfterEnv": ["./init.js"],
"testEnvironment": "node"
3) firstTest.spec.js
测试失败的测试套件
describe("Example", () =>
beforeEach(async () =>
await device.reloadReactNative()
)
it('should be visible the account number', async () =>
const usernameInput = await element(by.id("loginScreen-accountNumber"))
await expect(usernameInput).toBeVisible()
)
// the failing test is below
it("should have welcome screen", async () =>
await expect(element(by.id("WelcomeScreen"))).toBeVisible()
)
)
预期行为
我相信,预期的行为是测试报告结束而不显示错误。
设备日志
adb_logs.log
环境:
排毒:16.0.1
React Native:0.61.5
节点:12.16.1
设备:AVD Android Studio Nexus 4 API 28
操作系统:Ubuntu 18.04.4 LTS
Test-runner(选择一项):Jest(如上图package.json
所示)
【问题讨论】:
【参考方案1】:错误是完全合法的,指出Detox
按预期工作。
在测试编排和执行方面,Detox
实际上只是实际测试运行器的包装——在您的情况下为Jest
(更好的选择 IMO :)。 setup guide 中提到了这一事实,并在更具体的 guide for setting up Jest 中进行了更详细的解释:
As already mentioned in the Getting Started guide, Detox itself does not effectively run tests logic, but rather delegates that responsibility onto a test runner.
Jest is the recommended runner for projects with test suites that have become large enough so as to require parallel execution.
反过来,这也会影响Detox
CLI 的作用——即使用适当的参数简单地执行测试运行程序。因此,总而言之,当所有测试都通过时,Jest 会成功且无声地结束。当某事失败时,Jest 记录一个错误,给出导致错误的线索,告诉每个人它失败了,并返回一个非 0 值。这与您所描述的完全一致。
【讨论】:
感谢您的澄清!我认为它会像所有测试通过时一样完成,而不会在最后抛出错误,但现在我明白了它是如何与 Detox 一起工作的。再次感谢!以上是关于在 Android 上运行测试失败时不断收到错误消息的主要内容,如果未能解决你的问题,请参考以下文章
运行cordova build android时出错(退出代码1)