On Fri, Nov 30, 2018, 1:03 PM Adam Johnson <m...@adamj.eu wrote: > Tobias - using database updates isn't always viable. Also the system under > test might need to take in the model instance, mutate it and execute its > own save(), and then there's no way of rolling that back if the object > wasn't deepcopy'd >
Fair enough, but for those cases, one could just as easily deepcopy the object in the test itself. Again, it's more explicit, gives the developer control over exactly what they want to happen, and makes failures more obvious. I suppose if the API allowed one to mix and match approaches for different tests and model objects (like Simon's testdata app does right now), that would work, too. Tobias -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to firstname.lastname@example.org. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMGFDKQPcL_xEY5J-jGXj5BfzD2fCO8MsEgZoH9cmx4OMAqDHw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.