Test Driven Development (TDD)
8The reason a development method like TDD helps development is because we want to structurally write high quality code that’s readable, maintainable and most importantly, does what you want it do to and not more or less. Unfortunately, the traditional way of developing is to just think hard about a problem, come up with a solution in your mind and start writing code. And that’s not a good recipe for a good solution. So, after writing some code, we start debugging it and changing it until we think it’s correct and doesn’t produce any obvious errors.
| 15+ Years Experience Learn from industry leaders |
Tailor-made Learning Journeys Become the expert you want to be! |
| Hands-On Approach Immediately start applying your craft |
Rated 8,3 Highly reviewed by your peers |
Upcoming courses
- Software Developer
- Dutch
- English
Short summary
The problem is that the solution that pops in your head first isn’t necessarily the best or complete solution, and perhaps isn’t the best next step to take. However, it often does feel like it is. We humans have the tendency to overestimate our abilities and programming is not an exception on this. If you have a lot of faith in your own mind, I’d recommend reading “Thinking, fast and slow”, written by Daniel Kahneman. After reading this book, you stop putting so much faith in the humans’ ability to rationally think about problems and start questioning your own judgment some more.
And that’s where Test Driven Development can help. It forces you to incrementally develop your solution in small cycles by making every outcome of a step explicit and think about the simplest order of steps to come up with your solution, not more and not less. To make the verification of the outcome of a step fast and easy, we use unit tests which we can run a couple of times each cycle. In TDD the developer works in a cycle where he first writes a failing test, then makes it pass and finally refactors the code. This approach prevents the developer from doing multiple things at once which can lead to errors.
If you as a developer don’t practice Test Driven Development yet, this training will help you to really understand what TDD is all about and to be able to apply it in your development work.
Our Trainer
Phani Bhushan
Technical Consultant & trainer
Phani works as a Technical Consultant and a Scrum.org/DevOps Institute trainer at DevOn, helping organizations to make the transition to the Agile way of working.
Course objectives
The learning objectives for Test Driven Development include an understanding of:
- Knowledge and experience with developing using Test Driven Development which can directly be applied in practice.
- Knowledge about clean code, design principles and patterns
Course topics
- Test Driven Development
- Clean code, design patterns & principles
- Unit testing
- Recognizing and preventing “Gold Plating”
- Pair Programming
Target audience
- Developers working with or are well familiar with an Object Oriented programming language like Java or C# (.NET). The training isn’t fit for testers, Scrum Masters or others that don’t have a programming background.
Testimonials
-
Really good structure, clean code part
TDD
-
I was given a different (better) perspective on unit tests
TDD
-
Changing the mindset in the right direction
Payment methods
Need help?
Please contact us via email or call us by the number stated below. We are more than happy to help you.
+31 (0)15 - 241 19 00
academy@devon.nl
What’s next for me?
Take a look at what trainings you should follow next to become a true expert in your field.
SRE Foundation
FAQ
After your registration has been confirmed, you are still able to change the date up to 20 days before the first day of the training. You are able to do this once. Please send your request to academy@devon.nl or call +31(0)15-24 11 900 for further assistance.
Two weeks before each training, we will check if we have enough participants for the training course to be valuable and continue. If this is not the case, we will inform you by e-mail, with options for a new date and location. After this notification, you will have the right to cancel or change your registration within 5 working days.
On the website you can choose to pay via iDeal, creditcard or by invoice with a payment period of 30 days.
Most of our courses are available in both English and Dutch. We have a selection of training courses which are only available in English, which will be on that training page. Our rule of thumb for courses in the Netherlands is – the course is in English unless everybody speaks Dutch, then the course is in Dutch. If you want to be sure you are in a Dutch course, please get in touch with academy@devon.nl in case the information on a specific date is not available on the course page.
Unless mentioned otherwise, the course fee includes the cost of training material, exam cost, the use of the location, catering and parking.
When you click on the orange arrow, the menu will unfold further. More locations and dates might appear.
The costs that apply to our programs initiated from the Netherlands are exempt from sales tax as per Article 11-1-o of the 1968 Sales Tax Act. In other locations/countries, the prices shown are excluding VAT, which will be added.
Is the ‘register’ headline visible? This means you can register and attend the training. Does the headline say ‘full’? Give us a call and we’ll try and help you out!
All course material for the open registrations is in English.
If you are doing the PSD (Scrum.org) or one of the certified DevOps Institute trainings, you will receive your exam code on the final day of the training.
We have a payment term of up to 30 days
