2017-12-29 59 views
1

https://github.com/blizzerand/pastebin-angularをダウンロードして、 "ng test"または "npm run test"同じ)。"ng e2e"はおそらくプロキシの理由で面倒ですが、 "ng serve"と "ng test"が動作しています

C:\_pocs\ws_vsc\pastebin-angular-master>npm run test 

    > [email protected] test C:\_pocs\ws_vsc\pastebin-angular-master 
    > ng test 

    10% building modules 1/1 modules 0 active29 12 2017 18:13:27.927:WARN [karma]: No captured browser, open http://localhost:9876/ 
    29 12 2017 18:13:27.998:INFO [karma]: Karma v1.7.0 server started at http://0.0.0.0:9876/ 
    29 12 2017 18:13:28.002:INFO [launcher]: Launching browsers Chrome, ChromeNoSandboxHeadless with unlimited concurrency 
    29 12 2017 18:13:28.013:INFO [launcher]: Starting browser Chrome 
    29 12 2017 18:13:28.032:INFO [launcher]: Starting browser Chrome    29 12 2017 18:13:39.229:WARN [karma]: No captured browser, open http://localhost:9876/ 
    29 12 2017 18:13:40.708:INFO [HeadlessChrome 0.0.0 (Windows 10 0.0.0)]: Connected on socket UDrOcB34PHgK-7M-AAAB with id 48647093 
    29 12 2017 18:13:40.708:INFO [Chrome 63.0.3239 (Windows 10 0.0.0)]: Connected on socket 8ZsdfQHAmDKzVaoHAAAA with id 86143812 
    Chrome 63.0.3239 (Windows 10 0.0.0): Executed 31 of 31 SUCCESS (3.745 secs/3.714 secs) 
    HeadlessChrome 0.0.0 (Windows 10 0.0.0): Executed 31 of 31 SUCCESS (3.807 secs/3.779 secs) 
    TOTAL: 62 SUCCESS 
    TOTAL: 62 SUCCESS 

私は "NGのE2E" をしようとしたとき、私は "ETIMEDOUT xxxxは:443" を取得

C:\_pocs\ws_vsc\pastebin-angular-master>ng e2e 
Your global Angular CLI version (1.6.3) is greater than your local 
version (1.1.0). The local Angular CLI version is used. 

To disable this warning use "ng set --global warnings.versionMismatch=false". 
** NG Live Development Server is listening on localhost:49152, open your browser on http://localhost:49152 ** 
(node:5784) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead. 
Hash: 5891176eb0b28d7d1f89 
Time: 12097ms 
chunk {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 160 kB {4} [initial] [rendered] 
chunk {1} main.bundle.js, main.bundle.js.map (main) 29.2 kB {3} [initial] [rendered] 
chunk {2} styles.bundle.js, styles.bundle.js.map (styles) 10.5 kB {4} [initial] [rendered] 
chunk {3} vendor.bundle.js, vendor.bundle.js.map (vendor) 2.82 MB [initial] [rendered] 
chunk {4} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered] 
webpack: Compiled successfully. 
events.js:183 
     throw er; // Unhandled 'error' event 
    ^

Error: connect ETIMEDOUT x.x.x.x:443 
    at Object._errnoException (util.js:1024:11) 
    at _exceptionWithHostPort (util.js:1046:20) 
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14) 

それは何に依存しますので、だから私は "NG E2E --no-webdriverを更新" に変わりありませんプロキシはまったくありません。

C:\_pocs\ws_vsc\pastebin-angular-master>ng e2e --no-webdriver-update 
Your global Angular CLI version (1.6.3) is greater than your local 
version (1.1.0). The local Angular CLI version is used. 

