This repository has been archived by the owner on Jul 17, 2023. It is now read-only.
Releases: etas/vs-boost-unit-test-adapter
Releases · etas/vs-boost-unit-test-adapter
v1.0.9
Enhancements:
- Added Boost version identification.
- Added
One
test batch strategy (available as part of Boost.Test in Boost 1.63). - Suppress blocking assertion message boxes for test execution.
- Added Boost 1.64, Boost 1.65 support.
- Removed dependency over the need of debug symbols (PDB files).
- Identify test adapter execution through
BUTA
environment variable.
Bug fixes:
- Support file paths which utilise characters from system (native) encoding.
- Harden
--list_content=DOT
execution and react to process exit code. - Improve test adapter reaction to exceptional cases and note errors as test failures.
Contributions/Special Thanks:
- @gastart -
BUTA
environment variable red pill - @LukaszMendakiewicz - Boost 1.64, Boost 1.65 support
Pre-Requisites:
- Boost Libraries. The following versions are supported:
- Boost 1.60 and greater
- Microsoft Visual Studio. The following versions are supported:
- Visual Studio 2015 (Community, Professional, Enterprise).
Note:
- Test Adapter for Boost.Test for Visual Studio 2017 is now available from the Visual Studio Gallery courtesy of Microsoft.
v1.0.8
Enhancements:
- When using custom PATH environment, default PATH is no longer prepended.
- Filename is evaluated so as to allow the custom injection of custom command-line arguments.
- Added Boost 1.62 support.
- Removed the usage of the label trait so that multiple labels can be attributed to one test.
- Fixed symbol options to allow proper reading from release PDBs built using Visual Studio 2015 Update 3.
- Enhanced job management so as to ensure that cancelled test executions also cancel the currently running test.
- Added hyper linkable error stack trace.
- When relative paths are used, test navigation from the test explorer is not available, so logger output has been added so as to warn user that relative paths are in use.
- Enforced backward slashes for the working directory, that was causing the debugger to not launch.
- Fixed installation failure when a .Net framework version is higher than 4.5
- Discovery timeout increased from a default of 5 seconds to 30 seconds.
Breaking changes:
- Dropped support for Visual Studio 2012 and Visual Studio 2013.
- Dropped support for Boost 1.59 and less.
- Dropped test discovery option via source code parsing. Tests are enumerated only via the DOT report increasing the overall robustness and correctness of the test discovery. A warning is also issued in case the command --list_content=DOT is not available.
v1.0.7
Bug fixes:
- Better handling for cases when Boost Test report is not available.
- Memory leak reports are now scanned from standard error.
- Fix line number offsets when multi-line string literals are defined.
- Assume
BOOST_VERSION
macro.
New features:
- Environment specified in project properties are now taken into consideration for test discovery/exectution.
- Working Directory specified in project properties are now taken into consideration for test discovery/exectution.
- Support for
--list_content=DOT
test discovery. - Test
labels
are now exposed as test traits.
Enhancements:
- Better formatting and handling for test context information.
Breaking changes:
- Boost Test adapter now takes into consideration the Working Directory as specified in the Debugging section of the project properties.
v1.0.6
Bug fixes:
- Added more robust handling of any invalid characters (such as the Control characters) that might be present in the XML files generated by certain versions of the Boost Unit Test framework and that are then consumed by the Boost Unit Test Adapter in order to display the test results in the Test explorer window.
- Fix report and log
XML
format request for Boost 1.60. Thanks to @sergegers.
New features:
- Added configuration element
<CatchSystemErrors>
in the .runsettings file so as to support the functionality made available by the catch system errors parameter in the Boost Unit Test Framework. - Allow for configurable test execution. Tests can be batched depending on the
<TestBatchStrategy>
configuration element specified in the .runsettings file. - Experimental support for
--list_content
test discovery.
Enhancements:
- Optimized the speed of the String literals filter algorithm.
- Optimized the Boost Test Keywords search algorithm so as to permit faster test discovery.
- Harden external test runner discovery. Tests can also be filtered by path. Thanks to @teajay-fr.
- Allow
BOOST_TEST_
declarations to span over multiple lines. Thanks to @sergegers.
v1.0.5.0
Bug fixes:
- Property 'CreateNoWindow' of 'ProcessStartInfo' is set to true, as as to avoid having command-prompt windows popping up when running tests in Visual Studio 2015.
- The test execution time is set to be at least 1 tick long (because when the test execution time is very low, Boost UTF does not register it) so that a successfully executed test is properly listed in the adapter.
Build changes:
- The packages directory has been removed from source control and put under the control of NuGet (Nuget version 2.8.5 or later has to be utilized on the development machine)
v1.0.4.0
Misc:
- A major code re-factoring activity has been done.
- Release code as open source
New features:
- In the previous versions of the Boost Unit Test Adapter, there was no reporting with respect to memory leaks. The memory leaks information reported by Boost Unit Test Framework is now being parsed and reported to the user. The user is also given the possibility to fail a test if any memory leaks are discovered via a user settable option.
- In the previous versions only the last test result of a particular unit test was reported back to the user. In this new version, the user is able to see all the test results respective to a test.
- All the output (being what is commonly referred to as stdout and stderr) generated by a unit test is reported into an output screen accessible at unit test level.
- Any exceptions raised by the Boost Unit Test Adapter itself and any informational logs are now logged to a log file.
- Added support for nested test suites. The user is able to deduce the nesting level via the naming of the testcase as presented in the test explorer.
- Replaced and updated the user manual which was previously in a pdf format to one written in a GitHub flavoured markdown format.
- The user can now specify an execution timeout. If a test takes more than a configurable amount of time, the test is considered as failed.
- Conditional Inclusions statements such as #if....#elif....#else....#endif, #ifdef, #if defined, #ifndef, #if !defined are now supported with some limitations on the conditional complexity.
- Filtering for multi-line comments and single line comments are now much more robust.
- Created a Boost External Test Runner so that users can execute Boost Unit test project compiled as a dynamic link library.
- Added support to Microsoft Visual Studio 2015 RC.
- Added support that in case a source file is excluded from build(https://raw.githubusercontent.com/netspiri/vs-boost-unit-test-adapter/master/Doku/images/excluded_from_build.png) the source file is not parsed for any Boost Unit Tests.
- Header files are now also parsed for Boost Unit Tests.