This is the first article in a series of three in which I will explain how I have setup unit testing for a JavaScript module. It documents the initial project setup and explains in a step-by-step fashion what I have done to get it up in running. In future articles I will explain how to add code coverage reports and integration with a continuous integration (CI) server.
This is the second article in a series of three in which I will explain how I have setup unit testing for a JavaScript module. It documents how I have added code coverage reports using Istanbul. In the next article I will explain how to integrate with a continuous integration (CI) server.
This is the last article in a series of three in which I explain how I setup my JavaScript unit testing with code coverage and getting it to run on a CI Server. First I described how to add unit testing and then I showed how to configure Istanbul and Grunt to generate code coverage reports. In this third step I will explain how I configured the project to use a continuous integration (CI) server like Travis CI or Wercker to run the unit tests when changes are pushed to the Git server.
In this article I will show the VanillaJS Date / Time picker I've developed. It is meant as an easy, user friendly component for entering a date and / or time.
When it came to adding comments to my blog I quickly decided on using Disqus to get the job done. It was easy to implement and I had seen it in use on many different website already. While I was quite happy with the result I wasn't too happy with the increase in page weight. On every visit to a page with comments enabled the Disqus code will pull in a lot of data. Because I am trying to build something light weight and friendly to people who have a slow connection or a fixed data allotment this didn't sit well with me. Let's see how we can make it into something that has a better user experience .