hbenl / vscode-test-explorer

The VS Code Test Explorer extension

Test Explorer for Visual Studio Code

This extension provides an extensible user interface for running your tests in VS Code. It can be used with any testing framework if there is a corresponding Test Adapter extension.

Other extensions can get full access to the Test Adapters by acting as Test Controllers.

The Test Explorer can also be used in VS Live Share sessions by installing the Test Explorer Live Share extension.

This extension will be automatically installed when you install one of the Test Adapters, so there is usually no need to install this extension manually.

Migrating to native testing

In version 1.59, VS Code added an official API and UI for running tests, which provides all the functionality of this extension and more. Therefore this extension is now deprecated. I will keep maintaining it so it will remain usable but I don't plan to add any major new features to it.

Changes for users

You can keep using this extension as before, but you now also have the option to use VS Code's native testing UI instead by setting testExplorer.useNativeTesting to true in your VS Code settings.

Changes for extension authors

If you plan to write a new testing extension for VS Code, I recommend you use the native testing API as it's more flexible and has more features than this extension's Test Adapter API. Here's the official guide for the native testing API.

If you're maintaining an extension that uses the Test Adapter API, here is a short guide how to migrate your Test Adapter to the native API. The migration isn't strictly necessary because this extension will remain usable and your users can switch to the native testing UI using the testExplorer.useNativeTesting setting anyway, but you might find the additional flexibility of the native testing API useful in the future.

Test Adapters

Currently the following Test Adapters are available:

Javascript

• Mocha Test Explorer
• Jasmine Test Explorer
• Angular/Karma Test Explorer
• Jest Test Explorer
• AVA Test Explorer
• TestyTs Test Explorer
• React-scripts Test Adapter

ABAP

• ABAP remote filesystem

C

• Ceedling Test Explorer
• CppUTest Test Explorer
• Unity Framework for C Test Explorer
• Acutest Test Explorer

C++

• C++ TestMate
• CMake Test Explorer
• CppUnitTestFramework Explorer
• Bandit Test Explorer
• catkin-tools
• CppUTest Test Explorer
• Boost.Test Explorer
• Acutest Test Explorer
• CppUnit Test Explorer

Elixir

• Elixir Test Explorer

Elm

• Run Elm tests

Go

• Go Test Explorer

Haxe

• Haxe Test Explorer

Java

• Apache NetBeans Language Server

Lua

• LuaUnit Test Explorer

Python

• Python Test Explorer

PHP

• PHPUnit Test Explorer
• PHP Tools for VSCode

R

• R Test Explorer

REST/GraphQL

• Ply

Ruby

• Ruby Test Explorer

Rust

• Rust Test Explorer

Swift

• Swift Test Explorer

.NET Framework

• NXunit Test Explorer
• .Net Core Test Explorer

Powershell

• Pester Test Explorer

VHDL/SystemVerilog

• VUnit Test Explorer

Z80 Assembler

• Z80 Unit Tests

Live Share

• The Test Explorer Live Share extension creates Test Adapters in Live Share guests that act as proxies for the Test Adapters in the Live Share host.

If there is no Test Adapter for your favorite testing framework yet, you can easily create your own.

Test Controllers

Currently the following Test Controllers are available:

• The Test Explorer UI (which is the main part of this extension) is itself implemented as a Test Controller
• The Test Explorer Diagnostics Controller adds test results to the Problems panel in VS Code.
• The Test Explorer Status Bar extension provides information about the current test suite in the Status Bar.
• The Test Explorer Live Share extension creates Test Controllers in the Live Share host that act as proxies for the Test Explorers in the Live Share guests.

Do you have a new idea for interacting with the Test Adapters? You can easily get full access to all Test Adapters in your own extension by implementing your own controller.

Configuration

The following configuration properties are available:

