Willingness to co-operate tea factory or dealer , welcomed the visitor, call test.
愿意合作的茶厂或经销商，欢迎来人、来电考查。
To test out a phone-based application, you obviously need a phone, and that implies a number to call.
为了测试基于电话的应用程序，您显然需要一台电话，这就意味着一个呼叫号码。
That way if you ever have to change the way you search, you can change it in one place and it gets fixed in all your test scripts that call that module.
使用这种方式，如果您在某一时间必须修改您搜索的方法，您可以在一个地方修改它，它会在您所有调用该模块的测试脚本中生效。
Under each SIP test, the complete SIP call flow (SIP requests and responses) for the SIP test and the verdict for that test are shown.
在每一项SIP测试之下，SIP测试的完整SIP访问流(SIP请求与回应)，以及该测试的结论将会显示出来。
For a SIP test, the SIP call flow in this TAB is a very important and pertinent piece of information.
对于一次SIP测试，该项中的SIP访问流是一条十分重要且恰当的信息。
Another advantage is that each developer can deploy the latest update of the applications to the development test server for other developers to call.
另一个好处是，每位开发人员都可以将应用程序的最新更新部署到开发测试服务器，以便其他开发人员调用。
An obvious location for the SQA workflow is within the Test workflow and the defined activities that call for evaluation.
关于SQA工作流的一个明显之处是在测试工作流和要求评估的已定义活动中。
If you fail at a test or perform poorly at an audition, you could erroneously call yourself a failure.
如果你考试失败，或者在观众面前表现糟糕，于是你错误的把自己称之为失败者。
The test was susceptible to errors induced by monomorphic call transformation and subsequent deoptimization.
测试容易受到由单一调用转换引起的错误以及随后的反优化的影响。
This is challenging because there is no network in a unit test and the AJAX call will fail.
这很有挑战性，因为单元测试中没有网络，AJAX调用会失败。
This allows you to simply call the necessary method (for example to query on a table) from your test scripts.
这样您就可以简单地从您的测试脚本中调用必要的方法(例如在一个表格中查询)。
Figure 11 shows the information provided by this TAB for the Call Forwarding test.
图11显示了该项为CallForwarding测试提供的信息。
An unscheduled call that rings on my phone fails the conversational Turing test: it's almost certainly junk, so I ignore it.
来安排。一个未经预约就打到我手机上的电话通过不了对话图灵测试(conversational Turing test)：这个电话几乎肯定是垃圾电话，因此我忽略它。
The physical test environment shown in Figure 3 has been used to test the Call Forwarding sample.
图3显示的物理测试环境，用于测试CallForwarding示例。
Create a test database on your DB2 server, and call it TESTDB, using the steps below.
按照以下步骤，在DB 2服务器上创建一个测试数据库，并把它命名为testdb。
The default symbol is: each, meaning RSpec will call the set up block before each test.
默认的标志为：each，表示RSpec将在每次测试之前调用set u p代码块。
There's no doubt that this test is correct because all it does is set up expectations, invoke the system under test, call getters, and make assertions.
毫无疑问，此测试是正确的，因为它已经完成了设置预期值，调用被测试的系统，调用getter和作出声明。
The integration test client calls the import and lets the binding complete the service call.
集成测试客户端将调用导入，并让绑定完成服务调用。
The test developers can call the above API from any Robot scripts, as shown in Figure 14.
测试开发人员可以调用任意robot脚本中如上文所示的API，如图14所示。
Listing 5. Script updated to call your functional test scripts.
列表5更新的脚本，能调用你的功能测试脚本。
Once that is done the ObserveOnTest function attaches the unit test framework to the call chain via a specialized scheduler called the WorkItemTestScheduler.
一旦完成，ObserveOnTest函数就会通过一个叫做WorkItemTestScheduler的特殊计划程序把单元测试框架关联到调用链上。
By default, EasyMock only allows the test case to call the methods you specify with the arguments you specify.
在默认情况下，EasyMock只允许测试用例用指定的参数调用指定的方法。
For example, with my test, I'll first call the getDefinition() method and then provide an implementation of a Timer's run() method.
以我的测试为例，我将首先调用getDefinition()方法，然后提供一个Timer的run() 方法的实现。
In the of the HTML page, we then call the print_sequence function twice, using different arguments to test the function. Calling print.php.
在html页面的中，我们接着使用不同参数两次调用print_sequence函数，以测试该函数。
When build Server triggers a build, it will remotely call SSP, passing a RuleApp and the list of scenarios to test.
当BuildServer触发一个构建时，它将远程调用SSP，传递一个RuleApp和场景列表进行相应测试。
A first test call fails returning the message SQL30082N Security processing failed with reason "3" (" PASSWORD MISSING ").
第一个测试调用失败，返回消息SQL 30082n Securityprocessingfailed withreason “3 ” (“ PASSWORD MISSING ”)。
TestCaller is templatized with this class and, as in the case of TestRunner, you make a call to the run method for test execution.
用这个类对TestCaller 进行模板化，与使用TestRunner 时一样，通过调用run方法执行测试。
The first test asked me to call my dog using a variety of words that were not her name to gauge whether she could tell the difference.
第一项测试要求我用不同的词来呼唤她，看看她能不能把自己的名字从其他词中区别出来。
My implementation filters files by their filenames, but it isn't convenient to test whether the plug-in is necessary on every call.
这里的实现根据文件名过滤文件，但是每次调用都检查需要插件是否会带来很大的不便。
No, we weren't able to extensively test it, but you can see below for in-call screens and the like.
但我们没办法进行更详细的测试。你可以看看文末提供的通话中的照片。
应用推荐