To disable this warning use "ng set --global warnings.versionMismatch=false". 
** NG Live Development Server is listening on localhost:49152, open your browser on http://localhost:49152 ** 
(node:14496) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead. 
Hash: 5891176eb0b28d7d1f89 
Time: 13274ms 
chunk {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 160 kB {4} [initial] [rendered] 
chunk {1} main.bundle.js, main.bundle.js.map (main) 29.2 kB {3} [initial] [rendered] 
chunk {2} styles.bundle.js, styles.bundle.js.map (styles) 10.5 kB {4} [initial] [rendered] 
chunk {3} vendor.bundle.js, vendor.bundle.js.map (vendor) 2.82 MB [initial] [rendered] 
chunk {4} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered] 
webpack: Compiled successfully. 
[18:20:39] I/launcher - Running 1 instances of WebDriver 
[18:20:39] I/direct - Using ChromeDriver directly... 
[18:20:39] E/direct - Error code: 135 
[18:20:39] E/direct - Error message: Could not find update-config.json. Run 'webdriver-manager update' to download binaries. 
[18:20:39] E/direct - Error: Could not find update-config.json. Run 'webdriver-manager update' to download binaries. 
    at Direct.getNewDriver (C:\_pocs\ws_vsc\pastebin-angular-master\node_modules\protractor\built\driverProviders\direct.js:63:31) 
    at Runner.createBrowser (C:\_pocs\ws_vsc\pastebin-angular-master\node_modules\protractor\built\runner.js:195:43) 
    at q.then.then (C:\_pocs\ws_vsc\pastebin-angular-master\node_modules\protractor\built\runner.js:339:29) 
    at _fulfilled (C:\_pocs\ws_vsc\pastebin-angular-master\node_modules\protractor\node_modules\q\q.js:834:54) 
    at self.promiseDispatch.done (C:\_pocs\ws_vsc\pastebin-angular-master\node_modules\protractor\node_modules\q\q.js:863:30) 
    at Promise.promise.promiseDispatch (C:\_pocs\ws_vsc\pastebin-angular-master\node_modules\protractor\node_modules\q\q.js:796:13) 
    at C:\_pocs\ws_vsc\pastebin-angular-master\node_modules\protractor\node_modules\q\q.js:556:49 
    at runSingle (C:\_pocs\ws_vsc\pastebin-angular-master\node_modules\protractor\node_modules\q\q.js:137:13) 
    at flush (C:\_pocs\ws_vsc\pastebin-angular-master\node_modules\protractor\node_modules\q\q.js:125:13) 
    at _combinedTickCallback (internal/process/next_tick.js:131:7) 
    at process._tickCallback (internal/process/next_tick.js:180:9) 
[18:20:39] E/launcher - Process exited with error code 135 

は、私が得たので、「更新-config.jsonを見つけることができませんでした。ファイル名を指定して実行 『webdriverを-managerのアップデート』を」私はdownlodそれを試してみましたが、明示的に

C:\_pocs\ws_vsc\pastebin-angular-master>webdriver-manager update --proxy http://myproxy.vm.mycompany.net:3128 
[18:23:19] I/update - geckodriver: file exists C:\Users\dca\AppData\Roaming\nvm\v8.9.3\node_modules\protractor\node_modules\webdriver-manager\selenium\geckodriver-v0.19.1.zip 
[18:23:19] I/update - geckodriver: unzipping geckodriver-v0.19.1.zip 
[18:23:19] I/update - geckodriver: geckodriver-v0.19.1.exe up to date 
[18:23:20] E/downloader - Expected response code 200, received: 403 
[18:23:20] I/update - chromedriver: file exists C:\Users\dca\AppData\Roaming\nvm\v8.9.3\node_modules\protractor\node_modules\webdriver-manager\selenium\chromedriver_2.34.zip 
[18:23:20] I/update - chromedriver: unzipping chromedriver_2.34.zip 
(node:14648) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Invalid filename 
(node:14648) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. 
[18:24:29] I/update - selenium standalone: file exists C:\Users\dca\AppData\Roaming\nvm\v8.9.3\node_modules\protractor\node_modules\webdriver-manager\selenium\selenium-server-standalone-3.8.1.jar 
[18:24:29] I/update - selenium standalone: selenium-server-standalone-3.8.1.jar up to date 

