全部

1·Functional Verification Test (FVT).

功能验证测试(FVT)。

2·Commands functional verification tests.

命令功能的验证测试。

3·System call functional verification tests.

系统调用功能的验证测试。

4·This step should happen after functional verification for two reasons.

这一步骤在验证功能之后执行，这样做有两个理由。

5·Functional verification is an important bottleneck in millions gates IC design.

功能验证是百万门级IC设计中的一个重要瓶颈。

6·In the functional verification, instruction functions and exception behaviors are verified.

在功能验证中，覆盖了普通指令的功能和异常行为。

7·This testing typically starts after the completion of development and functional verification testing.

此测试一般在完成开发和功能验证测试之后进行。

8·Start functional verification of the environment, such as VIOS failover and application startup and test.

开始对环境进行功能性检验，比如VIOS故障转移以及应用程序启动和测试。

9·Traditional functional verification method is hard to make verification scenarios and cover corner cases.

传统的功能验证方法难以构建复杂的验证场景，并且边缘情况难以覆盖。

10·Test engineers can use it to catch memory errors during functional verification and system integration testing.

测试工程师可以利用它获取功能验证和系统整合测试期间的存储错误。