Test Driven Development
October 23 11:00am MT
I Tried Unit Testing But Testing My Existing Code Is Too Hard!
That’s because you have got the order wrong! Writing unit tests after the fact is possible, but it is always hard. Why? Because whoever wrote it never thought about testing it and therefore did not design it in a way that made it easy to test.
When you write the tests first you can be sure your code is testable. You are forced to design it to be testable. An added benefit is that you will write better code. Why? Because the same properties that make code testable, make for better code in general: less coupling and more cohesion.
If you have legacy code that you need to add unit tests to, unfortunately the answer is often to change your design. You may have to add things like humble objects and dependency injection. There may be no way around it. If you need help with those, I have a whole series of blog posts about them. https://blog.sasworkshops.com/sw-engineering/unit-tes…
“If you don’t like the results you are getting, then change what you are doing.”
Going forward, do things differently. Write the tests first. It will change the way you design your software. You’ll thank me for it later.
If you want to learn more about TDD or need some inspiration, then this webinar is for you. I’ll explain a little bit about TDD and then walk you through a real life example so you can see it in action.
This Webinar Is For
- Developers who are tired of trying to retrofit unit tests into existing code, or those who just simply want to write better software.
- Architects who want the assurance of having unit tests in place, so they can plan major refactorings without worrying about breaking existing functionality.
- Project Managers who are looking for a way to ensure higher quality software with fewer defects.
What you will learn
- The basic idea behind TDD
- The basic process of TDD
- A real world example
- Lessons learned
There are limited seats so please RSVP and reserve your seat today!