(I've made this comment before on CasperJS/PhantomJS postings, but I've never gotten an answer.)<p>I love the idea, but I'm a bit worried that it's just webkit. Aren't all the other browsers important too? This is why I feel that Selenium still has a place, even though I agree that Casper is easier to use. Perhaps browserling is an appropriate answer?<p>I don't mean to disrespect CasperJS <i>or</i> PhantomJS, they're certainly wonderful tools, and any final automated functional test like this is infinitely better than none, but it's bad enough that people are developing for Webkit, do we really have to make it explicit by only testing on Webkit? ;)
If you're looking to use Casper.js on a Django project, have a look at the small wrapper around LiveServerTestCase we wrote to make it easier to call Casper, pass params (like server url), and the like: <a href="https://github.com/dobarkod/django-casper" rel="nofollow">https://github.com/dobarkod/django-casper</a>
Casper.js (and Phantom, for that matter) has been pretty buggy and difficult to work with for me. Had better luck with Selenium, which makes me unhappy because I'd rather use something more code oriented.