Simplify Unit Tests

This change means we can't use the harness provided by VS Code, but that's fine for now. I only intend to test service classes that generally don't have concrete dependencies on VS Code anyway.

package.json

@@ -143,7 +143,7 @@
         "compile": "npm run lint && tsc -p ./",
         "watch": "tsc -watch -p ./",
         "postinstall": "node ./node_modules/vscode/bin/install",
-        "test": "npm run compile && node ./node_modules/vscode/bin/test",
+        "test": "npm run compile && mocha ./out/test/**/*.js",
         "lint": "tslint -p tslint.json --fix"
     },
     "devDependencies": {

src/test/index.ts

@@ -1,22 +0,0 @@
-//
-// PLEASE DO NOT MODIFY / DELETE UNLESS YOU KNOW WHAT YOU ARE DOING
-//
-// This file is providing the test runner to use when running extension tests.
-// By default the test runner in use is Mocha based.
-//
-// You can provide your own test runner if you want to override it by exporting
-// a function run(testRoot: string, clb: (error:Error) => void) that the extension
-// host can call to run the tests. The test runner is expected to use console.log
-// to report the results back to the caller. When the tests are finished, return
-// a possible error to the callback or null if none.
-
-import * as testRunner from "vscode/lib/testrunner";
-
-// You can directly control Mocha options by uncommenting the following lines
-// See https://github.com/mochajs/mocha/wiki/Using-mocha-programmatically#set-options for more info
-testRunner.configure({
-    ui: "bdd",
-    useColors: true // colored output from test results
-});
-
-module.exports = testRunner;