Modularity模块化

Modularity in this context refers to test scripts, whereas independence refers to test cases. Given that your test library will include a number of scripts that together make up an automated test environment, modularity means scripts that can be efficiently assembled to produce a unified system without redundancy or omission.

模块化在这种情况下指的是测试脚本，而独立性是指测试用例。鉴于您的测试库将包括一些脚本，共同构成了一个自动化的测试环境，模块化意味着可以有效地组合，以产生一个统一的系统，而无需冗余或遗漏脚本。

Tie script design to application design

将脚本设计应用于应用程序设计

Ideally, the test scripts should be comprised of modules that correspond to the structure of the application itself, so that when a change is made to the application, script changes are as localized as possible. Depending on the automation approach selected, this may require separate scripts for each window, for example, or for each type of method of interacting with a control.

理想的是，测试脚本应包括对应于应用程序本身的结构，这样当对应用程序进行了更改，更改脚本的测试是尽可能为本地化。取决于所选择的自动化方法，这可能需要对每个窗口单独的脚本，例如，或对于每种类型的具有控制交互的方法的。

But modularity should not be taken to an extreme: scripts should not be broken down so minutely that they lose all individual meaning. This will raise the same issues that lengthy, convoluted scripts do: where should changes be made?

但模块化不应该被发挥到了极致：脚本应该不会这么精细，他们失去了所有个人意义细分。这将提高冗长的、 令人费解的脚本做的同样的问题: 在哪里进行更改?

Identify common scripts

识别常见的脚本

Modularity also means that common functions needed by all tests should not be duplicated within each individual script; instead, they should be shared as part of the overall test environment. Suggested common routines are described further in the Test Framework chapter.

模块化也意味着需要通过所有测试常用的功能应该不是每个脚本中被复制;相反，它们应被共享作为整个测试环境的一部分。建议的常见例程将进一步在测试框架本章的介绍。