Write comprehensive tests for recurring todos

[dnrce]

Migrated from the original issue at https://www.assembla.com/spaces/tracks-tickets/tickets/1006

Recurring todos have a huge amount of frontend and model code. This needs a comprehensive test suite.

I'm working on cleaning up the model and views in a branch at http://github.com/epall/tracks/tree/recurring-cleanup, but I can't really ensure things are working without comprehensive tests. I already broke some functionality in the jQuery re-write, so this has all ready been a problem for us.

Originally reported by epall on March 3, 2010 at 16:42:14 (-0500) against version git-devel

[dnrce]

On March 3, 2010 at 16:48:14 (-0500), epall commented:

Related association with ticket #967 was added

[dnrce]

On March 3, 2010 at 04:10:46 (-0500), lrbalt commented:

I made lots of tests for the model. The front-end needs tests. I needed to get the cucumber working first to tackle the front-end.

[dnrce]

@lrbalt What do you think about moving this to 2.3? The recurring todos haven't been exercised much since the refactor. I would feel better if we had a good test suite prior to release.

[lrbalt]

I think we can close this one. With the last refactor, I have added a lot of tests. This should cover most use cases I think