Method and apparatus for generating testing script and testing method and apparatus and system

[0026] The first embodiment is a method for generating test scripts. The flowchart is shown in Fig. 1, including:

[0027] 101. Identify the CDR type.

[0028] In this embodiment, the process of identifying the type of CDR includes:

[0029] Match the bill format first; then determine the bill type according to the bill format.

[0030] In this embodiment, the matching of the bill format can be adopted: obtaining the length of the bill; searching and obtaining the bill format corresponding to the length of the bill. There are many standard formats of the existing call bill formats, such as: Internet call bill format, roaming call bill format, Monternet call bill format, IDD format, etc.

[0031] It is understandable that the matching bill format can also be matched by other existing conventional implementation manners, and the specific method of matching the bill format does not constitute a limitation to the present invention.

[0032] By identifying the format of the call bills, the call bill types can be divided into: Internet bills, roaming bills, Monternet bills, and international toll bills.

[0033] In this embodiment, the bill types are classified according to the bill format, and different bill formats will correspond to different test script templates.

[0034] It is understandable that the type of the bill can also be determined jointly according to the format of the bill and the content of the bill. That is to say, the dialogue list can be further classified in more detail according to the matching bill format.

[0035] For example, first identify the format of the call bill, and get the call bill as an international long-distance call bill. Based on the content of the call bill, the type of the call bill is derived: an international long-distance short message call bill.

[0036] 102. Search and obtain a test script template corresponding to the CDR type.

[0037] In this embodiment, the test script template corresponding to the call ticket type is prepared in advance. The type and number of CDRs and the number of test script templates can be determined according to the specific situation. The following provides an example of the structure of a test script template:

[0038]

[0039]

[0040] Test Case title

[0041]

[0042]

[0043]

[0044]

[0045]

[0046]

[0047]

[0048]

[0049]

[0050]

[0051]

[0052]

[0053]

[0054]

[0055]

[0056] First command Target Value Second command Target Value

[0057]

[0058]

[0059] Among them, First command and Second command represent the command to be executed, and Target represents the specified target, that is, the position where the configuration data is filled, such as a drop-down box on the page, a single selection box, etc. Value represents the value that needs to be entered, such as the value to be filled in the text box, the value of a column selected in the drop-down box, etc., that is, the configuration data found in the subsequent steps. For example: First command is: fill in the representative value of the short message bill, Target indicates the target location to fill in, the value of the value is the value corresponding to the short message bill, where the value is "01", which represents the value of the short message bill "01", after the data is configured, when the test system processes the bill, the value of the field representing the business type of the bill will be obtained. If the obtained value is "01", the business type of the bill can be obtained by matching It is a short message bill.

[0060] 103. Search and obtain configuration data corresponding to the content of the CDR.

[0061] In the embodiment of the present invention, the configuration data corresponding to the content of all the fields of the CDR can also be searched and obtained. It is also possible to search for the configuration data corresponding to the contents of some fields, and the selection of specific field contents can preset the fields to be processed.

[0062] It can be understood that there is no absolute order between step 103 and step 101 to step 102 in this embodiment. As long as the content of each field of the CDR is recognized, step 103 can be performed.

[0063] In this embodiment, the configuration data corresponding to the content of the bill is stored in the maintenance database in the maintenance server. When the configuration data is actually obtained, it can interact with the maintenance server to search and obtain the required configuration data through a specific data interface. It is understandable that a large amount of configuration data can also be stored locally for searching.

[0064] The configuration data is data related to settlement, such as operator information, location information, tariffs, etc.

[0065] 104. Fill the test script template with the configuration data to generate a test script of the call bill.

[0066] In this embodiment, when preparing the test script template, a plurality of variables to be assigned or filled are set, and after the configuration data found is filled, a complete test script is formed.

[0067] In the first embodiment of the present invention, by identifying the call bill type; searching for the test script template corresponding to the call bill type; searching and obtaining the configuration data corresponding to the call bill content; filling the configuration data in the test script template generating station The test script of the narrative list realizes the automatic generation of the test script. Compared with the prior art, testers manually write scripts, which greatly reduces the workload of the testers, improves the efficiency of the system test of the test, and speeds up the overall progress of the system test process.

[0068] The second embodiment is a method for generating a test script. The method flow is shown in Fig. 2 and includes:

[0069] 201, match the CDR format.

[0070] 202. Determine the type of the call bill according to the call bill format and the call bill content.

[0071] The bill type can be determined jointly according to the bill format and the bill content. That is, after the CDR formats that can be matched, the CDRs can be classified in more detail according to the content of the CDRs.

[0072] 203. Search and obtain a test script template corresponding to the CDR type.

[0073] 204. Acquire a key field of the bill corresponding to the bill type.

[0074] 205. Search and obtain configuration data corresponding to the content of the key field of the CDR.

[0075] In this embodiment, considering the particularity of the settlement system, the processing of the call bill is mainly for the special data related to the call bill and settlement, so the data configuration required to process the call bill is also for the processing of these special data. The configuration of the data. The fields storing these special data are the key fields, and the configuration of the key fields depends on the type of the bill.

[0076] It can be understood that step 204 is based on step 202 as the premise and trigger, and there is no absolute order in execution of step 204 and step 203.

[0077] 206. Fill the test script template with the configuration data to generate a test script of the call bill.

[0078] The difference between the second embodiment of the present invention and the first embodiment is that the second embodiment further classifies the CDRs according to the CDR format and the content of the CDRs, and searches for configuration data according to the content of the key fields of the CDR corresponding to the CDR type; The more detailed the classification, the more types of test script templates need to be preset. However, because of the refinement of the classification, there are fewer different fields in the CDRs of the same category. You can preset more presets in the test script template. Configuration Data. When searching for configuration data, there are fewer key fields and their corresponding content; this reduces the interaction with the maintenance database, and speeds up the search for configuration data and the filling of templates. Therefore, when the tester classifies the call ticket type and configures the test script template, the tester can select an appropriate number of category dialogs according to the actual situation to classify and configure the test script template corresponding to the category type.

