Effective Developer Workflows With Quarkus

In this video I'm showing how to leverage that and how to build up a local development workflow that is efficient to use.
For more information see:
Effective Development With Quarkus Course: www.sebastian-daschner.com/co...
Effective Testing Course: www.sebastian-daschner.com/co...

[@omar.rivera]

You came back 🎉

[@SebastianDaschnerIT]

Yes I know, had a very busy summer/fall and wanted to publish again much earlier 🙂

[@sergeyshvyrev969]

Наконец-то!!!! Так ждал вашего нового видео!!! Спасибо!!!! ))))

[@fauntleroycliftonguitar5489]

What are the disadvantages? What if the test suite is quite large? It would take long to run all of them after each file change detection.

[@SebastianDaschnerIT]

Actually it doesn't, Quarkus only recompiles what has changed and this works very well even for huge code bases. Even if you were to recompile everything, only compilation is also surprisingly fast (recently tested on a project with ~ 100,000 classes). JUnit is very quick in running many test cases as well. Still, at some point you'd probably want to split up your test suite (if you have, like > 1,000 system test requests per suite run or so), which you can do with the quarkus test properties / using packages / using tags, etc.

[@im_andre6dev56]

Hi Sebastian, is it possible to ask questions directly within the Quarkus course?

[@SebastianDaschnerIT]

Hi, yes there is a way to send messages / ask in a written form