Test adapter improvements by billti · Pull Request #1524 · microsoft/nodejstools
and others added 19 commits
October 14, 2016 16:08* have run_tests return structured result used by TestExecutor * have run_tests accept test data from stdin * run_tests receives test data over stdin * expose StandardOutput and disable async readline * TestExecutor receives test results over process StandardOutput * include testing framework in testInfo object sent to run_tests.js * comments * close readline interface after running test * revert ProcessOutput * use JsonConvert.DeserializeObject<TestResult>() instead * create GetTestResultFromProcess() method * use Process, copy over helper methods from ProcessOutput * close StandardInput after sending test info * include dependency for copied ProcessOutput method * launch node inside of RunTestCases instead * remove some debugging stuff * handle case if result is null * pass in streams as parameters to allow continual reading/writing * move setup logic to RunTests * only remove double quotes from test case info * move Process launch logic into function * mocha uses runner events to determine test pass/fail * get TestExecutor in working state, still launching one process per one test * get TextExecutor code into working state * fixes from PR feedback
* prepare run_tests to run multiple tests * have tape.js run_tests use callback to return result * launch node if test run from 'run selected tests'
…1383) * run_tests accepts a list of tests * mocha.js runs a list of tests and records duration * use full title for tests and initialize time to 0 * run ExportRunner tests with single node instance * close readline interface after tests are done * have ExportRunner tests record test duration * tape framework runs multiple tests with one node instance * enable TestExecutor to run multiple tests with one instance of node * add comment
billti
deleted the
billti/test-adapter-improvements
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters