A developer's cheat sheet for adding Java/Spring tests

I can confidently say that this is the best lecture among all the lectures I paid for at Inflearn. The original curriculum structure that was created by racking my brain without copying from books, the essence of each lecture, no rambling, clean comments and sentences, appropriate speed and clear speech, and the concrete practical method of testing to draw the big picture of design, and then draw the test under the design again. You can see how much the instructor has thought, repeated, improved, and developed. He has amazingly incorporated all of that into the lecture. I have only taken one or two lectures at Inflearn, but I have never seen A/S as refined as this lecture. After filming, videos are not as easy to edit as text, and due to the nature of the lecture, there must be a strong desire to always show something beautiful and without a single mistake, so I have refined those parts without any additions or subtractions. When the instructor makes a mistake or says, "I wish I had done this," there is a section where the screen turns gray and only the voice appears. When this part comes up, I can check if I'm listening with my wits about me, compare it to my thoughts, and think that the instructor also has such concerns. Anyway, these A/S videos are like a well-written script, and they serve as great educational tools. I bought the test, but the design came with it. But the design was more expensive than the test. I'm writing a review for the first time because I'm mad that there are only 54 reviews for this crazy great lecture. The content, voice, audio, video, and length... everything was cohesively put together, so it was like looking at a beautiful design. Personally, I liked Instructor Kim Woo-geun's lecture much better than the named lecture with +9,999 students.

I've been a developer for less than 2 years. I suffered for almost a year due to low-quality code, poor design, and legacy code where tests were nowhere to be found. Since most of my work involved developing Spring/Spring Boot applications using server-side rendering with JSP or Thymeleaf, the larger the scale became with maintenance, the more manual testing I had to do with each release. Each time, my desire for testing really intensified. I read 2 books related to testing (1. by Choi Beom-gyun, 2. by Kent Beck), but while they explained the importance, philosophy, and methods of testing, I remember they didn't talk much about design. Even if they did, they weren't tied to DDD like this course. Moreover, while those books were helpful and got me excited right after reading them, applying them in practice was somewhat challenging. But with this course, I feel like blocked channels have been cleared refreshingly. I can now picture how I should develop going forward~ The truth that development-design-testing should work together like a trinity! Domain-driven development focusing on the core business rather than peripheral technologies like UI or infrastructure! Testing creates good design! 😊😊 Thank you for this valuable course! With the help of this course, I feel like I can grow into a better developer^^ I think this course is really great for beginners who have some concerns about design and motivation for testing, and I strongly recommend it!

This lecture is not a simple test lecture. I was learning and applying how to use JUnit, Mockito, etc. to write tests. Then, I became curious about good test code and well-written test code beyond simply using test tools, and I found this lecture. I had enjoyed watching the instructor's first lecture, so I had a high level of trust in it, and the contents of the table of contents seemed interesting. I took all the lectures and am leaving a review. This lecture is not a simple test lecture, but a very great lecture that helps me think about good architecture and OOP. For me, whose purpose of writing tests was simply to prevent regression, testing and design are mutually complementary, and it made me think about good design naturally while informing me of the problems of the existing layered architecture, and the limitations of tests written in the layered architecture. It does not just point out problems in theory, but suggests better structures and test code writing through the process of refactoring code. I was learning Mockito for the first time recently and was impressed by the tests using stubbing. This was a great experience for me to test the tests that required Mockito in pure Java without an external library. In the end, it is a good lecture that continues the words of the first part that everything is OOP. In addition, it was good to talk about the concepts needed for testing and the opinions that contained the instructor's personal concerns. I learned a lot because I could indirectly feel the seriousness and attitude toward the development field. Thank you for the great lecture.

It was so much fun to watch and I think I'll reflect on it when newbies ask us, "Don't we have test code?" ㅠ_ㅠ.

While studying Spring and looking at the codes on how to write tests, I noticed that there were many meaningless, repetitive tests. So I wondered why they were writing such repetitive tests. Then, I happened to see a new lecture on Infraon titled Why Spring Test Developers Fail to Write Tests. I thought it was just for me! So I boldly paid for it. After completing the course, I think I made a choice I don't regret. I paused the lecture for 10 minutes and thought carefully about what the instructor was talking about. So, although the lecture was 6 hours long, I felt that it had the quality of 60 hours. I am grateful to the instructor for broadening my perspective on software engineering.

I've never left a review for a class before, but this course is awesome.

This is a really great lecture. Thank you!!!!

I feel like the knowledge I kept hearing somewhere was organized through this lecture. I have definitely engraved in my head that writing testable code is directly related to good design. I started a project and I think it will be a great help in writing test code. The lecture structure and the instructor's tone of voice were also very good. PS. The only thing that bothered me was that he often used the word "Anyway". It may have been because it was repeated as I listened to the lecture continuously. (The lecture content is really great!)