它可能源自测试容器状态的方法。
It probably comes from a way of testing the condition of a container.
在必要时，请包含中继资料档案或测试容器所在之资料夹的路径。
If necessary, include the path to the folder in which the metadata file or test container resides.
其他工具，如JUnitBe，允许在一个网络容器中执行测试用例以测试容器资源。
Other tools, like JUnitEE, allow test cases to be executed within a web container to test container resources. All of these tools typically.
60名学步儿童被各自引导着与一位手持塑料容器的成人测试员认识。
Sixty toddlers were each introduced to an adult tester holding a plastic container.
另外一半（孩子）发现容器是空的，并意识到测试员欺骗了他们。
The other half discovered the container was empty—and realized the tester had fooled them.
您的对象也可以在容器外运行 ——例如，在一个测试用例中。
Your objects can also run outside the container -- for example, in a test case.
对于您所定义的测试变量和容器，使用有意义的名字会是一个不错的主意。
It is always good to use meaningful names for your test variables and the containers that you define.
相反，开发者必须要有J2EE容器来运行和测试它们。
Instead, a developer needs a J2EE container to run and test them.
第一个非常简单的测试是要确保业务流程容器浏览器在每个成员上运行。
A first, very simple test is to ensure that the business process container explorer is running on each member.
您还可以将这个可嵌入的容器轻松用于单元测试。
You can also use this embeddable container easily with unit tests.
通常，这些组件没有容器不能运行，并要求您在测试前和拆卸后执行特殊设置。
Normally, these components don't run without a container, requiring you to perform special setup before testing and teardown afterward.
这就是可靠测试需要某类容器内策略和数据库访问的原因。
That's why reliable testing requires some sort of in-container strategy with database access.
使用模拟容器可降低测试时间，而不减弱门户服务器功能。
Using mock containers reduces your testing time without compromising the portal server functions.
在容器之外测试服务层也变得非常容易，从而极大地加速了开发周期。
Testing the service layer outside the container also becomes very easy, which can significantly speed up the development cycle.
在不同的工作站上运行单元测试需要有能运行容器的应用程序服务器。
Running unit tests on different workstations requires application servers where the containers can run.
脱离容器单独测试流转。
要测试应用程序，就需要容器或容器角色。
To test applications you need containers, or the role of containers.
在您为测试定义更多的测试变量时，您可以添加子容器以帮助您组织它们。
As you define more test variables for a test, you can add sub-containers to help organize them.
同样，如果您不希望在测试中使用与生产中相同数目的容器，就缩短列表并使用较少容器。
Also, if you do not wish to use the same number of containers in test that are in production, shorten the list and use fewer containers.
使用可嵌入容器的容器内测试可实现它的目标，但过程比较缓慢，因为容器启动时间就需要大概30秒。
The in-container testing with the embeddable container achieved its goal but was relatively slow, with the container startup time being around 30 seconds.
您需要从应用程序服务器容器内进行测试，才能得到准确的测试结果。
It is necessary to test from within the application server container for accurate test results.
目前有许多单元测试框架使用模拟容器来执行测试。
There are many unit testing frameworks available today that use mock containers for testing.
因为在容器以外测试JSF组件有所限制，所以大家一直认为对于JSF应用进行单元测试是困难的。
Unit testing JSF based web applications has been considered difficult because of the constraints of testing JSF components outside the container.
测试之中的 TestVariables容器是从不能删除的记录中生成的，但是它可以得到重命名。
The Test Variables container in a test that is generated from a recording cannot be deleted, but it can be renamed.
在测试框架中，开发者能按步骤地加载Seam容器，然后运行测试。
In your test framework, you can load the Seam container programatically and then run the tests.
在本文中，我们将为您演示如何编写简单的portlet并使用Pluto portlet容器测试它。
In this article, we'll show you how to write a simple portlet and test it against the Pluto portlet container.
因为我们继承了Spring的DI容器实现，因而可以从Spring的测试与产品使用中获益。
Because we inherited the DI container implementation from Spring, we have the benefit of all the testing and production use behind it.
此时您可以使用一个模拟portlet容器来测试portlet。
At this point you can use a mock portlet container to test the portlets.
Seam用嵌入的轻量级容器来帮助该类测试。
Seam comes with an embeddable lightweight container that helps this type of testing.
portletUnit用于测试一个portlet容器之外符合JSR-168的portlet。
portletUnit is used to test JSR-168-compliant portlets outside of a portlet container.
应用推荐