One of the reasons for AngularJS’ success is its outstanding ability to be tested. The main factor that made Sébastien switch from “Well, I just launch the app and see if everything works” to “I’ve got unit tests!” was that, for the first time, he could focus on what matters and on what he enjoys in programming: creating smart algorithms and nice UIs. After having fixed it, re-updated the application and apologized to customer service, he decided to entirely rewrite this component in test-driven development style. The test file ended up being twice as long as the component file. It has been improved a lot since, especially its poor performance, but it never failed again in production. Rock-solid code.
Read more…
As much as we aim to design our mobile apps and websites for contextual use, testing their usability in context can be challenging. One approach to mobile testing is participatory design. A participatory design test session typically takes about an hour and has four parts. In this article, Marina Lin conducted this type of study while researching how visitors to Cars.com’s app use their mobile device while purchasing a car on a dealer’s lot.
Read more…
With a distinct lack of debugging tools, developers turned to a variety of hacks. In general, these hacks were an attempt to recreate a given issue in a desktop browser and then debug with Chrome Developer Tools or a similar desktop toolkit. To put it bluntly, these hacks don’t work. If you’re recreating issues on the desktop, then you can’t be certain that any of your fixes will work. In this article, Jon Raasch will explore a variety of emulators and simulators that you can use for quick and easy testing. Then, he’ll look at remote debugging tools, which enable you to connect a desktop computer to a mobile device and leverage a rich debugging interface.
Read more…
Back then, when every home had broadband and before anyone had a smartphone, we were living in the Golden Age of web development. We never knew how easy our jobs were. Because of all the things we have to support now, testing has become really difficult and also super-expensive. Now with responsive web design, we have at least 15 browsers working on a myriad of different-sized devices, with many different input types, multiple pixel resolutions and hugely varying connection speeds. There must be a better way to deal with the problem that responsive design has created for testing. In this article, Tom Maslen will devise a testing strategy so that you don’t have to test every device every time you want to update a live website.
Read more…
The method of pitting two versions of a landing page against each other in a battle of conversion is called A/B testing, and it lets you test two entirely different designs for a landing page or you can test small tweaks, like changes to a few words in your copy. Running A/B tests on your website can help you improve your communication with visitors and back up important design decisions with real data from real users. With the multitude of tools available, split testing has become easy for even non-technical people to design and manage.
Read more…
In this article, Anselm Hannemann suggests how we can manage to test on multiple devices to resolve errors, without pouring a truck-load of money into actually buying all of these different devicessince these tasks haven’t become any simpler since the wide variety of smartphones, tablets and other devices that sport various operating systems and versions.
Read more…
At the heart of testing is the capability to ask challenging and relevant questions. Rosie Sherry takes us through the thought process of testers and discuss the types of things they consider when testing a mobile app.
Read more…
This article will cover most of the things needed to be considered when opening a device lab. It will also work as a guide and give practical tips: things like location, how to get devices, what devices to get and what software to use.
Read more…
You probably know that testing is good, but the first hurdle to overcome when trying to write unit tests for client-side code is the lack of any actual units; JavaScript code is written for each page of a website or each module of an application and is closely intermixed with back-end logic and related HTML. In the worst case, the code is completely mixed with HTML, as inline events handlers.
Read more…
In this multi-part post, Addy Osmani takes you through the exact set-up he uses to accurately test content that will be potentially viewed by up to millions of users with a very diverse set of browsers.
Read more…
