A system test environment mirrors the production environment more closely than does a development integration environment.
与开发集成环境相比，系统测试环境更接近地反映了生产环境。
Better system test application.
较好的系统测试应用程序。
Goals for system test team involvement.
系统测试团队参与的目的。
Improved full system test ramp-up time.
提高了的全部系统测试的加速时间。
More robust and realistic system test application
更健壮且更实际的系统测试应用程序
Figure 4 shows an example system test environment.
图4展示了示例系统测试环境。
A system test environment may serve multiple masters.
系统测试环境可以服务多种角色。
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.
在产品周期较早期除去一些系统测试缺陷。
As with a system test environment, one application is tested at a time.
如同系统测试环境的情况一样，一个应用程序只测试一次。
After completing the system test report, the COE initiates NFR testing.
完成系统测试报告以后，COE将发起nfr测试。
Software quality: Unit test progress, system test progress, test coverage.
软件质量：单元测试进展、系统测试进展、测试覆盖率。
These criteria must be met to officially start system test and claim results.
必须达到这些标准，从而正式地开始系统测试并要求结果。
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.
因此，系统测试环境的构建和维护相对便宜。
Use the migration of a system test environment to learn the ropes and make mistakes.
在迁移系统测试环境中学习迁移规则，它也允许您犯错。
In week 6, the system test team presented their iteration results to the overall team.
在第6周，系统测试团队向整个团队提出他们的迭代结果。
System test scenario execution for new functionality only occurred during weeks 5 and 6.
对于新功能的系统测试场景的执行只发生在第5和6周。
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.
跨多个迭代增量地构建更健壮且实际的系统测试应用程序。
It nicely balances some generic system test best practices with the challenges that freeze progress.
它在冻结进度的挑战下，很好地平衡了一些普通系统测试的最佳实践。
In general, there was more development focus on system test defects during the agile development cycle.
一般来说，在敏捷的开发周期中对系统测试缺陷的开发关注较多。
应用推荐