ビットのために混乱を私の地元のプロキシを使用します私は "E /ダウンローダー - 予想される応答コード200、受け取った:403"が表示されますが、最後に "I/update - selenium standalone:selenium-server-standalone-3.8.1.jar up to date"を参照してください。私はそれを正しくダウンロードすると仮定します。今度は "ng e2e"を繰り返しますが、上記のエラーが発生しました。私がポート番号443を見るので、私は何か "n2 e2e --skip-ssl"を試してみることにしました。私もe2e --webdriver-update = falseを試しましたが、私はまだ "update-config.jsonを見つけることができませんでした"というメッセージが表示されます。

は、私が試した最後の仮の

C:\_pocs\ws_vsc\pastebin-angular-master>npm run e2e 

> [email protected] e2e C:\_pocs\ws_vsc\pastebin-angular-master 
> ng e2e 

** NG Live Development Server is listening on localhost:49152, open your browser on http://localhost:49152 ** 
(node:9036) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead. 
Hash: 5891176eb0b28d7d1f89 
Time: 11115ms 
chunk {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 160 kB {4} [initial] [rendered] 
chunk {1} main.bundle.js, main.bundle.js.map (main) 29.2 kB {3} [initial] [rendered] 
chunk {2} styles.bundle.js, styles.bundle.js.map (styles) 10.5 kB {4} [initial] [rendered] 
chunk {3} vendor.bundle.js, vendor.bundle.js.map (vendor) 2.82 MB [initial] [rendered] 
chunk {4} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered] 
webpack: Compiled successfully. 
events.js:183 
     throw er; // Unhandled 'error' event 
    ^

Error: connect ETIMEDOUT 172.217.17.48:443 
    at Object._errnoException (util.js:1024:11) 
    at _exceptionWithHostPort (util.js:1046:20) 
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14) 
npm ERR! code ELIFECYCLE 
npm ERR! errno 1 
npm ERR! [email protected] e2e: `ng e2e` 
npm ERR! Exit status 1 
npm ERR! 
npm ERR! Failed at the [email protected] e2e script. 
npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 

npm ERR! A complete log of this run can be found in: 
npm ERR!  C:\Users\dca\AppData\Roaming\npm-cache\_logs\2017-12-29T17_33_44_400Z-debug.log 

だったし、ここには関連性がある場合は、ログ

