Write the setup and teardown methods.
编写setup和teardown方法。
FBI Vehicle-Tracking Device: The teardown.
FBI的汽车跟踪设备：拆解。
So, why don't you add this functionality in the setup/teardown routines?
那么，为什么不在设置/清除例程中添加这种功能呢？
These "teardown reports" provide a glimpse into a company's manufacturing.
由此而来的这些“拆机报告”提供给我们一个机会一睹一家公司的生产作业。
A huge issue in designing and writing a test suite is how to handle common setup and teardown code.
在设计和编写测试套件时，一个大问题是如何处理共同的setup和teardown代码。
The next steps in a teardown are identifying the parts and calculating the costs of materials and assembly.
拆解的下一步工作就是辨认零部件以及计算这些零部件在材料和装配方面的成本。
The next steps in a teardown are identifying the parts and calculating the costs of materials and assembly.
拆卸“的进一步过程是辨识每一个部件，然后计算其物料和组装成本。
As you can see from this output, the setup and teardown routine messages appear once each per unit test execution.
正如在输出中看到的，每次执行单元测试都会显示设置和清除例程消息。
It also looks at details like how common test setup and teardown is supported, or not supported, by the three frameworks.
还讨论一些细节，比如这三种框架对共同的setup和teardown代码的支持情况。
So all of the cases are already handled, and any branches to weed out extra teardown steps will only serve to slow down the default case.
所以所有情况都已经得到了处理，清除额外的结束步骤的任何分支只会减慢对默认情况的处理。
Python's with statement provides a very convenient way of dealing with the situation where you have to do a setup and teardown to make something happen.
有一些任务，可能事先需要设置，事后做清理工作。对于这种场景，Python的with语句提供了一种非常方便的处理方式。
The “teardown” graphic below, based on data from iSuppli, a market-research firm, shows who makes what inside the iPhone, and how much the various bits cost.
如下所示的苹果“拆机”图，基于iSuppli的资料（一市场研究公司），显示了手机里各组件由谁生产，以及各个组件的费用。
To eliminate repetitious code like this, many testing frameworks provide a way to indicate once what setup and teardown code needs to run for each of entire groups of tests.
为了消除这些重复的代码，许多测试框架提供了一次性指定每个测试都需要运行的setup和teardown 代码的机制。
There is one case in which nose does not care about the name of setup and teardown functions: when you specify them explicitly for a particular function using the @with_setup decorator.
在一种情况下，nose不考虑setup和teardown函数的名称：使用 @with_setup 修饰符为某一函数显式地指定它们。
And while a teardown doesn't account for the costs of design, software, manufacturing, or shipping, these cost estimates help fill in the blanks toward estimating the profit on each device sold.
但拆解并没有计入设计，软件，生产和运输的成本。这样的开销估算填补了对每一台售出设备的利润估计的空白。
Each test function call is sandwiched between a call to setUp and tearDown.
每个测试函数的调用被夹在setUp和tearDown调用之间。
Therefore, it's a good idea to use assertion macros in the TearDown code for better maintenance.
因此，为了便于维护，最好在TearDown代码中使用断言宏。
A tearDown method is also a good idea, but not strictly necessary, unless you're running integration tests.
包括tearDown方法也很不错，但不作严格要求，除非要运行集成测试。
The setUp method is called before execution of a unit test, and tearDown is called when the test is executed.
在执行单元测试之前调用setUp方法，在测试执行完时调用tearDown。
The tearDown function provides the test author with his or her opportunity to clean up or reset the test fixture.
tearDown函数则给测试者提供了另外一个机会，可以去清除或者重置测试夹具。
JUnit 4 also introduces a new feature that really has no equivalent in JUnit 3: class-scoped setUp and tearDown methods.
JUnit4也引入了一个JUnit3中没有的新特性：类范围的setUp和tearDown方法。
Because JUnit itself decorates all test cases with a setUp and a tearDown method, execution times must be considered within the overall context of a test scenario.
由于JUnit本身用一个setUp和一个tearDown方法装饰所有测试样例，所以要在测试场景的整个上下文中考虑执行时间。
You can now see how the various Setup and TearDown functions might allow you to control the test environment so that your test cases can be repeated as often as necessary and give consistent results.
现在你可以看到，不同的Setup和TearDown方法是怎样允许你控制测试环境，从而保证你的测试用例能根据需要而重复执行并给出恒定的结果。
You can now see how the various Setup and TearDown functions might allow you to control the test environment so that your test cases can be repeated as often as necessary and give consistent results.
现在你可以看到，不同的Setup和TearDown方法是怎样允许你控制测试环境，从而保证你的测试用例能根据需要而重复执行并给出恒定的结果。
应用推荐