TWI655535B - Program changes management system and program changes management method - Google Patents

Abstract

The present disclosure provides a program change management system to assist a user in developing test assistance. The program change management system has a communication unit, a storage unit and a processing unit. The communication unit is connected to the terminal device to receive the test command transmitted by the terminal device. This test command has a test program number. The storage unit stores a test report generation module and a test case library. The processing unit is coupled to the communication unit and the storage unit, and the processing unit executes the test report generation module. When the communication unit receives the test instruction from the terminal device, the test report generation module queries the test case database, the corresponding test case corresponding to the test program number, and establishes a test report according to the test instruction and the mandatory test case. The disclosure further provides a corresponding program change management method.

Description

Program change management system and program change management method

The present invention relates to a management technique, and in particular to a program transaction management system and a program transaction management method.

The quality of the application system is the cornerstone of the electronic business. Therefore, in the process of program development or transaction, the quality control of the program is often performed by "instance test". From the perspective of quality control, in the process of the example test, although there is no way to conduct actual tests for all cases, the specific program can be tested according to the past experience. For example, when a program exception occurs in a specific program execution instance test, in the future when this particular program changes and needs to be tested in an instance, the instance test can be performed on a specific case based on past error experience to reduce the program. Common blind spots and errors in design.

However, the application system includes hundreds of programs. It is not easy to manage the cases that must be tested for each program. Not only that, the use of the program may be quite long and has been modified several times. In this process, managers and testers may change, causing the case records that must be tested to become cluttered or missing, thus making management more difficult. Based on this, how to provide a management mechanism that is convenient for testing is a subject of the technical staff of the field.

The present disclosure provides a program change management system and a program change management method for automatically introducing a test case to test the change of the program to enhance the quality management of the program.

The program change management system disclosed in the present disclosure is used to assist the user in developing test support. The program change management system has a communication unit, a storage unit and a processing unit. The communication unit is connected to the terminal device to receive the test command transmitted by the terminal device. The test command has a test program number. The storage unit stores a test report generation module and a test case library. The processing unit is coupled to the communication unit and the storage unit, and the processing unit executes the test report generation module. When the communication unit receives the test instruction from the terminal device, the test report generation module queries the test case database, the corresponding test case corresponding to the test program number, and establishes the test report according to the test instruction and the mandatory test case.

The program change management method disclosed in the present disclosure is used to assist the user in developing test support. The program transaction management method includes the steps of: receiving a test command from a terminal device, wherein the test command has a test program number; querying a test case corresponding to the test program number; and establishing a test report according to the test command and the mandatory test case.

Based on the above, the program change management system and the program change management method provided by the present disclosure automatically introduce a test case that must be tested while the user generates a test report for the program to be tested. In this way, to ensure that the necessary test cases that must be tested will not be lost or forgotten, the quality control of the program is strengthened.

The above described features and advantages of the invention will be apparent from the following description.

The program change management system provided by the present disclosure is for providing user management of program changes in the program change management system through the terminal device, for example, program change version record, test report record, transaction time management, etc., in particular, The user can obtain the auxiliary function of the test management through the program change management system when the program is to be tested.

FIG. 1 is a block diagram of a program change management system according to an embodiment of the present disclosure. Referring to FIG. 1, the program change management system 100 provided by the present disclosure is connected to the terminal device 10 of the user. The terminal device 10 is a device that is operable by a user and has a connection function. For example, a mobile phone, a personal computer, a notebook computer, a tablet computer, etc., the disclosure does not limit the type of the terminal device 10. The user can connect to the program change management system 100 through the terminal device 10 in a wired or wireless manner to perform program change management.

The program change management system 100 of the present disclosure has a communication unit 110, a storage unit 120, and a processing unit 130. The communication unit 110 is configured to transmit and receive an operation signal of the user. In an embodiment of the disclosure, the communication unit 110 is implemented by using a communication chip, which can support Global System for Mobile communication (GSM), Personal Handy-phone System (PHS). ), Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, Long Term Evolution (LTE) system, Worldwide Interoperability for Microwave Access (Worldwide) Interoperability for Microwave Access, WiMAX) systems, Wireless Fidelity (Wi-Fi) systems, or Bluetooth signal transmission components.