Property	Description
testExplorer.onStart	Retire or reset all test states whenever a test run is started
testExplorer.onReload	Retire or reset all test states whenever the test tree is reloaded
testExplorer.codeLens	Show a CodeLens above each test or suite for running or debugging the tests
testExplorer.gutterDecoration	Show the state of each test in the editor using Gutter Decorations
testExplorer.errorDecoration	Show error messages from test failures as decorations in the editor
testExplorer.errorDecorationHover	Provide hover messages for the error decorations in the editor
testExplorer.sort	Sort the tests and suites by label or location. If this is not set (or set to null), they will be shown in the order that they were received from the adapter
testExplorer.showCollapseButton	Show a button for collapsing the nodes of the test tree
testExplorer.showExpandButton	Show a button for expanding the top nodes of the test tree, recursively for the given number of levels
testExplorer.showOnRun	Switch to the Test Explorer view whenever a test run is started
testExplorer.addToEditorContextMenu	Add menu items for running and debugging the tests in the current file to the editor context menu
testExplorer.mergeSuites	Merge suites with the same label and parent
testExplorer.hideEmptyLog	Hide the output channel used to show a test's log when the user clicks on a test whose log is empty
testExplorer.hideWhen	Hide the Test Explorer when no test adapters have been registered or when no tests have been found by the registered adapters. The default is to never hide the Test Explorer (some test adapters only work with this default setting).
testExplorer.useNativeTesting	Disable the Test Explorer UI and use VSCode's native Testing UI instead

Further configuration options are provided by the Test Adapters.

Commands

The following commands are available in VS Code's command palette, use the ID to add them to your keyboard shortcuts:

ID	Command
test-explorer.reload	Reload tests
test-explorer.run-all	Run all tests
test-explorer.run-file	Run tests in current file
test-explorer.run-test-at-cursor	Run the test at the current cursor position
test-explorer.rerun	Repeat the last test run
test-explorer.debug-test-at-cursor	Debug the test at the current cursor position
test-explorer.redebug	Repeat the last test run in the debugger
test-explorer.cancel	Cancel running tests

vscode-test-explorer's Issues

Request: Karma Test Adapter

It would be nice to support Karma Test Runner https://karma-runner.github.io/latest/index.html

Suite description and tooltip cant be updated with TestSuiteEvent just at first time

Easy setup:
1 suite with 2 tests.
I run the suite after and after, updating the suite and the test descriptions and events too.
Test infos update but suite infos don't.

Need PHP support

Thank you very much.

EACCES error while loading tests

For Version 0.2.1.

I'm using the Google Test Explorer version 0.2.0 in Visual Studio Code Version 1.23.1 on MacOS. When I press the play button for the test, the following warning notification appears on the bottom right.

Error while loading tests: Error: spawn EACCES

test results greyed out when retire getter missing from adapter

Hi,

when using Haxe Test Explorer extension I noticed that my test results always showed up with correct icons but they remained greyed out (or fainted?) instead of showing in solid colours like they used to.

I fixed it in Haxe Test Explorer bei adding a retire getter, even though it's marked as optional.
It seems test explorer's handling of old API adapters is broken.

Expose & use TreeItem description and/or resourceUri through API for file differentiation

I'm working on a project which has multiple folders below the project root, and each folder has its own tests.py. So my Test Explorer looks like this:

... which is not hugely helpful when trying to find the right one. (I'm using the Python Test Adapter, but this problem could apply to all of them.)

When dealing with multiple identically-named files, VSCode's practice is to differentiate on path by adding a smaller path description to tab headers:

Note that VSCode includes logic to work out the best text for these descriptions, based on where the paths differentiate.

These smaller, lighter/darker labels (a.k.a. Descriptions) are now available in extension tree views. You can provide the string for the description directly, or simply tell VSCode to work it out (using its path differentiation logic) from the TreeItem's resourceUri, which might be much easier.

Add enumDescriptions

The enum values in contributes.configuration should have enumDescriptions.

Unable to run tests from sub directories

I get the following error when I try to debug tests for a component in a sub dir:

    at require (internal/module.js:11:18)
    at Object.<anonymous> (/Users/rrajaratnam/.vscode/extensions/hbenl.vscode-mocha-test-adapter-0.4.1/out/worker/runTests.js:19:5)
    at Module._compile (module.js:649:14)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
Waiting for the debugger to disconnect...

My config:

"mochaExplorer.cwd": "app",
"mochaExplorer.require": [
    "ts-node/register"
],
"mochaExplorer.files": "app/test/**/*spec.ts",

I believe this is being caused by the mochaExplorer.cwd option not being honoured in the debug run, as tests work fine when not debugging.

Enzyme Adapter not loading on click of individual test.

We are using Enzyme with our Mocha unit tests. I can run all tests using the play button the Test Explorer UI. If I go to click on an actual test from the tree, I get the following error in the Test Explorer output:

Error: 
      Enzyme Internal Error: Enzyme expects an adapter to be configured, but found none.
      To configure an adapter, you should call `Enzyme.configure({ adapter: new Adapter() })`
      before using any of Enzyme's top level APIs, where `Adapter` is the adapter
      corresponding to the library currently being tested. For example:

      import Adapter from 'enzyme-adapter-react-15';

      To find out more about this, see http://airbnb.io/enzyme/docs/installation/index.html
    
    at validateAdapter (node_modules/enzyme/build/validateAdapter.js:16:11)
    at getAdapter (node_modules/enzyme/build/getAdapter.js:27:36)
    at new ReactWrapper (node_modules/enzyme/build/ReactWrapper.js:126:49)
    at mount (node_modules/enzyme/build/mount.js:21:10)
    at mount (packages/arcadia-ui/src/test-utils/createMount.js:12:53)
    at Context.mount (packages/arcadia-ui/src/styles/withStyles.test.js:318:9)

I have the following in <projectRoot>/test/mocha.opts:

--require @babel/register
--require jsdom-global/register
--reporter dot
--recursive
test/utils/setup.js

Our <projectRoot>/test/utils/setup.js contains:

/* eslint-disable no-console */
import { configure } from 'enzyme';
import Adapter from 'enzyme-adapter-react-16';

// Set to true for Mocha.
process.browser = true;

// Configure console.error calls.
console.error = (...args) => {
  console.info(...args);
  throw new Error(...args);
};

// Attach the Enzyme Adapter
configure({ adapter: new Adapter() });

It appears the root call to run the tests is using Mocha as expected, but direct calls are not. Let me know if I can provide any other information (not really sure what else to add at this time).

Need a configuration to enable auto run by default

It is annoying that users need to click enable auto run every time they open VSCode workspace. It will be nice if there is a configuration to make auto run the default.

Click to view code for test

As a user,
I would like to be able to view the code for the test I have clicked on the side bar, in the editor area
So that I can better understand what the test is doing.

Make debug optional

I am working on an adapter for a language that does not have a debugger. It would be nice if I could declare that it does not support debugging so that those options are hidden.

Test out of order

I believe the last VS Code update broke the ordering of tests. If I recall correctly, they used to be in alphabetical order.

VS Code: 1.32.1

Please add test-explorer.debug-test-at-cursor command

In addition to the existing test-explorer.run-test-at-cursor command, a test-explorer.debug-test-at-cursor that can be accessed from the Command Palette and/or bound to a shortkey would be extremely useful.
Thanks for considering this.

Getting "Error while loading tests" for python adapter

when clicking on the text below getting this:

SyntaxError: Unexpected token I in JSON at position 0
    at JSON.parse (<anonymous>)
    at Object.parseTestSuites (/Users/philippk/.vscode/extensions/littlefoxteam.vscode-python-test-adapter-0.3.0/src/pytest/pytestTestCollectionParser.ts:13:28)
    at PytestTestRunner.<anonymous> (/Users/philippk/.vscode/extensions/littlefoxteam.vscode-python-test-adapter-0.3.0/src/pytest/pytestTestRunner.ts:95:24)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/philippk/.vscode/extensions/littlefoxteam.vscode-python-test-adapter-0.3.0/node_modules/tslib/tslib.js:104:62)
    at <anonymous>

[Question] Is lazy-load supported?

From my understanding, currently, the test adapter needs to search for all the test items and return them to the UI in one call.

