A system test environment mirrors the production environment more closely than does a development integration environment.
与开发集成环境相比，系统测试环境更接近地反映了生产环境。
These are the parameters Settings used in our system test.
下面是在我们的系统测试中使用的参数设置。
Closer communication between development and system test teams.
开发和系统测试团队之间更密切的交流。
After completing the system test report, the COE initiates NFR testing.
完成系统测试报告以后，COE将发起nfr测试。
The system test application increased in functionality and complexity as well.
系统测试应用程序的功能和复杂度也增加了。
In week 6, the system test team presented their iteration results to the overall team.
在第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.
在六个迭代中，系统测试核心团队与开发团队并行工作。
If the integration build passes system test, the build can be deployed and released to customers.
如果这次集成编译的版本通过了系统测试，那么这个版本就可以给客户进行布署。
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.
一般来说，在敏捷的开发周期中对系统测试缺陷的开发关注较多。
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显示了一般的迭代规划，以及为每个星期计划的具体的系统测试活动。
Software defect submission is more than a communication vehicle between development and system test groups.
软件缺陷交付不仅仅是开发和系统测试组之间的交付工具。
The system test team USES this environment to observe how the application works in a load-balanced environment.
系统测试团队使用这种环境来观察应用程序如何运行在负载平衡的环境中。
One way of addressing this is to make testing thread allocation and management part of your regular system test.
解决这个问题的一种方法是将线程分配和管理的测试作为您的常规系统测试的一部分。
In particular, there is no need to equip the system test environment with large scale high performance hardware.
特别地，没有必要为系统测试环境配备大规模高性能硬件。
This enabled a subset of traditional system test application development and execution runs during every iteration.
这能够让传统的系统测试应用程序的子集的开发和执行在每个迭代的过程中执行。
A number of "System Test" Environments may be configured, depending on your specific needs and budgetary constraints.
可能要配置大量的“系统测试”环境，这取决于您的特定需要和预算限制。
Like the system test environment, the performance test environment is a carefully controlled formal test environment.
类似于系统测试环境，性能测试环境同样是一个精心控制正式测试环境。
Finally, and in the most extreme case, the development integration run time and system test environments can be combined.
最后，在最极端的情况下，开发集成运行时环境和系统测试环境可以组合在一起。
This environment also mirrors the production environment, but at a generally larger scale than a system test environment.
这种环境也反映生产环境，只不过是以比系统环境更大的规模这样做。
These demos required significant preparation, and system test team participation became more difficult in later iterations.
这些演示需要大量的准备，而在后面的迭代中系统测试团队的参与更困难。
In iteration 1, the system test team defined templates for those test scenarios, and created common configuration documents.
在迭代1中，系统测试团队为那些测试场景定义模板，并且创建公共的配置文档。
A subset of system test was performed throughout all iterations, even though the system test timeframe per iteration is limited.
在所有的迭代过程中都执行系统测试的子集，即使每个迭代的系统测试时间都是有限的。
应用推荐