What is Test-Driven Development (TDD)?
Test-driven development is all about writing code that you trust, maintainable, and you won’t call it legacy code straight out of the box. It means you write the test first and then you start to write code. In contrast with common beliefs, you save time with this technique because you have to write the tests once and it will test your production code as many times you want. You will rarely have to test your code manually again. You will see examples for this in the course I review for you below.
What is the course like?
The first impression as you start to watch the course is: why is the teacher is all the time in the frame. You can see that this is one of his first courses. He is a little bit shy at the beginning and probably his heart is in his mouth, but he picks up the speed and courage quite quickly. You wouldn’t tell but he is a Ph.D. student at that time in software testing.
He soon reveals a really simple piece of code that shows quickly why is testing so important and how easy it is to write code that would fail in real-life scenarios: in production. The logic looks good, the results are looking good, but hey, there is that one case when our code fails. And it is all happening in the first 10 minutes.
Do you know what these steps are?
-
Scenario
-
Action
-
Validation
If not I recommend you read through this review and watch the course on Udemy.
Reviewed course link:
[If you get this course through my affiliate I will get a commission. It won’t affect the original price you pay for this course.]
He shows the test naming conventions for the jUnit. After that (and it is a really good point) he shows that his test could run in only 0.033 seconds. I bet it is a little bit quicker than a human manual test 🙂
After that there are questions you will know the answer for like:
-
What is a happy path?
-
What is the sad path?
-
How to find cases to test the same logic from many aspects.
-
Naming conventions
-
Testing rules
-
Design Patterns: You will see many examples with Design Patterns that are useful in everyday scenarios.
Useful Questions to answer:
-
Why did I choose this course to watch?
-
I chose this course to watch because it was recommended by my colleagues.
-
I see every day the value of Test Driven Development and the pain when the code lacks proper tests.
-
With automated tests, you can save your code from becoming tomorrow’s legacy code. Keeping your code always fresh and documented is like having food that can be consumed any time in the future and find it fresh and tasty. Yummy.
-
-
The programming language used for this course: Java
-
What test framework is in use?
-
Starts with simple System.out.printline
-
changes the simple examples to jUnit with a nice touch to understand the essence of test case writing.
-
-
Whit IDE (Integrated Development Environment) does it use?
Eclipse
-
Can the gained knowledge be used for other technologies: Yes it can. The mindset that is important not the tools that he uses. (Although for Java he used rally convincing tools.)
-
Who should watch this course? With what experience level?
Course Level: Beginner. This is for those who never wrote tests before or still learning how to write code.
-
Did it meet my expectations / Would I recommend it?
If I would be in my Junior years this course would be a really great first step toward learning Test Driven Development. If you never worked with TDD before I recommend this course because it sums up the main features of TDD and you will get a good understanding of it et the end of the course. Although the teacher is Brasilian and his English is a bit slow, you can solve it by speeding up the video a bit. The teacher’s Ph.D. on the topic gave me confidence that he knows what he is talking about, so it met my expectations. Good work.
-
Can I ask questions before I commit my time to this course, just to be sure?
Of course, you can. That is why I am here. To answer useful questions.
I hope you found this review useful. If you liked my review and watched this course I would highly appreciate it if you would leave some feedback to know I am doing a great job that helps you, my reader.
