A payment terminal embedded software testing workload statistics system

Abstract

The invention relates to a payment terminal embedded software test workload statistics system. The system is coordinated with multiple payment terminals carrying software to be tested, and comprises a test task dividing module, a unit test case control module, a comprehensive test case control module, a unit test module, a comprehensive test module, a time statistics module, a task time statistics module, a data uploading unit and a total test workload statistics unit. According to the payment terminal embedded software test workload statistics system, a test workload statistics method which is easy to use, feasible, meticulous, supported by sufficient data and applicable to an embedded software system is provided, and can be flexibly expanded according to newly added test demands.

Description

technical field [0001] The invention relates to payment terminal embedded software test workload statistics, in particular to a payment terminal embedded software test workload statistics system. Background technique [0002] Existing payment terminal embedded software testing requires unit, stress, crossover, performance, compatibility, reliability, usability and other tests for all functional modules, even if there is already a relatively complete set of test cases and test standards provided However, due to the complexity of the embedded system, the difference in the work efficiency of the testers, the difference in the robustness of the tested version, etc., there has not been a more accurate and efficient method to count the test time required to complete the intrusive software test. [0003] The existing statistical test workload methods in the IT industry include: Ad-hoc method, percentage method of development time, analogy method (empirical value method or historica...

AI Technical Summary

Problems solved by technology

[0002] Existing payment terminal embedded software testing requires unit, stress, crossover, performance, compatibility, reliability, usability and other tests for all functional modules, even if there is already a relatively complete set of test cases and test standards provided However, due to the complexity of the embedded system, the difference in the work efficiency of the testers, the difference in the robustness of the tested version, etc., there has not been a more accurate and efficient method to count the test time required to complete the intrusive software test.

[0003] The existing statistical test workload methods in the IT industry include: Ad-hoc method, percentage method of development time, analogy method (empirical value method or historical data method), WBS (workbreakdown structure) estimation method, etc., but these methods exist: need Defects such as relying on development workload, large differences in statistical results, low efficiency, large errors, insufficient measurement basis (unable to convince superiors due to lack of data support), insufficient flexibility, etc.

Images