|
Line 4: There are some basic tests for containers, so we should import them. Freebie tests are always good.
|
|
|
第4行：免费的测试件总是好的，我们为容器导入一些基本测试。 |
|
Line 5-7 &13: We simply register the mail subscription adapter that we just developed, so that the mailer can find the subscribers in the messages.
|
|
|
第5-7&13行:我们简单地注册我们刚刚开发的邮件订阅适配器，因此邮件收发器可以在消息中找到订户。 |
|
Line 54-55: Just stick a plain, empty Message instance in the adapter.
|
|
|
第54-55行:仅仅在适配器中生成一个纯文本的、空的消息实例。 |
|
Line 5: This registers the Help Topic as the default context help for message board objects. This is an optional attribute.
|
|
|
第5行:为消息栏对象作为预设上下文帮助注册帮助主题。这是个可选属性。 |
|
Line 5: You declare all incoming requests on port 80 as virtual hosting sites.
|
|
|
行5:声明所有在80端口上进入的请求作为虚拟主机的站点。 |
|
Line 6-14: This is the actual recursive method that searches for all the pending messages.
|
|
|
第6-14行:这其实是递归方法用以搜索所有待审消息。 |
|
Line 7 specifies the DN suffix for queries to pass to this database.
|
|
|
第7行为通往该数据库的查询指定DN后缀。 |
|
Line 7-10: In doc tests it helps very much if you emphasize how you setup your test case.
|
|
|
第7–10行：在文档测试中，强调如何设定你的测试事例是非常有帮助的。 |
|
Line 7-12: Iterate over all message entries and create links to each pending message, displaying its title.
|
|
|
第7-12行:遍历所有消息条目并为每个待审消息创建链接和显示标题。 |
|
Line 8-10: This is some backward compatibility for the messages that were created before we added the workflow feature.
|
|
|
第8-10行:这里为在我们添加工作流功能之前被创建的消息提供向后兼容性。 |
|
Line 8: However, the TextTest base comes with some rules we have to abide to. Specifying this _Field_Factory attribute is required, so that the correct field is tested.
|
|
|
第8行：然而，`TextTest`要求我们必须遵守一些规则，它要求我们必须指定_Field_Factory属性，以致于正确的域能被测试。 |
