MockQueryable.Core
7.0.4-beta
dotnet add package MockQueryable.Core --version 7.0.4-beta
NuGet\Install-Package MockQueryable.Core -Version 7.0.4-beta
<PackageReference Include="MockQueryable.Core" Version="7.0.4-beta" />
paket add MockQueryable.Core --version 7.0.4-beta
#r "nuget: MockQueryable.Core, 7.0.4-beta"
// Install MockQueryable.Core as a Cake Addin #addin nuget:?package=MockQueryable.Core&version=7.0.4-beta&prerelease // Install MockQueryable.Core as a Cake Tool #tool nuget:?package=MockQueryable.Core&version=7.0.4-beta&prerelease
MockQueryable
Extensions for mocking Entity Framework Core (EFCore) operations such ToListAsync, FirstOrDefaultAsync etc. by Moq, NSubstitute or FakeItEasy When writing tests for your application it is often desirable to avoid hitting the database. The extensions allow you to achieve this by creating a context – with behavior defined by your tests – that makes use of in-memory data.
When should I use it?
If you have something similar to the following code:
var query = _userRepository.GetQueryable();
await query.AnyAsync(x =>...)
await query.FirstOrDefaultAsync(x =>...)
query.CountAsync(x => ...)
query.ToListAsync()
//etc.
and you want to cover it by unit tests
How do I get started?
//1 - create a List<T> with test items
var users = new List<UserEntity>()
{
new UserEntity{LastName = "ExistLastName", DateOfBirth = DateTime.Parse("01/20/2012")},
...
};
//2 - build mock by extension
var mock = users.BuildMock();
//3 - setup the mock as Queryable for Moq
_userRepository.Setup(x => x.GetQueryable()).Returns(mock);
//3 - setup the mock as Queryable for NSubstitute
_userRepository.GetQueryable().Returns(mock);
//3 - setup the mock as Queryable for FakeItEasy
A.CallTo(() => userRepository.GetQueryable()).Returns(mock);
Do you prefer DbSet?
//2 - build mock by extension
var mock = users.AsQueryable().BuildMockDbSet();
//3 - setup DbSet for Moq
var userRepository = new TestDbSetRepository(mock.Object);
//3 - setup DbSet for NSubstitute or FakeItEasy
var userRepository = new TestDbSetRepository(mock);
//3 - setup the mock as Queryable for FakeItEasy
A.CallTo(() => userRepository.GetQueryable()).Returns(mock);
Can I extend the mock object created by MockQueryable with custom logic?
MockQueryable creates for your tests a mock object based on in-memory data, but you can also add some custome logic to it.
var userId = Guid.NewGuid();
var users = new List<UserEntity>
{
new UserEntity{Id = userId,LastName = "ExistLastName", DateOfBirth = DateTime.Parse("01/20/2012")},
//etc.
};
var mock = users.AsQueryable().BuildMockDbSet();
//Aditional setup for FindAsync
mock.Setup(x => x.FindAsync(userId)).ReturnsAsync((object[] ids) =>
{
var id = (Guid)ids[0];
return users.FirstOrDefault(x => x.Id == id);
});
var userRepository = new TestDbSetRepository(mock.Object);
//Execution FindAsync
var user = await ((DbSet<UserEntity>) userRepository.GetQueryable()).FindAsync(userId);
Check out the sample project
Where can I get it?
First, install NuGet.
If you are using Moq - then, install MockQueryable.Moq from the package manager console:
PM> Install-Package MockQueryable.Moq
If you are using NSubstitute - then, install MockQueryable.NSubstitute from the package manager console:
PM> Install-Package MockQueryable.NSubstitute
If you are using FakeItEasy - then, install MockQueryable.FakeItEasy from the package manager console:
PM> Install-Package MockQueryable.FakeItEasy
Can I use it with my favorite mock framework?
You can install MockQueryable.EntityFrameworkCore from the package manager console:
PM> Install-Package MockQueryable.EntityFrameworkCore
or even MockQueryable.Core
PM> Install-Package MockQueryable.Core
Then make your own extension for your favorite mock framework
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.1 is compatible. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.1
- No dependencies.
NuGet packages (4)
Showing the top 4 NuGet packages that depend on MockQueryable.Core:
Package | Downloads |
---|---|
MockQueryable.EntityFrameworkCore
Extension for mocking Entity Framework Core operations such ToListAsync, FirstOrDefaultAsync etc. When writing tests for your application it is often desirable to avoid hitting the database. The extension allows you to achieve this by creating a context – with behavior defined by your tests – that makes use of in-memory data. |
|
Matt.SharedKernel
This NuGet package offers a versatile collection of interfaces and classes meticulously crafted to streamline DDD practices, leverage the Specification Pattern, and more. |
|
Matt.Paginated
Package Description |
|
Matt.ResultObject
Package Description |
GitHub repositories (2)
Showing the top 2 popular GitHub repositories that depend on MockQueryable.Core:
Repository | Stars |
---|---|
CodeMazeBlog/CodeMazeGuides
The main repository for all the Code Maze guides
|
|
nuyonu/N-Tier-Architecture
This is a n-layer architecture based on Common web application architectures.
|
Version | Downloads | Last updated |
---|---|---|
7.0.4-beta | 9,096 | 9/24/2024 |
7.0.3 | 619,117 | 9/2/2024 |
7.0.2 | 117,263 | 8/20/2024 |
7.0.1 | 1,901,950 | 3/7/2024 |
7.0.0 | 4,312,426 | 11/21/2022 |
6.0.1 | 4,767,896 | 3/28/2022 |
6.0.0 | 303,289 | 3/24/2022 |
5.0.2 | 293,257 | 3/24/2022 |
5.0.1 | 3,162,419 | 5/25/2021 |
5.0.0 | 1,293,344 | 11/12/2020 |
5.0.0-preview.7 | 29,737 | 7/28/2020 |
3.1.3 | 2,108,572 | 5/19/2020 |
3.1.2 | 174,380 | 4/17/2020 |
3.1.1 | 441,808 | 1/25/2020 |
3.0.2 | 61,327 | 12/20/2019 |
3.0.1 | 79,080 | 10/11/2019 |
3.0.0 | 21,407 | 9/30/2019 |
1.1.0 | 755,214 | 2/28/2019 |
1.0.4 | 74,039 | 1/29/2019 |
1.0.3 | 275,590 | 8/30/2018 |
1.0.2 | 82,362 | 1/17/2018 |
1.0.1 | 2,366 | 12/26/2017 |
1.0.0 | 24,531 | 12/26/2017 |
#81 Add support to ExecuteDelete and ExecuteUpdate - Thanks @lazaro-ansaldi