Software developers generally don’t write poor, unmaintainable code out of any malicious or deliberate intent. They do it because software development is complex and there is not enough feedback in the process to ensure they adhere to good SOLID (Single responsibility, Open-closed, Liskov substitution, Interface segregation and Dependency inversion) object …
Classic old-school TDD recommends refactoring as part of every cycle — red, green, refactor. In fact, it recommends refactoring mercilessly. Relentlessly. To succeed at classic TDD, you have to be some kind of refactoring maniac!
As a new Ruby developer, I expected to be challenged intellectually as I dove into algorithms, data structures, and object-oriented design, but I was disturbed to realize that coding, especially in an Agile workflow, actually challenged me personally. Web development pushes us to our limits, not only of cognition, but …
What is better than Test-Driven Development? Even more test driven development – this time with deeper tests. Unit tests are useful, but a few examples don’t prove our Ruby code correct. Can we approach mathematical proof without ballooning the lines of test code we maintain?
Writing clean, testable JavaScript can be a daunting task for front-end developers. Many find it difficult to get into and thus discard it. Test automation is an essential part of modern web applications, especially when it comes to maintainability. In this talk, I show how easy and straightforward testable JavaScript …
Jim Lavin presents a Test Driven Development (TDD) approach to show how to write unit tests for your AngularJS components. The presentation covers creating a project from scratch using Yeoman and then adds functionality to a controller, service and directive using a Test Driven Development approach by writing unit tests …
