The most expedient solution here is to create a testing database and to programmatically get the input data from these rows , perform any parsing required , use the data as needed in the functional tester scripts , possibly updating the data within functional tester from one script to another , and then update or insert rows into the testing database with the data that should be used in the next test suite execution . refer to the decorator design pattern in 此处最有利的解决方案是建立测试资料库并透过程式设计的方式从那些行中获取输入资料，执行任意需要的语法分析，在functional tester中随需要使用资料，在functional tester中从一个脚本到另一个脚本进行资料更新，并更新或将带有在下一个测试程式执行中使用的资料的行插入到测试资料库中。
The basic generic functionality can serve as a foundation for testing many different types of components and as the interface to standard tools . " as with many test design patterns , this pattern at once illuminates an often - murky testing problem , namely that of repetition of testing code , and sheds light on a possible solution : create a reusable testing framework 一般的功能是作为测试许多不同类型元件的基础并作为标准工具的介面。 ”同许多测试设计样式一样，该样式立即说明了常常模糊的测试问题，也就是测试程式码的重复，并阐明了可能的解决方案：建立了一个可复用的测试框架。
An example would be the auto - generation of patient account numbers or general ledger numbers in which some semantics are embedded in the numbers and it is desired to maintain realism in such test data , especially if the data involves very large numbers which must be maintained in sequence between test suite executions 一个实例是自动产生持续的帐户或一般的分类帐户，在其中嵌入了一些语义，并且希望在那样的测试资料中维持真实性，特别是资料涉及非常大的必须在测试程式执行之间保持顺序的数位。
