A system test environment mirrors the production environment more closely than does a development integration environment.
与开发集成环境相比，系统测试环境更接近地反映了生产环境。
Goals for system test team involvement.
系统测试团队参与的目的。
More robust and realistic system test application
更健壮且更实际的系统测试应用程序
Figure 4 shows an example system test environment.
图4展示了示例系统测试环境。
These are the parameters Settings used in our system test.
下面是在我们的系统测试中使用的参数设置。
Incorporate internal customers to system test your product.
联合系统的内部客户来测试你的产品。
Table 1: Activities per iteration: development and system test.
表1：每个迭代的活动：开发和系统测试。
Closer communication between development and system test teams.
开发和系统测试团队之间更密切的交流。
Removal of some system test defects earlier in the product cycle.
在产品周期较早期除去一些系统测试缺陷。
Software quality: Unit test progress, system test progress, test coverage.
软件质量：单元测试进展、系统测试进展、测试覆盖率。
The system test application increased in functionality and complexity as well.
系统测试应用程序的功能和复杂度也增加了。
The system test environment is a carefully controlled formal test environment.
系统测试环境是精心控制的正式测试环境。
Performance testers might use a system test environment to do their work as well.
性能测试人员也用系统测试环境做他们的工作。
As such, a system test environment is relatively inexpensive to build and maintain.
因此，系统测试环境的构建和维护相对便宜。
Many concurrent bugs are found only at system test, functional test, or by the user.
许多并行bug只有在系统测试、功能测试时才能被发现或由用户发现。
Regression testing of system test scenarios occurred during iteration weeks 2 through 6.
系统测试场景的回归测试发生在第 2到6 的迭代周中。
Among the specific benefits associated with agile system test efforts were the following.
以下是与敏捷的系统测试工作相关的具体好处。
This was true across all teams associated with the product deliverable, including system test.
这对所有与产品交付件相关的团队来说都是正确的，包括系统测试。
The system test core team was engaged in parallel with the development team over six iterations.
在六个迭代中，系统测试核心团队与开发团队并行工作。
During week 2 the system test team presented the application design enhancements to the architects.
在第2周中，系统测试团队向架构师提出应用程序的设计增强。
A more robust and realistic system test application incrementally built across multiple iterations.
跨多个迭代增量地构建更健壮且实际的系统测试应用程序。
In general, there was more development focus on system test defects during the agile development cycle.
一般来说，在敏捷的开发周期中对系统测试缺陷的开发关注较多。
Typically, an application is load tested less frequently than it is run on the system test environment.
与运行在系统测试环境中相比，应用程序进行负载测试的频次更少。
The performance test environment is very much like a system test environment with a specialized purpose.
与系统测试环境非常相似的是，性能测试环境也具有特定的目的。
Following are some of the most important challenges faced in the course of agile system test activities.
以下是在敏捷系统测试活动中面临的一些最重要的挑战。
Table 1 shows the general iteration layout and the specific system test activities planned for each week.
表1显示了一般的迭代规划，以及为每个星期计划的具体的系统测试活动。
Once the flow application is fully developed, it is redeployed; first to system test, then to production.
一旦流应用程序完全开发出来，它就可以重新部署；第一次是部署到测试系统中，然后再部署到生产环境中。
The system test team USES this environment to observe how the application works in a load-balanced environment.
系统测试团队使用这种环境来观察应用程序如何运行在负载平衡的环境中。
In the past, a test tracking tool was used to define system test scenarios and document test execution results.
在过去，测试追踪工具用于定义系统测试场景及编档测试执行结果。
One way of addressing this is to make testing thread allocation and management part of your regular system test.
解决这个问题的一种方法是将线程分配和管理的测试作为您的常规系统测试的一部分。
应用推荐