Skip to main content

Can we mock an extension method?

Pentru teste mai mult ca sigur ati folosit un framework petru a face mock pe diferite obiecte. In general am folosit Moq pentru a putea face mock la date. Este destul de usor de folosit, mai jos puteti sa gasiti un exemplu:
Mock<IService> serviceMock = new Mock<IService>();
serviceMock
    .Setup(x=>x.Call(It.IsAny<string>))
    .Returns(()=> new Result());
Mai sus am creat un mock pentru IService, iar in momentul in care se apeleaza metoda Call cu orice parametru de tip string, se returneaza un nou obiect de tip Result.
Nimic deosebit pana acuma. Dar ce se intampla daca vrem sa facem mock la un extension method. Vestea proasta este ca nu se poate face. Majoritatea framework-urilor pentru mock-ing nu suporta aceasta functionalitate.
Cea mai buna solutie este sa refactorizam codul daca putem. Dar exista cazuri cand acest lucru nu il putem face sau extension method nu este declarat de noi si vine dintr-un assembly exterior.
O solutie comuna, care poate sa fie folosita atat pentru aplicatiile .NET classic, Silverlight, WP7, ... este sa injectam actiunea care apeleaza metoda noastra. De exemplu putem sa extragem intr-un Action actiunea care apeleaza extension method, iar aceasta sa fie injectata prin contructor folosind un factory de exemplu. O alta varianta este sa facem un wrapper peste clasa noastra.
Urmatoarea solutie nu functioneaza pe Silverlight din pacate. Ar fi fost nice sa fie suportatat macar in versiunea 5, dar nici o sansa. Solutie se refera la folosirea Microsoft Moles. Prin intermediul acestui framework putem sa inlocuim orice clasa, metoda cu un mole care sa faca ce vrem noi. Un mole, intercepteaza apelul spre o anumita metoda si se poate executa orice alt cod. Putem sa facem mole la orice fel de metoda, atat statica cat si extension method.

Comments

  1. Un extension method nu e decat o metoda statica, deci nu e de mirare ca majoritatea frameworkurilor de mocking care lucreaza cu metode "ortodoxe" nu au cum sa creeze un mock pentru asa ceva..

    Si Moles sau Typemock Isolator pot sa mockuiasca o metoda statica pentru ca se baga cu CLR profiler-ul si rescriu IL-ul, si alte ghidusii de genul.

    ReplyDelete
  2. Partea interesanta este cand ai un proiect Silverlight si nu ai aceste optiuni.
    Daca ar fi sa aleg intre Moles si Moq as alege Moq, dar uneori nu ai de ales, sau in cazul asta numarul de optiuni este egal cu 0.

    ReplyDelete
  3. Da, in cazul acesta daca mocking framework-ul nu are versiune de Silverlight, cam singura optiune e un adapter sau refactoring daca e posibil..

    ReplyDelete
  4. Am ajuns la o solutie asemanatoare. Putin de refactoring, un factory impreuna cu un adaptor. O sa revin maine cu implementarea exacta.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…