0 info it worked if it ends with ok 
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe', 
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js', 
1 verbose cli 'run', 
1 verbose cli 'e2e' ] 
2 info using [email protected] 
3 info using [email protected] 
4 verbose run-script [ 'pree2e', 'e2e', 'poste2e' ] 
5 info lifecycle [email protected]~pree2e: [email protected] 
6 info lifecycle [email protected]~e2e: [email protected] 
7 verbose lifecycle [email protected]~e2e: unsafe-perm in lifecycle true 
8 verbose lifecycle [email protected]~e2e: PATH: C:\Users\dca\AppData\Roaming\nvm\v8.9.3\node_modules\npm\bin\node-gyp-bin;C:\_pocs\ws_vsc\pastebin-angular-master\node_modules\.bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Windows\CCM;C:\Program Files (x86)\GnuWin32\bin;C:\Program Files (x86)\Skype\Phone\;C:\_t3\gradle-3.5\bin;C:\Program Files (x86)\Subversion\bin;C:\Program Files\Git\cmd;C:\Program Files (x86)\Yarn\bin;C:\Program Files\TortoiseSVN\bin;C:\Users\dca\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\dca\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Java\jdk1.8.0_112\bin;C:\_t\maven\bin;C:\Users\dca\AppData\Local\GitHubDesktop\bin;C:\Program Files\Microsoft VS Code\bin;C:\Users\dca\AppData\Local\Yarn\bin;C:\Users\dca\AppData\Roaming\nvm;C:\Program Files\nodejs 
9 verbose lifecycle [email protected]~e2e: CWD: C:\_pocs\ws_vsc\pastebin-angular-master 
10 silly lifecycle [email protected]~e2e: Args: [ '/d /s /c', 'ng e2e' ] 
11 silly lifecycle [email protected]~e2e: Returned: code: 1 signal: null 
12 info lifecycle [email protected]~e2e: Failed to exec e2e script 
13 verbose stack Error: [email protected] e2e: `ng e2e` 
13 verbose stack Exit status 1 
13 verbose stack  at EventEmitter.<anonymous> (C:\Users\dca\AppData\Roaming\nvm\v8.9.3\node_modules\npm\node_modules\npm-lifecycle\index.js:280:16) 
13 verbose stack  at emitTwo (events.js:126:13) 
13 verbose stack  at EventEmitter.emit (events.js:214:7) 
13 verbose stack  at ChildProcess.<anonymous> (C:\Users\dca\AppData\Roaming\nvm\v8.9.3\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14) 
13 verbose stack  at emitTwo (events.js:126:13) 
13 verbose stack  at ChildProcess.emit (events.js:214:7) 
13 verbose stack  at maybeClose (internal/child_process.js:925:16) 
13 verbose stack  at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5) 
14 verbose pkgid [email protected] 
15 verbose cwd C:\_pocs\ws_vsc\pastebin-angular-master 
16 verbose Windows_NT 10.0.14393 
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "e2e" 
18 verbose node v8.9.3 
19 verbose npm v5.5.1 
20 error code ELIFECYCLE 
21 error errno 1 
22 error [email protected] e2e: `ng e2e` 
22 error Exit status 1 
23 error Failed at the [email protected] e2e script. 
23 error This is probably not a problem with npm. There is likely additional logging output above. 
24 verbose exit [ 1, true ] 

あり、ここでpackage.json

{ 
    "name": "test-angulr", 
    "version": "0.0.0", 
    "license": "MIT", 
    "scripts": { 
    "ng": "ng", 
    "start": "ng serve", 
    "build": "ng build", 
    "test": "ng test", 
    "lint": "ng lint", 
    "e2e": "ng e2e" 
    }, 
    "private": true, 
    "dependencies": { 
    "@angular/animations": "^4.0.0", 
    "@angular/common": "^4.0.0", 
    "@angular/compiler": "^4.0.0", 
    "@angular/core": "^4.0.0", 
    "@angular/forms": "^4.0.0", 
    "@angular/http": "^4.0.0", 
    "@angular/platform-browser": "^4.0.0", 
    "@angular/platform-browser-dynamic": "^4.0.0", 
    "@angular/router": "^4.0.0", 
    "@types/faker": "^4.1.0", 
    "angular-in-memory-web-api": "^0.3.2", 
    "core-js": "^2.4.1", 
    "faker": "^4.1.0", 
    "rxjs": "^5.1.0", 
    "zone.js": "^0.8.4" 
    }, 
    "devDependencies": { 
    "@angular/cli": "1.1.0", 
    "@angular/compiler-cli": "^4.0.0", 
    "@angular/language-service": "^4.0.0", 
    "@types/jasmine": "2.5.45", 
    "@types/node": "~6.0.60", 
    "codelyzer": "~3.0.1", 
    "jasmine-core": "~2.6.2", 
    "jasmine-spec-reporter": "~4.1.0", 
    "karma": "~1.7.0", 
    "karma-chrome-launcher": "~2.1.1", 
    "karma-cli": "~1.0.1", 
    "karma-jasmine": "~1.1.0", 
    "karma-jasmine-html-reporter": "^0.2.2", 
    "karma-coverage-istanbul-reporter": "^1.2.1", 
    "protractor": "~5.1.2", 
    "ts-node": "~3.0.4", 
    "tslint": "~5.3.2", 
    "typescript": "~2.3.3" 
    } 
} 

