Skip to main content

Unit test classes - using a base class

Mai mult ca sigur cu toții am scris teste. 1,2, 3 .. n clase de teste. Într-un anumit moment ajungem sa dorim sa refactorizam codul, iar o parte din logica (setup-ul testelor) sa îl ducem în clasa de baza.
public class Test1: BaseTest
{
    [TestMethod]
    public void Method1Test()
    {
        Console.WriteLine("Method1Test");
    }

    [TestInitialize]
    public void TestInit()
    {
        Console.WriteLine("TestInitialize");
    }
   
    [TestCleanup]
    public void TestCleanup()
    {
        Console.WriteLine("TestCleanup");
    }
   
    [ClassInitialize]
    public static void ClassInit(TestContext testContext)
    {
        Console.WriteLine("ClassInit");
    }      
}
Sa ne uitam acuma la clasa de baza:
public class BaseTest{   
    [TestInitialize]
    public void BaseTestInit()
    {
        Console.WriteLine("BaseTestInitialize");
    }
   
    [TestCleanup]
    public void BaseTestCleanup()
    {
        Console.WriteLine("BaseTestCleanup");
    }
   
    [ClassInitialize]
    public static void BaseClassInit(TestContext testContext)
    {
        Console.WriteLine("BaseClassInit");
    }      
}
Totul pare in regula, in mod normal la rularea testului va asteptati sa ruleze in felul urmator:
  • BaseClassInit
  • ClassInit
  • BaseTestInit
  • TestInit
  • Method1Test
  • TestCleanup
Dar o sa avem parte de o surpriza:
  • ClassInit
  • BaseTestInit
  • TestInit
  • Method1Test
  • TestCleanup
BaseClassInit nu a fost apelat. Chiar dacă ne-am aștepta ca metoda din clasa de baza sa fie apelata, iar în alte framework-uri este suportat (NUnit) acest comportament, M$ nu ne prea ajuta în acest caz.
La aceasta problema eu am văzut 3 posibile soluții, de la caz la caz ele pot sa fie aplicate sau nu:
  1. clasa de teste care mosteneste clasa de baza sa apeleze explicit BaseClassInit. Dar acest lucru ne obliga avem o metoda decorata cu ClassInitialize in fiecare clasa derivata (poate nu ne dorim acest lucru);
  2. in unele situații, putem sa mutam logica din BaseClassInit în constructorul static:
static BaseTest()
{
    Console.WriteLine("BaseClassInit");
}
      3.  prin reflection putem sa facem un hook si sa ne implementam noi acest mecanism. Dar este destul de complex si nu cred ca merita;
Din fericire avem cateva solutii la indemana, dar uneori dupa o refactorizare ne putem trezi ca ne cad testele si sa nu gasim cauza exacta.

Comments

  1. Mi se pare normal ceea ce se întîmplă acolo. În momentul în care iterezi cu reflection prin clasa derivată o să vezi (în mod natural) doar metodele clasei derivate. Nu e M$ de vină, lucrurile sunt la fel implementate și în Java.

    ReplyDelete
  2. http://www.nunit.org/index.php?p=fixtureSetup&r=2.5.7
    La NUnit, nu este nevoie ca metoda sa fie statica, din aceasta cauza problema se rezolva destul de simplu.

    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…