Switch to vscodetestcover for running extension tests (#5458)

* Update vscode dependency (needed for test runner) to pull latest 1.x version

* Update to use 1.1.5 instead

* Undo change to vscode engine version

* Switch to using vscodetestcover for running tests

* Switch to cobertura output for coverage reports

* Remove vscode dependency from profiler extension

* Update yarn.lock with combined changes
This commit is contained in:
Charles Gagnon
2019-05-13 11:39:09 -07:00
committed by GitHub
parent 43293b98c0
commit dbac187b44
40 changed files with 5771 additions and 12674 deletions

View File

@@ -6,19 +6,23 @@ import * as vscode from 'vscode';
import { context } from './testContext';
const path = require('path');
const testRunner = require('vscode/lib/testrunner');
import * as testRunner from 'vscodetestcover';
const suite = 'Integration Tests';
const options: any = {
const testOptions: any = {
ui: 'tdd',
useColors: true,
timeout: 600000
};
const coverageConfig: any = {
coverConfig: '../coverageConfig.json'
};
if (process.env.BUILD_ARTIFACTSTAGINGDIRECTORY) {
options.reporter = 'mocha-multi-reporters';
options.reporterOptions = {
testOptions.reporter = 'mocha-multi-reporters';
testOptions.reporterOptions = {
reporterEnabled: 'spec, mocha-junit-reporter',
mochaJunitReporterReporterOptions: {
testsuitesTitle: `${suite} ${process.platform}`,
@@ -31,6 +35,6 @@ if (!vscode.workspace.getConfiguration('test')['testSetupCompleted']) {
context.RunTest = false;
}
testRunner.configure(options);
testRunner.configure(testOptions, coverageConfig);
export = testRunner;