Visiting Japan is definitely a unique experience. With my wife, we went there directly from the trip to Sri Lanka in July 2016. We have been travelling between numerous cities for 10 days. First we rode between Tokyo and Kobe by the famous bullet train Shinkansen. Then we spent one night in an historical Ryokan with hot springs in the Arima Onsen area located behind the Mount Rokko. We also visited two old capital cities Kyoto and Nara. Finally we had a chance to see Mount Fuji hidden behind the clouds from a Shinkansen car’s side window on our way back to Tokyo.
Software testing helps protect code from incoming bugs and improves general quality of the functionalities exposed to the users. When you look at it from the developer’s standpoint the first thing that comes to mind is unit testing. However it turns out tests come in many flavors. I have already shared in the recap from Advanced TDD workshop with Uncle Bob what kinds of tests a professional team should use to ensure that the application remains intact. The following items create a hierarchy:
At Automattic we use Mocha to run all tests written for Calypso project which powers WordPress.com. It also includes end-to-end tests, which live in their own repository. We have been using this setup for over 3 years now. I think it is a good moment to revisit this choice. I found this unit testing tools comparison very helpful when evaluating alternatives. I strongly agree with the conclusions shared by Martin Olsson in his article:
I have already published one post about Progressive Web Apps (PWA) a few months back. It looks like Google is investing a lot of efforts to make it a new standard of building websites. At the last Google I/O, there were a few announcements made related to making PWA a default feature in a few popular boilerplates and CLIs for libraries like React, Preact, Polymer or Vue. I recommend watching the following presentation by Addy Osmani:
I got very excited when watching this talk for React Europe by Leland Richardson: