running parallel tests in browserstack

Get help with testing, discuss unit testing strategies etc.
User avatar
jayaprakasha
Posts: 9
Joined: Thu Apr 27, 2017 1:38 pm

Re: running parallel tests in browserstack

Post by jayaprakasha » Tue Jul 18, 2017 7:34 am

Its the latest version, 4.3.0 standard.

User avatar
nickolay
Core Developer
Core Developer
Posts: 3357
Joined: Mon May 16, 2011 10:48 am

Re: running parallel tests in browserstack

Post by nickolay » Tue Jul 18, 2017 9:36 am

Ok, can you try launching siesta's own examples in BS in parallel, with small --chunk-size:

bin/webdriver http://localhost/siesta/examples/index.html --max-workers 5 --chunk-size 3 --browserstack....
We offer training in both Ext JS and our products, read more here.
Read the API documentation

User avatar
nayila
Posts: 4
Joined: Thu Apr 12, 2018 10:33 pm

Re: running parallel tests in browserstack

Post by nayila » Wed Jul 24, 2019 8:44 pm

I have a similar issue while running my siesta test suite in Jenkin. we have a below error popping up randomly every time when we run the test. It is not reproducible in the local though. Do you know why?
<Exception from launcher>
While running big script: return (function (args) {
var me = Siesta.my.activeHarness

return me ? me[ 'launchAutomatedTests' ].apply(me, args)
Exception: TypeError: Cannot set property 'automationElementId' of undefined
TypeError: Cannot set property 'automationElementId' of undefined
at Object.<anonymous> (http://elsevier.qa.ordersetsmanager.com/application/resources/siesta/siesta-all.js:46993:45)
at Object.map (http://elsevier.qa.ordersetsmanager.com/application/resources/siesta/siesta-all.js:67:28)
at Object.launchAutomatedTests (http://elsevier.qa.ordersetsmanager.com/application/resources/siesta/siesta-all.js:46990:43)
at Object.override [as launchAutomatedTests] (http://elsevier.qa.ordersetsmanager.com/application/resources/siesta/siesta-all.js:817:32)
at eval (eval at execute (http://elsevier.qa.ordersetsmanager.com/application/resources/siesta/siesta-all.js:46370:17), <anonymous>:4:58)
at eval (eval at execute (http://elsevier.qa.ordersetsmanager.com/application/resources/siesta/siesta-all.js:46370:17), <anonymous>:5:15)
at eval (eval at execute (http://elsevier.qa.ordersetsmanager.com/application/resources/siesta/siesta-all.js:46370:17), <anonymous>:5:2868)
at eval (<anonymous>)
at Object.execute (http://elsevier.qa.ordersetsmanager.com/application/resources/siesta/siesta-all.js:46370:17)
at Object.override [as execute] (http://elsevier.qa.ordersetsmanager.com/application/resources/siesta/siesta-all.js:817:32)
</Exception from launcher>
harness url: http://elsevier.qa.ordersetsmanager.com/application/smoke-test-harness_orderSets_Elsevier.html?selenium=true
<Exception from launcher>
While running big script: return (function (args) {
var me = Siesta.my.activeHarness

return me ? me[ 'launchAutomatedTests' ].apply(me, args)
Exception: TypeError: Cannot set property 'automationElementId' of undefined

User avatar
nickolay
Core Developer
Core Developer
Posts: 3357
Joined: Mon May 16, 2011 10:48 am

Re: running parallel tests in browserstack

Post by nickolay » Fri Jul 26, 2019 8:59 am

Hm.. Please check your test suite for the duplicated test urls? Currenly the urls of all test scripts should be unique, if you want to re-use the same script in several tests you can append some query parameter, like : `sometest.t.js?version=1`
We offer training in both Ext JS and our products, read more here.
Read the API documentation

Post Reply