Found 194 packages
Integration testing framework for developers. TestR allows automating testing of desktop and web applications.
Integration testing framework for developers. TestR allows automating testing of web applications. Adds PowerShell features that are not part of the regular deployment.
Package Description
A cli tool to manage executable test cases.
.NET mocking framework for integration testing
.Net Standard 2.0 implementation of the TestRail API
Package that helps (unit)testing Signalr scenarios.
Common code for all SignalR.UnitTestingSupport.* nugets . If you want support for unit testing signalR core (Hub and IHubContext) use one of this packages (NUnit, xUnit, MsTest version): https://www.nuget.org/packages/SignalR.UnitTestingSupport.NUnit, https://www.nuget.org/packages/SignalR.UnitTestingSupport.xUnit, https://www.nuget.org/packages/SignalR.UnitTestingSupport.MSTest Or use it directly only if you use different testing framework. See: https://github.com/NightAngell/SignalR_UnitTestingSupport/wiki/How-use-testing-support-if-you-don't-want-(or-you-can`t)-use-provided-by-me-base-classes-or-your-testing-framework-don't-support-before-and-after-each-test-code-execution-features https://github.com/NightAngell/SignalR_UnitTestingSupport/wiki/How-implement-testing-support-for-different-than-NUnit,-xUnit-or-MsTest-Framework
Example of SignalR with F-Sharp (and Silverlight 5 or Javascript): - SignalR is a library (for web-based Publish/Subscribe -pattern) on top of WebSockets, which is HTML5 API that enables bi-directional communication between the browser and server. SignalR will fallback to other techniques and technologies when WebSockets are not available. http://signalr.net/ - F-Sharp (F#) is multiparadigm (functional-first) programming language mainly for .NET environment. http://fsharp.org/ - This sample uses Reactive Extensions 2.1 to communicate with SignalR, on both client and server side. Reactive Extensions is a library to compose asynchronous and event-based programs using observable collections and LINQ-style query operators. http://msdn.microsoft.com/en-us/data/gg577609.aspx - For server side: This could work purely from F# as Owin (http://owin.org/) console application but now F#-server-side is called from an empty ASP.NET C# Web Application. (Still you can start OWin from F# Interactive...) - For client side: Silverlight 5.0 application using F#-library and Silverlight 5.0 XAML/C# application to show the user interface. http://www.silverlight.net There is also jQuery/JavaScript test page, if you don't want to use Silverlight. - This proof of concept/sample/tutorial/demo is developed with Visual Studio 2012. References are resolved via NuGet. F# compiler won't auto-restore packages on compile. So go first to Tools -> Library Package Manager -> NuGet and press "Restore" to restore all the references, and then rebuild. - SignalR supports two kinds of connections: Hub and PersistentConnection Both are working with Silverlight and JavaScript.
Easy to use, small, SignalR Core unit testing support with xUnit and Moq. Check my github for NUnit or MSTest version.
SmartSql = MyBatis + Cache(Memory | Redis) + ZooKeeper + R/W Splitting +Dynamic Repository ....
Gurock.Testrail Unofficial package
Easy to use, small, SignalR Core unit testing support with MSTest and Moq. For Nunit or xUnit version see my github.
In-memory testing the full SignalR pipline
# EventFlow   ``` $ dotnet add package EventFlow ``` EventFlow is a basic CQRS+ES framework designed to be easy to use. Have a look at our [getting started guide](https://geteventflow.net/getting-started/), the [do’s and don’ts](https://geteventflow.net/additional/dos-and-donts/) and the [FAQ](https://geteventflow.net/additional/faq/). Alternatively, join our [Discord](https://discord.gg/QfgNPs5WxR) server to engage with the community. Its hopefully getting a reboot to kickstart the upcoming release of v1. ## Features * **Easy to use**: Designed with sensible defaults and implementations that make it easy to create an example application * **Highly configurable and extendable**: EventFlow uses interfaces for every part of its core, making it easy to replace or extend existing features with custom implementation * **No use of threads or background workers** * **MIT licensed** Easy to understand and use license for enterprise ## Versions Development of version 1.0 has started and is mainly braking changes regarding changes related to replacing EventFlow types with that of Microsoft extension abstractions, mainly `IServiceProvider` and `ILogger<>`. The following list key characteristics of each version as well as its related branches (not properly configured yet). * `1.x` Represents the next iteration of EventFlow that aligns EventFlow with the standard packages for .NET. Releases here will only support .NET Standard, .NET Core and .NET versions 6+ going forward. - Released - Still development - Not all projects migrated yet Read the [migration guide](https://geteventflow.net/migrations/v0-to-v1/) to view the full list of breaking changes as well as recommendations on how to migrate. ### Documentation Version 1.x documentation has been pulled into this repository in order to have the code and documentation closer together and have the documentation updated in the same pull-requests as any code changes. The compiled version of the documentation is available at https://geteventflow.net/. ### NuGet package status - 🟢 ported - 💚 newly added to 1.0 - 🟠 not yet ported to 1.0 - 💀 for packages that are removed as part of 1.0 (see the [migration guide](https://geteventflow.net/migrations/v0-to-v1/) for details) Projects - 🟢 `EventFlow` - 🟠 `EventFlow.AspNetCore` - 💀 `EventFlow.Autofac` - 💀 `EventFlow.DependencyInjection` - 🟠 `EventFlow.Elasticsearch` - 🟢 `EventFlow.EntityFramework` - 🟠 `EventFlow.EventStores.EventStore` - 🟢 `EventFlow.Hangfire` - 🟢 `EventFlow.MongoDB` - 🟢 `EventFlow.MsSql` - 💀 `EventFlow.Owin` - 🟢 `EventFlow.PostgreSql` - 🟠 `EventFlow.Redis` - 🟢 `EventFlow.RabbitMQ` - 🟢 `EventFlow.Sql` - 🟢 `EventFlow.SQLite` - 🟢 `EventFlow.TestHelpers` ### Branches - `develop-v1`: Development branch, pull requests should be done here - `release-v1`: Release branch, merge commits are done to this branch from `develop-v1` to create releases. Typically each commit represents a release * `0.x` (legacy) The current stable version of EventFlow and has been the version of EventFlow for almost six years. 0.x versions have .NET Framework support and limited support to the Microsoft extension packages through extra NuGet packages. Feature and bug fix releases will still be done while there's interest in the community. ### Branches - `develop-v0`: Development branch, pull requests should be done here - `release-v0`: Release branch, merge commits are done to this branch from `develop-v0` to create releases. Typically each commit represents a release ### Documentation Version 0.x documentation is (although a bit outdated) is live at https://docs.geteventflow.net/.
Easy to use, small, SignalR Core unit testing support with NUnit and Moq. Check my github for xUnit or MSTest version
SpecificatR UnitTest Abstractions contains all the essentials to unit test specifications created with SpecificatR.
Executes datasets by way of MediatR