3wetwetw
Some features are not sexy, nor cool.
How to test code that wasn't designed for testability
Proof of Unit Testing's Time Savings
The best thing is to make sure you're using tools that are flexible and scalable. Also, decide what to test. You don't test basic logic like 1+1=2.
Unit tests are intended to catch a specific type of bugs but not all errors. It's not usability testing. If you're not doing TDD (ideally) at least you can test legacy code and strive for high code coverage
The Problems with Unit Testing Frameworks
In fact, we wrote about this before http://bitly.com/zdyJfl
We're hosting a webinar on Wednesday about different kinds of testing and when a unit test is appropriate and when another kind of test, like an integration test, may be a better choice - http://bitly.com/xeYSYg.
Unit tests have a time and place. There are times in which they are a must if you want to reduce technical debt and test your code - both if you're writing mission critical stuff or even when you're writing the latest social sharing app (remember the Fail Whale? We all hate that!). But, no, you don't need TDD on greenfield code all the time and you shouldn't have to write tests for logic.
How do you fix your bugs?
Does Agile Denote Deeper Lifecycle Presence For Testing?
Design for Testability – The True Story
Do Tests Get Too Much Respect?
How to Test Dependencies and Legacy Code
Reasons to Avoid Test Driven Development
Today - Jan 4: How to Start Unit Testing
What's ahead for 2012?
Happy New Year!What's ahead for 2012? What will we see with the rise in software -- even your non-techy relatives are reliant on software. What does that mean for developers and startups?