This video is a look at how to make unit tests run parallel. We'll use the junit-jupiter framework to make that a reality. In this video I talk about the difference between making tests in parallel between classes and between the different implementation methods that define each unit tests. Calling tests unit tests or integration tests naturally depends on whether they connect to outside containers or if they interact with other external parties. Having said that in their essence they are all JUnit tests and this is an important distinction since we are looking at how to make JUnit tests go parallel and further we are also going to have a brief look at how these tests can work with making forks to the actuall JVM and see the different processes ids they generate, the PIDs, and how that affects the tests. As usual remember to stay tech, keep programming, be kind and have a good one!
---
Chapters:
00:00:00 Start 00:00:33 Travelling Intro 00:00:45 Intro 00:02:45 Introduction to the project 00:04:35 Using simple properties to configure Jupiter to run in parallel 00:18:22 Configuring maven with JVM forks 00:26:54 Configuring gradle with JVM forks 00:33:28 Closing notes 00:34:56 See you in the next video! 00:35:59 End Credits 00:36:23 Disclaimer
As a short disclaimer, I'd like to mention that I'm not associated or affiliated with any of the brands eventually shown, displayed, or mentioned in this video.
---
All my work and personal interests are also discoverable on other different sites:
If you have any questions about this video please put a comment in the comment section below and I will be more than happy to help you or discuss any related topic you'd like to discuss.
If you want to discover more about my open-source work please visit me on GitHub at:
