Spring Boot TDD - Beginner to Practice Accurately

I really enjoyed the lecture. It was the most helpful lecture I've seen recently. Thank you very much for preparing such a thoughtful lecture. I'm also very interested in testing and have purchased and studied several lectures and books related to testing, such as unit tests and TDD, but I was always at a loss as to how to apply what I learned to actual projects. So I thought it would be great if there was a lecture that taught how to properly introduce TDD or testing into projects, and through this lecture, I was able to grasp a major direction for TDD. Thanks to this, I feel like I can now cautiously try introducing TDD into my own projects. And I really hope a lecture on legacy code, which you briefly mentioned at the end, will also be released. A message for those considering purchasing the lecture: If you want to introduce TDD but are unsure how to proceed, this lecture will definitely be a great help.

This lecture clearly teaches that our work isn't just simple design and code writing, but understanding real-world customer problems and solving them through software. To someone who has only learned server, API, and databases, it's not easy to understand what it means to "develop in a customer-oriented way." Someone might tell them that using "Clean Architecture" or "Ports and Adapters" architecture makes it easy to handle changing requirements. Even after studying hard and applying patterns, it's not easy to feel like you are developing in a customer-oriented way. This lecture provides clear guidelines to such people. The content taught in the lecture is about well-organizing customer requirements and writing code that fulfills them. And in this process, it lets you realize how effective "Test-Driven Development" is. If you follow the lecture to the end and pay attention to its purpose, the question mark you have about TDD will turn into an exclamation mark.

I was able to internalize TDD through hands-on coding exercises in a way that focused on the practical value of software and could also increase productivity, without getting bogged down in theory. I felt that the examples covered in the lecture were carefully refined and structured to cover the necessary knowledge for the lecture while still feeling relevant to real-world industry situations. I believe this lecture can be a truly accurate solution for people like me who have a habit of building things hastily, spending time debugging, failing, and starting over, or for those whose coding habits, including writing clumsy tests, actually lower productivity.

This lecture resolves common questions about TDD methodologies and applications often encountered. It effectively conveys the instructor's philosophy on how TDD helps us and its meaning from a problem-solving perspective.

Beyond learning the TDD development methodology itself, it also contains important discussions on the perspective to take and the areas to prioritize when proceeding with software design and implementation. Also, while the difficulty of the exercises might be considered quite easy, I felt that complex problems or phenomena that can arise during the actual development process were transformed into a simple and seemingly straightforward form and included in the lecture within apparently simple scenarios. I strongly recommend it not only for those new to TDD but also for those new to software engineering or those who wish to grow from a new perspective, moving beyond existing habits.

I had always been told to write test code, but when I actually tried to write it, I was worried about how much to cover. It was good that I could get a feel for it by trying everything from documentation to code implementation through the course. I'm also looking forward to the remaining courses.

"How on earth do you write tests first and then develop?" This was the lecture that first resolved my biggest question (?) about this concept. This is actually the first time I'm leaving a course review after taking many lectures, and I think this is an excellent lecture that covers not just TDD but overall concepts about testing. I always wrote unit tests, integration tests, etc. separately when writing tests. In that process, there were some overlapping parts, and I often wondered if this was really efficient. But I think I just wrote them that way without a clear opinion of my own, simply because that's what people around me did. I really liked how the lecture mentioned and explained these aspects as well. I haven't finished the entire course yet, but I'm very satisfied and enjoying it so far.

Thank you for helping me realize the importance of test scenarios. I should develop the habit of starting by writing unit tests according to test scenarios, even if it's not strictly TDD. Thank you.