Issue with BrowserStack when using browser.reloadSession() - there is always an extra test being executed #13799

jadersonts · 2024-10-24T18:00:24Z

jadersonts
Oct 24, 2024

Description

In order to report every test (therefore: it() block) in BrowserStack, I tried to use the following snippet in our wdio.conf file:

    afterTest: async function(test, context, { error, result, duration, passed, retries }) {
         await browser.reloadSession()
    }

Using as example a suite called "Login" (therefore: describe() block), having 2 tests: Login as Coach and Login as Player, we have the results reported, separated and properly recorded in BrowserStack.

However, out of nowhere a 3rd test starts to run in BrowserStack, and it seems to start and end once the results from previous (and official tests) got updated. You can watch below:

wdio.mov

I would like to know how to prevent this "extra test". Is there anything missing here? Or BrowserStack known issue?

Appreciate your help!

Answered by jadersonts

Oct 25, 2024

I created a solution - in wdio.conf file I added a countItBlocksInFile that will count how many it blocks we have in a spec file

const countItBlocksInFile = (filePath) => {
    const content = fs.readFileSync(filePath, 'utf-8');
    const matches = content.match(/it\(\s*['"`](.*?)['"`]\s*,/g);
    return matches ? matches.length : 0;
}

Then I use it in beforeSuite hook. At the same time, I added a counter++ in beforeTest hook. So in order to not call reloadSession after the last test:

afterTest: async function() {
    if(runCounter < numberOfTests){
        await browser.reloadSession()
    }
}

Reports are working fine in BrowserStack

View full answer

christian-bromann · 2024-10-24T18:45:47Z

christian-bromann
Oct 24, 2024
Maintainer

I would like to know how to prevent this "extra test". Is there anything missing here? Or BrowserStack known issue?

I would not recommend to call reloadSession after every test since re-creating a new browser session takes very long. You can avoid the extra session by not calling reloadSession after the last test did run.

2 replies

jadersonts Oct 24, 2024
Author

I understand reloadSession will take longer but client wants less and less number of spec files, and create the reports from each it block. Your suggestion by not calling reloadSession after the last test did run sounds pretty good. However I am struggling to find a way to check beforehand what is the "last test". For example, I expected to work around suite object in beforeSuite hook, but there is no useful key/value. Other than that, creating a countItBlocks.js, but it seems too radical. Do you have any suggestion in between? Thanks for the support!

christian-bromann Oct 24, 2024
Maintainer

Unfortunately I don't.

jadersonts · 2024-10-25T01:30:50Z

jadersonts
Oct 25, 2024
Author

I created a solution - in wdio.conf file I added a countItBlocksInFile that will count how many it blocks we have in a spec file

const countItBlocksInFile = (filePath) => {
    const content = fs.readFileSync(filePath, 'utf-8');
    const matches = content.match(/it\(\s*['"`](.*?)['"`]\s*,/g);
    return matches ? matches.length : 0;
}

Then I use it in beforeSuite hook. At the same time, I added a counter++ in beforeTest hook. So in order to not call reloadSession after the last test:

afterTest: async function() {
    if(runCounter < numberOfTests){
        await browser.reloadSession()
    }
}

Reports are working fine in BrowserStack

1 reply

DhanalakshmiRamasamy Sep 4, 2025

@jadersonts - Are you not encountering Session error when you are using Cloud services ? Its because the session reload takes time and the cloud runners are still referring to older session meanwhile.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Issue with BrowserStack when using browser.reloadSession() - there is always an extra test being executed #13799

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 3 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

Issue with BrowserStack when using browser.reloadSession() - there is always an extra test being executed #13799

Uh oh!

jadersonts Oct 24, 2024

Description

Replies: 2 comments · 3 replies

Uh oh!

christian-bromann Oct 24, 2024 Maintainer

Uh oh!

jadersonts Oct 24, 2024 Author

Uh oh!

christian-bromann Oct 24, 2024 Maintainer

Uh oh!

jadersonts Oct 25, 2024 Author

Uh oh!

DhanalakshmiRamasamy Sep 4, 2025

jadersonts
Oct 24, 2024

Replies: 2 comments 3 replies

christian-bromann
Oct 24, 2024
Maintainer

jadersonts Oct 24, 2024
Author

christian-bromann Oct 24, 2024
Maintainer

jadersonts
Oct 25, 2024
Author