search
Found 19 packages
NUnit.Runners✓
This package is now obsolete and has been replaced by the NUnit.Console package. It includes the nunit3-console runner and test engine for version 3 of the NUnit unit-testing framework. The following extensions are included with this package: * NUnitProjectLoader - loads tests from NUnit projects * VSProjectLoader - loads tests from Visual Studio projects * NUnitV2ResultWriter - saves results in NUnit V2 format. * NUnitV2FrameworkDriver - runs NUnit V2 tests. * TeamCityEventListener - supports special progress messages used by teamcity. Other extensions, if needed, must be installed separately.
v3.12.0
↙ 16.7M / total
nunittesttestingtddrunner
NUnit.Runners.Net4
NUnit features a fluent assert syntax, parameterized, generic and theory tests and is user-extensible. A number of runners, both from the NUnit project and by third parties, are able to execute NUnit tests. Version 2.6 is the seventh major release of this well-known and well-tested programming tool. This package includes the NUnit console, gui and pnunit runners and is compatible with all NUnit framework versions 2.0 through 2.6. The NUnit project editor is also included. This unofficial package is limited to run on the 4.x framework which improves compatibility with Mono when running tests compiled for 4.x.
v2.6.4
↙ 903.8K / total
nunittesttestingtddrunner
SpecFlow.NUnit.Runners✓
Combined package to setup SpecFlow with NUnit easily for running the tests with the NUnit runners.
v3.9.74
↙ 3.9M / total
specflownunitnunit.runnersnunit-console
NUnit.Engine✓
This package includes nunit.engine and related assemblies, for use by runner programs. It is not intended for direct use by users who simply want to run tests.
v3.22.0
↙ 6.7M / total
nunittesttestingtddengine
NUnit.Engine.Api✓
This package includes the nunit.engine.api, which is normally the only assembly referenced by runners as well as by engine extensions. It is not intended for direct use by users who simply want to run tests using NUnit.
v3.22.0
↙ 2.6M / total
nunittesttestingtddengine
NUnit.Runners.lite
This package provides just NUnit (v2.6.4) console and gui runners (no x86) for .NET 4. It is a modification of the package NUnit.Runners. DO NOT INSTALL using Visual Studio package manager (not even the console). DO INSTALL with nuget command line: "nuget.exe install nunit.runners.lite -OutputDirectory tools". Complete the installation with a generic "NUnit" symbolic link by executing "add-link.cmd" from within latest version installed.
v2.6.4.20150512
↙ 43.0K / total
testtestingtddrunner
NUnitV2.Core
The NunitV2.Core package is aimed at third-party test runners that will normally include the assemblies directly in their own packages. It allows loading and running tests at a fairly low level.
v2.7.1
↙ 259.0K / total
nunittesttestingtddrunner
pNUnit
PNUnit provides a way to test applications composed of distributed, communicating components. It was developed by the folks at Codice Software for their internal use and contributed to NUnit. Note that pNUnit is not intended for running tests in parallel simply to make them run faster. It requires careful setup of each parallel test using an XML description of the individual cooperating tests. This package includes only the pNUnit framework assembly, which is referenced by your tests. Executing the tests requires using the pNUnit launcher, which is distributed as part of the NUnit.Runners package.
v2.6.4
↙ 82.8K / total
nunittesttestingtddframework
NUnit.Editor✓
The NUnit project editor allows easy editing of NUnit projects. It supports a form-based interface for editing properties as well as a rudimentary XML editor. This package includes only the editor, which is also available as a part of the NUnit.Runners package.
v2.6.4
↙ 65.8K / total
nunittesttestingframeworkproject
pkg
NUnitOrange
NUnitOrange is now discontinued and superseded by ReportUnit (http://reportunit.relevantcodes.com/), its replacement, which now generates reports for several other test-runners besides NUnit NUnitOrange creates masonry style HTML reports for NUnit. Its a simple Console application that creates easy to use, attractive dashboard. It shows the XML output from NUnit in a presentable manner with charts, graphs and tables.
v2.1.0
↙ 61.5K / total
NUnitReportHTMLOrangeNUnitOrange
NUnitCF
NUnit features a fluent assert syntax, parameterized, generic and theory tests and is user-extensible. This package includes the NUnit 3.0 framework assembly for .NET Compact Framework 3.5, which is referenced by your tests. You will need to install the NUnitLiteCF package in order to run the tests. Two separate packages are used because future versions will be supported by additional runners.
v3.5.0
↙ 23.4K / total
nunittesttestingtddframework
pkg
TestBase
*TestBase* gives you a flying start with - fluent assertions that are easy to extend - sharp error messages - tools to help you test with “heavyweight” dependencies on - AspNetCore.Mvc, AspNet.Mvc or WebApi Contexts - HttpClient - Ado.Net - Streams & Logging - Mix & match with your favourite test runners & assertions. ``` UnitUnderTest.Action() .ShouldNotBeNull() .ShouldEqualByValueExceptFor(new {Id=1, Descr=expected}, ignoreList ) .Payload .ShouldMatchIgnoringCase("I expected this") .Should(someOtherPredicate); .Items .ShouldAll(predicate) .ShouldContain(item) .ShouldNotContain(predicate) .Where(predicate) .SingleOrAssertFail() .ShouldEqualByValue().ShouldEqualByValueExceptFor(...).ShouldEqualByValueOnMembers() work with all kinds of object and collections, and report what differed. string.ShouldMatch(pattern).ShouldNotMatch().ShouldBeEmpty().ShouldNotBeEmpty() .ShouldNotBeNullOrEmptyOrWhiteSpace().ShouldEqualIgnoringCase() .ShouldContain().ShouldStartWith().ShouldEndWith().ShouldBeContainedIn(), ... numeric.ShouldBeBetween().ShouldEqualWithTolerance()....GreaterThan....LessThan...GreaterOrEqualTo ... ienumerable.ShouldAll().ShouldContain().ShouldNotContain().ShouldBeEmpty().ShouldNotBeEmpty() ... stream.ShouldHaveSameStreamContentAs().ShouldContain() value.ShouldBe().ShouldNotBe().ShouldBeOfType().ShouldBeAssignableTo()... ``` Testable Logging is in packages Extensions.Logging.ListOfString and Serilog.Sinks.ListOfString ``` // Extensions.Logging.ListOfString var log = new List<String>(); ILogger mslogger= new LoggerFactory().AddStringListLogger(log).CreateLogger("Test2"); // Serilog.Sinks.ListOfString Serilog.Logger slogger= new LoggerConfiguration().WriteTo.StringList(log).CreateLogger(); ```
v4.4.4
↙ 472.7K / total
nunittestunittest
JetBrains.dotMemoryUnit✓
dotMemory Unit is an additional unit testing framework that allows you to write tests that check code for all kinds of memory issues. For example, these can be tests that determine leaks by checking memory for objects of a particular type, or tests that track memory traffic and fail in case the traffic exceeds some threshold. In other words, dotMemory Unit extends your unit testing framework (NUnit, MSTest, or other) with the functionality of a memory profiler. To run tests that use dotMemory Unit, you should reference the dotMemory.Unit assembly (which is a part of this package) from your test project. Tests with the support for dotMemory Unit can be run either with a standalone unit test runner of your choice or with the ReSharper unit test runner. For standalone runners, you should use a mediator - the standalone dotMemory Unit launcher. If you want to use the ReSharper unit test runner, you should have either ReSharper 9.1 (or later) or dotCover 3.1 (or later) installed on your machine
v3.2.20220510
↙ 12.8M / total
profilingmemory-leakmemoryunit-testingtesting
Blackbaud.UAT.SpecFlow.Selenium
Blackbuad UAT SpecFlow Generator Plugin. Produces bindings with dual signatures enabling that the tests for both MSTest and NUnit compatible runners. Manages chromedriver lifecycle. Based on http://www.baseclass.ch/Contrib/SpecFlowSelenium. See http://www.baseclass.ch/documents/MITLicense.txt.
v1.0.20221027.1
↙ 10.6K / total
BlackbaudUATSpecflowSeleniumMSTest
pkg
TestBase.HttpClient.Fake
*TestBase* gives you a flying start with - fluent assertions that are simple to extend - sharp error messages - tools to help you test with “heavyweight” dependencies on - AspNetCore.Mvc, AspNet.Mvc 3-5, or WebApi Contexts - HttpClient - Ado.Net - Streams & Logging - Mix & match with your favourite test runners & assertions. # TestBase.HttpClient.Fake ``` //Arrange var httpClient = new FakeHttpClient() .SetupGetUrl("https://host.*/").Returns(request=> "Got:" + request.RequestUri) .SetupGetPath("/uri[Pp]attern/").Returns("stringcontent") .SetupPost(".*").Returns(response) .SetupPost(".*", new byte[]{1,2,3}).Returns(otherResponse) .SetupPost(".*", "a=1&b=2") .Returns( request => "You said : " + request.Content.ReadAsStringAsync().ConfigureFalseGetResult(), HttpStatusCode.Accepted) .Setup(x=>x.RequestUri.PathAndQuery.StartsWith("/this")).Returns(response) .Setup(x=>x.Method ==HttpMethod.Put) .Returns(new HttpResponseMessage(HttpStatusCode.Accepted)); // Act var putResponse = await httpClient.PutAsync("http://localhost/thing", new StringContent("{a=1,b=2}")); var postResponse= await httpClient.PostAsync("http://[::1]/", new StringContent("a=1&b=2")); //Debug httpClient.Invocations .ForEach(async i =>Console.WriteLine("{0} {1}",i.RequestUri, await i.Content.ReadAsStringAsync())); //Assert putResponse.StatusCode.ShouldBe(HttpStatusCode.Accepted); postResponse.ShouldBe(response); // ==> SetupPost(".*").Returns(response) was the first // matched setup. Setups are tried in first-to-last order. httpClient.Verify(x=>x.Method ==HttpMethod.Put, "Expected Put, but no matching invocations."); httpClient.Verify( x=>x.Method ==HttpMethod.Post && x.Content.ReadAsStringAsync().ConfigureFalseGetResult()=="a=1&b=2", "Expected Post a=1&b=2"); httpClient.VerifyAll(); // ==> "Exception : 4 unmatched expectations" ``` ### TestBase Chainable fluent assertions get you to the point concisely. ``` UnitUnderTest.Action() .ShouldNotBeNull() .ShouldEqualByValueExceptFor(new {Id=1, Descr=expected}, ignoreList ) .Payload .ShouldMatchIgnoringCase("I expected this") .Should(someOtherPredicate); .ShouldEqualByValue().ShouldEqualByValueExceptFor(...).ShouldEqualByValueOnMembers() work with all kinds of object and collections, and report what differed. string.ShouldMatch(pattern).ShouldNotMatch().ShouldBeEmpty().ShouldNotBeEmpty() .ShouldNotBeNullOrEmptyOrWhiteSpace().ShouldEqualIgnoringCase() .ShouldContain().ShouldStartWith().ShouldEndWith().ShouldBeContainedIn().ShouldBeOneOf().ShouldNotBeOneOf() numeric.ShouldBeBetween().ShouldEqualWithTolerance()....GreaterThan....LessThan...GreaterOrEqualTo ... ienumerable.ShouldAll().ShouldContain().ShouldNotContain().ShouldBeEmpty().ShouldNotBeEmpty() ... stream.ShouldHaveSameStreamContentAs().ShouldContain() value.ShouldBe().ShouldNotBe().ShouldBeOfType().ShouldBeAssignableTo()... .ShouldAll(predicate), .SingleOrAssertFail()... ``` See also - [TestBase](https://www.nuget.org/packages/TestBase) - [TestBase.AspNetCore.Mvc](https://www.nuget.org/packages/TestBase.AspNetCore.Mvc) - [TestBase-Mvc](https://www.nuget.org/packages/TestBase-Mvc) - [TestBase.AdoNet](https://www.nuget.org/packages/TestBase.AdoNet) - [Serilog.Sinks.ListOfString](https://www.nuget.org/packages/Serilog.Sinks.Listofstring) - [Extensions.Logging.ListOfString](https://www.nuget.org/packages/Extensions.Logging.ListOfString)
NBi.VisualStudio
This package retrieves NUnit runners and NBi framework from Nuget before creating an empty test-suite, a config file and NUnit-project file. It also reconfigure the project to start NUnit GUI and the test-suite when pressing F5 (debug).
v1.22.1
↙ 66.5K / total
NBiTestBISQLSSAS
Dneedy.Specflow.Synchotron
Synchronise Resources using Blocking behaviour. (Assume that all resources can be run in parallel, apart from some that are flagged to only run with no other resources in action). In the context of Specflow, scenarios can be flagged to run alone using traits. Prevents test runners having to edit the assembly info and rebuild between sequential/parallel run contexts. Hopefully at some point the Specflow bods autogenerate this sort of this, but not yet, so here we are.
v2.0.0
↙ 2.2K / total
specflownunitparallelsequentialblock
DBConfirm.Core✓
A testing library written to easily add unit tests to cover behaviour held in SQL Server databases. This library allows you to write SQL unit tests in code alongside all your other unit tests, including running them from within your IDE and as part of CI builds. This package is the core logic; see the MSTest/NUnit packages for the framework-dependent runners.
v1.1.0
↙ 38.5K / total
SQLMSSQLUnitIntegrationTest
pkg
OneClickBuild
Simplify your build, run tests and coverage.
v1.13.0
↙ 94.6K / total
continuousintegration