I just managed to publish a new version of the package FluentValidation.Validators.UnitTestExtension. This package allows you to write unit tests for Fluent Validators in a more effective way. The major change introduced in the latest version is support for FluentValidation 10. More information about the project is available on GitHub.
I just managed to publish a new version of package Moq.EntityFrameworkCore. This package allows you to write unit tests in the project that are using EntityFrameworkCore package in a more effective way. With version 5.0.0.1 following changes have been introduced: support for EntityFrameworkCore v5.0 extension of mock strategy to support sequential mocks More information about the project is available on GitHub.
I just managed to publish a new version of package Moq.EntityFrameworkCore. This package allows you to write unit tests in the project that are using EntityFrameworkCore package in a more effective way. With version 3.1.2.6 following changes have been introduced: extension of package support to objects that do not have DbContext as a based type More information about the project is available on GitHub.
I just managed to publish a new version of package FluentValidation.Validators.UnitTestExtension. This package allows you to write unit tests for Fluent Validators in a more effective way. With version 1.5 following changes have been introduced: support for the new version of FluentValidation (>8.4) More information about the project is available on GitHub.
I just managed to publish a new version of package FluentValidation.Validators.UnitTestExtension. This package allows you to write unit tests for Fluent Validators in a more effective way. With version 1.4 following changes have been introduced: new verifiers that check the configuration of EnumValidator, MaxLengthValidator, MinLenghtValidator, ExactLengthValidator, ExclusiveBetweenValidator and InclusiveBetweenValidator support for .NETStandard 1.6 and .NETStandard 2.0 More information about the project is available on GitHub.
From yesterday you can download package that will help you with mocking DbSet<TEntity> when you are using Moq. You can find sources and short instruction on GitHub portal or download compiled version from NuGet. New package works in the same way as Moq.EntityFramework.Helpers.
I just managed to publish new version of packgage FluentValidation.Validators.UnitTestExtension. This package allows you to write unit tests for Fluent Validators in more effective way. With version 1.1 following changes have been introduced: support for new version of FluentValidation 7.* new verifiers that check configuration of ScalePrecisionValidator and RegularExpressionValidator. More information about project is available on GitHub.
As you probably know I wrote two articles about mocking DbSet<TEntity> with Moq: synchronous calls – Mocking DbContext and DbSet with Moq asynchronous calls – EntityFramework – asynchronous queries unit tests I combined those solution to one library and published in on NuGet – Moq.EntityFramework.Helpers. […]
I already mentioned about AutoFixture in one of the posts – Lightning talk – Autofixture. Main goal of this library is to help us with reduction of Arrange part of unit tests. With this library we can focus on the main scenario of unit test instead of focusing on building objects that are needed for test. Moreover AutoFixture will protect us against modification of classes that are being used in our unit tests. But it is not perfect. Sometimes duration of unit tests can increase dramatically. Especially when you are creating objects used by EntityFramework. […]
I would like to introduce a new small library that I published – FluentValidation.Validators.UnitTestExtension. Main purpose of this library is to extend and simplify possibilities of testing code that is using FluentValidation package. You can install it by nuget: Install-Package FluentValidation.Validators.UnitTestExtension or download it from GithHub. One of approach of testing Fluent rules is presented in FluentValidation wiki page. You can find there information that FluentValidation comes with two extension methods ShouldHaveValidationErrorFor and ShouldNotHaveValidationErrorFor that can make it easier to write unit tests for validators. […]
