输入文件将包含多组测试事件。
开始执行之前，将调用此方法以启用对单元测试事件的订阅。
Before execution starts, this method is called to enable subscription to the Unit Test Events.
对于每一个测试事件，你应该输出颠倒后的结果，一行一个答案。
For each test case, you should output its reverse number, one case per line.
请记住，您在Monitor测试环境中创建的仪表板实际上仅用于测试事件和警报的功能。
Remember that the ones you created in the Monitor test Environment were really only for testing the functionality of the events and alerts.
过去，测试的目的过分集中于前者，这就是为什么在测试事件中通常存在非常少的互操作性问题。
In the past there has been too much focus on the former and this is why there are usually very few interoperability issues found during the testing events.
要测试事件的执行，查找根用户的主目录中的cpulog . txt文件和web接口中TRUESAMPLES的非零值。
To test execution of the event, look for the file cpulog.txt in the root user's home directory and a non-zero value of TRUESAMPLES in the web interface.
在针对历史堆栈的测试应用程序中，只存储随机数作为事件。
In the testing application for the history stack, we only stored random Numbers as events.
必须彻底测试所有用户定义、事件、请求、更新、更改和需求的管理。
Management of all user definitions, events, requests, updates, changes, and requirements must be tested thoroughly.
测试某些功能或事件的内部遵从性审核可能相当麻烦。
Internal compliance audits that test certain features or events can be rather invasive.
手动测试可以轻松检测到复杂系列的事件，并决定测试执行的方向。
Manual testing can easily detect this complex set of events and determine the direction of test execution.
它试图解释某一个事件，它同理论类似，是可测试的、可证伪的，只是其适用的范围比较狭窄。
It attempts to explain an event, and is testable and falsifiable like a theory is, but on a more narrow scale.
在此阶段，您需要为下一个步骤中的单元测试创建仪表板，以确保发射事件、做出计算并显示结果。
At this stage, you need to create the dashboards for unit testing in the next step to ensure that events are emitted, calculations are made, and results are displayed.
在调用其他服务调用时，将在测试客户机中显示更多的事件。
More events appear in the test client as it calls the rest of the services calls.
若要使用实际的数据库驱动的事件来测试整个应用程序，请再次打开DB 2命令中心。
To test the entire application with real database-driven events, open the DB2 command center again.
我们让参与者回到真实世界，然后在扫描仪里面测试他们对日常生活事件的记忆。
We're taking participants out into the real world, and then in the scanner we'll test their memories for events from their everyday lives.
考察我们是否实际地关注了好测试的方法是，如果我们觉得在离开事件时与进入时一样，那么我们真正完全地致力于该活动。
A good test to see if we actually did pay attention is that, if we feel exactly the same coming out of an event as going in, we didn't truly and fully engage in that activity.
但是，在实际的环境中，执行一个测试操作组成了一个复杂而又内联的事件，很多时候测试执行的本质就取决于它。
However, in actual environments, executing a test constitutes a complex and inter-related set of events on which, many times, the nature of test execution depends.
测试运行后，操作的输出将显示为返回事件。
After the test runs, the output of the operation will display as a Return event.
一旦用例被充分开发产生事件流，就可以得到测试程序。
As soon as use cases are developed enough to have a flow of events, then test procedures can be derived.
“政策总是把事情搞糟的一个原因——思考一下‘卡特里娜’飓风事件——是因为它从未得到测试，”他说。
"One reason that policy keeps screwing up - think Katrina - is because it never gets tested," he says.
“政策总是把事情搞糟的一个原因——思考一下‘卡特里娜’飓风事件——是因为它从未得到测试，”他说。
“One reason that policy keeps screwing up — think Katrina — is because it never gets tested, ” he says.
为希望测试的事件输入值并选择事件的单选按钮。
Enter values for the event you want to test and select the event's radio button.
等待数据提交以进行事件测试——大部分现有测试框架没有能力等候多个异步事件。
Wait for the data to be committed for event testing - Large portions of existing testing frameworks do not have the ability to wait for multiple asynchronous events.
当出现生产环境(或其他任何测试环境)意外停机事件时，管理员可以有效地从更改控制工具提取有关环境中发生了何种更改的信息。
When a production (or any other test environment) outage occurs, the administrators can efficiently extract information from the change control tooling about what changes occurred in the environment.
这个Events树列出了所有的测试执行事件，比如脚本起始和终结、循环、调用、通知，或者结果。
The Events tree lists all test execution events, such as the script start and end, loop, invocation, message, or verdict.
测试客户机现在会发出事件，从而允许直接在WebSphereIntegrationDeveloper 中测试监视器模型，而不必首先部署到 WebSphere BusinessMonitor。
The test client now emits events, enabling the testing of a monitor model directly in WebSphere Integration Developer, without having to first deploy to WebSphere Business Monitor.
在测试执行之后，在问题事件中，从左边窗格之中选择Defects以选择其中一个选项。
After test execution, in the event of a problem, select Defects from the left panel to choose either of these options.
为RPT,InternetExplorer使用默认浏览器，创建一个新项目叫作SimpleProject，并一个新测试来记录事件。
Using the default browser for RPT, Internet Explorer, create a new project called SimpleProject with a new test to record events.
图2显示了选择模拟事件和测试人员为checkPurchaseOrder操作输入的返回值为 true 时集成测试客户端的运行情况。
Figure 2 shows an integration test client run where an emulation event is selected and where the tester entered a return value of true for the checkPurchaseOrder operation.
当测试客户端停止在CustomerInformationPartner的手动模拟事件时，为Out put参数键入true。
When the test client stops at the manual emulation event for the CustomerInformationPartner, type true for the Output parameter.
应用推荐