blocks|key|1332893|text|测试这些东西的最好方法是将所需的功能从命令本身提取到独立的函数或类中。它有助于从“命令执行内容”中抽象出来，并在没有额外要求的情况下编写测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1332894|但是，如果您由于某种原因不能解耦逻辑表单命令，您可以使用call_command方法从任何代码中调用它，如下所示：|offset|length|1332895|from+django.core.management+import+call_command

call_command('my_command',+'foo',+bar='baz')|code-block|syntax|javascript|1332896|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.djangoproject.com/en/2.0/ref/django-admin/#running-management-commands-from-your-code^0|0|S|C|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@$D|U|E|V|1|W]]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

The best way to test such things - extract needed functionality from command itself to standalone function or class. It helps to abstract from "command execution stuff" and write test without additional requirements.

But if you by some reason cannot decouple logic form command you can call it from any code using <a href="https://docs.djangoproject.com/en/2.0/ref/django-admin/#running-management-commands-from-your-code" rel="noreferrer">call_command</a> method like this:

<pre><code>from django.core.management import call_command

call_command('my_command', 'foo', bar='baz')
</code></pre>

blocks|key|1548313|text|您可以通过执行以下操作来运行任务，而不是使用call_command技巧：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1548314|from+myapp.management.commands+import+my_management_task
cmd+=+my_management_task.Command()
opts+=+{}+#+kwargs+for+your+command+--+lets+you+override+stuff+for+testing...
cmd.handle_noargs(**opts)|code-block|syntax|javascript|1548315|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Rather than do the call_command trick, you can run your task by doing:

<pre><code>from myapp.management.commands import my_management_task
cmd = my_management_task.Command()
opts = {} # kwargs for your command -- lets you override stuff for testing...
cmd.handle_noargs(**opts)
</code></pre>

blocks|key|1548381|text|基于内特的回答，我有以下结论：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1548382|def+make_test_wrapper_for(command_module):
++++def+_run_cmd_with(*args):
++++++++"""Run+the+possibly_add_alert+command+with+the+supplied+arguments"""
++++++++cmd+=+command_module.Command()
++++++++(opts,+args)+=+OptionParser(option_list=cmd.option_list).parse_args(list(args))
++++++++cmd.handle(*args,+**vars(opts))
++++return+_run_cmd_with|code-block|syntax|javascript|1548383|用法：|1548384|from+myapp.management+import+mycommand
cmd_runner+=+make_test_wrapper_for(mycommand)
cmd_runner("foo",+"bar")|1548385|这里的优点是，如果您使用了其他选项和OptParse，这将为您理清思路。它不是很完美--它还不能通过管道输出--但它将使用测试数据库。然后，您可以测试数据库效果。|1548386|我敢肯定，在测试过程中使用Micheal模拟模块和重新连接stdout将意味着您可以从这项技术中获得更多--测试输出、退出条件等。|1548387|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Building on Nate's answer I have this:

<pre><code>def make_test_wrapper_for(command_module):
 def _run_cmd_with(*args):
 """Run the possibly_add_alert command with the supplied arguments"""
 cmd = command_module.Command()
 (opts, args) = OptionParser(option_list=cmd.option_list).parse_args(list(args))
 cmd.handle(*args, **vars(opts))
 return _run_cmd_with
</code></pre>

Usage:

<pre><code>from myapp.management import mycommand
cmd_runner = make_test_wrapper_for(mycommand)
cmd_runner("foo", "bar")
</code></pre>

The advantage here being that if you've used additional options and OptParse, this will sort the out for you. It isn't quite perfect - and it doesn't pipe outputs yet - but it will use the test database. You can then test for database effects.

I am sure use of Micheal Foords mock module and also rewiring stdout for the duration of a test would mean you could get some more out of this technique too - test the output, exit conditions etc.

blocks|key|1548435|text|以下代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1548436|from+django.core.management+import+call_command
call_command('collectstatic',+verbosity=3,+interactive=False)
call_command('migrate',+'myapp',+verbosity=3,+interactive=False)|code-block|syntax|javascript|1548437|...is等于在终端中键入的以下命令：|1548438|$+./manage.py+collectstatic+--noinput+-v+3
$+./manage.py+migrate+myapp+--noinput+-v+3|1548439|参见running+management+commands+from+django+docs。|offset|length|1548440|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.djangoproject.com/en/1.7/ref/django-admin/#running-management-commands-from-your-code^0|0|0|0|0|2|18|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|10|8|@]|9|@$M|11|N|12|1|13]]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

the following code:

<pre><code>from django.core.management import call_command
call_command('collectstatic', verbosity=3, interactive=False)
call_command('migrate', 'myapp', verbosity=3, interactive=False)
</code></pre>

...is equal to the following commands typed in terminal:

<pre><code>$ ./manage.py collectstatic --noinput -v 3
$ ./manage.py migrate myapp --noinput -v 3
</code></pre>

See <a href="https://docs.djangoproject.com/en/1.7/ref/django-admin/#running-management-commands-from-your-code">running management commands from django docs</a>.

blocks|key|1548489|text|Django+documentation+on+the+call_command没有提到必须将out重定向到sys.stdout。示例代码应为：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1548490|from+django.core.management+import+call_command
from+django.test+import+TestCase
from+django.utils.six+import+StringIO
import+sys

class+ClosepollTest(TestCase):
++++def+test_command_output(self):
++++++++out+=+StringIO()
++++++++sys.stdout+=+out
++++++++call_command('closepoll',+stdout=out)
++++++++self.assertIn('Expected+output',+out.getvalue())|code-block|syntax|javascript|1548491|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.djangoproject.com/en/1.10/topics/testing/tools/#management-commands^0|1B|3|1I|A|0|14|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|F|3|G|5|H|7|10|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

The <a href="https://docs.djangoproject.com/en/1.10/topics/testing/tools/#management-commands" rel="noreferrer">Django documentation on the call_command</a> fails to mention that <code>out</code> must be redirected to <code>sys.stdout</code>. The example code should read:

<pre><code>from django.core.management import call_command
from django.test import TestCase
from django.utils.six import StringIO
import sys

class ClosepollTest(TestCase):
 def test_command_output(self):
 out = StringIO()
 sys.stdout = out
 call_command('closepoll', stdout=out)
 self.assertIn('Expected output', out.getvalue())
</code></pre>

I want to write a unit test for a Django manage.py command that does a backend operation on a database table. How would I invoke the management command directly from code? 

I don't want to execute the command on the Operating System's shell from tests.py because I can't use the test environment set up using manage.py test (test database, test dummy email outbox, etc...)

How can I call a custom Django manage.py command directly from a test driver?

单元测试

数据库

Django

我想为在数据库表上执行后端操作的Django manage.py命令编写一个单元测试。如何直接从代码中调用管理命令？我不想从tests.py在操作系统外壳上执行命令，因为我不能使用使用manage.py测试设置的测试环境(测试数据库、测试虚拟电子邮件发件箱等)。

问如何直接从测试驱动程序调用自定义Django manage.py命令？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何直接从测试驱动程序调用自定义Django manage.py命令？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何直接从测试驱动程序调用自定义Django manage.py命令？
EN