Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 1
    You should write unit tests first from now one this helps you spot testability problems in your design before the actual production code is written. Commented Aug 21, 2013 at 9:10
  • 3
    That's helpful, but doesn't really address the issue of how to best test inherently stateful, ORM-heavy applications. Commented Aug 22, 2013 at 15:58
  • 1
    You have to abstract away the persistence layer Commented Aug 23, 2013 at 9:07
  • 1
    Sounds great hypothetically, but when it comes to project maintenance, I think there's a non trivial cost to inserting a custom-made persistence layer between the business logic and the extremely well-documented Django ORM. Suddenly, the classes become packed with a bunch of tiny intermediary methods that themselves need to be refactored over time. But perhaps this is justified in places where testability is critical. Commented Aug 26, 2013 at 14:07
  • Checkout this : vimeo.com/43612849 and this : vimeo.com/15007792 Commented Aug 26, 2013 at 14:36