Provide a way to connect a role (or role set) to a concurrent connection

What is your Scenario?

We have a complex multi-tenant SaaS product. And we test our product using a server. We need to make sure that every concurrent browser test is working in a separate tenant (separate Role making sure it’s not used twice in the same time) to avoid errors.

What are you suggesting?

Maybe provide a current thread/browser index through t.testRun.browserConnection.index? Or update t.testRun.browserConnection.id that it would start with {index}_ prefix?

Basically we need an ability to select Role1, Role2, ..., RoleX based on some condition provided from the test runned, making sure it’s not overlaps

What alternatives have you considered?

No response

Additional context

Checked this one https://github.com/DevExpress/testcafe/issues/5356

Playwright has workerInfo.workerIndex https://playwright.dev/docs/next/test-fixtures#worker-scoped-fixtures

[syabro]

Hmmm. If I get correct and you’re saying that ids will be permanent for all threads during all tests then it definitely could work. Thank you.

[AlexKamaev]

You can use the following code to map browser connection ids to the indices:

import { getBrowserIndex } from "./browser-indices";

fixture `f`
    .page `http://example.com`

for (let i = 0; i < 100; i++) {
    test(`test${i}`, async t => {
        console.log('browserIndex: ' + getBrowserIndex(t.testRun.browserConnection.id));
    });
}

const BROWSER_INDICES = {};

export function getBrowserIndex (id) {
    if (!BROWSER_INDICES[id])
        BROWSER_INDICES[id] = Object.keys(BROWSER_INDICES).length;

    return BROWSER_INDICES[id];
}