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:
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)
.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:


  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".


Post a Comment

Popular posts from this blog

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 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 …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.