Get help with testing, discuss unit testing strategies etc.


Post by Hakim »

Hi all,
I upgraded siesta version to 5.5.1 yesterday, but I am having issues with test launchers such as webdriver and puppeteer.

  1. webdriver:

    siesta-5.5.1-standard/bin/webdriver http://localhost:1841/myApp/test/Siesta/test.html --include GridUT.t.js

    exits immediately to the next line without any message. Tests are not executed

  2. puppeteer :

    siesta-5.5.1-standard/bin/puppeteer http://localhost:1841/myApp/test/Siesta/test.html --include GridUT.t.js

    Here is the SS of the error
    Image


Post by nickolay »

Hi,

The webdriver may fail due to version of Chrome being greater than version of chrome driver bundled with Siesta. It should show this error message in this case however:

nickolay@frontier:~/workspace/Bryntum/siesta$ bin/webdriver lh/siesta/examples/browser
[ERROR] Setup failed: Error: Can't create first page, runner: a Siesta.Launcher.Runner.WebDriverNodeJS, exception: SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 84

In such case you can download a matching ChromeDriver version from here: https://chromedriver.chromium.org/downloads
and place the binary file into /siesta/bin/binary/chromedriver/__you_arch__

As about Puppeteer - this is very strange, it works fine on my machine.

Perhaps you've ran npm install after unpacking Siesta archive? No need to do that.


Post by Hakim »

Okay, thanks for the reply.
I had to remove node from my machine completely before it works
About Webdriver

I downloaded the binary and replaced the old driver but I had to realize that if my current version of chrome is greater or less than 84, webdriver won't still work on chrome. Here an extra work is needed to downgrade your chrome version


Post by pmiklashevich »

Is your issue solved?

Pavlo Miklashevych
Sr. Frontend Developer


Post by Hakim »

Hi pmiklashevich,
Not entirely.
Now it is about the coverage report:
with this cmd :

siesta-5.5.1-standard/bin/webdriver http://localhost:1841/myApp/test/Siesta/test.html --include UT --coverage-report-format=HTML --coverage-report-dir /myApp/test/Siesta/report201014

,
I get this result
Image
in which there are no percentages.
Note: just want to remind you the current version of extjs being used in case of version compatibility:

ext-7.3.0

. Not sure about what's going on yet
Do I need an extra flag in the cmd above?
thanks


Post by nickolay »

I had to remove node from my machine completely before it works

This is strange - Siesta does not use the nodejs from the OS, it uses the nodejs which is bundled into the package.

I downloaded the binary and replaced the old driver but I had to realize that if my current version of chrome is greater or less than 84, webdriver won't still work on chrome. Here an extra work is needed to downgrade your chrome version

Well, yes, the versions of Chrome and ChromeDriver need to match, thats how it works. In general you usually need to download new ChromeDriver binary after every Chrome upgrade.


Post by nickolay »

About the coverage report - did it work in 5.5.0? Perhaps you need to include the files to the coverage using --nyc.include command line option. See this guide for details: https://www.bryntum.com/docs/siesta/#!/guide/code_coverage


Post by Hakim »

yes, it worked in 5.5.0. I will try with

--nyc.include

and see what happens


Post by fabio.policeno »

Great Hakim, please keep us updated if it works for you. Thanks!

Fabio Jr. Policeno
Core Developer


Post by Hakim »

Hi,
unfortunately, it did not work out


Post Reply