feat: [ISSUE-624] Send worker name as part of step execution.

[arvindkumarc]

This helps to have more control over the workers and take better data slicing even with single iteration and parallel running loads.

Consider the following example:

export const settings: TestSettings = {
  loopCount: 1,

  stages: [
    {
      duration: `2m`,
      target: 5,
    },
  ],
};

We expect 5 parallel workers being launched, and there is no unique way to identify these workers.
The TestData circular() or shuffle will not help here since they work based on the loopCount. shuffle to an extent but with duplicates.

With this approach, we will be able to slice the data based on the launched workers and control which to be picked.

More details in #624

Thank you!

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
element-docs	❌ Failed (Inspect)			Jul 21, 2023 0:48am

[vipulsharma144]

@arvindkumarc Thanks for the fix However i tried installing via your fork and it seems to give me undefined for reporter.worker.name with --mu . Can you provide some steps to follow please .
Thanks