Timeline for Unit testing in Django
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 21 at 5:08 | history | protected | gnat | ||
| Feb 20 at 18:44 | answer | added | Hamzah Haider | timeline score: 0 | |
| Aug 26, 2013 at 14:36 | comment | added | Chedy2149 | Checkout this : vimeo.com/43612849 and this : vimeo.com/15007792 | |
| Aug 26, 2013 at 14:07 | comment | added | acjay | 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. | |
| Aug 23, 2013 at 9:07 | comment | added | Chedy2149 | You have to abstract away the persistence layer | |
| Aug 22, 2013 at 15:58 | comment | added | acjay | That's helpful, but doesn't really address the issue of how to best test inherently stateful, ORM-heavy applications. | |
| Aug 21, 2013 at 9:10 | comment | added | Chedy2149 | 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. | |
| Jun 9, 2013 at 2:07 | history | tweeted | twitter.com/#!/StackProgrammer/status/343549924765466624 | ||
| Mar 4, 2013 at 21:24 | answer | added | acjay | timeline score: 6 | |
| Mar 4, 2013 at 15:07 | history | edited | acjay | CC BY-SA 3.0 |
Clarifications
|
| Mar 4, 2013 at 14:55 | history | edited | acjay | CC BY-SA 3.0 |
Clarifications
|
| Mar 4, 2013 at 5:57 | history | edited | acjay | CC BY-SA 3.0 |
added 286 characters in body
|
| Mar 4, 2013 at 5:50 | history | asked | acjay | CC BY-SA 3.0 |