Provide the capability to access browser information from test code

[inikulin]

Make browser information available in the test controller - add the t.browserInfo property.

There are various use cases for this feature, including conditional test actions and assertions:

test('My Test', async t => {
    if(t.browserInfo.name === 'IE')
        await t.click('#some-div');
});

[AlexanderMoskovkin]

It would be useful to add a concurrent worker number to the browserInfo (initially proposed in the #1778)

[dlangerenken]

are there any updates on this? any planned release date? @AndreyBelym

[AndreyBelym]

We have plans to implement this feature, but I can't give you an estimate yet. As a workaround, you can retrieve the navigator.userAgent property via a ClientFunction and then parse it using a third-party module (useragent):

import { ClientFunction } from 'testcafe';
import useragent from 'useragent';

fixture `get ua`
    .page `http://example.com`;

const getUA = ClientFunction(() => navigator.userAgent);

test('get ua', async t => {
    const ua = await getUA();

    console.log(useragent.parse(ua).family);
});

[lock]

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.