It is a great introduction for testing with Spring and can say that as a Junior developer I have learned a trick or two! Thanks a lot for preparing this talk.
The description states that "This talk will give you an overview of best practices, pitfalls, and recipes for testing Spring Boot applications". But better name for this talk is "Introduction into Spring Boot Testing". So it just gives basic things from reference documentation of Spring Boot Test without any "best practices" and "pitfalls". I guess the main idea of this talk is the last slide where speaker advertises his own master-class.
With this talk, I tried to introduce Spring Boot testing for Spring Boot newcomers (0/1/2 years of experience). I haven't seen many conference talks focussing on things that help new developers quickly get up-to-speed with things. Indeed, most of this stuff can also be found in the docs. But who reads the docs 🤪? Naming it "Introduction into Spring Boot Testing" would have sounded too boring, IMHO. The advertisement on the last page is what helps me sponsor this trip, compensate for the time, pay the hotel and the flight as the conference organizers didn't cover it :(
Please don't use `assertEquals`, which expects the actual result on the left side, which is weird, it's like Yoda-style code ("blue is the sky"). AssertJ is much more readable in that regard, which puts the variable/expression on the left. JUnit's built-in assertions were never meant to replace a fully-fledged assertion framework, they leave that goal to libraries.
That presentation is broken from the start - why the guy says "testing spring application"? Why not just "testing application"? Why couple your tests to the framework?
It is a great introduction for testing with Spring and can say that as a Junior developer I have learned a trick or two! Thanks a lot for preparing this talk.
The description states that "This talk will give you an overview of best practices, pitfalls, and recipes for testing Spring Boot applications". But better name for this talk is "Introduction into Spring Boot Testing". So it just gives basic things from reference documentation of Spring Boot Test without any "best practices" and "pitfalls". I guess the main idea of this talk is the last slide where speaker advertises his own master-class.
With this talk, I tried to introduce Spring Boot testing for Spring Boot newcomers (0/1/2 years of experience). I haven't seen many conference talks focussing on things that help new developers quickly get up-to-speed with things. Indeed, most of this stuff can also be found in the docs. But who reads the docs 🤪?
Naming it "Introduction into Spring Boot Testing" would have sounded too boring, IMHO.
The advertisement on the last page is what helps me sponsor this trip, compensate for the time, pay the hotel and the flight as the conference organizers didn't cover it :(
The title clearly states what to expect, you are reading too much into it. Let's be gentle to each other and be thankful.
One of the best course to buy. Money well worth spending. Still one of my reference sources of information daily.
Great introduction into Spring Boot testing. All things mentioned here are part of the official 4-day Spring Core and Spring Boot course
Oh nice, I wasn't aware that I just summarized the official Spring courses 😅
Where is the full course link
Gold Nugget for Spring Testing Lovers
Thanks bro! Really helpful information!!! ✊✊
Slicing might decrease the test runtime drastically and saves potentially a lot of energy when ran often e.g. in CI
Thanks, great intro!
Great Video! Thanks
Interesting 😀 thank you Philip Riecks
Didn't know about JSONassert, thank you)
thanks Phil. really useful talk
Great video, thank you!
Please don't use `assertEquals`, which expects the actual result on the left side, which is weird, it's like Yoda-style code ("blue is the sky"). AssertJ is much more readable in that regard, which puts the variable/expression on the left. JUnit's built-in assertions were never meant to replace a fully-fledged assertion framework, they leave that goal to libraries.
Great talk! 👍
Great job. Thanks.
Thanks 🙏
That presentation is broken from the start - why the guy says "testing spring application"? Why not just "testing application"? Why couple your tests to the framework?
Very useful video
very useful content