Discuss anything related to web development but no technical support questions


Running tests in console

Post Reply

Post by klodoma »

Hi,

I am trying to run the tests in an automated way, but without success. I am trying to execute first the examples provided.
I am following this documentation:
https://www.bryntum.com/docs/siesta/#!/ ... automation

Tried it with both 4.1.4 and also with the latest trial version without success.

Any tips/documentation how to do it?
c:\devkit\siesta\4.1.4\bin>webdriver https://localhost/vendor/js/siesta/4.1.4/examples
[ERROR] Setup failed: Error: Can't create first page, runner: a Siesta.Launcher.Runner.WebDriverNodeJS, exception: SessionNotCreatedError: session not created exception
from unknown error: Runtime.executionContextCreated has invalid 'context': {"auxData":{"frameId":"33556.1","isDefault":true},"id":1,"name":"","origin":"://"}
  (Session info: chrome=59.0.3071.115)
  (Driver info: chromedriver=2.22.397933 (1cab651507b88dec79b2b2a22d1943c01833cc1b),platform=Windows NT 10.0.14393 x86_64)

c:\devkit\siesta\4.1.4\bin>webdriver https://localhost/vendor/js/siesta/4.1.4/tests
[ERROR] Setup failed: Error: Can't create first page, runner: a Siesta.Launcher.Runner.WebDriverNodeJS, exception: SessionNotCreatedError: session not created exception
from unknown error: Runtime.executionContextCreated has invalid 'context': {"auxData":{"frameId":"34952.1","isDefault":true},"id":1,"name":"","origin":"://"}
  (Session info: chrome=59.0.3071.115)
  (Driver info: chromedriver=2.22.397933 (1cab651507b88dec79b2b2a22d1943c01833cc1b),platform=Windows NT 10.0.14393 x86_64)

c:\devkit\siesta\4.1.4\bin>

Post by nickolay »

Hi,

You should stick with the latest version - it has newer versions of webdrivers, etc. Can you try with the Firefox? (--browser firefox)

Post by klodoma »

Well, it kind of worked with: 
webdriver https://localhost/vendor/js/siesta/4.1.4/tests --browser ie
What works better seems: 
phantomjs https://localhost/vendor/js/siesta/4.1.4/tests
But I am a bit confused why it doesn't work. As I see 4.1.4 comes with all the software required to run the tests...

I've tried it with the trial version as well, same issue. 
c:\devkit\siesta\siesta-4.2.2-trial\bin>webdriver https://localhost/vendor/js/siesta/4.2.2-trial/examples
Caught unhandled exception:  { [WebDriverError: unknown error: cannot get automation extension
from unknown error: page could not be found: chrome-extension://aapnijgdinlhnhlmodcfapnahmbfebeb/_generated_background_page.html
  (Session info: chrome=59.0.3071.115)
  (Driver info: chromedriver=2.24.417431 (9aea000394714d2fbb20850021f6204f2256b9cf),platform=Windows NT 10.0.14393 x86_64)] name: 'WebDriverError' } WebDriverError: unknown error: cannot get automation extension
from unknown error: page could not be found: chrome-extension://aapnijgdinlhnhlmodcfapnahmbfebeb/_generated_background_page.html
  (Session info: chrome=59.0.3071.115)
  (Driver info: chromedriver=2.24.417431 (9aea000394714d2fbb20850021f6204f2256b9cf),platform=Windows NT 10.0.14393 x86_64)
    at WebDriverError (c:\devkit\siesta\siesta-4.2.2-trial\node_modules\selenium-webdriver\lib\error.js:27:10)
    at Object.checkLegacyResponse (c:\devkit\siesta\siesta-4.2.2-trial\node_modules\selenium-webdriver\lib\error.js:639:15)
    at parseHttpResponse (c:\devkit\siesta\siesta-4.2.2-trial\node_modules\selenium-webdriver\http\index.js:545:13)
    at c:\devkit\siesta\siesta-4.2.2-trial\node_modules\selenium-webdriver\http\index.js:479:11
    at ManagedPromise.invokeCallback_ (c:\devkit\siesta\siesta-4.2.2-trial\node_modules\selenium-webdriver\lib\promise.js:1379:14)
    at TaskQueue.execute_ (c:\devkit\siesta\siesta-4.2.2-trial\node_modules\selenium-webdriver\lib\promise.js:2913:14)
    at TaskQueue.executeNext_ (c:\devkit\siesta\siesta-4.2.2-trial\node_modules\selenium-webdriver\lib\promise.js:2896:21)
    at c:\devkit\siesta\siesta-4.2.2-trial\node_modules\selenium-webdriver\lib\promise.js:2820:25
    at c:\devkit\siesta\siesta-4.2.2-trial\node_modules\selenium-webdriver\lib\promise.js:639:7
    at process._tickCallback (node.js:369:9)
From: Task: WebDriver.manage().window().setSize(1279, 1023)
    at Driver.schedule (c:\devkit\siesta\siesta-4.2.2-trial\node_modules\selenium-webdriver\lib\webdriver.js:377:17)
    at Window.setSize (c:\devkit\siesta\siesta-4.2.2-trial\node_modules\selenium-webdriver\lib\webdriver.js:1402:25)
    at __dirname.undefined.Class.methods.open (c:\devkit\siesta\siesta-4.2.2-trial\bin\siesta-launcher-all.js:342:452)
    at b [as open] (c:\devkit\siesta\siesta-4.2.2-trial\bin\siesta-launcher-all.js:27:357)
    at Class.methods.openHarness (c:\devkit\siesta\siesta-4.2.2-trial\bin\siesta-launcher-all.js:229:409)
    at b [as openHarness] (c:\devkit\siesta\siesta-4.2.2-trial\bin\siesta-launcher-all.js:27:357)
    at c:\devkit\siesta\siesta-4.2.2-trial\bin\siesta-launcher-all.js:279:100
    at c:\devkit\siesta\siesta-4.2.2-trial\bin\siesta-launcher-all.js:234:161
    at c:\devkit\siesta\siesta-4.2.2-trial\bin\siesta-launcher-all.js:350:49
    at process._tickCallback (node.js:369:9)
What is the best-practice in order to execute the tests in console?

Post by nickolay »

The best practice is to use "bin/webdriver".

Probably the chrome webdriver is outdated. Chrome webdrivers supports only certain range of Chrome versions. Try to download the latest version: https://chromedriver.storage.googleapis ... path=2.30/ and put the executable in the 'siesta/bin/binary/chromedriver/windows'

Post by klodoma »

nickolay wrote:The best practice is to use "bin/webdriver".

Probably the chrome webdriver is outdated. Chrome webdrivers supports only certain range of Chrome versions. Try to download the latest version: https://chromedriver.storage.googleapis ... path=2.30/ and put the executable in the 'siesta/bin/binary/chromedriver/windows'
Thanks for the feedback! It works!
I'll continue from here the digging.
Post Reply