Effective Test Execution With Quarkus

Ғылым және технология

The dev mode in Quarkus and especially the continuous testing feature is one of the fastest ways to execute tests and get feedback. Triggering your tests with a single keystroke and receiving feedback in a matter of milliseconds is a game changer in minimizing turnaround times. With Quarkus 3.2, there are more interesting ways to add to this way of testing, which I’m presenting in the this video.
For more information see: blog.sebastian-daschner.com/e...
Effective Development With Quarkus Course: www.sebastian-daschner.com/co...
Effective Testing With Quarkus Course: www.sebastian-daschner.com/co...

Пікірлер: 9

  • @ferjava
    @ferjava11 ай бұрын

    Wow, this alias approach is very very useful... I also tested this other tip of "misusing" Quarkus dev-mode for testing other kind of apps and is very cool too, thanks! ;)

  • @gaglh3603
    @gaglh36037 ай бұрын

    Oh noez, just found this channel and no videos for 4 months, don't tell me you stopped making videos 😱

  • @SebastianDaschnerIT

    @SebastianDaschnerIT

    6 ай бұрын

    Just being quite busy, there will be new ones soon, no worries :) Which topics would help you the most?

  • @gaglh3603

    @gaglh3603

    5 ай бұрын

    @@SebastianDaschnerIT a overview guide on the quarkus annotations and their use would be very helpfull for me. Also your thoughts on REST vs message broker. Or how does a CD setup for several quarkus-services look in the field, if you have access to such. :)

  • @bCool-sl5cy
    @bCool-sl5cy4 ай бұрын

    Vielen Dank Sebastian für das Video! It's really awesome! 👍 I have a question regarding the use of Dev Services in integration tests: locally they work perfectly, but how about runing them in GitLab? Do I have to do extra coding/configuration to let them run smoothly? Will the docker containers akso be strated in GitLab/ArgoCD (for example)? Do you have any experience with that? Thank you in advance!

  • @SebastianDaschnerIT

    @SebastianDaschnerIT

    4 ай бұрын

    Thanks, happy to hear that :) Yes, I'd recommend to make the environment more specific for your CI/CD environment. Either you use some codified form of running the required containers (e.g. using Testcontainers) as part of your test suite, or, (what I recommend because of multiple reasons) is to setup the environment as part of your pipeline but outside of your test classes. Docker containers, compose, etc. is your friend here. You can use a more complex way using GitOps and things like ArgoCD, which then results in a pipeline that comes along with deployment to a (test) K8s environment, and after successful deployment executes the tests against that environment.

  • @W0rldBr3aker
    @W0rldBr3aker10 ай бұрын

    Hey yo Sebastian! What about htmx + quarkus + qute?

  • @SebastianDaschnerIT

    @SebastianDaschnerIT

    10 ай бұрын

    Hey, been thinking about this combination as well. In general, htmx could be very interesting with a Quarkus backend... Did you use it somewhere already?

  • @W0rldBr3aker

    @W0rldBr3aker

    10 ай бұрын

    ​​@@SebastianDaschnerIT Nope, but looking forward, since it much easier for me to code the UI logic in server-side. Would be really nice to see you (guru) playin' with it :)

Келесі