These reports can take your requirements, changes, and test results, and then provide you with a comprehensive lifecycle view for software delivery.
这些报告可以您的需求，变化以及测试结果，然后向您提供一个软件交付的综合性生命周期的见解。
Changes couldn.t easily be associated with integration and test (I&T) issues or software change requests.
变更不能被容易的关联到集成与测试（I&T）的问题或者软件的变更请求上。
Using existing products as the basis for new test automation changes the focus to integration rather than development.
使用已存在的产品作为新测试自动化基础，改变了集成的关注点，而不是开发的关注点。
In all cases, you should implement and test all changes in your test environment before you consider adding them to your production environment.
无论何种情况，您都应该在考虑将更改添加到生产环境之前在您的测试环境中实现并测试它们。
If, however, either the product or the test material changes significantly over time, the instrumentation exercise will need to be repeated.
然而，如果产品或测试材料随着时间的推移变化很大，那么就需要重复实施装置。
And you can combine utilities that automatically track code changes, trace test coverage, submit defects, inspect code profiles and memory usage, and so forth.
你还可以结合一些应用，它们可以自动跟踪代码的变化，跟踪测试覆盖，提交错误，检查代码外形和存储使用，等等。
Another advantage of using automation tools to perform regression tests nightly is fewer changes introduced since the last test.
使用自动化工具来执行持续多日的回归测试的另一个优点是，和上一次测试相比变化较小。
The pane on the right in the editor changes to show the response code verification test element details.
编辑器右边的格子发生改变，以显示响应代码验证测试元素细节。
Some of the parallelization of development was necessary to allow others to test large changes before they were accepted.
为了让其他人在他们所做的改变被接受之前可以进行测试，有一些开发需要并行化。
This is definitely a trivial change, but why won't you test such trivial changes if they don't take much effort and have potential to fatten your bottomline?
这无疑是一个微不足道的变化。但如果这些细微的改变占用不了你多少精力，同时又有可能充实你的底线，你为什么不试一试呢？
Understanding if the successful test was the most optimal test possible, or if changes to the application code or envoironment configuration are needed.
了解成功的测试是否是最优测试，或者是否需要对应用程序代码或环境配置进行更改。
I started relying heavily on functional tests (over unit tests) which allowed me to test changes as a user would.
我开始严重依赖功能测试，而且超过了对单元测试的依赖，这让我能像用户那样测试应用中的变化。
Analysis can be performed from time to time whenever source code or test code changes, to see what it might uncover.
只要源代码发生变化，分析可以一直进行，以看看有什么发现。
To mirror this in the test database, Erik decides to create a schema named CHANGES in the test database GSDBDEV to hold the change he will be making.
为了将它复制到测试数据库，Erik决定在测试数据库gsdbdev中创建一个名为CHANGES的模式来保存将要进行的修改。
Without Optim Database Administrator, Erik would have to manually write scripts to migrate and test the changes in the test system, which could be both time consuming and error prone.
如果没有IBM OptimDatabaseAdministrator,Erik就必须手动编写脚本来移植和测试他在测试系统所做的修改，这既耗时又容易出错。
Migrate the changes from the test database (GSDBDEV) back to the production database (GSDB).
将测试数据库(GSDBDEV)的修改移植到生产数据库(GSDB)。
Make your changes to the design document and test plans as you go.
在工作进行当中，对你的设计文档和测试计划进行修改。
If you create a baseline at this point, changes made to your test assets since the last checkin will not be part of this baseline.
如果您在此时创建一个基线，在您最后检入时所做的测试资产变更将不会成为基线的一部分。
Then, we will be able to control the changes, and test the results before implementing them on our live site.
这样，我们就能够控制变更并测试结果，然后在我们的站点上应用它们。
For example, you may need to make design changes or change the planned test sequence as the software evolves.
比如，在软件进化的过程中你可能需要对设计或是计划的测试序列做出更改。
Often, we find that each new build of our application under test changes our object recognition properties enough that our automation breaks.
我们常常发现，在测试中，每次构建新的应用程序，对象识别属性的更改都很大，以致于破坏了自动化。
The biggest issue for us is simply the amount of time it takes to test and verify changes and additions to the framework.
我们所面对的最大的问题，就是对修改和新增内容的测试和验证花去了大量的时间。
Then, your test case makes changes to the database and tests the results of those changes.
然后，测试用例对数据库进行修改，并测试这些修改的结果。
When you modify old code you have to both test your changes and then perform a set of regression tests to make sure you didn't break any of the existing code.
而当你修改旧有代码时，你不得不既要测试你更改的部分，还要进行一系列的兼容测试，以保证你没有破坏任何的旧有代码。
This allows the QA team to only receive the changes that they are ready to test.
这样一来，QA团队就只会接收到他们准备好测试的变更。
This makes it very easy to make changes and to test the policies within your development environment.
这使得在开发环境中进行更改及测试策略变得非常轻松。
Make changes and test them out — just be sure to keep your source tree in sync with your deployment tree!
做出更改并完成们测试——一定要使源代码树与部署树保持同步！
After making small changes to the test plans, we delivered them to the customer for a quick review; we agreed that the changes were small enough that another TRR wouldn't be needed.
在对测试计划进行了小的变更后，我们为一个快速检查向客户交付了测试计划；我们同意变更是非常小的，并不需要其他的TRR。
In test or development systems, changes are frequent, so for example cache updates would likely be set to occur more frequently.
在测试或开发系统中，修改比较频繁，所以缓存更新应该设置得比较频繁。
Also, changes move from development to test, and ultimately into production in a consistent, orderly, and reproducible manner.
而且，当改变由开发阶段进入测试阶段时，就从根本上提供了一个一致的、有序的、可重现的产品。
应用推荐