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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP