(Video) Let There Be Load! - Part 2: Map Load Runner Feat. Batch Test Loop
In the previous video, both the Map Load Runner and the Batch Test Loop were introduced in theoretical terms, so it’s about time we get our hands dirty by examining how the Map Load Runner/Batch Loop combination can be utilized in scope of a real-world example!
This is part 2 of the “Let There Be Load” series, and, as such, constitutes the logical continuation to the previous video – the latter introduced Hazeltest’s Map Load Runner and both the Batch Test Loop and the Boundary Test Loop in theoretical terms, so it’s obvious the ensuing video had to introduce one of the possible combinations of Map Load Runner plus one of the two test loops in more practical terms. I decided to make this video about the Map Load Runner/Batch Test Loop combination because the Batch Test Loop is not only the older feature in Hazeltest, but also – primarily – because the kind of testing the combination enables typically happens in very early phases of testing, whereas the Map Load Runner/Boundary Test Loop combination tends to come in much later.
The video does a short recap of previously covered material before diving into the live demo, in scope of which we do three iterations on the configuration for a Hazelcast Helm chart, thus treating the latter as our release candidate. Each iteration is exposed to load created by the Map Load Runner/Batch Test Loop combination, which increases in its intensity as we progress through the demo.
As becomes apparent, running “sanity checks” in the form of smoke tests right in the CI/CD pipeline building, publishing, and deploying the release candidate is a jolly great idea.
Enjoy the video!
Let There Be Load! - Part 2: Map Load Runner Feat. Batch Test Loop
