42348b12af
* Update to NUnit 4 This commit is based on the work of Sean Killeen in PR #112. Additional changes: * add net462 as target framework * set C# version in test projects to C# 10 so that file scoped namespaces work * Use constraint assertion model even in NUnit 3 adapter - This improves consistency between NUnit 3 and 4 adapters * Convert "AssertEqual-with-comparer" to NUnit constraint model Our adapters are no longer using custom assertions. This will result in failure reports that are consistent with other NUnit reports, especially when the report output changes (like it did between NUnit 3 and 4). * Apply ".editorconfig" configuration to "Directory.Build.props" This commit only changes indentation whitespace, making this MSBuild file consistent with other MSBuild files in the repository (.csproj). * Add missing/recommended NuGet package properties * Replace obsolete "PackageIconUrl" with "PackageIcon" Fixes warning NU5048 during "dotnet pack". https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu5048 * Replace obsolete "PackageLicenseUrl" with "PackageLicenseExpression" * Simplify ".csproj" files + move common references to "Directory.Build.props" * Dynamically fill in current copyright year * Consolidate release notes + bump version to 1.6.0-preview.1 * Move "PackageReference" back to ".csproj" files * Fix NuGet package name in "RELEASE_NOTES.md" - Thanks FarrisPandell * NuGet update 2024-09-06 Akka.TestKit 1.5.28, Microsoft.NET.Test.Sdk 17.11.1 * Delete empty lines after version headers in "RELEASE_NOTES.md" - Empty lines are confusing Nuke build --------- Co-authored-by: Urs Metz <urs.metz@gmx.de> |
||
|---|---|---|
| .github | ||
| .nuke | ||
| build | ||
| src | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| Akka.TestKit.Nunit.sln | ||
| LICENSE | ||
| README.md | ||
| RELEASE_NOTES.md | ||
| appsettings.json | ||
| build.cmd | ||
| build.ps1 | ||
| build.sh | ||
README.md
Akka.TestKit.Nunit
This is the NUnit TestKit integration plugin for Akka.NET. Please check out our documentation for examples on how to create and run tests using this plugin.