すべてtentatives Iであります私の環境を整えるために2日間(16時間)苦労した後でした。私が "ng test"と理解している限り、Jasmine sintaxesとprotractor sintaxesに基づく "ng e2e"に基づくテストを実行します(私はそれが非常にダミーの比較であることを知っています)。

最後に、「ng serve」と「ng test」の両方が完全に機能していることがわかると、問題がさらに複雑になることがわかりました。

C:\_pocs\ws_vsc\pastebin-angular-master>ng serve 
Your global Angular CLI version (1.6.3) is greater than your local 
version (1.1.0). The local Angular CLI version is used. 

To disable this warning use "ng set --global warnings.versionMismatch=false". 
** NG Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200 ** 
Hash: 68480633f4a6979c64f6 
Time: 12524ms 
chunk {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 160 kB {4} [initial] [rendered] 
chunk {1} main.bundle.js, main.bundle.js.map (main) 29.2 kB {3} [initial] [rendered] 
chunk {2} styles.bundle.js, styles.bundle.js.map (styles) 10.5 kB {4} [initial] [rendered] 
chunk {3} vendor.bundle.js, vendor.bundle.js.map (vendor) 2.82 MB [initial] [rendered] 
chunk {4} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered] 
webpack: Compiled successfully. 

...

C:\_pocs\ws_vsc\pastebin-angular-master>ng test 
Your global Angular CLI version (1.6.3) is greater than your local 
version (1.1.0). The local Angular CLI version is used. 

To disable this warning use "ng set --global warnings.versionMismatch=false". 
10% building modules 1/1 modules 0 active29 12 2017 18:46:45.409:WARN [karma]: No captured browser, open http://localhost:9876/ 
29 12 2017 18:46:45.487:INFO [karma]: Karma v1.7.0 server started at http://0.0.0.0:9876/ 
29 12 2017 18:46:45.487:INFO [launcher]: Launching browsers Chrome, ChromeNoSandboxHeadless with unlimited concurrency 
29 12 2017 18:46:45.502:INFO [launcher]: Starting browser Chrome 
29 12 2017 18:46:45.523:INFO [launcher]: Starting browser Chrome    29 12 2017 18:46:57.058:WARN [karma]: No captured browser, open http://localhost:9876/ 
29 12 2017 18:46:58.843:INFO [Chrome 63.0.3239 (Windows 10 0.0.0)]: Connected on socket ZyuotOYE2ISz30vzAAAA with id 41727568 
29 12 2017 18:46:58.910:INFO [HeadlessChrome 0.0.0 (Windows 10 0.0.0)]: Connected on socket yBro2KHiWGptHCihAAAB with id 10384190 
Chrome 63.0.3239 (Windows 10 0.0.0): Executed 31 of 31 SUCCESS (4.328 secs/4.288 secs) 
HeadlessChrome 0.0.0 (Windows 10 0.0.0): Executed 31 of 31 SUCCESS (4.279 secs/4.24 secs) 
TOTAL: 62 SUCCESS 
TOTAL: 62 SUCCESS 

webdriverを-Managerは、正しく起動:上記の可能な誤解を確認または訂正する

C:\_pocs\ws_vsc\pastebin-angular-master>webdriver-manager start proxy http://xxx.vm.xxx.net:3128 
[18:52:18] I/start - java -Dwebdriver.gecko.driver=C:\Users\dca\AppData\Roaming\nvm\v8.9.3\node_modules\protractor\node_modules\webdriver-manager\selenium\geckodriver-v0.19.1.exe -jar C:\Users\dca\AppData\Roaming\nvm\v8.9.3\node_modules\protractor\node_modules\webdriver-manager\selenium\selenium-server-standalone-3.8.1.jar -port 4444 
[18:52:18] I/start - seleniumProcess.pid: 11540 
18:52:19.437 INFO - Selenium build info: version: '3.8.1', revision: '6e95a6684b' 
18:52:19.438 INFO - Launching a standalone Selenium Server 
2017-12-29 18:52:19.546:INFO::main: Logging initialized @387ms to org.seleniumhq.jetty9.util.log.StdErrLog 
18:52:19.577 INFO - Using `new FirefoxOptions()` is preferred to `DesiredCapabilities.firefox()` 
18:52:19.593 INFO - Using `new ChromeOptions()` is preferred to `DesiredCapabilities.chrome()` 
18:52:19.608 INFO - Using `new EdgeOptions()` is preferred to `DesiredCapabilities.edge()` 
18:52:19.608 INFO - Driver class not found: com.opera.core.systems.OperaDriver           18:52:19.608 INFO - Using `new OperaOptions()` is preferred to `DesiredCapabilities.operaBlink()` 
18:52:19.608 INFO - Using `new SafariOptions()` is preferred to `DesiredCapabilities.safari()` 
18:52:19.608 INFO - Driver class not found: org.openqa.selenium.phantomjs.PhantomJSDriver        18:52:19.655 INFO - Driver provider class org.openqa.selenium.safari.SafariDriver registration is skipped:    registration capabilities Capabilities {browserName: safari, platform: MAC, version: } does not match the current platform WIN10 
18:52:19.702 INFO - Using `new ChromeOptions()` is preferred to `DesiredCapabilities.chrome()` 
18:52:19.702 INFO - Using `new EdgeOptions()` is preferred to `DesiredCapabilities.edge()`        18:52:19.702 INFO - Using `new FirefoxOptions()` is preferred to `DesiredCapabilities.firefox()` 
18:52:19.702 INFO - Using `new OperaOptions()` is preferred to `DesiredCapabilities.operaBlink()`      18:52:19.702 INFO - Using `new SafariOptions()` is preferred to `DesiredCapabilities.safari()` 
18:52:19.718 INFO - Using the passthrough mode handler 
2017-12-29 18:52:19.751:INFO:osjs.Server:main: jetty-9.4.7.v20170914 
2017-12-29 18:52:19.778:WARN:osjs.SecurityHandler:main: [email protected]@757942a1{/,null,STARTING} has uncovered http methods for path:/
2017-12-29 18:52:19.787:INFO:osjsh.ContextHandler:main: Started [email protected]{/,null,AVAILABLE}2017-12-29 18:52:19.913:INFO:osjs.AbstractConnector:main: Started [email protected]{HTTP/1.1,[http/1.1]}{0.0.0.0:4444} 
2017-12-29 18:52:19.916:INFO:osjs.Server:main: Started @756ms 
18:52:19.917 INFO - Selenium Server is up and running 

ものは非常にappreciattedされます。

環境変数が示唆されなくて、私がしようとした場合、私が得た:別の手で

C:\_pocs\ws_vsc\pastebin-angular-master>ng e2e 
Your global Angular CLI version (1.6.3) is greater than your local 
version (1.1.0). The local Angular CLI version is used. 

