Decreasing the slope of the learning curve.
In the previous article I made the case for Automated Testing. Today we will talk about the tools.
I will use the terms Harness, Framework and Library interchangeably. Be warned.
All of this and more, after a few choice bold words, a digit, a hash, and a hyphen.
One of the Devs I used to work with has been asking a lot of questions recently, all revolving around what can only be considered the principles I hold dear as a TDD champion. I don’t claim to be a guru, but I hope to be able to start some conversation about the importance of automated testing, some of the principles I hold dear and most of all I intend to engage you readers so I can learn from your experiences and possibly guide you if questions arise.
Let’s dive in.
For all things web development you have to be able to test them and confirm that they work. With the progression of AJAX and DOM altering JavaScript testing these web applications has become more and more of a chore. Unit tests and frameworks provide a certain level of quality assurance from the back but the user’s experience needs to be confirmed as well. The last four years of work at Broadcom has afforded me a number of opportunities to diversify and expand my skills palette, but no matter what I do I always find myself back in the role of a tester, unfortunately.