In a multi-step Transaction Test, there may be situations in which the first request in a step gets grouped with the previous step when viewing test results in our analysis tools. For example, Step 2 of a Transaction Script might begin with a clickAndWait() command, but later, when viewing the results, this request is shown as part of Step 1.
This can occur when the first request in a step does not end up being considered the root URL of that step. The root URL is determined by identifying the first request that loaded an HTML or text file, or, if none is found, the first request exceeding 100 bytes. If a clickAndWait() command does not load an HTML of text file (perhaps the clicked element runs a script or opens some other file type), then a subsequent command in the same step might end up being considered the Root URL. In such a situation, the first command gets grouped with the previous step. To prevent this, consider dividing these actions into separate steps (i.e. let the clickAndWait() occupy its own step.) This will reduce the chance of child requests inadvertently being selected as the root URL.
Note that this applies to Transaction Test type, but our Playwright and Puppeteer tests incorporate advanced logic to mitigate this issue.