To disable this warning use "ng set --global warnings.versionMismatch=false". 
** NG Live Development Server is listening on localhost:49152, open your browser on http://localhost:49152 ** 
(node:8044) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead. 
Hash: 5891176eb0b28d7d1f89 
Time: 12039ms 
chunk {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 160 kB {4} [initial] [rendered] 
chunk {1} main.bundle.js, main.bundle.js.map (main) 29.2 kB {3} [initial] [rendered] 
chunk {2} styles.bundle.js, styles.bundle.js.map (styles) 10.5 kB {4} [initial] [rendered] 
chunk {3} vendor.bundle.js, vendor.bundle.js.map (vendor) 2.82 MB [initial] [rendered] 
chunk {4} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered] 
webpack: Compiled successfully. 
[16:12:48] E/downloader - Connection timeout downloading: https://chromedriver.storage.googleapis.com/2.34/chromedriver_win32.zip. Default timeout is 4 minutes. 
[16:12:48] I/update - chromedriver: file exists C:\_pocs\ws_vsc\pastebin-angular-master\node_modules\protractor\node_modules\webdriver-manager\selenium\chromedriver_2.34.zip 
[16:12:48] I/update - chromedriver: unzipping chromedriver_2.34.zip 
[16:12:49] I/update - chromedriver: chromedriver_2.34.exe up to date 
[16:12:49] I/launcher - Running 1 instances of WebDriver 
[16:12:49] I/direct - Using ChromeDriver directly... 
[16:12:49] E/downloader - Connection timeout downloading: https://chromedriver.storage.googleapis.com/2.34/chromedriver_win32.zip. Default timeout is 4 minutes. 

DevTools listening on ws://127.0.0.1:12268/devtools/browser/71d97023-dae5-4b24-8ecc-98922db60bf5 
Jasmine started 

Executed 0 of 0 specs SUCCESS in 0.002 sec. 
[16:12:53] I/launcher - 0 instance(s) of WebDriver still running 
[16:12:53] I/launcher - chrome #01 passed 

を、環境変数を設定した後、私が得た:

解決策が見つかった後に編集

  • C:\_pocs\ws_vsc\pastebin-angular-master>ng e2e 
    Your global Angular CLI version (1.6.3) is greater than your local 
    version (1.1.0). The local Angular CLI version is used. 
    
    To disable this warning use "ng set --global warnings.versionMismatch=false". 
    ** NG Live Development Server is listening on localhost:49152, open your browser on http://localhost:49152 ** 
    (node:2288) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead. 
    Hash: 5891176eb0b28d7d1f89 
    Time: 12368ms 
    chunk {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 160 kB {4} [initial] [rendered] 
    chunk {1} main.bundle.js, main.bundle.js.map (main) 29.2 kB {3} [initial] [rendered] 
    chunk {2} styles.bundle.js, styles.bundle.js.map (styles) 10.5 kB {4} [initial] [rendered] 
    chunk {3} vendor.bundle.js, vendor.bundle.js.map (vendor) 2.82 MB [initial] [rendered] 
    chunk {4} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered] 
    webpack: Compiled successfully. 
    [16:19:30] I/update - chromedriver: file exists C:\_pocs\ws_vsc\pastebin-angular-master\node_modules\protractor\node_modules\webdriver-manager\selenium\chromedriver_2.34.zip 
    [16:19:30] I/update - chromedriver: unzipping chromedriver_2.34.zip 
    [16:19:30] I/update - chromedriver: chromedriver_2.34.exe up to date 
    [16:19:30] I/launcher - Running 1 instances of WebDriver 
    [16:19:30] I/direct - Using ChromeDriver directly... 
    
    DevTools listening on ws://127.0.0.1:12462/devtools/browser/86f2d2f5-3312-48e6-8d05-25241eeba843 
    Jasmine started 
    
    Executed 0 of 0 specs SUCCESS in 0.003 sec. 
    [16:19:34] I/launcher - 0 instance(s) of WebDriver still running 
    [16:19:34] I/launcher - chrome #01 passed 
    

答えて

1

1)ng e2eを実行すると、エラーが報告されます。あなたがエラーを参照してください、なぜこれがですError: connect ETIMEDOUT x.x.x.x:443

ng e2eのオプション--webdriver-updateのデフォルト値はtrueで、プロキシの背後にあるネットワークので、-マネージャをwebdriverをするには、ネットワークプロキシを告げず、webdriverを-マネージャの更新がネットワークに接続するために失敗しますので、 。

私は https://github.com/angular/angular-cli/blob/master/packages/%40angular/cli/tasks/e2e.tsng e2eのソースコードに見て、私たちは npm run e2e後ろに従うことによって、プロキシを渡すことはできません気づいたが、私たちは、あなたがにポストの下に従うことができます実行する前に読みます webdriver-manager的環境変数にプロキシを設定することができます環境Varableでのセットプロキシ: how to check what is causing webdriver-manager to fail

2)更新をwebdriverをスキップするng e2e --no-webdriver-updateを実行すると、それがエラーを報告:Error message: Could not find update-config.json

それは更新-config.jsonはproject_folder\node_modules\protractor\node_modules\webdriver-manager\selenium

には存在しないことを意味210

プロジェクトwebdriver-manager(project_folder \ .bin \ webdriver-manager)ではなく、グローバルwebdriver-mangerを使用してwebdriverのアップデートを実行したためです。

正しい方法はその後、更新-config.jsonがあるだろうとng e2e --no-webdriver-managerが動作するようになりましたnode_modules\.bin\webdriver-manager update --proxy http://myproxy.vm.mycompany.net:3128 を実行し、まずCMDウィンドウでyour_projectフォルダに切り替えています。

ng e2eは、グローバルwebdriver-managerを使用することはできませんが、唯一のプロジェクトは、地元node_modules\.bin\webdriver-manger

環境VS NPMの代理変数プロキシ

1)NPMプロキシ

NPMプロキシはコマンドのみのために働きます:npmこのコマンド・インプリメンテーションは、evniroment変数からプロキシを読み取ることはないため、プロキシをnpmに設定するには、コマンドnpm config setまたはユーザーのホームフォルダまたはプロジェクトフォルダの下にある.npmrcファイルを直接変更します。

2)環境変数プロキシ

環境変数からプロキシ設定を読み込みます実装するだけのツール/ソフト/プログラム/コマンドは、環境変数プロキシは、それらに影響を与えることができます。

環境変数プロキシがツール/ソフト/プログラム/コマンドに影響することはユーザーには分かりません。特に、初めて触れる新しいことです。

しかし、一般的に、コマンドウィンドウから実行されるすべてのものが環境変数からプロキシ設定を読み込むと考えることができますが、これは常にそうではありません。npmのように、

webdriver-managerに戻ると、最初はほとんどの場合コマンドウィンドウから実行されましたが、実際には環境変数プロキシを決定する最終決定者が実装自体であるかどうかは判断されません。

webdriver-managerで実装し、まず、それは次のようなコマンドラインでオプションとして渡されたプロキシを読み込みます:webdriver-manager update --proxy http://proxy.company.com:1234

をあなたはそれが環境変数からプロキシを読み込みます、コマンドラインでプロキシを通過しない場合。

+0

あなたの2番目の提案は私にとってはまったく効果がありませんでした。私はすでにproject_folder /.../ selenium update-config.jsonファイルにいました。しかし、あなたの最初の提案は、すべてが期待どおりに機能するように思えます。上の2つの出力で、 "webpack:Compiled successfully"の次の行を比較するだけです。あなたは私の質問に答えました。あなたが気にしないならば、ちょうど控えめな説明 "npm(npm設定リスト)でhttp-proxy、https-proxy、およびproxy setupを持っていたのですが、設定したenvironmnet変数の後にのみ、 "NO_PROXY = .mycompany.net、localhost、127.0.0.1"? –

+1

実際には、webdriver-managerはnpmプロキシとは関係ありません。webdriver-mangerの実装では、最初にオプションで渡されたコマンドラインからプロキシを読み込みます:--proxyあなたがコマンドラインでプロキシを渡さないと、2番目に環境変数からプロキシを読み込みます。したがって、npmプロキシを設定しても、webdriver-mangerは気にしません。 – yong

+1

そして、この点をクリアする必要があります:webdriver-manger run npmでインストールされたwebdriver-manager、webdriver-managerはnpmに関係するものに依存しません。npm proxy/cache/registry – yong

関連する問題