Skip to content

Commit 62d6712

Browse files
authored
Version 1.1.0 Release
Version 1.1.0 Release
2 parents c43455c + 5030d07 commit 62d6712

File tree

4 files changed

+30
-27
lines changed

4 files changed

+30
-27
lines changed

README.md

Lines changed: 22 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,38 +1,39 @@
11
# Akka.MultiNode.TestAdapter
22

3-
Visual Studio 2019 Test Explorer and .NET CLI Test runner for the Akka.NET MultiNode tests
3+
Visual Studio 2019 Test Explorer, JetBrains Rider, and .NET CLI Test runner for the Akka.NET MultiNode tests
44

55
## Documentation
6-
`Akka.MultiNode.TestAdapter` is a standalone .NET CLI and VSTest adapter for Akka.NET multi node testkit;
7-
It allows you to run multinode tests directly inside Visual Studio Text Explorer window and run them
8-
using the `dotnet test` .NET CLI command.
6+
`Akka.MultiNode.TestAdapter` is a standalone test adapter for Akka.NET multi node testkit; it is based on the popular Xunit test framework to allow multinode tests to run directly inside popular C# IDE such as Microsoft Visual Studio and JetBrains Rider and run them using the `dotnet test` .NET CLI command.
97

10-
To use the VSTest test adapter in your multinode spec projects, You will need to add these nuget packages:
8+
To use the test adapter in your multinode spec projects, You will need to add these nuget packages:
119
- [Akka.MultiNode.TestAdapter](https://www.nuget.org/packages/Akka.MultiNode.TestAdapter)
1210
- [Microsoft.NET.Test.Sdk](https://www.nuget.org/packages/Microsoft.NET.Test.Sdk/)
1311

1412
Documentation regarding the multinode specs themselves can be read in the Akka.NET documentation pages:
1513
- [Using the MultiNode TestKit](https://getakka.net/articles/networking/multi-node-test-kit.html)
1614
- [Multi-Node Testing Distributed Akka.NET Applications](https://getakka.net/articles/testing/multi-node-testing.html)
1715

18-
### VSTest .runsettings
19-
This is the .runsettings XML sub-section `Akka.MultiNode.TestAdapter` can use:
20-
```xml
21-
<?xml version="1.0" encoding="utf-8"?>
22-
<RunSettings>
23-
<MultiNodeTestRunnerOptions>
24-
<ListenAddress>127.0.0.1</ListenAddress>
25-
<ListenPort>0</ListenPort>
26-
<ClearOutputDirectory>false</ClearOutputDirectory>
27-
<UseTeamCityFormatting>false</UseTeamCityFormatting>
28-
</MultiNodeTestRunnerOptions>
29-
</RunSettings>
16+
### Json Settings
17+
18+
This test adapter follows the Xunit convention on loading test configuration via a json file. It will
19+
check the directory where the test assembly is located for a `[Assembly Name].xunit.multinode.runner.json`
20+
or a `xunit.multinode.runner.json` file.
21+
22+
```json
23+
{
24+
"outputDirectory": "TestResults",
25+
"failedSpecsDirectory": "FAILED_SPECS_LOGS",
26+
"listenAddress": "127.0.0.1",
27+
"listenPort": 0,
28+
"clearOutputDirectory": false
29+
}
3030
```
3131

32-
- **ListenAddress**: Determines the address that this multi-node test runner will use to listen for log messages from individual spec.
33-
- **ListenPort**: Determines the port number that this multi-node test runner will use to listen for log messages from individual spec.
34-
- **ClearOutputDirectory**: Clear the output directory before running the test session. If set to false, all test logs are appended to the out file.
35-
- **UseTeamCityFormatting**: Use TeamCity formatting on the log outputs.
32+
* **outputDirectory**: Determines output directory for all log output files.
33+
* **failedSpecsDirectory**: Determines output directory for aggregated failed test logs.
34+
* **listenAddress**: Determines the address that this multi-node test runner will use to listen for log messages from individual spec.
35+
* **listenPort**: Determines the port number that this multi-node test runner will use to listen for log messages from individual spec.
36+
* **ClearOutputDirectory**: Clear the output directory before running the test session. If set to false, all test logs are appended to the out file.
3637

3738
## Building this solution
3839
To run the build script associated with this solution, execute the following:

RELEASE_NOTES.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,8 @@
1-
#### 1.1.0-beta2 December 23 2019 ####
1+
#### 1.1.0 January 6 2022 ####
2+
3+
Version 1.1.0 release.
4+
5+
#### 1.1.0-beta2 December 23 2021 ####
26
- [Add support for Xunit TestFrameworkAttribute attribute](https://github.com/akkadotnet/Akka.MultiNodeTestRunner/pull/116)
37

48
In this release we added `MultiNodeTestFramework` to simplify non-parallel test setup. This test
@@ -18,7 +22,7 @@ Note that you can also use this assembly level attribute to achieve more or less
1822
[assembly: CollectionBehavior(DisableTestParallelization = true)]
1923
```
2024

21-
#### 1.1.0-beta1 October 20 2019 ####
25+
#### 1.1.0-beta1 October 20 2021 ####
2226

2327
- [Switch to pure Xunit implementation](https://github.com/akkadotnet/Akka.MultiNodeTestRunner/pull/105)
2428

src/Akka.MultiNode.TestAdapter/xunit.multinode.runner.json

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,5 @@
33
"failedSpecsDirectory": "FAILED_SPECS_LOGS",
44
"listenAddress": "127.0.0.1",
55
"listenPort": 0,
6-
"reporter": "console",
7-
"clearOutputDirectory": false,
8-
"teamCityFormatting": false
6+
"clearOutputDirectory": false
97
}

src/common.props

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@
2222
<NetCoreTestVersion>netcoreapp3.1</NetCoreTestVersion>
2323
<NetTestVersion>net5.0</NetTestVersion>
2424
<NetStandardLibVersion>netstandard2.0</NetStandardLibVersion>
25-
<FluentAssertionsVersion>6.2.0</FluentAssertionsVersion>
25+
<FluentAssertionsVersion>6.3.0</FluentAssertionsVersion>
2626
<FsCheckVersion>2.9.0</FsCheckVersion>
2727
<AkkaVersion>1.4.31</AkkaVersion>
2828
<!--

0 commit comments

Comments
 (0)