Because of this and other differences in the two versions, we recommend that you test the maps after migration.
由于这两个版本之间的种种差异，我们建议您在完成迁移后对映射进行测试。
Depending on your needs, an entire project can be migrated, or you can select test artifacts for migration.
根据您的需要，可以迁移整个的项目，或者您可以为迁移选择测试工件。
As always, I strongly recommend that you test your procedures in a non-production environment before attempting a storage migration on a production system.
与以往一样，我强烈建议您在尝试在产品系统中进行存储迁移之前先在一个非生产环境内测试您的过程。
This will help you better test and tune the application, estimate how long the migration will take, and help you avoid surprises.
这有助于您更好地测试和调整应用程序，评估迁移需要多长时间，并帮助您规避一些意外。
For example, depending on the load simulation performed when migrating the test environment, the migration might complete successfully.
例如，根据在迁移测试环境时执行的负载模拟，迁移可能获得完全成功。
If LDAP is to be used in the production environment, it is essential that it be included in the migration test environment.
如果产品环境中使用的是LDAP的话，那么将其包含到迁移测试环境的话，就非常重要。
You need to use two migration files, one to migrate test scripts and the other to migrate test cases.
您需要使用两个迁移文件，一个去迁移测试脚本，另一个去迁移测试用例。
Perform the test migration using the removed hardware.
使用删除的硬件来执行测试迁移。
While doing the migration, test cases should be migrated along with the code.
在迁移过程中，测试案例应随代码一起迁移。
Of course, run time migration does require careful planning and so the training schedule should be adjusted to accommodate the time required to assemble and test an effective migration plan.
当然，运行时迁移也需要仔细的计划，因此培训进度也需要进行适当的调整，以适应编制和测试有效的迁移计划所需的时间。
If not, migration looks exactly like a failover test because the failback technique replaces the old style backout plan.
如果不成功，迁移看起来完全就像故障转移测试，因为退回技术取代了旧式的撤销计划。
The QA environment can withstand generally longer periods of down time which makes it an appropriate environment to test your migration plan.
QA环境通常容许更长时间的停机，这使它成为测试您的迁移计划的适当环境。
Once you have completed the auto migration, you will still need to test your migrated map file to ensure that it produces the desired results.
完成了自动迁移后，仍然需要对迁移后的映射文件进行测试，以确保它生成了理想的结果。
Be sure to test your run time migration plans in a test environment before starting the migration of your production run time.
在开始迁移您的生产运行时之前，应该确保您的运行时迁移计划已经在实验环境中进行了测试。
Based on the lessons learned through this migration, formulate a plan to effect the entire migration and test that plan against the QA environment.
在这个迁移中学到的教训的基础上，制定一个计划来指导整个迁移并在QA环境中测试该计划。
Improved release process. It now reuses the last non-released version thus enabling migration from non-released to released version of the profile even in test models.
改进的发布流程：可以在当前使用上一个未发布的版本，这样就可以将测试模块的概要文件从上一个老版迁移到新版本。
During the test phase, the mission-critical products in a previous release are kept running, while migration teams practice the migration of the components on test systems.
在测试迁移期间，前一版本中的关键业务产品保持运行，同时迁移团队在测试系统上执行组件迁移。
With the proper mapping of your test assets, and paying careful attention to pre-requisites explained here, this migration can help you capture the strategic advantages offered by this migration.
在将您的测试资源进行合适的映射之后，并对这里介绍的前提条件投入一定的关注，这种迁移可以帮助您获取该迁移所提供的战略性优势。
When migration is necessary, it is easier to get downtime for a development or to test LPAR during business hours than to schedule a production application outage.
当需要迁移时，让开发或测试LPAR在工作时间停机比安排在生产应用程序停机更容易。
If there are thousands of configured test cases, manual scripts, and test logs, migration could take several hours.
如果有大量配置测试用例，手动脚本以及测试日志的话，那么迁移过程可能会耗费大量的时间。
Ideally, an identical migration plan is executed in both test and production to maximise the chance of finding potential problems in test rather than in production.
理想情况下，测试环境中使用的迁移计划应该与生产环境中使用的迁移计划一样，以便在测试中最大限度地发现潜在的问题，而不是将那些潜在问题留在生产环境中。
As you know, that command generates your model, migration, unit test, and even a default fixture.
正如您所知，该命令可生成模型、迁移、单元测试甚至一个默认的fixture。
The Rational Functional Tester projects can also be copied from the existing production environment into the migration test environment.
您也可以将RationalFunctionalTester项目，从已存在的产品环境复制到迁移测试环境中。
In addition, Tcat Server provides deployment capabilities which makes the application migration from dev to test to staging to production environments very easy.
此外，Tcat服务器还提供了部署的能力，它使得将应用程序从开发环境迁移到测试环境最终到生产环境变得非常容易。
The process for setting up the migration test environment will be similar to the following steps.
创建迁移测试环境的过程类似于下面的步骤。
After the migration you'll be able to take advantage of the enhanced Rational Quality Manager collaboration, test planning, review, workflow, reporting, and dashboard capabilities.
在迁移完成之后，您就能够利用增强的Rational QualityManager协作、测试规划、评审、工作流程、报表与操作等功能带来的便利了。
Contact the Rational ClearQuest test manager administrator for the project that requires migration and get the ClearQuest schema used for that project.
联系需要迁移的项目的RationalClearQuestTestManager管理员，并得到该项目所用的Rational ClearQuestschema。
Test your run time migration plans in a test environment before starting the migration of your production run time. Migration is more than just installing new products.
在开始移植您的生产运行时以前，先在测试环境下测试您的运行时移植计划。
Create a new Rational project in the migration test environment by using Rational Administrator.
使用Rational Administrator，来在迁移测试环境之中创建一个新的Rational项目。
Finally, log in to Rational Quality Manager and ensure that the test asset totals match those in the post-migration summary.
最后，登录到Rational QualityManager，并确保测试资源总量匹配后面迁移总结中的总量。
应用推荐