[0079] The following provides the third embodiment of the present invention, which is based on the data configuration method of the test script generation method of the first embodiment above. The flowchart is shown in Fig. 3 and includes:

[0080] 301: Identify the type of CDR.

[0081] In this embodiment, the process of identifying the type of CDR includes:

[0082] Match the bill format first; then determine the bill type according to the bill format.

[0083] 302. Search and obtain a test script template corresponding to the call ticket type.

[0084] 303. Search and obtain configuration data corresponding to the content of the CDR.

[0085] In the embodiment of the present invention, the configuration data corresponding to the content of all the fields of the CDR can also be searched and obtained. You can also find the configuration data corresponding to the content of some fields, and the tester can set the fields that need to be processed in advance for the selection of the specific field content.

[0086] It can be understood that there is no absolute sequence between step 303 and steps 301 to 302 in this embodiment. As long as the content of each field of the CDR is recognized, step 303 can be performed.

[0087] In this embodiment, the configuration data corresponding to the content of the bill is stored in the maintenance database in the maintenance server. When the configuration data is actually obtained, it can interact with the maintenance server to search and obtain the required configuration data through a specific data interface. It is understandable that a large amount of configuration data can also be stored locally for searching.

[0088] The configuration data is data related to settlement, such as operator information, location information, tariffs, etc.

[0089] 304. Fill the test script template with the configuration data to generate a test script of the call bill.

[0090] In this embodiment, when the test script template is pre-compiled, multiple variables to be assigned or filled are set, and after the found configuration data is filled, a complete test script is formed.

[0091] 305. Run the test script to perform data configuration on the settlement system.

[0092] In this embodiment, running the test script may be the direct operation of the settlement system for data configuration. It is understandable that other test servers may also run the test script to drive the settlement system to complete the data configuration.

[0093] The third embodiment of the present invention is to identify the type of the call bill; search to obtain the test script template corresponding to the call bill type; search to obtain the configuration data corresponding to the content of the call bill; fill the configuration data in the test script template generating station State the test script of the CDR, and run the test script to configure the data of the settlement system. The automatic generation of test scripts and the automatic configuration of settlement system data are realized. It avoids the testers from manually writing scripts or manual data configuration, greatly reducing the workload of the testers, improving the efficiency of the system test of the test, and speeding up the overall progress of the system test process.

[0094] The fourth embodiment of the present invention is a data configuration method based on the test script generation method of the second embodiment above. The flowchart of the method is shown in Fig. 4 and includes:

[0095] 401, match the CDR format.

[0096] 402. Determine the type of the bill according to the format and content of the bill.

[0097] The bill type can also be determined jointly according to the bill format and the bill content. That is, after the CDR formats that can be matched, the CDRs can be classified in more detail according to the content of the CDRs.

[0098] 403. Search and obtain a test script template corresponding to the call ticket type.

[0099] 404. Acquire a key field of the CDR corresponding to the CDR type.

[0100] 405. Search and obtain configuration data corresponding to the content of the key field of the CDR.

[0101] In this embodiment, considering the particularity of the settlement system, the processing of the call bill is mainly for the special data related to the call bill and settlement. Therefore, the data configuration required to process the call bill is also for the processing of these special data. The configuration of the data. The fields storing these special data are the key fields, and the configuration of the key fields depends on the type of the bill.

[0102] It can be understood that step 404 is based on and triggered by step 402, and there is no absolute order in execution of step 404 and step 403.

[0103] 406. Fill the test script template with the configuration data to generate a test script of the call bill.

[0104] 407. Run the test script to perform data configuration on the settlement system.

[0105]The difference between the fourth embodiment of the invention and the third embodiment is that the second embodiment further classifies the bills according to the bill format and bill content, and searches for the configuration data according to the key field content of the bill type corresponding to the bill type; The more detailed it is, more types of test script templates need to be preset, but because of the refinement of the classification, there are fewer different fields in the same category of CDRs. You can preset more configurations in the test script template. data. When searching for configuration data, there are fewer key fields and their corresponding content; this reduces the interaction with the maintenance database, and speeds up the search for configuration data and the filling of templates. Therefore, when the tester classifies the call ticket type and configures the test script template, the tester can select an appropriate number of category dialogs according to the actual situation to classify and configure the test script template corresponding to the category type.

[0106] The fifth embodiment is a system test method based on the data configuration method of the third embodiment or the fourth embodiment. The flowchart is shown in FIG. 5 and includes:

[0107] 501, identify the type of bill;

[0108] 502. Search and obtain a test script template corresponding to the call ticket type.

[0109] 503. Search and obtain configuration data corresponding to the content of the CDR;

[0110] 504. Fill the test script template with the configuration data to generate a test script of the call bill.

[0111] 505. Run the test script to configure data for the settlement system;

[0112] 506. The settlement system uses the configured data to process the call bill.

[0113] In this embodiment, the processing of the bill by the settlement system includes:

[0114] Format conversion of the input bill;

[0115] Solve the elements of the transferred call bill and rate the bill to generate a detailed bill of call charges;

[0116] Accumulate and settle the detailed call bill to obtain a report.

[0117] 507. Compare the processing result with the expected result to obtain a test result.

[0118] In this embodiment, the test result is obtained by comparing the report obtained by the processing with the expected report. If the report is the same, it is judged that the processing process of the test system is normal. If the report is different or the report obtained by processing is obviously wrong, the judgment is The process handled by the test system is abnormal and needs to be debugged and modified.