it's easier to kick off in a jenkins pipeline since it's standalone but is otherwise less powerful, less general purpose, and the architecture to support the co

it's easier to kick off in a jenkins pipeline since it's standalone but is otherwise less powerful, less general purpose, and the architecture to support the commercial/cloud offering causes some weird trade-offs when you are crafting test cases. As a url-blaster it's working fine for me, though. "modern developer focused" normally means elegant code like found on the (helpful link https://k6.io/blog/announcing-jmeter-to-k6-js-converter-tool https://k6.io/blog/announcing-jmeter-to-k6-js-converter-tool) const index = __ITER - ((__ITER / 2) | 0) * 2; switch (index) { case 0: