Improved file watcher handling

[1.4.3] - 2020-09-04

Added

• Further detail around file discovery configuration (#41)

Fixed

• Fix duplication during file watcher events (#41)
• Fix test removal during file watcher events (#41)
• Fix namespace retrieval with non-dll assemblies (#39)

Changed

• Omnisharp extension name (#37)

Thanks to @vchirikov for spotting and fixing several of these issues

Test grouping and file path handling fixes

[1.4.1] - 2020-07-31

Added

• It's now possible to debug C# or C++ during test debugging
• New setting, attachCpp, flips between attaching a C# debugger or C++ debugger
• searchpatterns now additionally accepts an object to allow test grouping. Check the updated README for usage information. (#31)

Changed

• File watchers are now aligned with the search performed in the initial discovery phase

Fixed

• Test commands were run without the local environment (including PATH). This caused issues using the adapter locally in macOS.
• State management is not updated correctly when a test run is cancelled (#30)

For more detail about this release see #29 and #31

v1.2.0

[1.2.0] - 2020-02-19

Added

• Collect and report various errors encountered during discovery in a non-noisy way
• Report various error encountered during file watcher update
• Reporting file search and test loading separately during load operation
• Detecting errors encountered by vstest during discovery
• Detecting suites without test methods as a discovery error

Changed

• Pipe vstest output to ".Net Core Test Output" pane during discovery
• Use VSCode workspace.fs API for performant, compatible file operations

Fixed

• Loaded counts are reset prior to each load
• Previously reloading or updating (via file watchers) the suite was additive causing duplicate tests to appear. New suites replace old ones where the suite id matches
• Loaded count summarisation didn't correctly construct sentences when some counts were zero

More detail about this release

v1.1.0

[v1.1.0] - 2020-02-18

Added

• CodeLens integration can be disabled via a new codeLens setting. You'll need to reload the project for this to take effect

Changed

• The skippatterns array setting has changed to a string based skippattern setting. This is due to the glob optimising issue mentioned in "Fixed".

Fixed

• The adapter would previously attempt to optimise test discovery by combining glob patterns in the searchpatterns and skippatterns settings. This was done using the group condition syntax (i.e. {a,b}). When one of the provided glob patterns also used the group condition syntax, VSCode would throw an unreported error as it does not allow nested group conditions. We no longer apply this optimisation to skippatterns (which is why this is now a single string; see "Changed") and only apply the optimisation to searchpatterns where the syntax isn't used.

More detail about this release

Bump patch with correctly cased build files

Simple patch bump release to ensure built files had correct casing.

v1.0.0

Initial non-beta release of adapter