Is it possible to support lazy-load for the explorer? For example, each time the user clicks on a tree node, the Explorer UI will call the adapter to return the direct children for that node?

Can't handle 200 test suites (800 tests/suite)

vscode-test-explorer/src/tree/testCollection.ts

Line 155 in dd46287

this.allRunningTests.push(...allTests(node));

can throw RangeError: Maximum call stack size exceeded.

Ruby support

Specifically Rspec, though Minitest is also a fairly popular testing framework for Ruby.

There are some existing extensions that are somewhat similar, but they don't have a UI to display the tests:

• Ruby Test Launcher: https://marketplace.visualstudio.com/items?itemName=blakeh.ruby-test-launcher
• Rails Test Runner: https://marketplace.visualstudio.com/items?itemName=davidpallinder.rails-test-runner

[Discussion] Explore adding support for VS Live Share

VS Live Share allows devs to collaborate with others in real time, directly from within VS Code. All of the “guests” that join a Live Share session are remotely connecting to the “host” (the person who shared), and can edit, debug, access terminals (if allowed), run tasks, etc. without needing to download any files or setup their environment.

Because “guests” are pulling their state from the “host”, and don’t have local file access, certain extensions (like this one!) don’t work out of the box. However, we just published an API that allows extensions to detect the presence of a Live Share session, and then use the secure connection that is established between all participants. You can then use this to send RPC messages, such as retrieving the list of tests from the host, requesting to run a test, etc.

It would be cool to explore an integration between this extension and Live Share, in order to allow tests to be collaboratively viewed and run (which is a common feature request for us!). We need to enable automatically syncing output channels (so that test results would be transparently shared), to fully complete this scenario. But I’d be curious to hear if this kind of integration would be interesting or not. Thanks!

How can I see output of tests?

I would like to see all the output of the test (stderr and stdout).
This is useful for example:

• When comparing arrays, chai prints the actual and expected values. I couldn't find a way to see this in Test Explorer
• When a test throws an exception it is valuable to see the stacktrace of the exception

I tried checking the OUTPUT tab of Test Explorer but nothing is printed there.

Test Explorer pane in sidebar remains after Test Explorer UI extension uninstalled

But the "Test Explorer UI" (and Python Test Explorer) have been uninstalled, and vscode restarted.

Strangely, reinstallling gives an even stranger result...

Scrolling while test is running

Scrolling in the test explorer with an executable expanded keeps snapping to top. If you have all of the executables collapsed scrolling works great.

Sending retire event for 3 tests opens the picker

I think it should not.

Add Python adapter to readme

I just noticed that someone published a Python adapter to the marketplace 🚀. It would be great to add this to the readme for visibility purposes.

Switch to the Test activity automatically when a run test command is invoked

It would be useful to show the test tree when tests are started to avoid having to switch to the Test activity manually. Almost every time I need to run tests (either via a hot-key assigned to the "Run all tests" command or via the hyperlink in the code), I like to see how the test run is progressing by looking at the test tree.

BTW, it looks like vscode API supports this via the reveal method on the view:

Question about `autorun` feature

Calling my adapter's autorunEmitter.fire() event will cause two run([...]) calls.

The second one is definitely a duplicate.

Let me know, if you need more info.

Regards,

Question: Considered taking a dependency on the vstest platform?

Hi, just a question here.

I was wondering if you had considered using the vstest platform as the underlying test runner for this extension? It's cross-platform, extensively used, open source, and community test adapter authors are familiar with it because of the Visual Studio extensions they've written. It's definitely not fine-tuned to the VSCode scenario, but I feel like a lot of functionality could be reused. I'd also love to hear what may have made you decide against it if you had considered it.

Thank you for your time!

Autorun only changed suites/tests

Hello,

I have a feature idea:

It would be nice to rerun only the 'changed' executable's suite ONLY.
It is not possible now.

So for example a possible solution could be:
TestAdapter interface having a

readonly autorunChanged?: vscode.Event<ids:string[]>;

And I could fire it with the relevant suite/test id(s).
In the menu '...' we need another option like: Run changed tests automatically.

