add integration tests for typescript language

[akosyakov]

What it does

Added integration tests for typescript.

• find a way to start ts server only once -> included examplese/browser/src-gen into the root tsc project
• add integration tests for typescript language #7265 (comment)
• test webview keydown event propagation
• add integration tests for typescript language #7265 (comment) -> it happens because the server process gets killed when tests are finished

How to test

CI should be green.

Review checklist

• as an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• as a reviewer, I agree to behave in accordance with the review guidelines

[vince-fugnitto]

@akosyakov I like the changes and the fact we can use this test as a basis for additional tests, and for new languages as well. Should you amend the pull-request, I don't see Travis started?

[akosyakov]

@vince-fugnitto It is just a start, I will work more next days. For now this PR only enable awaiting of typescript extension activation and do one dummy test.

[akosyakov]

Weird that travis does not start job for this PR. Do we only build PRs against master?

[vince-fugnitto]

Weird that travis does not start job for this PR. Do we only build PRs against master?

I'm not sure but it might be the case with this config:

theia/.travis.yml

Lines 65 to 67 in 357b8e9

	branches:
	only:
	- master

[akosyakov]

Added more tests for reveal definition for different kind of links (internal, external) and between different widgets (editor and editor preview). It looks good.

I will add tests for peek widget tomorrow and then for other language features, hope it will go faster.

[akosyakov]

I've added tests for peek definition and will test other features after the lunch. I've done with the VSX Registry integration and will have more time for testing Monaco this week :)

[akosyakov]

I've increased timeout. Could you try again?

[RomanNikitenko]

maybe your machine is not enough fast

I thought my machine was good enough until you asked me...
😃

Testing...

[RomanNikitenko]

@akosyakov
Tested after update, one test was still failing

I wonder do you have some custom plugins installed

you are right, found two extra extension in plugins folder

After removing them I can not reproduce the problem - all tests are success for me!

[akosyakov]

@RomanNikitenko I will keep timeouts, if it slows down ci, i will reduce them. It should not do it for successful builds.

[akosyakov]

Currently tests are based on generated src-gen/server.js file. I will change it to generate a custom test file under src-gen to prevent breaking them by changing server generator.

[RomanNikitenko]

@akosyakov

I will change it to generate a custom test file under src-gen to prevent breaking them by changing server generator.

Are you going to do it within current PR or a separate PR?

[akosyakov]

@RomanNikitenko I will rebase and clean up the PR on Monday and then ping you.

[akosyakov]

@RomanNikitenko tests are changed to use own test file, instead of generated server.ts

[akosyakov]

@vince-fugnitto Changed to master and travis is running again, tests are passing now.

[RomanNikitenko]

I have run the tests multiple times: they pass successfully and look stable for me!

[akosyakov]

I've updated CHANGELOG and applied all suggestions, going to merge it the build is green.