Akka.MultiNode.TestAdapter v1.5.19

1.5.19 April 20 2024

• Updated Akka.NET to 1.5.19
• Fix TRX exporter NullReferenceException bug

1.5.18 April 12 2024

• Updated Akka.NET to 1.5.18
• Dependency updates:
  • Update System.CodeDom to 8.0.0
  • Update TeamCity.ServiceMessages to 4.1.1
  • Update xUnit to 2.5.3

1.5.13 September 19 2023

• Updated Akka.NET to 1.5.13
• Dependency updates:
  • Update xUnit to 2.5.0
  • Update TeamCity.ServiceMessages to 4.0.0

1.5.8 June 15 2023

• Updated Akka.NET to 1.5.8 - which resolves issues with Akka.NET runtime and Polyfill errors.

Changes:

• 89a0cd8 Update RELEASE_NOTES.md for 1.5.19 release (#235)
• 74a9ccb Bump Akka.Cluster.TestKit from 1.5.18 to 1.5.19 (#233)
• 682fb03 Fix TRX NRE bug (#234)

This list of changes was auto generated.

Akka.MultiNode.TestAdapter v1.5.18

1.5.18 April 12 2024

• Updated Akka.NET to 1.5.18
• Dependency updates:
  • Update System.CodeDom to 8.0.0
  • Update TeamCity.ServiceMessages to 4.1.1
  • Update xUnit to 2.5.3

1.5.13 September 19 2023

• Updated Akka.NET to 1.5.13
• Dependency updates:
  • Update xUnit to 2.5.0
  • Update TeamCity.ServiceMessages to 4.0.0

1.5.8 June 15 2023

• Updated Akka.NET to 1.5.8 - which resolves issues with Akka.NET runtime and Polyfill errors.

Changes:

• 78057df Update RELEASE_NOTES.md for 1.5.18 release (#232)
• 191cbd0 Modernize NuGet packages to fit Akka.NET 1.5.18 (#228)
• e13ce3c Bump xunit.runner.visualstudio from 2.5.0 to 2.5.7 (#222)
• abfa4d2 Bump TeamCity.ServiceMessages from 4.0.0 to 4.1.1 (#205)
• 5e06e59 Bump System.CodeDom from 7.0.0 to 8.0.0 (#217)
• 0ab411a Bump Microsoft.NET.Test.Sdk from 17.7.2 to 17.8.0 (#216)
• 83c80e9 Bump Microsoft.SourceLink.GitHub from 1.1.1 to 8.0.0 (#218)
• a8c6888 Bump xunit.runner.utility from 2.5.0 to 2.6.2 (#220)

This list of changes was auto generated.

Akka.MultiNode.TestAdapter v1.5.13

1.5.13 September 19 2023

• Updated Akka.NET to 1.5.13
• Dependency updates:
  • Update xUnit to 2.5.0
  • Update TeamCity.ServiceMessages to 4.0.0

1.5.8 June 15 2023

• Updated Akka.NET to 1.5.8 - which resolves issues with Akka.NET runtime and Polyfill errors.

Changes:

• fe97ba5 Update RELEASE_NOTES.md for 1.5.13 release (#203)
• 94ef39c Modernize solution (#201)
• a9b0a59 Bump Microsoft.NET.Test.Sdk from 17.6.3 to 17.7.2 (#197)
• 22fcceb Bump Microsoft.NET.Test.Sdk from 17.6.2 to 17.6.3 (#186)
• e358601 Bump FluentAssertions from 6.6.0 to 6.11.0 (#174)

This list of changes was auto generated.

Akka.MultiNode.TestAdapter v1.5.8

1.5.8 June 15 2023

• Updated Akka.NET to 1.5.8 - which resolves issues with Akka.NET runtime and Polyfill errors.

Changes:

• 60e6cea Added v1.5.8 release notes (#185)
• 0132489 Bump Microsoft.NET.Test.Sdk from 17.5.0 to 17.6.2 (#184)
• 7d2acf6 Bump Akka.Cluster.TestKit from 1.5.6 to 1.5.7 (#182)

This list of changes was auto generated.

Akka.MultiNode.TestAdapter v1.5.6

1.5.6 May 16 2023

• Updated Akka.NET to 1.5.6

1.5.0 March 02 2023

• Updated Akka.NET to 1.5.0

1.5.0-beta1 February 21 2023

• Updated Akka.NET to 1.5.0-beta1
• Bump XUnit from 2.4.1 to 2.4.2

1.1.1 April 21 2022

• Updated Akka.NET to 1.4.37
• Enabled the built-in TRX reporter that is compatible with AzDo test error reporting.
  To enable this TRX reporter, add "useBuiltInTrxReporter": true inside the xunit.multinode.runner.json settings file.

1.1.0 January 6 2022

Version 1.1.0 release.

1.1.0-beta2 December 23 2021

• Add support for Xunit TestFrameworkAttribute attribute

In this release we added MultiNodeTestFramework to simplify non-parallel test setup. This test
framework is a simple override of the built-in XunitTestFramework that disables/ignores the
Xunit CollectionBehaviorAttribute, put all test classes from a single assembly into a single test
collection, and disables the test collection parallelization.

To use this test framework, you will need to add an assembly level attribute that tells Xunit to
use this custom test framework instead:

[assembly: TestFramework("Akka.MultiNode.TestAdapter.MultiNodeTestFramework", "Akka.MultiNode.TestAdapter")]

Note that you can also use this assembly level attribute to achieve more or less the same effect:

[assembly: CollectionBehavior(DisableTestParallelization = true)]

1.1.0-beta1 October 20 2021

• Switch to pure Xunit implementation

In this release we removed VSTest Adapter and moved to a pure Xunit implementation. This brings about a few changes that needs to be observed:

• Moved .runsettings configuration feature to xunit.multinode.runner.json

  .runsettings content are not passed downstream by dotnet test to the actual test runner, so this feature is moved to Xunit-like configuration through a .json file. You can declare your setting file name as either {assembly_name}.xunit.multinode.runner.json or xunit.multinode.runner.json. Supported settings are:

  • outputDirectory: the output directory where all the runner logs will be stored. Note that this is different than the dotnet test --result-directory settings which dictates where the VSTest reporter will export their outputs.
    Default: TestResults in the folder where the tested assembly is located.
  • failedSpecsDirectory: an output directory inside the outputDirectory where all aggregated failed logs will be stored.
    Default: FAILED_SPECS_LOGS
  • listenAddress: the host name or IP of the machine that is running the test. Will be bound to the TCP logging service.
    Default: 127.0.0.1 (localhost)
  • listenPort: the port where the TCP logging service will be listening to. a random free port will be used if set to 0.
    Default: 0
  • appendLogOutput: if set, all logs are appended to the old logs from previous runs.
    Default: true

• Parallelized test support (BETA)

  Tests can be run in parallel now, with caveats. Parallel test is not recommended if any of your tests are very timing dependent;
  it is still recommended that you do not run your tests in parallel. Note that Xunit turns this feature on by default, so if your tests are failing, make sure that this feature is properly turned off. Please read the xunit documentation on how to set this up.

  Note that the maxParallelThreads in Xunit will not be honored by this test adapter because MultiNode tests will spawn a process for every cluster node being used inside the test, inflating the number of threads being used inside a test.

1.0.0 October 20 2019

• Fix result folder clearing, add documentation

1.0.0-beta2 October 05 2019

• Fix, node runner should ignore runs not started by MNTR

1.0.0-beta1 October 05 2019

First beta release

0.1.13 October 05 2019

Initial commit

Changes:

• 522bdc8 Update RELEASE_NOTES.md for 1.5.6 release (#180)
• dfd24ae Bump Akka.Cluster.TestKit from 1.5.2 to 1.5.6 (#178)
• 202cbdf Bump xunit.runner.visualstudio from 2.4.2 to 2.4.5 (#166)
• 7dd7664 Bump Akka.Cluster.TestKit from 1.5.0 to 1.5.2 (#173)

This list of changes was auto generated.

Akka.MultiNode.TestAdapter v1.5.0

1.5.0 March 02 2023

• Updated Akka.NET to 1.5.0

1.5.0-beta1 February 21 2023

• Updated Akka.NET to 1.5.0-beta1
• Bump XUnit from 2.4.1 to 2.4.2

1.1.1 April 21 2022

• Updated Akka.NET to 1.4.37
• Enabled the built-in TRX reporter that is compatible with AzDo test error reporting.
  To enable this TRX reporter, add "useBuiltInTrxReporter": true inside the xunit.multinode.runner.json settings file.

1.1.0 January 6 2022

Version 1.1.0 release.

1.1.0-beta2 December 23 2021

• Add support for Xunit TestFrameworkAttribute attribute

In this release we added MultiNodeTestFramework to simplify non-parallel test setup. This test
framework is a simple override of the built-in XunitTestFramework that disables/ignores the
Xunit CollectionBehaviorAttribute, put all test classes from a single assembly into a single test
collection, and disables the test collection parallelization.

To use this test framework, you will need to add an assembly level attribute that tells Xunit to
use this custom test framework instead:

[assembly: TestFramework("Akka.MultiNode.TestAdapter.MultiNodeTestFramework", "Akka.MultiNode.TestAdapter")]

Note that you can also use this assembly level attribute to achieve more or less the same effect:

[assembly: CollectionBehavior(DisableTestParallelization = true)]

1.1.0-beta1 October 20 2021

• Switch to pure Xunit implementation

In this release we removed VSTest Adapter and moved to a pure Xunit implementation. This brings about a few changes that needs to be observed:

• Moved .runsettings configuration feature to xunit.multinode.runner.json

  .runsettings content are not passed downstream by dotnet test to the actual test runner, so this feature is moved to Xunit-like configuration through a .json file. You can declare your setting file name as either {assembly_name}.xunit.multinode.runner.json or xunit.multinode.runner.json. Supported settings are:

  • outputDirectory: the output directory where all the runner logs will be stored. Note that this is different than the dotnet test --result-directory settings which dictates where the VSTest reporter will export their outputs.
    Default: TestResults in the folder where the tested assembly is located.
  • failedSpecsDirectory: an output directory inside the outputDirectory where all aggregated failed logs will be stored.
    Default: FAILED_SPECS_LOGS
  • listenAddress: the host name or IP of the machine that is running the test. Will be bound to the TCP logging service.
    Default: 127.0.0.1 (localhost)
  • listenPort: the port where the TCP logging service will be listening to. a random free port will be used if set to 0.
    Default: 0
  • appendLogOutput: if set, all logs are appended to the old logs from previous runs.
    Default: true

• Parallelized test support (BETA)

  Tests can be run in parallel now, with caveats. Parallel test is not recommended if any of your tests are very timing dependent;
  it is still recommended that you do not run your tests in parallel. Note that Xunit turns this feature on by default, so if your tests are failing, make sure that this feature is properly turned off. Please read the xunit documentation on how to set this up.

  Note that the maxParallelThreads in Xunit will not be honored by this test adapter because MultiNode tests will spawn a process for every cluster node being used inside the test, inflating the number of threads being used inside a test.

1.0.0 October 20 2019

• Fix result folder clearing, add documentation

1.0.0-beta2 October 05 2019

• Fix, node runner should ignore runs not started by MNTR

1.0.0-beta1 October 05 2019

First beta release

0.1.13 October 05 2019

Initial commit

Changes:

• 34333d6 upgraded to Akka.NET v1.5 (#171)
• 57f8b9f Bump System.CodeDom from 6.0.0 to 7.0.0 (#153)
• 0c92e61 Bump Akka.Cluster.TestKit from 1.5.0-beta1 to 1.5.0-beta3 (#168)
• e8093b2 Bump Microsoft.NET.Test.Sdk from 17.4.1 to 17.5.0 (#164)

This list of changes was auto generated.

Akka.MultiNode.TestAdapter v1.5.0-beta1

1.5.0-beta1 February 21 2023

• Updated Akka.NET to 1.5.0-beta1
• Bump XUnit from 2.4.1 to 2.4.2

1.1.1 April 21 2022

• Updated Akka.NET to 1.4.37
• Enabled the built-in TRX reporter that is compatible with AzDo test error reporting.
  To enable this TRX reporter, add "useBuiltInTrxReporter": true inside the xunit.multinode.runner.json settings file.

1.1.0 January 6 2022

Version 1.1.0 release.

1.1.0-beta2 December 23 2021

• Add support for Xunit TestFrameworkAttribute attribute

In this release we added MultiNodeTestFramework to simplify non-parallel test setup. This test
framework is a simple override of the built-in XunitTestFramework that disables/ignores the
Xunit CollectionBehaviorAttribute, put all test classes from a single assembly into a single test
collection, and disables the test collection parallelization.

To use this test framework, you will need to add an assembly level attribute that tells Xunit to
use this custom test framework instead:

[assembly: TestFramework("Akka.MultiNode.TestAdapter.MultiNodeTestFramework", "Akka.MultiNode.TestAdapter")]

Note that you can also use this assembly level attribute to achieve more or less the same effect:

[assembly: CollectionBehavior(DisableTestParallelization = true)]

1.1.0-beta1 October 20 2021

• Switch to pure Xunit implementation

In this release we removed VSTest Adapter and moved to a pure Xunit implementation. This brings about a few changes that needs to be observed:

• Moved .runsettings configuration feature to xunit.multinode.runner.json

  .runsettings content are not passed downstream by dotnet test to the actual test runner, so this feature is moved to Xunit-like configuration through a .json file. You can declare your setting file name as either {assembly_name}.xunit.multinode.runner.json or xunit.multinode.runner.json. Supported settings are:

  • outputDirectory: the output directory where all the runner logs will be stored. Note that this is different than the dotnet test --result-directory settings which dictates where the VSTest reporter will export their outputs.
    Default: TestResults in the folder where the tested assembly is located.
  • failedSpecsDirectory: an output directory inside the outputDirectory where all aggregated failed logs will be stored.
    Default: FAILED_SPECS_LOGS
  • listenAddress: the host name or IP of the machine that is running the test. Will be bound to the TCP logging service.
    Default: 127.0.0.1 (localhost)
  • listenPort: the port where the TCP logging service will be listening to. a random free port will be used if set to 0.
    Default: 0
  • appendLogOutput: if set, all logs are appended to the old logs from previous runs.
    Default: true

• Parallelized test support (BETA)

  Tests can be run in parallel now, with caveats. Parallel test is not recommended if any of your tests are very timing dependent;
  it is still recommended that you do not run your tests in parallel. Note that Xunit turns this feature on by default, so if your tests are failing, make sure that this feature is properly turned off. Please read the xunit documentation on how to set this up.

  Note that the maxParallelThreads in Xunit will not be honored by this test adapter because MultiNode tests will spawn a process for every cluster node being used inside the test, inflating the number of threads being used inside a test.

1.0.0 October 20 2019

• Fix result folder clearing, add documentation

1.0.0-beta2 October 05 2019

• Fix, node runner should ignore runs not started by MNTR

1.0.0-beta1 October 05 2019

First beta release

0.1.13 October 05 2019

Initial commit

Changes:

• 0d4f7e6 Update RELEASE_NOTES.md for 1.5.0-beta1 release (#165)
• 8294e54 Bump NuGet dependencies to match Akka.NET 1.5 (#163)
• 4117353 Add v1.x branch CI/CD support (#161) (#162)

This list of changes was auto generated.

Akka.MultiNode.TestAdapter v1.1.1

1.1.1 April 21 2022

• Updated Akka.NET to 1.4.37
• Enabled the built-in TRX reporter that is compatible with AzDo test error reporting.
  To enable this TRX reporter, add "useBuiltInTrxReporter": true inside the xunit.multinode.runner.json settings file.

1.1.0 January 6 2022

Version 1.1.0 release.

1.1.0-beta2 December 23 2021

• Add support for Xunit TestFrameworkAttribute attribute

In this release we added MultiNodeTestFramework to simplify non-parallel test setup. This test
framework is a simple override of the built-in XunitTestFramework that disables/ignores the
Xunit CollectionBehaviorAttribute, put all test classes from a single assembly into a single test
collection, and disables the test collection parallelization.

To use this test framework, you will need to add an assembly level attribute that tells Xunit to
use this custom test framework instead:

[assembly: TestFramework("Akka.MultiNode.TestAdapter.MultiNodeTestFramework", "Akka.MultiNode.TestAdapter")]

Note that you can also use this assembly level attribute to achieve more or less the same effect:

[assembly: CollectionBehavior(DisableTestParallelization = true)]

1.1.0-beta1 October 20 2021

• Switch to pure Xunit implementation

In this release we removed VSTest Adapter and moved to a pure Xunit implementation. This brings about a few changes that needs to be observed:

• Moved .runsettings configuration feature to xunit.multinode.runner.json

  .runsettings content are not passed downstream by dotnet test to the actual test runner, so this feature is moved to Xunit-like configuration through a .json file. You can declare your setting file name as either {assembly_name}.xunit.multinode.runner.json or xunit.multinode.runner.json. Supported settings are:

  • outputDirectory: the output directory where all the runner logs will be stored. Note that this is different than the dotnet test --result-directory settings which dictates where the VSTest reporter will export their outputs.
    Default: TestResults in the folder where the tested assembly is located.
  • failedSpecsDirectory: an output directory inside the outputDirectory where all aggregated failed logs will be stored.
    Default: FAILED_SPECS_LOGS
  • listenAddress: the host name or IP of the machine that is running the test. Will be bound to the TCP logging service.
    Default: 127.0.0.1 (localhost)
  • listenPort: the port where the TCP logging service will be listening to. a random free port will be used if set to 0.
    Default: 0
  • appendLogOutput: if set, all logs are appended to the old logs from previous runs.
    Default: true

• Parallelized test support (BETA)

  Tests can be run in parallel now, with caveats. Parallel test is not recommended if any of your tests are very timing dependent;
  it is still recommended that you do not run your tests in parallel. Note that Xunit turns this feature on by default, so if your tests are failing, make sure that this feature is properly turned off. Please read the xunit documentation on how to set this up.

  Note that the maxParallelThreads in Xunit will not be honored by this test adapter because MultiNode tests will spawn a process for every cluster node being used inside the test, inflating the number of threads being used inside a test.

1.0.0 October 20 2019

• Fix result folder clearing, add documentation

1.0.0-beta2 October 05 2019

• Fix, node runner should ignore runs not started by MNTR

1.0.0-beta1 October 05 2019

First beta release

0.1.13 October 05 2019

Initial commit

Changes:

• 79992ec Version 1.1.1 Release
• 0c26871 Merge branch 'dev'
• 2dcd783 Update RELEASE_NOTES.md for 1.1.1 release (#135)
• 56ef6fc Bump System.CodeDom from 5.0.0 to 6.0.0 (#106)
• e764691 Bump Akka.Cluster.TestKit from 1.4.35 to 1.4.37 (#133)
• 1ed1172 Bump FluentAssertions from 6.3.0 to 6.6.0 (#131)
• 59673eb Bump Microsoft.NET.Test.Sdk from 17.0.0 to 17.1.0 (#128)
• ff2d528 Enable the built in TRX reporter for proper error reporting in AzDo (#134)
• 0d1c66b Bump Akka.Cluster.TestKit from 1.4.31 to 1.4.35 (#130)

This list of changes was auto generated.

Akka.MultiNode.TestAdapter v1.1.0

1.1.0 January 6 2022

Version 1.1.0 release.

1.1.0-beta2 December 23 2021

• Add support for Xunit TestFrameworkAttribute attribute

In this release we added MultiNodeTestFramework to simplify non-parallel test setup. This test
framework is a simple override of the built-in XunitTestFramework that disables/ignores the
Xunit CollectionBehaviorAttribute, put all test classes from a single assembly into a single test
collection, and disables the test collection parallelization.

To use this test framework, you will need to add an assembly level attribute that tells Xunit to
use this custom test framework instead:

[assembly: TestFramework("Akka.MultiNode.TestAdapter.MultiNodeTestFramework", "Akka.MultiNode.TestAdapter")]

Note that you can also use this assembly level attribute to achieve more or less the same effect:

[assembly: CollectionBehavior(DisableTestParallelization = true)]

1.1.0-beta1 October 20 2021

• Switch to pure Xunit implementation

In this release we removed VSTest Adapter and moved to a pure Xunit implementation. This brings about a few changes that needs to be observed:

• Moved .runsettings configuration feature to xunit.multinode.runner.json

  .runsettings content are not passed downstream by dotnet test to the actual test runner, so this feature is moved to Xunit-like configuration through a .json file. You can declare your setting file name as either {assembly_name}.xunit.multinode.runner.json or xunit.multinode.runner.json. Supported settings are:

  • outputDirectory: the output directory where all the runner logs will be stored. Note that this is different than the dotnet test --result-directory settings which dictates where the VSTest reporter will export their outputs.
    Default: TestResults in the folder where the tested assembly is located.
  • failedSpecsDirectory: an output directory inside the outputDirectory where all aggregated failed logs will be stored.
    Default: FAILED_SPECS_LOGS
  • listenAddress: the host name or IP of the machine that is running the test. Will be bound to the TCP logging service.
    Default: 127.0.0.1 (localhost)
  • listenPort: the port where the TCP logging service will be listening to. a random free port will be used if set to 0.
    Default: 0
  • appendLogOutput: if set, all logs are appended to the old logs from previous runs.
    Default: true

• Parallelized test support (BETA)

  Tests can be run in parallel now, with caveats. Parallel test is not recommended if any of your tests are very timing dependent;
  it is still recommended that you do not run your tests in parallel. Note that Xunit turns this feature on by default, so if your tests are failing, make sure that this feature is properly turned off. Please read the xunit documentation on how to set this up.

  Note that the maxParallelThreads in Xunit will not be honored by this test adapter because MultiNode tests will spawn a process for every cluster node being used inside the test, inflating the number of threads being used inside a test.

1.0.0 October 20 2019

• Fix result folder clearing, add documentation

1.0.0-beta2 October 05 2019

• Fix, node runner should ignore runs not started by MNTR

1.0.0-beta1 October 05 2019

First beta release

0.1.13 October 05 2019

Initial commit

Changes:

• 62d6712 Version 1.1.0 Release
• 5030d07 Merge branch 'dev'
• 3c8e570 Update RELEASE_NOTES.md for v1.1.0 release (#121)
• db9f6c0 Update README for the new json based settings (#120)
• e926f2e Bump FluentAssertions from 6.2.0 to 6.3.0 (#119)

This list of changes was auto generated.

Akka.MultiNode.TestAdapter v1.1.0-beta2

1.1.0-beta2 December 23 2019

• Add support for Xunit TestFrameworkAttribute attribute

In this release we added MultiNodeTestFramework to simplify non-parallel test setup. This test
framework is a simple override of the built-in XunitTestFramework that disables/ignores the
Xunit CollectionBehaviorAttribute, put all test classes from a single assembly into a single test
collection, and disables the test collection parallelization.

To use this test framework, you will need to add an assembly level attribute that tells Xunit to
use this custom test framework instead:

[assembly: TestFramework("Akka.MultiNode.TestAdapter.MultiNodeTestFramework", "Akka.MultiNode.TestAdapter")]

Note that you can also use this assembly level attribute to achieve more or less the same effect:

[assembly: CollectionBehavior(DisableTestParallelization = true)]

1.1.0-beta1 October 20 2019

• Switch to pure Xunit implementation

In this release we removed VSTest Adapter and moved to a pure Xunit implementation. This brings about a few changes that needs to be observed:

• Moved .runsettings configuration feature to xunit.multinode.runner.json

  .runsettings content are not passed downstream by dotnet test to the actual test runner, so this feature is moved to Xunit-like configuration through a .json file. You can declare your setting file name as either {assembly_name}.xunit.multinode.runner.json or xunit.multinode.runner.json. Supported settings are:

  • outputDirectory: the output directory where all the runner logs will be stored. Note that this is different than the dotnet test --result-directory settings which dictates where the VSTest reporter will export their outputs.
    Default: TestResults in the folder where the tested assembly is located.
  • failedSpecsDirectory: an output directory inside the outputDirectory where all aggregated failed logs will be stored.
    Default: FAILED_SPECS_LOGS
  • listenAddress: the host name or IP of the machine that is running the test. Will be bound to the TCP logging service.
    Default: 127.0.0.1 (localhost)
  • listenPort: the port where the TCP logging service will be listening to. a random free port will be used if set to 0.
    Default: 0
  • appendLogOutput: if set, all logs are appended to the old logs from previous runs.
    Default: true

• Parallelized test support (BETA)

  Tests can be run in parallel now, with caveats. Parallel test is not recommended if any of your tests are very timing dependent;
  it is still recommended that you do not run your tests in parallel. Note that Xunit turns this feature on by default, so if your tests are failing, make sure that this feature is properly turned off. Please read the xunit documentation on how to set this up.

  Note that the maxParallelThreads in Xunit will not be honored by this test adapter because MultiNode tests will spawn a process for every cluster node being used inside the test, inflating the number of threads being used inside a test.

1.0.0 October 20 2019

• Fix result folder clearing, add documentation

1.0.0-beta2 October 05 2019

• Fix, node runner should ignore runs not started by MNTR

1.0.0-beta1 October 05 2019

First beta release

0.1.13 October 05 2019

Initial commit

Changes:

• c43455c Version 1.1.0-beta2 release
• 4578657 Merge branch 'dev'
• 25499db Update RELEASE_NOTES.md for 1.1.0-beta2 release (#117)
• 350d87c Add Xunit TestFrameworkAttribute support (#116)
• 7ff1f5d Bump Akka.Cluster.TestKit from 1.4.27 to 1.4.31 (#115)
• c0f0679 Bump MSBuild.Sdk.Extras from 3.0.38 to 3.0.44 (#114)
• 7bc2ac2 Bump Microsoft.SourceLink.GitHub from 1.0.0 to 1.1.1 (#111)
• 529608f 1.1.0-beta1 Release
• 8724ee5 Merge branch 'dev'
• 25c3214 Update release notes for 1.1.0 beta1 (#108)

See More

• 5047db5 Pure Xunit implementation (#105)
• bebe537 Fix console output problem, dotnet test appeared to hang (#102)
• bf04a68 Bump TestSdkVersion from 16.11.0 to 17.0.0 (#99)
• 97f7814 Bump FluentAssertions from 6.1.0 to 6.2.0 (#98)
• af3a22f Merge remote-tracking branch 'upstream/master'
• 04be23e Merge branch 'dev'
• 8138353 Update RELEASE_NOTES.md for 1.0.0 release (#96)
• fb7ec45 Add documentation (#95)

This list of changes was auto generated.