|
1 | | -#### 1.5.6 May 16 2023 |
| 1 | +#### 1.5.8 June 15 2023 |
2 | 2 |
|
3 | | -* [Updated Akka.NET to 1.5.6](https://github.com/akkadotnet/akka.net/releases/tag/1.5.6) |
4 | | - |
5 | | -#### 1.5.0 March 02 2023 |
6 | | - |
7 | | -* [Updated Akka.NET to 1.5.0](https://github.com/akkadotnet/akka.net/releases/tag/1.5.0) |
8 | | - |
9 | | -#### 1.5.0-beta1 February 21 2023 |
10 | | - |
11 | | -* [Updated Akka.NET to 1.5.0-beta1](https://github.com/akkadotnet/akka.net/releases/tag/1.5.0) |
12 | | -* [Bump XUnit from 2.4.1 to 2.4.2](https://github.com/akkadotnet/Akka.MultiNodeTestRunner/pull/163) |
13 | | - |
14 | | -#### 1.1.1 April 21 2022 #### |
15 | | - |
16 | | -* [Updated Akka.NET to 1.4.37](https://github.com/akkadotnet/akka.net/releases/tag/1.4.37) |
17 | | -* [Enabled the built-in TRX reporter](https://github.com/akkadotnet/Akka.MultiNodeTestRunner/pull/134) that is compatible with AzDo test error reporting. |
18 | | -To enable this TRX reporter, add `"useBuiltInTrxReporter": true` inside the `xunit.multinode.runner.json` settings file. |
19 | | - |
20 | | -#### 1.1.0 January 6 2022 #### |
21 | | - |
22 | | -Version 1.1.0 release. |
23 | | - |
24 | | -#### 1.1.0-beta2 December 23 2021 #### |
25 | | -- [Add support for Xunit TestFrameworkAttribute attribute](https://github.com/akkadotnet/Akka.MultiNodeTestRunner/pull/116) |
26 | | - |
27 | | -In this release we added `MultiNodeTestFramework` to simplify non-parallel test setup. This test |
28 | | -framework is a simple override of the built-in `XunitTestFramework` that disables/ignores the |
29 | | -Xunit `CollectionBehaviorAttribute`, put all test classes from a single assembly into a single test |
30 | | -collection, and disables the test collection parallelization. |
31 | | - |
32 | | -To use this test framework, you will need to add an assembly level attribute that tells Xunit to |
33 | | -use this custom test framework instead: |
34 | | - |
35 | | -```c# |
36 | | -[assembly: TestFramework("Akka.MultiNode.TestAdapter.MultiNodeTestFramework", "Akka.MultiNode.TestAdapter")] |
37 | | -``` |
38 | | - |
39 | | -Note that you can also use this assembly level attribute to achieve more or less the same effect: |
40 | | -```c# |
41 | | -[assembly: CollectionBehavior(DisableTestParallelization = true)] |
42 | | -``` |
43 | | - |
44 | | -#### 1.1.0-beta1 October 20 2021 #### |
45 | | - |
46 | | -- [Switch to pure Xunit implementation](https://github.com/akkadotnet/Akka.MultiNodeTestRunner/pull/105) |
47 | | - |
48 | | -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: |
49 | | - |
50 | | -- Moved `.runsettings` configuration feature to `xunit.multinode.runner.json` |
51 | | - |
52 | | - `.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: |
53 | | - - `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. |
54 | | - __Default:__ `TestResults` in the folder where the tested assembly is located. |
55 | | - - `failedSpecsDirectory`: an output directory __inside the `outputDirectory`__ where all aggregated failed logs will be stored. |
56 | | - __Default:__ `FAILED_SPECS_LOGS` |
57 | | - - `listenAddress`: the host name or IP of the machine that is running the test. Will be bound to the TCP logging service. |
58 | | - __Default:__ `127.0.0.1` (localhost) |
59 | | - - `listenPort`: the port where the TCP logging service will be listening to. a random free port will be used if set to 0. |
60 | | - __Default:__ 0 |
61 | | - - `appendLogOutput`: if set, all logs are appended to the old logs from previous runs. |
62 | | - __Default:__ true |
63 | | - |
64 | | -- Parallelized test support (__BETA__) |
65 | | - |
66 | | - Tests can be run in parallel now, with caveats. Parallel test is not recommended if any of your tests are very timing dependent; |
67 | | - 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](https://xunit.net/docs/running-tests-in-parallel) on how to set this up. |
68 | | - |
69 | | - 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. |
70 | | - |
71 | | -#### 1.0.0 October 20 2019 #### |
72 | | -- Fix [result folder clearing, add documentation](https://github.com/akkadotnet/Akka.MultiNodeTestRunner/pull/95) |
73 | | - |
74 | | -#### 1.0.0-beta2 October 05 2019 #### |
75 | | -- Fix, [node runner should ignore runs not started by MNTR](https://github.com/akkadotnet/Akka.MultiNodeTestRunner/pull/93) |
76 | | - |
77 | | -#### 1.0.0-beta1 October 05 2019 #### |
78 | | -First beta release |
79 | | - |
80 | | -#### 0.1.13 October 05 2019 #### |
81 | | -Initial commit |
| 3 | +* [Updated Akka.NET to 1.5.8](https://github.com/akkadotnet/akka.net/releases/tag/1.5.8) - which resolves issues with Akka.NET runtime and `Polyfill` errors. |
0 commit comments