nickolay wrote:Siesta is a web app as well it does not know anything about your backend.
What it does: 1) creates an empty iframe 2) loads the files from "preload" in the iframe. 3) launch the tests
You need to include the same files your include in your application normally.
Ok, i knew this, but this provider is put in between the front and the back, and it indicates how they comunicate, so i have to configure it on the enviroment in order to Siesta to be able to "hit" some button and that button fire a request to the server. In order to be able to get to the server, this wrapper must be configured.
Not following you. You mean your app needs some additional executable file to be running in background? Then you just launch that file when opening a test suite.
nickolay wrote:Not following you. You mean your app needs some additional executable file to be running in background? Then you just launch that file when opening a test suite.
One question that raised from your comment
If i have a web app, with front end and back end, i should run the back end (ie local enviroment), and then launch the tests right?
About the configuration, i found out that this wrapper generates the json config for the provider, i ve captured it and i ll test with that config.... as soon i have an outcome i ll post it here.
What worries me, is that there might be more "magic" that this component does, that generates any other ext.js code that must be included :/
When i run the test, on the dom panel it shows up the login page correctly, and the labels (even the buttons) are displayed correctly, but arent found by the component query.
You should not use waitForXtype with Ext JS 3, since it doesn't have Ext.ComponentQuery (which is the error you're seeing). Your tests should rely on pure CSS for Ext JS version < 4.