Status Updates From Test-Driven JavaScript Deve...
Test-Driven JavaScript Development by
Status Updates Showing 1-7 of 7
Mike
is on page 73 of 528
A good insight into unit testing, I understand now that merely adding tests to your code isn't enough with TDD, and that the primary idea of TDD is to get you to think about the problem you're trying to solve before you write the code. Very enlightening.
— Nov 02, 2014 07:04AM
Add a comment
Carl-Erik Kopseng
is on page 200 of 701
Chapter seven has some really good content in which the author explains the pros and cons of the various ways of achieving inheritance in JavaScript. Crockford's module pattern/functional inheritance is given a better description here than in Crockford's own book!
— Jul 28, 2013 12:56AM
Add a comment
Nephi
is on page 247 of 528
Just read through the first 'example' chapter which walked through a real part of a project. Now about to code it following the example.
— Jan 11, 2012 11:37PM
Add a comment
Nephi
is on page 197 of 528
I just completed the chapter on unobtrusive JavaScript which had both a description of what that is, and a concrete example. Having coded for accessibility before, I greatly appreciated this chapter.
— Jan 07, 2012 09:31AM
Add a comment
Nephi
is on page 159 of 528
I just finished the section on prototypical inheritance and I learned a great deal. Now I need more practice.
— Dec 29, 2011 11:37PM
Add a comment
Nephi
is on page 136 of 528
I am well into the parts that are all about JavaScript and less about TDD. I like how the author uses tests as examples of the code he is teaching, because TDD can be explained in very little time, but requires a lot of practice to get good at. This may not be a book for people who already have a good grasp of JavaScript, but for Java developers like me, it is a great beginning.
— Dec 29, 2011 12:05AM
Add a comment

