T/EGAG 012.1-2022 Active Group standards

T/EGAG 012.1-2022 Functional Automated Testing Tool Part 1: Quality Testing Specifications

T/EGAG 012.1-2022

Publish Date: 2022-09-23 Implement Date: 2022-10-01 For services related to genuine standard inquiry, procurement, translation, and other related services in China, please Contact Us

Price: $ 20.00

Out of stock

Basic Information

Standard Code: T/EGAG 012.1-2022

Standard Type: Group standards

Standard Status: Active

is_force_gb: no

CCS Name: -

ICS Name: Comprehensive Application of Information Technology

Publish Date: 2022-09-23

Implement Date: 2022-10-01

Scope

Scope: This part of T/EGAG 012 specifies the test indicators, test methods, and requirements for functional automation testing tools in terms of functionality, performance efficiency, reliability, and ease of use. This part is applicable to third-party organizations conducting quality testing and evaluation of functional automation testing tools, as well as to enterprises using it as a reference for improving and evaluating their own developed functional automation testing tools. Main technical content: This part specifies the test indicators, test methods, and requirements for functional automation testing tools in terms of functionality, performance efficiency, reliability, and ease of use. It is applicable to third-party organizations conducting quality testing and evaluation of functional automation testing tools, as well as to enterprises using it as a reference for improving and evaluating their own developed functional automation testing tools. 1. Tool execution process: The functional automation testing tool should include six processes, namely visual operation, automatic generation of use cases, batch execution, action execution, automatic collection of test results, and automatic generation of all documents. 2. Quality testing indicators: The quality testing items of the functional automation testing tool are regulated from six aspects, namely product documentation, functionality, performance efficiency, reliability, ease of use, and portability. For example, the product documentation should explain the tool name and software version number; the functionality testing items include test project management, script management, test execution, test case management, test case execution, and test result management; and the ease of use includes intuitiveness, consistency, and rationality. 3. Quality testing methods: The testing methods, test environment preparation, product documentation indicators testing methods, functionality indicators testing methods, p