Is it possible to run very long tests using selenium-side-runner

[Gaspode]

Hello,

I have a test scenario where I want to monitor a web page for several hours to verify regularily updated dynamic data.

For the test it is important, that it runs several hours in one session.

I have created a test with Selenium IDE, which logs into the web page with username/password and then gathers every 2 minutes the updated data for verification. This works in Selenium IDE.

Now I want to use selenium-side-runner to perform this test, but the test times out after300000ms = 5 minutes (error message see below).

Is it possible to increase this 300000ms timeout? If not, is there another possibility to use a session in a test scenario for several hours?

Thanks in advance.

$ selenium-side-runner ./VerifyData.side
info:    Running ./VerifyData.side
 FAIL  ./DefaultSuite.test.js (312.549s)
  Default Suite
    ✕ VerfyData (303613ms)

  ● Default Suite › VerfyData

    : Timeout - Async callback was not invoked within the 300000ms timeout specified by jest.setTimeout.Timeout - Async callback was not invoked within the 300000ms timeout specified by jest.setTimeout.Error:

       8 | jest.setTimeout(300000);
       9 | describe("Default Suite", () => {
    > 10 |   it("VerfyData", async () => {
         |   ^
      11 |     await tests["VerfyData"](driver, vars);
      12 |     expect(true).toBeTruthy();
      13 |   });

      at new Spec (../../../usr/local/lib/node_modules/selenium-side-runner/node_modules/jest-jasmine2/build/jasmine/Spec.js:116:22)
      at Suite.Object.<anonymous>.describe (DefaultSuite.test.js:10:3)

  ● Default Suite › VerfyData

    NoSuchSessionError: This driver instance does not have a valid session ID (did you call WebDriver.quit()?) and may no longer be used.

      at promise.finally (../../../usr/local/lib/node_modules/selenium-side-runner/node_modules/selenium-webdriver/lib/webdriver.js:729:38)
      at Object.thenFinally [as finally] (../../../usr/local/lib/node_modules/selenium-side-runner/node_modules/selenium-webdriver/lib/promise.js:124:12)

Test Suites: 1 failed, 1 total
Tests:       1 failed, 1 total
Snapshots:   0 total
Time:        313.207s
Ran all test suites.
$

[MEA Engg QA]

I have been trying out the selenium-side-runner as well. All my test scripts pass in the Selenium IDE, but 99% of them have been consistently failing in the  selenium-side-runner...have had to give up on the selenium-side-runner for now so I can focus my attention on other more priority items (since the scripts run fine in the IDE). Will hopefully find some time in the near future to dig into this further-I'll post my findings at that time. I know this is not very helpful... my apologies,

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/5239fe5c-2245-4997-84c4-98670cc667a2%40googlegroups.com.

[Gaspode]

Thank you for your response. So it seems that the side runner is only useful for small, easy test scenarios.

Meanwhile I'm experimenting with Java/JUnit. The test runs in Eclipse so far without the annoying timeout problems now.

However, currently I'm struggling to start the JUnit project from the command line...