2019-03-20 16:30:59 +03:00
|
|
|
teamcity-event-listener 1.0.6 - Mar 20, 2019
|
2018-12-13 11:53:51 +03:00
|
|
|
|
|
|
|
New Features
|
|
|
|
|
2019-03-20 16:30:59 +03:00
|
|
|
* 0063 Support [test metadata](https://confluence.jetbrains.com/display/TCD18/Reporting+Test+Metadata), TeamCity 2018.2+.
|
|
|
|
* 0067 Support suite patterns
|
|
|
|
|
|
|
|
Issues Resolved
|
|
|
|
|
|
|
|
* 0065 The suite name is different for the test in two different builds for NUnit tests
|
|
|
|
* 0066 Use process ID as a root flow id if the root flow id environment variable (TEAMCITY_PROCESS_FLOW_ID) was not specified
|
2018-12-13 11:53:51 +03:00
|
|
|
|
|
|
|
teamcity-event-listener 1.0.5 - Nov 19, 2018
|
|
|
|
|
|
|
|
Issues Resolved
|
|
|
|
|
|
|
|
* Running NUnit3 multiple times results in test being categorized as "<no suite>" - add flowStarted and flowFinished for root flow from default
|
|
|
|
* Use TeamCity parent flow Id - use root flow id from env var TEAMCITY_PROCESS_FLOW_ID if is was specidied
|
|
|
|
* Support testStdErr
|
|
|
|
* the 'message' attribute used instead of the 'text' attribute on "message" service message
|
|
|
|
|
|
|
|
teamcity-event-listener 1.0.4 - Dec 5, 2017
|
2017-12-05 11:16:16 +03:00
|
|
|
|
|
|
|
Issues Resolved
|
|
|
|
|
|
|
|
* 0051 Add stack trace to tests' details of TeamCity service messages when tests fail during TestFixtureSetUpAttribute for NUnit framework 2
|
|
|
|
|
|
|
|
teamcity-event-listener 1.0.3 - Nov 22, 2017
|
2017-11-22 12:10:15 +03:00
|
|
|
|
|
|
|
Issues Resolved
|
|
|
|
|
|
|
|
* 0049 Add stack trace to tests' details of TeamCity service messages when tests fail during TestFixture SetUp/TearDown
|
|
|
|
|
|
|
|
teamcity-event-listener 1.0.2 - Oct 1, 2016
|
2016-09-28 16:21:18 +03:00
|
|
|
|
|
|
|
Issues Resolved
|
|
|
|
|
|
|
|
* 0006 TeamCity does not parse service messages inside errors/output of tests
|
|
|
|
* 0014 Erroneous TeamCity service messages with multiple test assemblies and (default) parallel execution
|