A test library to help in writing unit and integration tests for Visual Studio extensions.
Autofac extension supporting generation of NSubstitute objects.
Machine.Fakes attempts to simplify the usage of such frameworks on top of Machine.Specifications by helping to reduce a lot of the typical fake framwork related clutter code in specifications. If you choose so, Machine.Fakes even helps you to stay mostly independent of a concrete fake framework by providing a little wrapper API and a provider model for fake frameworks.
BDD style testing framework to allow unit testing with automated mocking, dependency injection and minimum friction based on the NUnit testing library. We at Leaping Gorilla strive to remove as much friction as possible from our testing methodology. To that end we wanted a drop dead simple way to create unit tests that adhered to a few core principles: 1. Must support constructor-based dependency injection 2. Must have the ability to automatically mock any dependencies we wish to use with our item under test 3. Must have the ability to override automatic mocking should the need arise 4. Must support a clean syntax for stubbing method calls on our dependencies 5. Must have a clean BDD style Given/When/Then flow From these needs LeapingGorilla.Testing was born.
Library to mocking gRPC client. Instead of Grpc.Core.Testing using extensions for Moq
This library should help you to test easily methods without writing all the mocks yourself. See - https://github.com/andireg/mockingbird
JSON and MediaTypeFormatter extensions for skwas.MockHttp.
A library for generating fake data e.g. for authoring tests, for preparing software demos or for creating screenshots. It includes generators such as Lorem text, Addresses, Company, PhoneNumber, Job Titles, etc. It comes with support for 51 locales out of the box and can be extended with custom locales. Licensed under the MIT license.
Provides testing platform APIs for Microsoft Fakes. To generate Fakes code, one needs a VS Enterise install. Additional details can be found at http://aka.ms/MicrosoftFakes.
An AutoFakerBinder for interfaces and abstract objects using NSubstitute
An AutoFakerBinder for interfaces and abstract objects using FakeItEasy
Rhino Mocks is using Castle Dynamic Proxy (http://www.castleproject.org/dynamicproxy/index.html) to handle proxying the types it needs to mock. The Dynamic Proxy project has been invaluable resource and made creating Rhino Mocks possible.
Package Description
A DivertR proxy factory implementation that supports proxying class types using Castle DynamicProxy
This package is a helper library containing implementations for classes that we often want to mock out.
Fake implementation of HttpContextBase for terse and expressive tests without the tedious setup of a mocking framework
This package contains components to test the functionnalities of HTC grid systems (e.g. IBM Symphony, Tibco Datasynapse, etc.).
Tools to help write tests for Microdot services. The project contains logic for Orleans host testers.
Helper methods to work with Entity Framework 6.* and Moq libraries doing mocks of Entity Framework main methods that access database. To understand how to mock on EF 6, then what this package can do for you, give a look at: http://www.codeproject.com/Tips/1045590/Testing-with-mock-on-Entity-Framework More info about how to use this library in GitHub repositoy: https://github.com/baderbuddy/EntityFramework.MoqHelper
Complete FastMoq testing framework with provider-first test doubles, automatic dependency injection, provider-neutral verification, and first-party helpers for EF Core, Azure SDK, Azure Functions, HttpClient, and ASP.NET Core. Includes Roslyn analyzers for migration guidance.
A unit-testing extension for verifying a logger mock.
Azure.Data.Wrappers Class Library
This library is a Generic Repository implementation for EF Core ORM which will remove developers' pain to write repository layer for each .NET Core and .NET project. This library includes the following notable features: 1. This library can be run on any .NET Core or .NET application which has .NET Core 3.1, .NET Standard 2.1 and .NET 5.0+ support. 2. It’s providing the Generic Repository with database transaction support. 3. It has all the required methods to query your data in whatever way you want without getting IQueryable<T> from the repository. 4. It also has Specification<T> pattern support so that you can build your query dynamically i.e. differed query building. 5. It also has database-level projection support for your query. 6. It also has support to run raw SQL command against your relational database. 7. It also has support to choose whether you would like to track your query entity/entities or not. 8. It also has support to reset your EF Core DbContext state whenever you really needed. 9. Most importantly, it has full Unit Testing support. Most importantly, it facilitates the writing unit test with mocking. 10. It also has pagination support. 11. Free raw SQL query support both for complex type and primitive types.
Common framework containing utilities and extension methods for fast development.
An InProcess HTTP server which can be mocked and asserted against to allow for full stack HTTP testing
- Firebase Cloud Messaging - Firebase Realtime Database (Basic Crud, no Offline or Streaming support) - Firebase Storage - Authentication (Generate Custom Token for users, no user management) - Logging (You can provide logger in FirebaseSDKConfiguration) - Support for plugging custom HttpClient for supprting mocks, IHttpClientFactory, Polly etc, see github repo.
This library should help you to test easily methods without writing all the mocks yourself. See - https://github.com/andireg/mockingbird
Roslyn plugin that provides helpful autocomplets when using Moq mocking library. Port of Resharper extension to Roslyn. NOTE: Works in VS 2017 only because plugin uses the latest Roslyn Autocomplete API.
Inject wrappers around unmockable objects. Use *Unmockable.Wrap* to wrap and *Unmockable.Intercept* to intercept calls to the unmockable object.
Tools to help write tests for Microdot services. The project contains logic for both Orleans and Non-Orleans host testers.
This library is a Generic Query Repository implementation for EF Core ORM which will remove developers' pain to write query repository layer for each .NET Core and .NET project. This library includes the following notable features: 1. This library can be run on any .NET Core or .NET application which has .NET Core 3.1, .NET Standard 2.1 and .NET 5.0+ support. 2. It has all the required methods to query your data in whatever way you want without getting IQueryable<T> from the repository. 3. It also has Specification<T> pattern support so that you can build your query dynamically i.e. differed query building. 4. It also has database-level projection support for your query. 5. It also has support to run raw SQL command against your relational database. 6. It also has support to choose whether you would like to track your query entity/entities or not. 7. Most importantly, it has full Unit Testing support. It facilitates the writing unit test with mocking. 8. It also has pagination support. 9. Free raw SQL query support both for complex type and primitive types.
Framework for unit testing AWS Step Functions state machine behavior using TestState and mocks
A set of pre-built mocks to help when testing file system interactions.
Hand-written idiomatic .NET client for MockServer's control-plane API. Provides fluent request/response builders and a When/Respond API for creating expectations, plus Verify, Clear, Reset, and Retrieve operations.
With inspiration taken from mocking frameworks like NSubstitute, FakeItEasy and JustMock this package adds some of the syntactic advantages of these frameworks to Moq. TransparentMoq allows to use Moq without having to store mocks in Mock<T> variables, instead a T variable can be used. This also removes the need to pass mocks with ".Object" everywhere as they can be passed directly. The library provides extension methods for most (if not all) of Moq's methods, so they can be called directly on the T variable. Examples: Instead of private Mock<IFileSystem> fileSystem = new Mock<IFileSystem>(); Write private IFileSystem fileSystem = New.Mock<IFileSystem>(); Instead of MethodThatTakesFileSystem(fileSystem.Object); write MethodThatTakesFileSystem(fileSystem); To arrange a mock everything remains the same: fileSystem.Setup(x => x.Exists(It.IsAny<string>())).Returns(true);
Provides common mock classes and extensions that are helpful for testing (unit + functional) Virtual Client platform components.