CSA序言信息技术部门内的标准制定与国际标准制定相协调。通过CSA信息技术技术委员会（TCIT），加拿大人担任加拿大标准委员会（SCC）ISO/IEC信息技术联合技术委员会（ISO/IEC JTC1）的SCC镜像委员会（SMC），该委员会是加拿大的ISO成员机构，也是IEC加拿大国家委员会的发起人。此外，作为国际电信联盟（ITU）的成员，加拿大还参加了国际电报和电话协商委员会（ITU）- T） 。范围ISO/IEC/IEEE 29119的这一部分定义了关键字驱动测试的有效且一致的解决方案，具体如下:-介绍关键字驱动测试；-提供实施关键字驱动测试的参考方法；-定义关键字驱动测试框架的需求，使测试人员能够共享他们的工作项，例如测试用例、测试数据、关键字或完整的测试规范；-定义支持关键字驱动测试的工具的需求。这些要求可适用于支持关键字驱动方法的任何工具（例如，测试自动化、测试设计和测试管理工具）； -定义接口和通用数据交换格式，以确保不同供应商的工具可以交换其数据（例如测试用例、测试数据和测试结果）；-定义分层关键字的级别，并建议使用分层关键字。这包括描述特定类型的关键字（例如用于导航或检查值的关键字）以及何时使用“平面”结构化关键字；-提供示例通用技术（低级）关键字的初始列表，例如“inputData”或“checkValue”。这些关键字可以用于在技术层面上指定测试用例，并且可以组合起来创建业务- 根据需要设置关键字级别。注:本标准适用于所有希望创建关键字驱动的测试规范、创建相应框架或基于关键字构建测试自动化的人。

CSA PrefaceStandards development within the Information Technology sector is harmonized with international standards development. Through the CSA Technical Committee on Information Technology (TCIT), Canadians serve as the SCC Mirror Committee (SMC) on ISO/IEC Joint Technical Committee 1 on Information Technology (ISO/IEC JTC1) for the Standards Council of Canada (SCC), the ISO member body for Canada and sponsor of the Canadian National Committee of the IEC. Also, as a member of the International Telecommunication Union (ITU), Canada participates in the International Telegraph and Telephone Consultative Committee (ITU-T).ScopeThis part of ISO/IEC/IEEE 29119 defines an efficient and consistent solution for Keyword-Driven Testing by: - giving an introduction to Keyword-Driven Testing; - providing a reference approach to implement Keyword-Driven Testing; - defining requirements on frameworks for Keyword-Driven Testing to enable testers to share their work items, such as test cases, test data, keywords, or complete test specifications; - defining requirements for tools that support Keyword-Driven Testing. These requirements could apply to any tool that supports the Keyword-Driven approach (e.g., test automation, test design and test management tools); - defining interfaces and a common data exchange format to ensure that tools from different vendors can exchange their data (e.g. test cases, test data and test results); - defining levels of hierarchical keywords, and advising use of hierarchical keywords. This includes describing specific types of keywords (e.g. keywords for navigation or for checking a value) and when to use "flat" structured keywords; - providing an initial list of example generic technical (low-level) keywords, such as "inputData" or "checkValue". These keywords can be used to specify test cases on a technical level, and may be combined to create business-level keywords as required. NOTE This standard is applicable to all those who want to create keyword-driven test specifications, create corresponding frameworks, or build test automation based on keywords.