0.6.0

CHANGELOG.md

@@ -1,4 +1,4 @@
-## 0.6 ()
+## 0.6.0 (2018-11-14)
 * [#165](https://github.com/formulahendry/vscode-dotnet-test-explorer/pull/165): Multiple workspace support
 * [#164](https://github.com/formulahendry/vscode-dotnet-test-explorer/pull/164): Double-quote argument to dotnet --filter
 * [#156](https://github.com/formulahendry/vscode-dotnet-test-explorer/pull/156): Fix unfound tests when using Go to Test feature with F# 

README.md

@@ -11,14 +11,11 @@
 * [.NET Core](https://www.microsoft.com/net/core) is installed
 * NUnit and MsTest requires a dotnet [sdk](https://www.microsoft.com/net/download) version of >= 2.1.2 and running dotnet tooling in english (see [#77](https://github.com/formulahendry/vscode-dotnet-test-explorer/issues/77) for details).
 
-## New in 0.5.5
+## New in 0.6.0
 
-* You can now stop the current test run. After killing the processe(s) it will perform a new test discovery.
-
-![test-explorer](images/stop.PNG)
-
-* If the build fails the tree reflects this better
-* Code lens status symbols and running in tests in context should now work again.
+* We now support multiple workspaces. We will try to find tests in all of the folders according to the testProjectPath setting. See the section regarding [configuring multiple test projects](#configuring-multiple-test-projects)
+* Tests written in fsharp should be less unfoundable when trying to navigate to them
+* Filter argument are now double-quoted (again, let's hope they stay that way from now on)
 
 ## Usage
 
@@ -41,6 +38,12 @@ the glob pattern "+(testProjectOne|testProjectTwo)" or "**/*Tests.csproj" should
 
 Due to some performance concerns discovery and test running over multiple directories are run one at a time in a synchronous fashion. When running specific tests (eg, not running all tests) the extension should be smart enought to figure out which test directory should be run and only run tests for that directory.
 
+#### Stopping the current test runner(s)
+
+Press the stop button in the top menu. After killing the processe(s) it will perform a new test discovery.
+
+![test-explorer](images/stop.PNG)
+
 #### Logging
 
 Text from the dotnet test output as well as debug info is written to the Output/Test explorer terminal window. To view the log you can access it simply by clicking the view log icon.

package.json

@@ -2,7 +2,7 @@
   "name": "dotnet-test-explorer",
   "displayName": ".NET Core Test Explorer",
   "description": "Test Explorer for .NET Core (MSTest, xUnit, NUnit)",
-  "version": "0.5.5",
+  "version": "0.6.0",
   "publisher": "formulahendry",
   "license": "MIT",
   "icon": "testexplorer_dark.png",