blocks|key|2286495|text|我的建议是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2286496|使用创建DirectoryTestCase(unittest.TestCase)|offset|length|style|CODE|2286497|2286498|安装程序:+i)删除(未跟踪的)目录(例如，tests/下的_tests+)+ii)创建空目录并将文件复制(测试)到该目录。|ordered-list-item|2286499|删除目录|2286500|2286501|其次，在该测试用例下创建测试。您可以测试移动到同一目录(重命名)，移动到一个新目录(在test目录下，如果它不存在或失败，是否应该创建？)在现有目录的封装下移动符号链接等。|2286502|如果您希望测试并行运行，请为目录指定一个唯一(随机但有效)的名称。|2286503|示例代码：|2286504|import+unittest
import+shutil
import+os
import+string
import+random


class+DirectoryTestCase(unittest.TestCase):
++++test_files+=+['file.txt']

++++def+setUp(self)+->+None:
++++++++unique_string+=+''.join(random.choices(string.digits,+k=10))

++++++++self.path+=+os.path.join(os.path.dirname(__file__),+'_temp'+%2B+unique_string)

++++++++shutil.rmtree(self.path,+ignore_errors=True)

++++++++os.makedirs(self.path,+exist_ok=True)

++++++++for+file+in+self.test_files:
++++++++++++shutil.copy(file,+self.path)

++++def+tearDown(self)+->+None:
++++++++shutil.rmtree(self.path,+ignore_errors=True)

++++def+test_basic(self):
++++++++#+validate+the+existence+of+the+file,+not+an+actual+test.
++++++++self.assertTrue(os.path.exists(os.path.join(self.path,+'file.txt')))|code-block|syntax|javascript|2286505|entityMap^0|0|4|10|0|0|M|6|U|6|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@$D|13|E|14|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|16|8|@$D|17|E|18|F|G]|$D|19|E|1A|F|G]]|9|@]|A|$]]|$1|L|3|M|5|K|7|1B|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1D|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1E|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1F|8|@]|9|@]|A|$]]|$1|U|3|V|5|W|7|1G|8|@]|9|@]|A|$X|Y]]|$1|Z|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|10|$]]

My recommendation would be 

create a <code>DirectoryTestCase(unittest.TestCase)</code> with

<ol>
<li>a setup that i) removes a (non-tracked) directory if it exists (e.g. <code>_tests</code> under <code>tests/</code>) ii) creates an empty directory and iii) copies (test) files to it.</li>
<li>a teardown that removes the directory</li>
</ol>

Second, create the tests under that test case. You can test moving to same directory (rename), to a new directory (under the test directory, should it create if it does not exist or fail?) move a symlink, etc., all under the encapsulation of the existing directory. 

If you want tests to run in parallel, give the directory a unique (random but valid) name.

Example code:

<pre><code>import unittest
import shutil
import os
import string
import random


class DirectoryTestCase(unittest.TestCase):
 test_files = ['file.txt']

 def setUp(self) -&gt; None:
 unique_string = ''.join(random.choices(string.digits, k=10))

 self.path = os.path.join(os.path.dirname(__file__), '_temp' + unique_string)

 shutil.rmtree(self.path, ignore_errors=True)

 os.makedirs(self.path, exist_ok=True)

 for file in self.test_files:
 shutil.copy(file, self.path)

 def tearDown(self) -&gt; None:
 shutil.rmtree(self.path, ignore_errors=True)

 def test_basic(self):
 # validate the existence of the file, not an actual test.
 self.assertTrue(os.path.exists(os.path.join(self.path, 'file.txt')))
</code></pre>

blocks|key|2499122|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2499123|由于在python中模拟操作系统模块是一件很困难的事情，你可以忽略编写单元测试|ordered-list-item|2499124|，但是单元测试意味着要用一些可能的场景来验证你的单个方法，所以如果你认为必须一直验证的话。那么单元测试是必须的。|2499125|2499126|entityMap^0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|I|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|J|7|@]|8|@]|9|$]]|$1|D|3|E|4|C|6|K|7|@]|8|@]|9|$]]|$1|F|3|-4|4|5|6|L|7|@]|8|@]|9|$]]|$1|G|3|-4|4|5|6|M|7|@]|8|@]|9|$]]]|H|$]]

<ol>
<li>since it is a difficulty to mock OS module in python, you can ignore to write unitest</li>
<li>But unit test means to validate your single method with some possible scenarios, so if you think that must validate all time. then a unit test is a must.</li>
</ol>

blocks|key|2499148|text|不需要测试os.rename，但是您的代码需要测试。对于您的特定情况，最简单的方法是为os.rename打补丁|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2499149|from+unittest.mock+import+patch

def+test_move_files():
++++files+=+['a.txt',+'b.txt']
++++path+=+'old'
++++expected+=+[(('a.txt',+'old/a.txt'),),
++++++++++++++++(('b.txt',+'old/b.txt'),)]
++++with+patch('os.rename')+as+rename:
++++++++move_files_to(files,+path)
++++++++assert+rename.call_args_list+==+expected|code-block|syntax|javascript|2499150|entityMap^0|5|9|17|9|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

There is no need to test <code>os.rename</code>, but your code needs to be tested. In your particular case the simplest way is to patch <code>os.rename</code>:

<pre><code>from unittest.mock import patch

def test_move_files():
 files = ['a.txt', 'b.txt']
 path = 'old'
 expected = [(('a.txt', 'old/a.txt'),),
 (('b.txt', 'old/b.txt'),)]
 with patch('os.rename') as rename:
 move_files_to(files, path)
 assert rename.call_args_list == expected
</code></pre>

Suppose I have the following function and I need to unit test it:

<pre><code>def move_files_to(files, path):
for file in files:
 os.rename(file, path + "/" + file)
</code></pre>

my thoughts on this topic:

Mocking os.rename would lead to no outcome, on the other hand, having files and renaming them would be "doing I/O" which should be avoided in unit tests. Please correct me, if I am wrong. Does testing make sense here?

Unit testing of "renaming files" in Python

单元测试

假设我有以下函数，并需要对其进行单元测试：def move_files_to(files, path):for file in files:    os.rename(file, path + "/" + file)我对这个话题的看法是：模拟os.rename不会导致任何结果，另一方面，拥有文件并重命名它们将是“执行I...

问Python中“重命名文件”的单元测试
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Python中“重命名文件”的单元测试EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Python中“重命名文件”的单元测试
EN