Factor common test code in to our own class about devday_website HOT 2 OPEN

Test for the apps should be as self-contained as possible, but I would not mind putting common constants into a baseapp/tests/test_utils.py.

I think it would be good if each app would provide default objects (like a User/Attendee in the attendee app, a Event in the event app, ...). Adding all these to a common test module in devday would lead to a dependency cycle and apps could no longer be used independently.

We have to think about whether we want to keep our apps reusable for others or whether we want to tighlty couple them to the devday project that is currently only used for aggregating the apps per the Django philosophy of independent apps. We already have some inter-app dependencies, but no cycles as far as I'm aware of.

from devday_website.

Maybe a couple of MixIns would be the right pattern.

Right now, it seems all apps except for the twitter stream are heavily entangled. Maybe a refactoring splitting out DevDayUser (after removing all the PII) as a simple EmailUser (or similar) would be nice, and combining Attendee, Event and everything in talk into its own conference app. I don't think we can usefully separate Attendee and Event from talk, or any model in there. The tests in each app make heavy use of the other apps, by necessity. But I'd be happy to be convinced of the opposite!

from devday_website.