I have been looking for a decent guide that covers testing in a solid,
thorough way - there are lots of fragmented pieces that cover
bits-and-pieces of what is needed for tests but not all the cases with a
start-to-end comprehensive approach for everything ("Obey the Testing Goat"
comes closest). I need to cover cases for the admin as well - with actions
and intermediate forms, some with file uploads. In those case, I assume (?)
that the action logic is equivalent to a view.The Django docs show examples as well but I have not see where they cover everything. This may all seem like trivial knowledge to people who have already done all this, but I struggle to see the full picture of what a whole test suite should look like, and what the details of all the tests would be. On 3 September 2017 at 09:07, James Schneider <jrschneide...@gmail.com> wrote: > > > On Sep 1, 2017 3:00 PM, "Derek" <gamesb...@gmail.com> wrote: > > Thanks Melvyn > > I already have tests for the processing of data when it has been uploaded > - which is actually the critical issue for the application. The "view" is > just really a thin wrapper around the two steps : form display & upload and > then the file processing itself : and those are the parts I need tests for. > > > I'd have to agree with Melvin. You should be testing your view code as > well, which would incorporate the tests for the form class. If the view is > broken out interacts badly with the form for whatever reason, the fact that > the form works on it's own is irrelevant. Plus it isn't that hard to add > in. > > I would test the view even if it is boiler plate code shared by all of > your forms, because you need to be certain that the combination of the view > and form in question work together. > > -James > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/django-users/GUStj-3rzD8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-users/CA%2Be%2BciUgbWkGFVrqBWKAYdifP% > 2BjTchZwHR0-GfPKGcTjP%3DBjfA%40mail.gmail.com > <https://groups.google.com/d/msgid/django-users/CA%2Be%2BciUgbWkGFVrqBWKAYdifP%2BjTchZwHR0-GfPKGcTjP%3DBjfA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAF1Wu3MqT1V85StnBg8D_eqrcjH%2BebjvDW41xg_V1t%3D9%3DeUk-Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
