Closed heiko-hardt closed 11 years ago
Thinking it may be a port or host problem i tried it within a local environment.
Started within IntelliJ looks like:
Kind regards Heiko
Problem found: It would be necessary to setup the right proxy (at the same host). Thanks for this tool ;-)
Kind regards Heiko
Hello Heiko, first, the timeouts in Chrome usually occur, when the chrome tab that is connected to testacular is not focused (i.e. you have multiple tabs open and one of them, but not the focued one, is connected to testacular).
Just updated to grunt 0.4.
To start testacular together with a server proxy, just do
./node_modules/.bin/grunt dev
, which should automatically start a connect server, set up the proxy and then start testacular.
Tobias
Hi Tobias,
i cloned your current master in my development-environment (Ubuntu 12.04) with current version of nodejs (v.0.8.19) and Testacular (v.0.4.0)
After starting the Tests (testacular start testacular.conf.js) the following errors occured:
Chrome (v.25.0.1364):![testacular](https://f.cloud.github.com/assets/2315719/188113/a24b3566-7dc4-11e2-8c17-4c9e939a1ac5.gif)
Firefox (v.18.0.2)![testacular-ff](https://f.cloud.github.com/assets/2315719/188115/cdcebf50-7dc4-11e2-8218-daec14b7aeb5.gif)
This project looks verry promising. Would be great if you can help me.
Kind regards Heiko