Marco Emrich wrote:If your tests/specs takes more than about two hours to run, you really have other problems In this case I would invest time in optimizing them first.
Two hours seems very long - unless you're doing full blown end-to-end testing, and even then I'd make that a scheduled event that runs when nobody's around and delivers a report after it's done.
For developers, I target five minutes for the suite so only unit tests (no network, no file handling, no db access, etc) are allowed, Otherwise it takes too long and they won't run the tests. Which reminds me, some testing frameworks allow the author to tag a test and then just run the tests with that tag - so you can have tests tagged with labels like '@Fast', or '@Slow-DB', so the test runner can run a subset of the test suite then (if those tests passed) run the rest of the suite. Does Jasmine support that? If not, are you aware of another framework that might?
Marco Emrich wrote:Do you do GUI tests with different browsers/emulators - for your Sencha Touch stuff?
The app I'm writing with Sencha is intended to be wrapped as a mobile app and run on a smartphone, so there's only one browser I have to support - though I have tested it out (manually) on Chrome as well.
Burk