The storage unit 120 is configured to store software, data, and various types of programs required to run the program change management system 100. The storage unit 120 can be any type of fixed or removable random access memory (RAM), read-only memory (ROM), flash memory, hard disk. (Hard Disk Drive, HDD), Solid State Drive (SSD) or the like or a combination of the above.

The processing unit 130 is connected to the communication unit 110 and the storage unit 120. The processing unit 130 can be a central processing unit (CPU), or other programmable general purpose or special purpose microprocessor (Microprocessor), digital signal processor (DSP), programmable The controller, the Application Specific Integrated Circuit (ASIC) or the like or a combination of the above elements, the disclosure is not limited thereto.

In order to ensure that the user, in particular the transaction engineer and the tester, can test the case of the specific program that must be tested (hereinafter referred to as the mandatory case) in the process of the program change according to the past actual measurement experience, the storage unit of the present disclosure The test report generation module 122, the test case library 124, and the test report result library 126 are further provided.

The test report generation module 122 is configured to access the test case library 124 and the test report result library 126. The test report generation module 122 accesses the test case library 124 and generates a test report based on the data accessed by the test. Moreover, the test report generation module 122 also generates test report results according to the test case test results and the test report, and stores them in the test report result library. The method by which test report generation module 122 generates test reports and test report results will be detailed later.

The test case library 124 stores a plurality of test cases to record the program number corresponding to the test case and whether it is a case that must be measured. These test cases are cases that may occur when the application system program is actually operated. Taking Table 1 as an example, it discloses a test case of an embodiment.  <TABLE border="1" borderColor="#000000" width="85%"><TBODY><tr><td> Case number</td><td> EX201710231042 </td></tr><tr> <td> Classification</td><td> Account Processing - Advance Account</td></tr><tr><td> Test Content</td><td> Set as Buyer Member of the Bank Account When the stored value account is deducted, the cross-bank transaction amount should be reduced by the inter-banking fee payable (for example, 15 yuan each). </td></tr><tr><td> Test Steps </td><td> 1. The buyer member is set to his account. 2. Query the stored value account balance and withdraw NT$1,000 from the stored value account. </td></tr><tr><td> Test Results Viewing Method </td><td> After the interbank transfer transaction is completed, NT$985 will be credited from his account. </td></tr><tr><td> Test necessity</td><td> 1. Must test (PPP001) 2. Select test (AAA001) </td></tr><tr>< Td> Reasons for </td><td> 2017-001 Common Opinion</td></tr><tr><td> Program Number</td><td> 1. PPP001 2. AAA001 </td> </tr><tr><td> Case usage record</td><td> Serial number</td><td> Test date</td><td> Test report number</td><td> Transaction number< /td></tr><tr><td> 1 </td><td> 2017/10/23 </td><td> PR2017001 </td><td> I-2017-020 </td> </tr><tr><td> Date of Archival</td><td> 2017/10/23 </td></tr></TBODY></TABLE> Table 1: Test Cases in Table 1 The test case records the case number, classification, test content, detailed test content, steps and results inspection method of this test case. In particular, the test case and the corresponding program number are recorded in the test case. That is, for the program with the program number PPP001, the test case with the case number EX201710231042 is mandatory. Therefore, in the subsequent test process, if the program with the program number PPP001 has to be tested and must be tested, the test report generation module 122 automatically introduces the test case with the case number EX201710231042 into the test report.  

It should be noted that the same test case can correspond to a plurality of different programs, and the test necessity of the same test case is not necessarily the same in different programs. Taking the above example as an example, for the program with the program number AAA001, the test case with the case number EX201710231042 is selected. Therefore, in the subsequent test process, if the program with the program number PPP001 has to be tested and the test must be performed, the test report generation module 122 does not automatically introduce the test case with the case number EX201710231042 into the test report. In some embodiments, the test report generation module 122 provides a test case with the case number EX201710231042 for the user to select whether to test the selected test case.

The test report result library 126 stores the test report results executed and stored by the user each time, so that the user can query in the process of subsequent program management, and modify the program content according to the test report results.

In an embodiment of the present disclosure, the test report generation module 122 provides a program transaction input interface, a case input interface, and a test report generation interface for the user to input program related information, test cases, and test report related data. For example, the program change manager will input the program data of the program change through the program input interface. The program change engineer will input the changed program and history in the program change input interface, and the test engineer will create multiple files through the case input interface. The case and the corresponding program, and through the test report interface to fill in the project name, test program number and other information of this test, however, this disclosure is not limited to the above-mentioned performers and the information they input.

