NUNIT framework
- Introduction To NUnit Testing Framework
- NUnit is a part of the .NET Foundation
- NUnit 3.12
- NUnit 2.7.1
- Nunit3: TestFixtureSetUpAttribute does not exist in namespace NUnit.Framework #974
- NUnit 2 vs NUnit 3. What you need to know.
- NUnit - Fails with TestFixtureSetUp method not allowed on a SetUpFixture
- SetUp and TearDown Changes
- NUnit.Framework Namespace
- Most Complete NUnit Unit Testing Framework Cheat Sheet
- Introduction to Unit Tests with NUnit
- Unit Testing Using NUnit
- NUnit Testing with Visual Studio 2015
- Environment Setup - NUnit Tutorial
- Installation=>Downloading the Zip File section
- Installation - Legacy documentation
- NUnit #
- Using NUnit with Visual Studio
NUNIT 3.12
This release of NUnit finally drops support for .NET 2.0. If your application still targets .NET 2.0, your tests will need to target at least .NET 3.5. Microsoft ended support for .NET 2.0 on July 12, 2011. Microsoft recommends that everyone migrate to at least .NET Framework 3.5 SP1 for security and performance fixes.
This release dramatically improves NUnit support for async tests including returning ValueTask and custom tasks from tests, improved handling of SynchronizationContexts and better exception handling.
The .NET Standard 2.0 version of NUnit continues to gain more functionality that is found in the .NET 4.5 version of the framework like setting the ApartmentState and enabling Timeout on tests.
NUnit 2.7.1
The primary purpose of this release is to add an ID filter to the set of filters supported by NUnit V2. This filter type is not used by any of the V2 runners and is intended for use by the V2 driver used when running V2 tests under NUnit 3 using the TestCentric GUI runner, which requires this type of filter.
One pending bug fix is also included. See the release notes at http://nunitsoftware.com/nunitv2/index.php?p=releaseNotes&r=2.7.1.
No comments:
Post a Comment