Skip to main content

How to write unit tests in JavaScript for a Windows Store Application

Did you ever tried to write a Windows Store Application for Windows 8 in JavaScript? If yes than I hope that you started working on unit tests also. If no, than in this post we discover how we can write unit test for JavaScript and how we can integrate them in Test Explorer.
First of all why we need to write unit test for JavaScript? Because is like any other programming language that we used until now. When we write code in any language we need to test it. The framework and steps that are describe in this post can be used to write unit tests for JavaScript for a ASP.NET application of for any other project written in JavaScript.
To be able to write test in JavaScript we need to define our test methods that contains a collection of checks. We can write this from scratch or we can use a framework. For this purpose I recommend qunit.  This is a great framework that can be used to write unit tests. We have different version of qunit for Windows Store Application and ASP.NET. After you download this package all that you need to do is to create a project and add this project to it.
After this, all that we need to do is to start writing the unit tests. Basically we need t define a list of function and using methods like equal we can check our unit test assertion. We have a lot of assertion:
  • equal – check if two values are equal
  • notEqual – check if two values are different
  • deepEqual – check if two values are equivalent
  • notDeepEqual – check if two values are not equivalent
  • strictEqual – check if two values are strict equal (“===”)
  • notStricEqual – check if two values are not stric equal (“!==”)
  • throws – check if our code throws an exception
The “test” method gives us the ability to define our test function and set the name of our test method. We can define a lot of things but these are the based things that we need. In the following example we define two test methods:
(function () {
    "use strict";
 
    test("my first test", function () {
        var v1 = 5;
        var v2 = 10;
        var sum = v1 + v2;
        equal(15, sum, "Our custom message.");
    });
 
    test("my seccond test", function () {
        var v1 = 5;
        var v2 = 10;
        var sum = v1 - v2;
        equal(15, sum, "Our custom message.");
    });  
})();
In a project for Windows Store when we will run it, qunit will generate a nice UI that will contain the status of each unit test.

As you can see we have a very nice interface that was created where we can read the status of our tests.
Another thing that I like to qunit is the way of output is generated. The output of running the tests is an XML. Over this file a styling is applied for a Windows Store Application. This XML can be used very easily with MSBUILD. There are a lot of scripts that already do this thing.
As you know Visual Studio 2012 contains an improved Test Explorer. Using a plug-in named Chutzpah Test Adapter for the Visual Studio 2012 we can integrate this test in our Test Explorer. In this way we will able to run our C# and JavaScript tests in the same time.
 Using qunit in combination with this plug-in we can create and run unit tests in JavaScript for Windows Store Application without any problem.
Good luck with unit tests.

Comments

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…