The use of special software to control the execution of tests and compare the expected results with the outcome provided by the tests, is called test automation.
With automated tests we can automate repeated actions which are time-consuming when performed manually, and ensure the functionality of our code. Test automation is critical for software development teams which produce software in short cycles in order to ensure that the software can be reliably released.
Hi!
I couldn’t find a better idea for this blogpost so I ended up with this.
Inspired from the page loaders that YouTube and GitHub uses, I thought I’d write something that resembles them.
The process is to create a div element that will represent the loader and absolute position it on top of the page.
Javascript is a language that is, by design, difficult to debug. It is dynamically typed, it is based around asynchronous callbacks, almost all data types are mutable, almost no functions of the standard library are pure, and the list goes on. And these are not just flaws in the design; they are what makes the language what it is. It is therefore important to be equipped with the correct tools when setting out to correct your code. I am not talking about fancy debuggers and static code analyzers, just two very simple libraries. So simple in fact they do not even qualify as separate libraries. They are just a couple of hundreds of locs that you can copy right into your project and modify to your needs. My sample implementation for each is provided.
Many testing frameworks exist in JavaScipt nowadays.
The combination that I got hands on is the mocha [1] testing framework combined with the chai [2] assertion library, the sinon [3] mocking framework and the karma [4] test runner.
I thought to gather some resources here on how to work with these tools.