Note that I always have to send a TestLoadFinishedEvent event because I have to reload the changed executable. I think I should fire autorunChanged after it. (?)

Also the TestLoadFinishedEvent will triggers your autorun mechanism, but that feature and the new one could live next to each other. It could cause that tests are run twice if both feature are enabled, but it can be the user's choice.

Or... TestLoadFinishedEvent interface could have a

changedIds: string[] //or similar

field. In this case you could see on time that you need to autorun by yourself or not.

I would prefer the first option, because I would like to add a dependsOn:string[] property. And in case of a change I would trigger the change of the related id(s).

Bests,

Feature Request: Command to reveal test-view

Description

It would be awesome if the extension could contribute a command that simply focuses the test view and bind it by default to Ctrl + Shift + T (Like Ctrl + Shift + E for the explorer view)

Use case

As a developer I want to be able to show/hide the test view via a keybinding to speed up my workflow.

Element with id .... is already registered, tests not runnable

Experienced with: Test Explorer UI 2.2.0, Jasmine Test Explorer 1.3.0

I've found that under certain circumstances, the Test Explorer UI will fail to render unit tests elements due to an apparent id conflict. Specifically, expanding a file in the Test Explorer UI under the following circumstances results in an error Element with id .... is already registered, and the tests are neither navigable nor runnable:

A spec file contains two identically-named describe blocks.

describe('Thing1', () => {
    it('should foo', pending);
});
describe('Thing1', () => {
    it('should bar', pending);
});

Two spec files each contain identically-named describe blocks.

foo/bar/bla/file1.spec.js:

describe('Thing1', () => {
    it('should foo', pending);
});

oh/boy/file2.spec.js:

describe('Thing1', () => {
    it('should bar', pending);
});

A describe block contains two identically-named tests

describe('Test1', () => {
    it('should foo', pending);
    it('should foo', pending);
});

Need Golang support

Hi,

Wanted to know if there is any plan for supporting go test cases?

Search tests

As a user
When there is a large number of tests
I would like to be able to filter the list of tests in the side
So that I can find a test I want to run/debug quickly

Q/R: How can I mark the result of the tests outdated?

Hello,

Here is the situation:

• User runs the tests Some of them fails, some of them succeeds.
• User recompile the executable.
  Now we don't know about the tests anything because all tests(contained by the executable) could be changed. (Also new tests created and old ones deleted, renamed.)

