Improve UI test suite

[vince-fugnitto]

Features:

• updated chromedriver, webdriverio and peer dependencies.
• broke down AppVeyor test-script into stages (following travis.yml).
• added appveyor-retry to reduce intermittent failures.
• reduced log noise (deprecation warnings, reduced verbosity).
• skipped broken cpp-change-build-config.ui-spec.ts tests.

Signed-off-by: Vincent Fugnitto vincent.fugnitto@ericsson.com

[paul-marechal]

First time in a long time that I see Appveyor green :)

Just clean your commits and should be good to go.

[vince-fugnitto]

@kittaakos I just wanted your feedback on appveyor.yml since I know you are mainly responsible for it.
I have broken down the job into three chunks (theia, browser, and electron) as well as included the appveyor-retry command to each in hopes of reducing potential intermittent errors. (both are inspired by the recent developments in the travis.yml configuration)

[kittaakos]

I just wanted your feedback on appveyor.yml since I know you are mainly responsible for it.

@vince-fugnitto, unti now... as I see you are just taking it over :)

Once the build is green, it is good to merge. Right now it's broken:

lerna ERR! [chrome #0-4]
3157lerna ERR! [chrome #0-4] 1) theia right panel "before all" hook:
3158lerna ERR! [chrome #0-4] Timeout of 30000ms exceeded. Try to reduce the run time or increase your timeout for test specs (http://webdriver.io/guide/testrunner/timeouts.html); if returning a Promise, ensure it resolves.
3159lerna ERR! [chrome #0-4] Error: Timeout of 30000ms exceeded. Try to reduce the run time or increase your timeout for test specs (http://webdriver.io/guide/testrunner/timeouts.html); if returning a Promise, ensure it resolves.
3160lerna ERR! [chrome #0-4]     at Hook.Runnable._timeoutError (C:\projects\theia\node_modules\wdio-mocha-framework\node_modules\mocha\lib\runnable.js:440:10)
3161lerna ERR! [chrome #0-4]     at Timeout.<anonymous> (C:\projects\theia\node_modules\wdio-mocha-framework\node_modules\mocha\lib\runnable.js:251:24)
3162lerna ERR! [chrome #0-4]     at ontimeout (timers.js:498:11)
3163lerna ERR! [chrome #0-4]     at tryOnTimeout (timers.js:323:5)
3164lerna ERR! [chrome #0-4]     at Timer.listOnTimeout (timers.js:290:5)
3165lerna ERR! [chrome #0-4]
3166lerna ERR! 
3167lerna ERR! info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
3168lerna ERR! 
3169lerna ERR!     at Promise.all.then.arr (C:\projects\theia\node_modules\lerna\node_modules\execa\index.js:236:11)
3170lerna ERR!     at <anonymous>
3171{ Error: Command failed: yarn run test
3172root WARN EditorNavigationContribution.onStart is slow, took: 18904 ms
3173root ERROR Uncaught Exception:  Error: write ECONNRESET
3174root ERROR Error: write ECONNRESET
3175    at Socket._writeGeneric (net.js:768:25)
3176    at Socket._write (net.js:787:8)
3177    at doWrite (_stream_writable.js:396:12)
3178    at writeOrBuffer (_stream_writable.js:382:5)
3179    at Socket.Writable.write (_stream_writable.js:290:11)
3180    at Socket.write (net.js:711:40)
3181    at Sender.sendFrame (C:\projects\theia\node_modules\ws\lib\sender.js:379:20)
3182    at Sender.send (C:\projects\theia\node_modules\ws\lib\sender.js:301:12)
3183    at WebSocket.send (C:\projects\theia\node_modules\ws\lib\websocket.js:336:18)
3184    at WebSocketChannel.doSend (C:\projects\theia\packages\core\lib\node\messaging\messaging-contribution.js:240:24)
3185error Command failed with exit code 1.
3186
3187$ wdio wdio.conf.js
3188

FYI: since you have bumped up the wdio versions it would be nice to see if we can build with Node.js 10. It does not mean we will switch to Node.js 10.

[vince-fugnitto]

@kittaakos the errors are intermittent, and sometimes occur on master, I really need to try and find the root cause. The purpose of the retry is to at least try and limit it, similar to vscode.

From my forked theia (with ci enabled), the tests pass https://ci.appveyor.com/project/vince-fugnitto/theia, I'll re-trigger the build on the main repo.

[vince-fugnitto]

Since are ui test cases are now faster to execute, I thought increasing the timeouts was acceptable.

After this change I noticed travis builds passed consistently each time, and appveyor's intermittent errors (network, timeout, etc.) were more controlled with the additional timeout buffer and retry attempts 😄

I did some research, and it looks like with appveyor's basic plan, performance is not always guaranteed or acceptable, so increasing timeout was a way we can control not exiting our test cases prematurely.

[vince-fugnitto]

@marcdumais-work I guess the next step would be to handle the CQ as you mentioned 😄

[marcdumais-work]

I guess the next step would be to handle the CQ as you mentioned

+1. I am working on it now.

[marcdumais-work]

Umbrella CQ registered, for all the repo's dev-dependencies as of ~1h ago: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=18832 . I believe that it covers all dev-dependencies changed in this PR. Since so far we have not had these dev-dependencies CQs, I would not block this PR to wait for approval, if/when otherwise ready to commit.

[vince-fugnitto]

thank you @marechal-p