Hello again. CI adapted tests are getting a lot of timeout errors. Normally it takes 761ms to load contents when running the application on web browser. But it takes to much longer when Selenium web driver runs the application and tests are keep failing through this error below;
Error happened before the test started
Waiting for Ext.onReady took too long - probably some dependency could not be loaded.
Check the `Net` tab in Firebug and the `loaderPath` config
I've already used timeout, isReadyTimeout configs as you'll notice on first method that runs on tests. But probably not enough or correct to avoid from this error. Is there any better approach to run test cases?
describe('Cloud App: Monkey Test', function (t) {
t.it('Should Login to App and doing some clicks on dashboard', function (t) {
t.chain(
{
login: t.next
}
)
});
I've notated isReadyTimeout on harness.configure as you mentioned and i did not face with any error based on "Timeout" for a while but now it started again!
As well somehow test suite gives error for several test cases spontaneously with this error below;
TypeError: a.pseudos[d] is not a function
at line 6, character 565881, of https://www.myapp/classic/app.js
When I ran test suit on local environment mostly passes whole cases. And when I ran through commands on CI server mostly throw this error but always for a different test case. Could you please give any advice for CI test cases;
Please enable "stop on exception" mode in chrome debugger and provide more information about the exception ("TypeError: a.pseudos[d] is not a function") you experience. You can observe the values of variables in the debugger.