Most of the cases are straight forward except when the adapter can find a test with the same name.
This case I would like to mark the test obsoleted(so all the old ones which haven't been deleted.) and also would like to still show the last valid result of the test.

Can I do that now? I'm asking, because I've noted that sometimes The tests are greyed out, but I'm not sure when. That actually could be a solution.
Or new states maybe. (for example: failedOutdated, passedObsoleted)

Best Regards,
Mate

add jest adapter

we use jest exclusively for our testing, so it would be awesome if you could add an adapter for it.

GoogleTest Adapter

Hi, I implemented a GoogleTest adapter.

Is it ok for you if I publish it on the marketplace?

Wrong test status icon after `completed` event

Hey,

Test tree:

all 
 |-- suite1
 |       |--  s1test1
 |       |--  s1test2 
 |       \__  s1test3
 |
 |-- suite2
 |       |--  s2test1
 |       |--  s2test2
 |       \__  s2test3
 |
 |-- suite3
 |       |--  s3test1
 |       |--  s3test2
 |       \__  s3test3

I'm sending events like this:

	  { type: 'started', tests: ['all'] }
	  { type: 'suite', suite: 'suite1', state: 'running' }
	  { type: 'test', test: 's1test1', state: 'running' }
	  { type: 'test', test: 's1test1', state: 'passed' }
          { type: 'test', test: 's1test2', state: 'running' }
	  { type: 'test', test: 's1test2', state: 'failed' }
	  { type: 'suite', suite: 'suite1', state: 'completed' }
	  { type: 'suite', suite: 'suite2', state: 'running' }
	  { type: 'test', test: 's2test1', state: 'running' }
	  { type: 'test', test: 's2test1', state: 'passed' }
          { type: 'test', test: 's2test2', state: 'running' }
	  { type: 'test', test: 's2test2', state: 'failed' }
          { type: 'suite', suite: 'suite2', state: 'completed' }
          { type: 'suite', suite: 'suite3', state: 'running' }
	  { type: 'test', test: 's3test1', state: 'running' }
	  { type: 'test', test: 's3test1', state: 'passed' }
          { type: 'test', test: 's3test2', state: 'running' }
	  { type: 'test', test: 's3test2', state: 'failed' }
	  { type: 'suite', suite: 'suite3', state: 'completed' }
	  { type: 'finished' }

Symptom: The status icons of suite1 and suite2 remain "red play" (running and failed) until the finished event. It should be a "red X" (finished and failed)

I think the problem is that there is no event about s1test3, s2test3 and s3test3.

Real example: My executable crashes during a test (test3->1 in the example bellow), I detect it, send a failed event, but no events for the rest of the tests in the executable.

(Also: test4's icon isn't right, but I assume it's a vscode drawing bug. It happens a lot on OSX 10.14.2. Appears after mouseover / mouse hover.)

Context:

• Test Explorer UI version: 2.3.1
• OS: OSX 10.14.2

Run test explorer in docker-compose

As the title says. Is it possible to run the test explorer in docker-compose? (I must run grunt inside of docker)

improve path handling for gutter and codelens

vscode-test-explorer/src/decorator.ts

Line 40 in a91fba0

(uriToFile(this.activeTextEditor.document.uri) === file)) {

when writing a test adapter for Haxe I ran into an issue that would only show on Windows. Gutter and codelens would not show any info, however "Show source" in tree would jump to the correct location.
After debugging what went wrong I found out my paths had / instead of \ and so they wouldn't match.
Windows accepts both variants, so they should probably also work here.

Show stack trace in TestExplorer output for failed tests

When clicking on a test, "Test Explorer" output for this test will show the output of the failed asserts:

It would be really nice if it would also show the call stack where the error occurred. The adapter returns the call stack in the decorations field of TestEvent.

Run individual tests from explorer

Issue

Currently, clicking to run an individual test (as opposed to all tests) does nothing.

Expectation/Suggestion

Clicking the run icon next to an individual test or file will run the respective test(s).

Current setup:

Using Jest on Linux - all tests are found, but are not ran when clicked individually.

EDIT:

By viewing the Jest Test Explorer Log I've found that the search query is incorrect:
test/unit/entity/Entity\\\\.spec\\\\.ts•^setLocation moves the object only when given location is different$

The correct folder is being searched, but the four backslashes on either side are incorrect, and I can not find supporting documentation on this issue.

jest.config.js:

module.exports = {
    // An array of file extensions your modules use
    moduleFileExtensions: ['js', 'ts', 'tsx'],

    // A list of paths to directories that Jest should use to search for files in
    roots: ['<rootDir>/test'],

    // The regexp pattern or array of patterns that Jest uses to detect test files
    testRegex: ['/__tests__/.*\\.(ts|tsx|js)$'],

    // A map from regular expressions to paths to transformers
    transform: {
        '\\.(ts|tsx)$': '<rootDir>/node_modules/ts-jest/preprocessor.js'
    }
};

If something is missing or incorrect on my end, please let me know. I've tried several configurations and nothing seems to get rid of the invalid path generated by trying to run single tests.

Cancelling a test run fails if one of the adapters throws an exception

I have the following TestExplorer extensions installed:

• Mocha
• Python
• Rust
• Catch2 and Google Test (C++)
• My own (unfinished) extension (in the debugger)

When I run my tests and then try to stop them, I get the following error in VSTest:

And here's the call stack, pointing to the Rust extension:

[2019-03-18 19:52:26.572] [exthost] [error] Error: Method not implemented.
at RustAdapter.cancel (/home/ciprian/.vscode/extensions/swellaby.vscode-rust-test-adapter-0.5.0/src/rust-adapter.js:106:15)
at TestAdapterDelegate.cancel (/home/ciprian/.vscode/extensions/hbenl.vscode-test-explorer-2.7.0/out/hub/testAdapterDelegate.js:25:22)
at cancel.collections.forEach.collection (/home/ciprian/.vscode/extensions/hbenl.vscode-test-explorer-2.7.0/out/testExplorer.js:126:67)
at Array.forEach (:null:null)
at TestExplorer.cancel (/home/ciprian/.vscode/extensions/hbenl.vscode-test-explorer-2.7.0/out/testExplorer.js:126:26)
at registerCommand (/home/ciprian/.vscode/extensions/hbenl.vscode-test-explorer-2.7.0/out/main.js:38:64)
at d._executeContributedCommand (/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:457:160)
....

It would be better if the Test Explorer extension wrapped each individual call to the adapter.cancel() in a try/catch block to allow non-failing extensions to continue the cancel operation.. Otherwise an extension that does not implement a certain operation (or has a bug) will stop the other extensions from working.

The same should be done for the other operations (e.g. run, load, etc)

After reloading a suite, the skipped (but already has run) test's state dissapears

Test Explorer version: 2.5

Output window's content still available, but the icon become

Let me know if this issue is too cheap and you need more info. Ty

Add top level filter for specs / tests

After running a full test suite, it would be practical to have a filter to let the user show only the tests that failed or that didn't run etc...

Request: xunit xml support?

Xunit xml offers a normalised way of reporting test results: https://xunit.github.io/docs/format-xml-v2

It seems to have fairly wide support in test runners. If test explorer supported this, it could be easier for adapter authors to report rich results eg ( kondratyev-nv/vscode-python-test-adapter#5 )

Show test statistics in the VSCode status bar

It would be useful if TestExplorerUI showed statistics in the status bar such as:

• total number of tests discovered (once discovery has completed)
• number of tests passed, failed, ignored/not run

Here's an example from the .Net Test Explorer extension:

Go to source doesn't work with absolute windows paths

When the file for a test case or suite is given as an absolute windows path, e.g. d:\src\test.cpp, fileToUri in util.ts parses it as an URI with scheme "d" instead of a file path, which then can't be opened.

A workaround could be:

const schemeMatcher = /^[a-z][a-z0-9+-.]*:/;
const winpathMatcher = /^[a-zA-Z]:\\/;
export function fileToUri(file: string): vscode.Uri {
	if (!winpathMatcher.test(file) && schemeMatcher.test(file)) {
		return vscode.Uri.parse(file);
	} else {
		return vscode.Uri.file(file);
	}
}

This should work as long as no test adapter produces absolute paths with forward slashes on windows...

Sort Test Suites

It would be nice to be able to sort the test suites alphabetically. If you have a lot of test suites in multiple folders, it's hard to find the one you are looking for in the explorer without going to the file and clicking the "Show in Test Explorer" button.

The "Run all tests" icon doesn't change (to red "Stop" icon) while the tests are running.

This was working yesterday.
(Since I refactored my code totally and changed vscode-test-adapter-api version too.)

Now:
"vscode-test-adapter-api": "^1.0.1"
Test Explorer UI: 2.0.1

(Maybe it is just me, 3th day with TS/JS and with VS Code)

What other relevant informations can I give?
(I will publish my source in a couple of days.)

Button on test tree to expand/collapse all test suites

Useful to quickly get a view of actual tests inside the test suites

Cancelling test run does not clear state of running suites/tests

If a test run locks up (or takes too long) and I cancel it by pressing the red stop button, my adapter will emit a TestRunFinishedEvent event ({ type: 'finished' }) to ensure the red button reverts to the 'play' icon. The problem is that the icons for the test suites that were still in progress do not change. It would be good if TestExplorer updated the states of these suites - perhaps to an "Errored" state?

Test suites before stopping the run:

and after stopping the run:

Note: in case it's relevant, when I run the tests, the adapter does not send TestSuiteEvents (either 'running' or 'completed') only TestEvents ('running', 'passed'/'failed'/etc.) The behaviour is as expected without the test suite events, except when stopping the test run.