#23663: Commands classes are not properly testable due to their initialization
in
execute() method!
-------------------------------------+-------------------------------------
Reporter: daveoncode | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.7
Component: Core (Management | Resolution:
commands) | Triage Stage: Ready for
Severity: Normal | checkin
Keywords: test, tdd, | Needs documentation: 0
management, commands | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by claudep):
Loïc, thanks, that's easier to review!
Traditionally, we have favored two interfaces to management commands: the
command line and `call_command`. I understand the need for fine-grained
unit testing, I just hope this won't entice users to run commands in new
"imaginary" ways... Whatever, go for it!
--
Ticket URL: <https://code.djangoproject.com/ticket/23663#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.009a008af1c090fa38af33cd058568b7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
