在码头容器上运行空手道测试时被覆盖的Chrome可执行文件 [英] Chrome Executable getting overriden while running the Karate test on a docker container
本文介绍了在码头容器上运行空手道测试时被覆盖的Chrome可执行文件的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
下面您可以看到空手道驱动程序的配置如下。之后它尝试使用user-data-dir,然后是位置。如何使用Chrome可执行文件路径的--user-data-dir禁用该进程:
build-env_1 | 12:10:42.702 [ForkJoinPool-1-worker-1] INFO com.intuit.karate - Karate Driver config:
build-env_1 | {
build-env_1 | "type": "chrome",
build-env_1 | "executable": "/usr/bin/karate_chrome_driver",
build-env_1 | "port": 9515,
build-env_1 | "httpConfig": {
build-env_1 | "readTimeout": 120000
build-env_1 | }
build-env_1 | }
build-env_1 | 12:10:42.727 [ForkJoinPool-1-worker-1] WARN com.intuit.karate - type was null, defaulting to 'chrome'
build-env_1 | 12:10:42.754 [ForkJoinPool-1-worker-1] DEBUG com.intuit.karate.shell.Command - found / verified free local port: 9222
build-env_1 | 12:10:42.759 [chrome_1603973442746] DEBUG c.i.k.driver.chrome_1603973442746 - command: [/usr/bin/google-chrome, --remote-debugging-port=9222, --no-first-run, --user-data-dir=/usr/regression/target/chrome_1603973442746, --disable-popup-blocking]
build-env_1 | 12:10:42.762 [ForkJoinPool-1-worker-1] DEBUG c.i.k.driver.chrome_1603973442746 - poll attempt #0 for port to be ready - localhost:9222
build-env_1 | 12:10:42.762 [chrome_1603973442746] ERROR com.intuit.karate.shell.Command - command error: [/usr/bin/google-chrome, --remote-debugging-port=9222, --no-first-run, --user-data-dir=/usr/regression/target/chrome_1603973442746, --disable-popup-blocking] - Cannot run program "/usr/bin/google-chrome" (in directory "target/chrome_1603973442746"): error=2, No such file or directory.
推荐答案
抱歉,您似乎试图混合使用空手道chrome
,并希望它使用chromedriver
。这不受支持。可执行文件应为Chrome可执行文件本身或默认可执行文件(推荐)。
也要阅读文档。如果使用chrome
,您可以将userDataDir: null
添加到配置中,这样就不会在命令行中使用它。
https://github.com/intuit/karate/tree/master/karate-core#configure-driver
这篇关于在码头容器上运行空手道测试时被覆盖的Chrome可执行文件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文