vscode-apollo 1.19.3 → 1.20.1

package/src/testRunner/README.md

@@ -1,23 +0,0 @@
-# Jest TestRunner
-
-Huge thanks to Unibeautify for their initial work on this. Most of the code in `/testRunner` is utilizing their work, barring some changes to configuration.
-
-For reference, see:
-https://github.com/Unibeautify/vscode/tree/master/test
-
-## Notes
-
-### .vscodeignore
-
-The test runner itself must be compiled for VSCode to run it, so it lives in `src` and gets compiled to js. However, it's not included in the final build via the [.vscodeignore](https://code.visualstudio.com/api/working-with-extensions/publishing-extension#.vscodeignore) file.
-
-### ts-jest
-
-The tests themselves don't need to be compiled due to `ts-jest`, so they're ignored in the `tsconfig.json`
-
-### jest-config.ts
-
-This is a standard Jest configuration object which is passed to the CLI. For a full reference, see [Jest Config](https://jestjs.io/docs/en/configuration.html). A couple noteworthy configuration options that are used:
-
-- `testEnvironment`: This points to the custom test environment that's provided in order to run vscode. The environment extends `NodeEnvironment`, however it also adds `vscode` to the `global` object.
-- `setupFilesAfterEnv`: Script to run for any initialization before tests are run. This mocks requests for the vscode module with the vscode object we've provided on the `global` object in the custom test environment.

package/src/testRunner/index.ts

@@ -1,72 +0,0 @@
-/*
- * Wrapper around Jest's runCLI function. Responsible for passing in the config,
- * executing, and passing along failures.
- */
-import { ResultsObject, runCLI } from "jest";
-import { resolve } from "path";
-import { config } from "./jest-config";
-
-export async function run(_testRoot: string, callback: TestRunnerCallback) {
-  const writeStreamRefs = forwardWriteStreams();
-
-  try {
-    const testDirectory = resolve(__dirname, "..", "..", "src");
-    const { results } = await runCLI(config, [testDirectory]);
-
-    restoreWriteStreams(writeStreamRefs);
-
-    const failures = collectTestFailureMessages(results);
-
-    if (failures.length > 0) {
-      callback(null, failures);
-      process.exit(1);
-    }
-
-    callback(null);
-  } catch (e) {
-    callback(e);
-    process.exit(1);
-  }
-}
-
-/**
- * Collect failure messages from Jest test results.
- *
- * @param results Jest test results.
- */
-function collectTestFailureMessages(results: ResultsObject): string[] {
-  const failures = results.testResults.reduce<string[]>((acc, testResult) => {
-    if (testResult.failureMessage) acc.push(testResult.failureMessage);
-    return acc;
-  }, []);
-
-  return failures;
-}
-
-/**
- * Forward writes to process.stdout and process.stderr to console.log.
- *
- * For some reason this seems to be required for the Jest output to be streamed
- * to the Debug Console.
- */
-function forwardWriteStreams() {
-  const outRef = process.stdout.write;
-  const errRef = process.stderr.write;
-
-  process.stdout.write = logger;
-  process.stderr.write = logger;
-
-  return { outRef, errRef };
-}
-
-function restoreWriteStreams(refs: { outRef: any; errRef: any }) {
-  process.stdout.write = refs.outRef;
-  process.stderr.write = refs.errRef;
-}
-
-function logger(line: string) {
-  console.log(line);
-  return true;
-}
-
-export type TestRunnerCallback = (error: Error | null, failures?: any) => void;

package/src/testRunner/jest-config.ts

@@ -1,17 +0,0 @@
-// Config to be handed off to jest
-// @see: https://jestjs.io/docs/en/configuration.html
-import { resolve } from "path";
-
-export const config = {
-  preset: "ts-jest",
-  moduleFileExtensions: ["ts", "js"],
-  rootDir: resolve(__dirname, "..", "..", "src"),
-  testEnvironment: resolve(__dirname, "jest-vscode-environment.js"),
-  setupFilesAfterEnv: [resolve(__dirname, "jest-vscode-framework-setup.js")],
-  globals: {
-    "ts-jest": {
-      tsConfig: resolve(__dirname, "..", "..", "tsconfig.test.json"),
-      diagnostics: false
-    }
-  }
-};

package/src/testRunner/jest-vscode-environment.ts

@@ -1,25 +0,0 @@
-/**
- * Exposes the Visual Studio Code extension API to the Jest testing environment.
- * For custom environments reference:
- * @see https://jestjs.io/docs/en/configuration.html#testenvironment-string
- */
-
-// Using import here results in `jest_environment_node_1.default`
-// The `.default` in this case doesn't exist. Interop issue with the built
-// version of the package?
-const NodeEnvironment = require("jest-environment-node");
-import vscode from "vscode";
-
-class VsCodeEnvironment extends NodeEnvironment {
-  public async setup() {
-    await super.setup();
-    this.global.vscode = vscode;
-  }
-
-  public async teardown() {
-    this.global.vscode = {};
-    return await super.teardown();
-  }
-}
-
-module.exports = VsCodeEnvironment;

package/src/testRunner/jest-vscode-framework-setup.ts

@@ -1,10 +0,0 @@
-/**
- * Takes the Visual Studio Code extension API which was exposed on the sandbox's
- * global object and uses it to create a virtual mock. This replaces vscode
- * module imports with the vscode extension instance from the test runner's
- * environment.
- *
- * @see https://github.com/Unibeautify/vscode/blob/61897cd6cd0567db2c8688c3c0b835f9b5c5b446/test/jest-vscode-framework-setup.ts
- */
-
-jest.mock("vscode", () => global.vscode, { virtual: true });

package/src/testRunner/jest.d.ts

@@ -1,37 +0,0 @@
-declare module "jest" {
-  /**
-   * Execute Jest and return a promise with the results.
-   *
-   * @see https://github.com/facebook/jest/blob/master/packages/jest-cli/src/cli/index.js
-   * @param jestConfig Jest configuration options.
-   * @param projects Paths to projects to run tests on.
-   */
-  export function runCLI(
-    jestConfig: object,
-    projects: string[]
-  ): Promise<{ globalConfig: object; results: ResultsObject }>;
-
-  export interface ResultsObject {
-    testResults: {
-      failureMessage?: string;
-    }[];
-  }
-}
-
-declare module "jest-environment-node" {
-  export default class NodeEnvironment {
-    public global: any;
-
-    constructor(config: any);
-
-    public setup(): Promise<void>;
-    public teardown(): Promise<void>;
-    public runScript(script: any): any;
-  }
-}
-
-declare namespace NodeJS {
-  interface Global {
-    vscode: any;
-  }
-}

package/src/testRunner/vscode-test-script.ts

@@ -1,38 +0,0 @@
-import { resolve } from "path";
-import { spawn } from "child_process";
-
-const cp = spawn(
-  `node ${resolve(
-    process.cwd(),
-    "..",
-    "..",
-    "node_modules",
-    "vscode",
-    "bin",
-    "test"
-  )}`,
-  [],
-  {
-    shell: true,
-    env: {
-      CODE_TESTS_PATH: `${process.cwd()}/lib/testRunner`,
-      CODE_TESTS_WORKSPACE: process.cwd(),
-      DISPLAY: process.env.DISPLAY
-    }
-  }
-);
-
-cp.stdout.on("data", data => {
-  console.log(data.toString());
-});
-
-cp.stderr.on("data", err => {
-  // Useful for debugging, but generally more noisy than useful
-  // console.error({ err: err.toString() });
-});
-
-cp.on("close", code => {
-  if (code !== 0) {
-    process.exit(code);
-  }
-});

package/tsconfig.test.json

@@ -1,4 +0,0 @@
-{
-  "extends": "../../tsconfig.test.base",
-  "include": ["**/__tests__/*", "**/__mocks__/*"]
-}