Install extension from vsix for integration tests (#377)

- Use bundled js in vsix instead of compiling it with ts-node when
testing
- Installing python extension is more stable now. 
- Also, the install is cached so it happens only 1 time - for the first
suite, so integration tests are faster by about 30%.

Co-authored-by: Fabian Jakobs <fabian.jakobs@databricks.com>

Author: kartikgupta-db

packages/databricks-vscode/package.json

@@ -527,7 +527,7 @@
         "fix": "eslint src --ext ts --fix && prettier . --write",
         "test:lint": "eslint src --ext ts && prettier . -c",
         "test:unit": "yarn run build && node ./out/test/runTest.js",
-        "test:integ:prepare": "yarn run package && rm -rf extension && mkdir -p extension && unzip databricks*.vsix -d extension",
+        "test:integ:prepare": "yarn run package",
         "test:integ:run": "wdio run src/test/e2e/wdio.conf.ts",
         "test:integ": "yarn run test:integ:prepare && yarn run test:integ:run",
         "test:cov": "nyc yarn run test:unit",

packages/databricks-vscode/src/test/e2e/configure.e2e.ts

@@ -1,11 +1,7 @@
 import assert from "node:assert";
 import path from "node:path";
 import * as fs from "fs/promises";
-import {
-    getViewSection,
-    waitForPythonExtension,
-    waitForTreeItems,
-} from "./utils";
+import {dismissNotifications, getViewSection, waitForTreeItems} from "./utils";
 import {
     CustomTreeSection,
     InputBox,
@@ -41,11 +37,7 @@ describe("Configure Databricks Extension", async function () {
         host = process.env.DATABRICKS_HOST;
 
         workbench = await browser.getWorkbench();
-    });
-
-    it("should install vscode python extension", async function () {
-        this.retries(1);
-        await waitForPythonExtension();
+        await dismissNotifications();
     });
 
     it("should open VSCode", async function () {

packages/databricks-vscode/src/test/e2e/resources/dummy-test/.eslintrc.json

@@ -0,0 +1,18 @@
+{
+    "root": true,
+    "parser": "@typescript-eslint/parser",
+    "parserOptions": {
+        "ecmaVersion": 6,
+        "sourceType": "module"
+    },
+    "plugins": ["@typescript-eslint"],
+    "rules": {
+        "@typescript-eslint/naming-convention": "warn",
+        "@typescript-eslint/semi": "warn",
+        "curly": "warn",
+        "eqeqeq": "warn",
+        "no-throw-literal": "warn",
+        "semi": "off"
+    },
+    "ignorePatterns": ["out", "dist", "**/*.d.ts"]
+}

packages/databricks-vscode/src/test/e2e/resources/dummy-test/.gitignore

@@ -0,0 +1 @@
+**/.yarn/**

packages/databricks-vscode/src/test/e2e/resources/dummy-test/.yarnrc

@@ -0,0 +1 @@
+--ignore-engines true

packages/databricks-vscode/src/test/e2e/resources/dummy-test/README.md

@@ -0,0 +1,71 @@
+# dummy-test README
+
+This is the README for your extension "dummy-test". After writing up a brief description, we recommend including the following sections.
+
+## Features
+
+Describe specific features of your extension including screenshots of your extension in action. Image paths are relative to this README file.
+
+For example if there is an image subfolder under your extension project workspace:
+
+\!\[feature X\]\(images/feature-x.png\)
+
+> Tip: Many popular extensions utilize animations. This is an excellent way to show off your extension! We recommend short, focused animations that are easy to follow.
+
+## Requirements
+
+If you have any requirements or dependencies, add a section describing those and how to install and configure them.
+
+## Extension Settings
+
+Include if your extension adds any VS Code settings through the `contributes.configuration` extension point.
+
+For example:
+
+This extension contributes the following settings:
+
+-   `myExtension.enable`: Enable/disable this extension.
+-   `myExtension.thing`: Set to `blah` to do something.
+
+## Known Issues
+
+Calling out known issues can help limit users opening duplicate issues against your extension.
+
+## Release Notes
+
+Users appreciate release notes as you update your extension.
+
+### 1.0.0
+
+Initial release of ...
+
+### 1.0.1
+
+Fixed issue #.
+
+### 1.1.0
+
+Added features X, Y, and Z.
+
+---
+
+## Following extension guidelines
+
+Ensure that you've read through the extensions guidelines and follow the best practices for creating your extension.
+
+-   [Extension Guidelines](https://code.visualstudio.com/api/references/extension-guidelines)
+
+## Working with Markdown
+
+You can author your README using Visual Studio Code. Here are some useful editor keyboard shortcuts:
+
+-   Split the editor (`Cmd+\` on macOS or `Ctrl+\` on Windows and Linux).
+-   Toggle preview (`Shift+Cmd+V` on macOS or `Shift+Ctrl+V` on Windows and Linux).
+-   Press `Ctrl+Space` (Windows, Linux, macOS) to see a list of Markdown snippets.
+
+## For more information
+
+-   [Visual Studio Code's Markdown Support](http://code.visualstudio.com/docs/languages/markdown)
+-   [Markdown Syntax Reference](https://help.github.com/articles/markdown-basics/)
+
+**Enjoy!**

packages/databricks-vscode/src/test/e2e/resources/dummy-test/package.json

@@ -0,0 +1,33 @@
+{
+    "name": "dummy-test",
+    "displayName": "dummy-test",
+    "description": "A dummy extension to run integration tests",
+    "version": "0.0.1",
+    "engines": {
+        "vscode": "^1.74.0"
+    },
+    "categories": [
+        "Other"
+    ],
+    "main": "./out/extension.js",
+    "scripts": {
+        "vscode:prepublish": "yarn run compile",
+        "compile": "tsc -p ./",
+        "watch": "tsc -watch -p ./",
+        "pretest": "yarn run compile && yarn run lint",
+        "lint": "eslint src --ext ts"
+    },
+    "devDependencies": {
+        "@types/glob": "^8.0.0",
+        "@types/mocha": "^10.0.1",
+        "@types/node": "16.x",
+        "@types/vscode": "^1.74.0",
+        "@typescript-eslint/eslint-plugin": "^5.45.0",
+        "@typescript-eslint/parser": "^5.45.0",
+        "@vscode/test-electron": "^2.2.0",
+        "eslint": "^8.28.0",
+        "glob": "^8.0.3",
+        "mocha": "^10.1.0",
+        "typescript": "^4.9.3"
+    }
+}

packages/databricks-vscode/src/test/e2e/resources/dummy-test/src/extension.ts

@@ -0,0 +1,10 @@
+// The module 'vscode' contains the VS Code extensibility API
+// Import the module and reference it with the alias vscode in your code below
+import * as vscode from "vscode";
+
+// This method is called when your extension is activated
+// Your extension is activated the very first time the command is executed
+export function activate(context: vscode.ExtensionContext) {}
+
+// This method is called when your extension is deactivated
+export function deactivate() {}

packages/databricks-vscode/src/test/e2e/resources/dummy-test/tsconfig.json

@@ -0,0 +1,15 @@
+{
+    "compilerOptions": {
+        "module": "commonjs",
+        "target": "ES2020",
+        "outDir": "out",
+        "lib": ["ES2020"],
+        "sourceMap": true,
+        "rootDir": "src",
+        "strict": true /* enable all strict type-checking options */
+        /* Additional Checks */
+        // "noImplicitReturns": true, /* Report error when not all code paths in function return a value. */
+        // "noFallthroughCasesInSwitch": true, /* Report errors for fallthrough cases in switch statement. */
+        // "noUnusedParameters": true,  /* Report errors on unused parameters. */
+    }
+}