Skip to main content

MSTEST - CollectionAssert

In orice proiect ar trebuii sa existe unit teste. In general, pentru validare, fiecare test poate sa contina Assert-uri de forma:
Assert.IsNotNull(result);
Assert.AreEqual(1,result.Count);
...
In cazul in care este nevoie sa validam o lista, folosim un foreach sau orice mod de a itera o lista:
foreach(var item in result.Items)
{
    Assert.IsTrue(baseResult.Contains(item));
}
.NET ne pune la dispoztie pe langa Assert si clasa CollectionAssert, prin intermediul careia putem sa validam o colectie. Mai jos o sa trec peste cateva metode care mi s-au parut mai importante:
  • CollectionAssert.AreNotNull - verifica ca toate elementele din colectie sa nu fie NULL
  • CollectionAssert.AllItemsAreInstancesOfType - verifica daca toate elementele din colectie sunt de un anumit tip( tipul poate sa fie si o interfata)
  • CollectionAssert.AllItemsAreUnique - verifica daca toate elementele din colectie sunt diferite( fiecare element din colectie se compara cu restul folosind metoda Equal). Optional se poate specifica un IComparer pentru a se face o comparatie custom.
  • CollectionAssert.AreEqual - Verifica daca doua colectii sunt egale( din nou metoda Equal este folosita)
  • CollectionAssert.AreEquivalent - Este asemanator cu AreEqual, dar elementele pot sa apara in orice ordine. De exemplu doua colectii o sa fie echivalente daca au acelasi numar de elemente si fiecare element din prima colectie este egal cu un element din a doua colectie.
  • CollectionAssert.Contains - verifica daca o colectie contine un anumit element
  • CollectionAssert.IsSubsetOf - verifica ca prima colectie este o submultime a celei de a doua colectie
Mai jos gasitit un exemplu care verifica ca doua colectii sunt egale:
HashSet<string> collectionOne = new HashSet<string>(){"A","B"};
HashSet<string> CollectionTwo = new HashSet<string>(){"B","A"};
CollectionAssert.AreEquivalent(collectionOne, collectionTwo);
Este bine de stiut ca fiecare din aceaste metode are si echivalentul pentru negatie. Pentru mai multe informatii puteti accesa: http://msdn.microsoft.com/en-us/library/microsoft.visualstudio.testtools.unittesting.collectionassert%28v=vs.100%29.aspx

Comments

  1. Ar fi frumos daca unit testing-ul nu ar mai fi 2nd hand citizen, si MS ar face niste upgrade-uri la el, gen support pentru lamba.
    Un candidat excepent ar fi chiar partea de collection assert unde uneori ai nevoie sa ai niste reguli de echivalenta "custom".

    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…