Contain side-effects from tests in C/I

[sourishkrout]

Follow up to #98.

• Break out specs into separate files
• Make them pass again

[sourishkrout]

Test passed for various vscode versions on a Linux box (in codespaces). Hopefully 🤞 this will make them pass in GH actions, @christian-bromann.

[christian-bromann]

Thanks for the patch 👌

[christian-bromann]

@sourishkrout shouldn't we remove the tests from the basic.e2e.ts since they have been moved out into separate files?

[sourishkrout]

@sourishkrout shouldn't we remove the tests from the basic.e2e.ts since they have been moved out into separate files?

I believe the whole file was removed. If not then I must have done something wrong during commit. Checking....

Also... Windows 🤦.

[sourishkrout]

Looks like this is right:

[christian-bromann]

Looks like this is right:

Yes, thanks for confirming. The GitHub UI tricked me here.

[sourishkrout]

Just pushed a wdio config change to turn on retries for occasional flakes @christian-bromann.

[christian-bromann]

I will rerun this a couple of times, knowing that some of these tests aren't stable.

[sourishkrout]

Got one of the culprits to pass consistently locally. Let's see if we can get a clean build, please, @christian-bromann.

[sourishkrout]

Chromedriver/Electron didn't even come up in the last run. Don't think that's related to the new commits. Crashed prematurely.

[sourishkrout]

🤦 whackamole continues

[sourishkrout]

🤞 hopefully this will fix it @christian-bromann

[christian-bromann]

Awesome, thanks a lot!