FIG. 2 is a flow chart of a program change management method according to an embodiment of the present disclosure. The details of the method for managing the program change management of the program change management system will be described below with reference to FIG. In the embodiment of the present disclosure, the processing unit 130 of the program change management system 100 continuously runs the test report generation module 122.

It should be noted that, in this embodiment, before the transaction management system 100 runs the program change management method, the program change manager must first input the program data and the transaction number of the program change. Then, the program change engineer will first enter the program number and modification content of the program to be modified based on the transaction number, to file the modified program.

During the testing phase, the user (for example, the tester) will select the program to be tested and input other test-related data based on the transaction number. After the user inputs the test data, the user transmits a test command corresponding to the test data to the program change management system through the terminal device 10. In this embodiment, the test command has a report creation date, a transaction number, a test program number, a person who executes the test report, and the like.

At this time, in step S210, when the communication unit 110 receives the test instruction from the terminal device 10, the test report generation module 122 queries the test case number corresponding to the test program number in the test case library 124 (ie, in the corresponding program to be tested) In the number, the test necessity is recorded as a mandatory test case).

In step S220, the test report generation module 122 establishes a test report according to the test instructions from the terminal device 10 and the necessary test cases.

Specifically, in steps S210-S220, the test report generation module 122 establishes a test according to the test instruction, the change number of the program to be tested, the program number to be tested, the report establishment date, and the person who executes the test report. Basic information of the report. Moreover, the test report generation module 122 queries the test case library for the case corresponding to the test program number according to the test program number carried in the test command. After the case corresponding to the program number to be tested is found, if the test necessity is recorded as a mandatory test in the program number corresponding to the test, the test report generation module 122 automatically displays the test case in the test report to List this test case as a necessary test item.

If the test necessity is recorded as the selection test in the program number corresponding to the test, the test report generation module 122 can selectively display the case for the user to select whether to test the case. After the user selects the selected test case, the test report generation module 122 generates a test report according to the basic data of the test report, the required test case, and the selected test case selected by the user, and displays it on the terminal device 10 for use. The test is based on this test report.

It should be noted that in the design of this disclosure, the addition and deletion of the mandatory cases can only be deleted through the new interface of the case. In the process of subsequent testing, the user may not delete the mandatory case in the test report through the terminal device 10. And in order to ensure that all the necessary test cases have been tested, the test report generation module 122 will change the status of the test report to completed only after all the necessary test cases have the corresponding case test results. Based on this, it can be ensured that the user has listed all the necessary test cases and tested them when testing the program to reduce the blind spots during the test.

In step S230, the user performs a test and inputs a case test result through the terminal device 10. Specifically, in the embodiment of the present disclosure, the process of the user performing the test is performed manually. That is to say, the user will operate according to the test steps of the test case and the selected test case, and input the case test result into the test report.

It should be noted that the disclosure does not limit the manner in which the user inputs the execution result. For example, the user can directly regard the value generated by the execution of the program as the case test result, and input the case test result into the test report. The test report generation module 122 determines whether the test result of the case meets the value recorded by the test result view method. Alternatively, the user can also determine whether the result of the program is in compliance with the test result viewing method, and the compliance/non-conformity is regarded as the case test result to be input to the test report.

In other embodiments, after the test report generation module 122 generates the test report, the user can issue a case test command to the test report generation module 122 through the terminal device 10, so that the test report generation module 122 according to the test step The corresponding values and environment are entered into the program to be tested, thereby generating a case test result. In fact, the manner in which the user performs the test and the result of the input case test are changed according to actual needs and design, and the disclosure is not limited thereto.

In step S240, when the test report generation module 122 receives the test report result generation instruction from the terminal device 10, the test report generation module 122 generates a test report result according to the test report and the case test result. It should be noted that, in order to ensure that all the required test cases have been tested, before the execution of step S240, the test report generation module 122 determines whether all the test cases in the test report have the corresponding case test results. If the test report generation module 122 determines that all the test cases have been tested, the test report generation module 122 can perform step S240. On the other hand, if the test report generation module 122 determines that the test case has not been tested yet, the test report generation module 122 does not perform step S240.

In addition, when step S240 is executed, the test report generation module 122 simultaneously changes the status of the test report to completed, and stores the test report result in the test report result library 126. It should be noted that the test report results described here are the summary and collation of all test cases.

