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.
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 believe that during your work with unit tests with applications that are using database for data storage you will need to isolate layer that is responsible for providing data. In this example I will use Entity Framework as ORM. Below you can find main elements of solution: public class User { public int Id { get; set; } public string Login { get; set; } public string Name { get; set; } public string Surname { get; set; } public bool AccountLocked { get; set; } public virtual List<Role> Roles { get; set; } } public class UsersContext [...]
Increasingly, the projects begin to use LINQ and begin to see advantages. Not only, that in this way can write some code, and gain some clarity. Below are some examples, which slowly skim through the LINQ. For demonstration purposes, let’s create a class Person, which objects will be represented by a person. […]
Sometimes there is a need to find information about what software is installed on your computer. For example, we want to know, if anyone has already installed the program and where it is installed. This knowledge is needed, example, if you add a file to a directory with the program already installed. The simplest example is to write different kinds of plugins. The problem does not occur if the application has been installed in the default directory, we know, but this can no longer guarantee. […]
