Support parallel execution and fix issue with testcase stats not available

[ilangv]

This PR addresses below issues:

Parallel Execution:

Running codecept tests in parallel using run-multiple or run-workers creates a new launch for each child process. With this approach test config can implement bootstrapAll and teardownAll functions to create a launch and pass the launch id to child processes and env variable as shown below:

bootstrapAll: async () => {
       const launchId = await startLaunch(config)
       process.env.RP_LAUNCH_ID = launchId
    },
      teardownAll: async () => {
      await finishLaunch()
    }

Testcase widget issues

Reportportal widgets like Most time consuming tests , Flaky tests table do not render any data. This is because all the nested steps are published with hasStats=false . In-order to get test or BDD scenario level stats, reportportal expects a Test -> Step -> Nested Step structure. Updated the events to follow this structure.

[m3t4n]

@AmsterGet @peterngtr @DavertMik any chance of merging this guys?

[m3t4n]

thank you for the merge @peterngtr 🙏 is it possible to trigger the publish the new version to npm registry? so that the dependency can be picked up from codeceptjs plugin side....

[kobenguyent]

Hi @m3t4n i don't think i have any permissions to publish the new version of this repo. 😅

[m3t4n]

thank you @peterngtr for the prompt response.
in that case, @AmsterGet or @DavertMik maybe? 🙏

[AmsterGet]

After that changes the structure TEST -> STEP -> NESTED STEP (if applicable) will be presented.
Is it a good idea to avoid suites in the reporting structure? I suggest to use the following structure: SUITE -> TEST (if applicable) -> STEP -> NESTED STEP (if applicable), as from reportportal side we expect the top level suite as a container of tests.

[AmsterGet]

@m3t4n & @ilangv guys, could you please look at my notes, will it suit you?

[AmsterGet]

And what do you think about @DavertMik work on this for Codecept 3.0+
#3
May be better to implement it on the integration side to avoid additional work with bootstrapAll and teardownAll?

[m3t4n]

hi @AmsterGet thank you for your attention.
I agree with the suite > test > step > nestedStep structure. However, on the RP side it's represented as LaunchName > Suite > Test > Step > nestedStep and hence I believe @ilangv 's change (i might be wrong). Whereas I agree with you but maybe an improvement point on this is that after Suite the tests can be expanded instead of navigating to a new page (like nested steps do). Personally, I find it hard to reach the steps.

On the other hand @DavertMik's change seems to be the stable choice. Currently, it is not possible to properly display the parallel executions without any update on this plugin side. The suites are randomly placed under launches and this makes it really hard to see which ones are under which launch. Another option might be appending the suite name to launch id (thinking out loud).

@DavertMik: any chance on finalizing the PR? CodeceptJS is already 3.2.3.