In step S250. The test report generation module 122 transmits the test report results back to the terminal device 10 to allow the user to view the results of the last generated test report.

In summary, the program change management system and the program change management method provided by the present disclosure automatically introduce a test case that must be tested according to the program number to be tested, while the user generates a test report for the program to be tested. In this way, when testing the transaction, it is necessary to ensure that the necessary test cases that must be tested are not forgotten. Moreover, when the control personnel change, these must-test cases will not be lost, thus strengthening the quality control of the program.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention, and any one of ordinary skill in the art can make some changes and refinements without departing from the spirit and scope of the present invention. The scope of the invention is defined by the scope of the appended claims.

10‧‧‧ Terminal devices

100‧‧‧Programming Management System

110‧‧‧Communication unit

120‧‧‧ storage unit

122‧‧‧Test report generation module

124‧‧‧Test case library

126‧‧‧Test report result library

130‧‧‧Processing unit

S210~S240‧‧‧Steps of Program Change Management Method

FIG. 1 is a block diagram of a program change management system according to an embodiment of the present disclosure. FIG. 2 is a flow chart of a program change management method according to an embodiment of the present disclosure.

Claims (10)

A program change management system is provided to assist a user in developing test support. The program change management system includes: a communication unit connected to the terminal device to receive a test command transmitted by the terminal device, wherein the test command includes a test program number; a storage unit, a test report generation module and a test case library, wherein the test case library includes a plurality of test cases, and the test cases respectively correspond to at least one program number, and the program number corresponds to a test necessity; a processing unit coupled to the communication unit and the storage unit, the processing unit executing the test report generation module, wherein when the communication unit receives the test command from the terminal device and selects a test case selection command, the test The report generation module queries the program number corresponding to the test cases in the test case library, and queries the necessary test case corresponding to the test program number and the necessity of the test, and according to the test instruction and the checked test result. Case and corresponding test case selection test of the selected test case Report. The program transaction management system of claim 1, wherein the communication unit receives the case test result input from the terminal device and the test report result generation instruction, and the test report generation module is based on the test report and the case The test result produces a test report result, and the test report result is transmitted back to the terminal device. The program transaction management system of claim 2, wherein after the communication unit receives the test report result generation instruction input from the terminal device, the test report generation module further determines the must in the test report If the test report generation module determines that the test case has the test result of the case, the test report generation module generates a test report result according to the test report and the case test result, and The test report result is sent back to the terminal device. If the test report generation module determines that the test case does not have the case test result, the test report generation module returns an error message to the terminal device. The program transaction management system of claim 1, wherein when the communication unit receives a case test instruction from the terminal device, the test report generation module according to the test step of the mandatory case, The value of the test case and the environment are input into the test program to generate a case test result, wherein when the communication unit receives the case test result input from the terminal device and the test report result generation instruction, the test report generation module basis The test report and the test result of the case generate a test report result, and the test report result is transmitted back to the terminal device. The program transaction management system described in claim 1, wherein the test case in the test report cannot be deleted. A program change management method for assisting a user in developing test assistance, the program change management method comprising the steps of: receiving a test instruction from a terminal device and selecting a test case selection instruction, wherein The test instruction includes a test program number; the necessary test case corresponding to the test program number and the necessity of the test is inquired according to the program number corresponding to the test case; and the required test case according to the test instruction and the query And a test report is established corresponding to the selected test case of the selected test case selection test instruction. The method for managing a program change according to claim 6, further comprising the steps of: receiving a case test result input from the terminal device and a test report result generating instruction; and generating a test report result according to the test report and the case test result; And returning the test report result to the terminal device. The program transaction management method of claim 7, wherein after receiving the test report result generating instruction input from the terminal device, determining whether the test case in the test report already has the case test result, If the test case has the test result of the case, the test report result is generated according to the test report and the test result of the case, and the test report result is returned to the terminal device, and if the test case does not have the case test result , return error message to the terminal device. The program transaction management method according to claim 6, wherein when the case test instruction from the terminal device is received, the test is based on the test case a test step of inputting a value and environment corresponding to the case to be tested into the test program to generate a case test result, wherein when the case test result received from the terminal device input and the test report result generation instruction are generated, according to the test report And the case test result produces a test report result, and the test report result is transmitted back to the terminal device. The method for managing a program change according to claim 6, wherein the test case in the test report cannot be deleted.