Quickly testing deep-linked screens...tips and tricks?

[subimage]

Hey guys,

Fairly new to Sencha here, and developing an app with routes.

It was pretty quick going when doing the "high level" screens, but I'm finding my workflow slowing down more and more the deeper into the app I get.

I'm working on the mobile portion to my SaaS app (http://cashboardapp.com), and I'm finding it difficult to quickly iterate on deeply linked pages.

For instance, if I'm linking to something like /projects/:id/filterTasks, I expect that the 'Projects' store has been loaded when tapping on /projects...so when I access /projects/:id it sees it doesn't have the project, and redirects back to /projects.

The end result is I end up having to manually walk down each path to test deeply linked screens, which is becoming a time sink.

Just not sure I'm doing this the best way possible.

Help?

[subimage]

I am finding the 'before (http://docs.sencha.com/touch/2-0/#!/api/Ext.app.Controller-cfg-before)' filter on routes a little helpful, as I'm able to load stores and pre-populate things - but it still would be nice if there were a best practices manual on this kind of stuff. I feel that's really missing with Sencha when compared to Rails, for example.

[stefankendall]

What's your test tool of choice? If you're using cucumber (http://cukes.info), you can use annotations to specify setup that runs before every test.

That could be a way to go about things.

[subimage]

Right now I'm not testing this Sencha app with anything automated (bad bad. I've read a lot on the subject, but haven't seen a definitive tool I like.

I'm familiar with Jasmine/Rspec/Selenium/Ruby Test::Unit...

Siesta looks ok...but I was trying to fit in something I already know. What do you suggest as a setup?