To address this lack of knowledge in the test team, tools such as penetration testing and fuzzing are becoming popular.
为了解决测试团队这方面知识的缺乏，贯穿测试和模糊测试这样的工具逐渐流行起来。
Goals for system test team involvement.
系统测试团队参与的目的。
IllustrationYour test team has been very successful.
插图您的测试团队已经非常成功了。
Staffing: Additions and attrition among the test team.
人员安排：在测试团队中的人员增加和削减。
Let's return to the characteristics of a good test team.
让我们回到优秀测试团队的特征上来。
Your software test team should plan for its future in the same way.
你的软件测试团队应该为未来作出同样的计划。
Inform the test team about the reworked code in time. (See Figure 12.)
通知测试团队及时改写代码(请看图12)。
The software test team starts working based on baseline bl1 (main branch).
软件测试团队在基线b11（主要分组）的基础上开始工作。
Allows the test team to select font and color for the text of script steps.
允许测试小组在脚本步骤中可以针对文本选择字体和颜色。
The team that identifies the use cases generally provides the input to the test team.
确定用例的团队通常为测试团队提供输入内容。
In week 6, the system test team presented their iteration results to the overall team.
在第6周，系统测试团队向整个团队提出他们的迭代结果。
The fast pace of modern software development creates tremendous challenges for the test team.
现代软件开发的快速节奏给测试团队带来了极大的难题。
During week 2 the system test team presented the application design enhancements to the architects.
在第2周中，系统测试团队向架构师提出应用程序的设计增强。
After some promising initial trials, however, the test team simply ran out of time on their laser lease.
然而，在充满希望的几次初试后，测试队伍的激光器租期却到了。
The system test team USES this environment to observe how the application works in a load-balanced environment.
系统测试团队使用这种环境来观察应用程序如何运行在负载平衡的环境中。
Early test case development allows the test team adequate time to do peer reviews and hold stakeholder reviews.
早期测试用例开发允许测试团队有足够的时间来处理同等的检验并保持涉众的评论。
Each test team that sends representatives to the meeting should map out its objectives for the meeting in advance.
每个测试团队派遣到会议的代表都应该为提前完成制定自己的目标。
The system test team distinguished between stop-ship and non stop-ship test scenarios in their test tracking tool.
系统测试团队在测试追踪工具中区别停船和非停船测试场景。
In SOA environments the test team goes beyond traditional application centric functionality and performance testing.
在SOA环境中，测试团队超越了传统的以应用程序为中心的功能和性能测试。
Now automated testing can proliferate across an entire test team - not just the subset of test automation engineers.
现在，自动化测试可以覆盖整个测试团队——不仅仅局限在只有测试自动化工程师才可以完成。
In these cases, the developers and test team can lose precious time waiting for a fully integrated and functional system.
这种情况下，开发和测试团队需要付出更多宝贵的时间才能实现一个完整的、有效的系统。
Early involvement of the test team minimizes the dependency on supportive documentation for writing effective test cases.
测试团队及早介入，于是在编写有效的测试案例时，尽可能不依赖支持文档。
Now, any time the test team encounters that module while testing manually, the team can simply invoke the automated script.
现在，在人工测试时，在任何时候测试团队遇到该模块，其都可以简单地调入已自动化的脚本。
These demos required significant preparation, and system test team participation became more difficult in later iterations.
这些演示需要大量的准备，而在后面的迭代中系统测试团队的参与更困难。
The test team then takes the use cases, builds the test scripts, and executes the test plans developed by the test planner.
测试团队然后采用这些用例，构建测试脚本并执行测试计划人员制定的测试计划。
The ability to generate the majority of test cases and scripts early has many benefits to the Systems Integration test team.
尽快掌握生成大多数测试用例和脚本的能力对系统集成测试团队来说有很多好处。
In iteration 1, the system test team defined templates for those test scenarios, and created common configuration documents.
在迭代1中，系统测试团队为那些测试场景定义模板，并且创建公共的配置文档。
These two features helped the test team develop and document repeatable test results, meeting the high-visibility challenge.
这两个特性帮助测试团队开发和文档化可重复的测试结果，从而满足“高可见性”的挑战。
To test all of these areas sufficiently and most effectively, the Systems Integration test team requires more than use cases.
要充分并有效地测试这些区域，系统集成测试团队需要的不仅仅是用例。
In the majority of scenarios, automation development teams design the tool which satisfies the requirements of only one test team.
在大多数的场景中，自动化开发团队都会设计只满足一个测试团队需求的工具。
应用推荐