51 packages tagged with “specifications”
Coyote is a library and tool for testing concurrent C# code and deterministically reproducing bugs.
Acceptance Test Driven Development and Executable Specifications for .Net
The Coyote systematic testing engine.
The Coyote core libraries and runtime.
Package Description
The Coyote .NET command-line tool.
P# is a framework for building reliable asynchronous software.
The self-contained Coyote command-line tool.
A small library for writing BDD-style specifications in C# / .NET. Spec4Net focuses on simplicity and ease-of-use. See the project home page for examples.
This package will help in domain integrity and base implementations
Recipe to Connect Storyteller to ASP.Net Core 2.* Systems
Recipes to Manipulate or Assert on Databases in Storyteller Specifications
Quarks.Specifications
A library for creating specifications in net core applications.
BDD test specifications for MSTest similar to MSTestContrib.
BDD test specifications for MSTest similar to MSTestContrib. Signed version!
A specification library
Base specification abstractions
Clean Architecture Infrastructure Layer - EF Core Integration, Repository Implementations, and Data Access
A Machine.Fakes context configuration which simplifies testing of AutoMapper Profile classes
library for the Sparkdo framework
BDD test specifications for windows store and windows phone apps similar to MSTestContrib. Signed version!
BDD test specifications for windows store and windows phone apps similar to MSTestContrib.
Plugins,Auth,Entity,Extention,Helper,Mvc,Log,Infrastructure,Specifications,Dapper,ModBus,PLC,Socket,Tencent,Weixin等DotNet Core基础类大全
A Machine.Fakes context configuration which mocks the Quarks.SystemTime class
A Machine.Fakes context configuration which simplifies testing of AutoMapper ValueResolver<TSource, TDestination> classes
TestRail integration for Storyteller
A Machine.Fakes context configuration which simplifies testing of AutoMapper TypeConverter<TSource, TDestination> classes
EFSpecs is a library to assist in testing your entity framework model mapping. It will create an entity with the values you provide it with, then send that entity off to the database, then pull it from the database to verify the values were saved correctly. And being the good citizen that it is, the whole thing is wrapped in a transaction so it all gets rolled back.