v0.14.0

• enhancement: new placeholders $(PlatformName) and $(ConfigurationName) are available (#170)
• enhancement: the option Use new test execution framework (experimental) has been renamed into Use native debugging. It now only affects debugging of tests: native debuging supports test crash detection and printing test output (#106)
• bugfix: tests without source location did not receive traits by regex (#249)
• bugfix: user-provided regexes could run forever (#239)
• maintenance: code coverage has been improved (#247, thanks to frboyer for pull request)
• maintenance: the SampleTests solution now uses Google Test 1.8.1 (#248)

v0.13.4

• bugfix: there seem to be problems with the latest versions of Visual Studio and Visual Assist which also affect GTA; it should now handle such problems gracefully (#246, thanks to my colleague SH for providing useful information)

v0.13.3

• bugfix: fixed performance regression during test discovery (#230, thanks to gobater for report, debugging, and testing)
• bugfix: type-parameterized tests where the type name ended with class or struct resulted in a wrong display name (#236, thanks to gobater for report and pull request)

v0.13.2

• bugfix: source locations for tests contained in namespaces are found again (#227, thanks to lyn444 and Michał Fita for report and testing)

v0.13.1

• bugfix: an empty Working directory option would result in the $(ExecutableDir) placeholder being used as working dir (#204, thanks to DOTTEL Gaël for report and testing)
• bugfix: invalid entries in PATH variable could make PdbLocator crash (#227, thanks to lyn444 for report and testing)

v0.13.0

• enhancement: GTA can now also be used with the standalone version of VsTest.Console.exe pulled in via NuGet (#216, thanks to Satya Madala for report and testing)
• enhancement: Settings files can now be provided via environment variable GTA_FALLBACK_SETTINGS. This is a workaround for #184; the referred settings file will be used only if GTA fails to receive settings from the VS test framework. Currently, this is only known to happen when running GTA through VsTest.Console.exe on VS 2017 V15.5 and later (#212)
• enhancement: options Working directory, Test setup batch file, Test teardown batch file, Additional PDBs, PATH extension, and Additional test execution parameters now support the usage of environment variables (to be provided in the form %VAR_NAME%). Not that this is a breaking change: Test setup batch file and Test teardown batch file have until now been interpreted locally to the solution directory. This is not the case any more. If you use these options, prefix your current setting with $(SolutionDir) to maintain the old behavior (#202, thanks to dmcminn for report and testing)
• enhancement: the $(SolutionDir) placeholder is now also available during test discovery (#214, thanks to Lysann Schlegel for report and testing)
• enhancement: Working directory and Additional test execution parameters options are also in effect now during test discovery (#214, thanks to Lysann Schlegel for report and testing)
• enhancement: The new option Additional PDBs allows to provide additional PDBs for finding source file locations. This is useful if GTA is not able to find the according PDBs automatically (#153, thanks to Tony for report and testing)
• enhancement: added option Skip check of file origin for cases where the test executable is not on the local machine. Note that this option can only be set via VS Options - values in settings files will be ignored for security reasons (#179, thanks to Dominic van Berkel for report and testing)
• bugfix: the test executable's working directory is now set to the directory containing that executable during test discovery; the same holds during test execution in case Working directory is left blank (#188, thanks to DOTTEL Gaël for testing)
• bugfix: GTA could not handle test runs with lots of gtest suites to be executed (#192, thanks to MartinOSchmidt for report and pull request)
• bugfix: Working dir and Additional test execution params options had no effect if provided through project settings nodes
  (#214, thanks to Lysann Schlegel for report, suggestion for fix, and testing)
• bugfix: GTA was not able to figure out the Visual Studio version under some circumstances (#204, thanks to zahirtezcan-bugs for report and pull request)

v0.12.3

• bugfix: if retrieving the settings from the VS test framework failed, GTA's logger would not be initialized, causing a NullReferenceException when trying to report that problem (#186)

v0.12.2

• bugfix: fixed ArgumentException caused by concurrent writing to a List during test discovery (#185)

v0.12.1

• bugfix: fixed NullReferenceException which could occur during test discovery (#178, thanks to wasabinza for report and suggestion for fix)

v0.12.0

• enhancement: many enhancements emerging from the collaboration with Microsoft have made it into this release - thanks, Microsoft (and Lukasz Mendakiewisz in particular)!
  • the GTA toolbar has new (and more appropriate) icons
  • test discovery has been slightly accelerated
  • the origin of test executables is verified before running them - if they have not been created on the local machine, they will be ignored with a warning
  • settings and test duration files are now validated against their respective XML schema
  • dependencies on 3rd party libraries have been reduced
• bugfix: under very special circumstances, test executables containing spaces in their paths could not be run (TAFGT #18, thanks to Lukasz Mendakiewisz for fix)
• maintenance: The solution structure has been changed to allow building of the GTA as well as the TAfGT flavor of the extension while sharing the vast majority of the code. As a side effect, the build process has become slightly more complicated; contributors are pointed to the wiki. Thanks to Microsoft's Lukasz Mendakiewisz for making most of this happen!