Configuration change processing method, device, computer equipment and storage medium

Abstract

This disclosure provides a method, apparatus, computer device, and storage medium for processing configuration changes. The method includes: acquiring a service to be configured and determining configuration change information matching the service to be configured; determining target verification test cases corresponding to the service requirements of the service to be configured based on a mapping relationship; wherein the mapping relationship indicates the mapping relationship between various types of service requirements and various verification test cases; performing verification processing on the configuration change information based on the target verification test cases to obtain a verification result of the configuration change information; wherein the verification result indicates whether the configuration change information contains abnormal information.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more specifically, to a method, apparatus, computer device, and storage medium for processing configuration changes. Background Technology

[0002] Currently, configuration change verification typically relies on manual verification. For example, configuration change work orders can be manually verified, or end-to-end (E2E) verification of configuration changes can be performed manually. However, these verification methods heavily depend on human experience and are prone to omissions, thus compromising the accuracy of configuration change verification and impacting the quality of configuration changes. Furthermore, this manual verification approach is inefficient, affecting the speed of configuration change deployment. Summary of the Invention

[0003] This disclosure provides at least one method, apparatus, computer device, and storage medium for processing configuration changes.

[0004] In a first aspect, embodiments of this disclosure provide a method for processing configuration changes. The method includes: acquiring a service to be configured and determining configuration change information matching the service to be configured; determining target verification test cases corresponding to the service requirements of the service to be configured based on a mapping relationship; wherein the mapping relationship is used to indicate the mapping relationship between various types of service requirements and various verification test cases; performing verification processing on the configuration change information based on the target verification test cases to obtain a verification result of the configuration change information; wherein the verification result is used to indicate whether the configuration change information contains abnormal information.

[0005] In one optional implementation, the mapping relationship includes an identifier mapping relationship. The step of determining the target verification use case corresponding to the service requirements of the service to be configured based on the mapping relationship includes: determining the service requirement identifier of the service to be configured; determining the use case identifier that matches the service requirement identifier based on the identifier mapping relationship; wherein the identifier mapping relationship is used to indicate the mapping relationship between the service requirement identifiers of each type of service requirement and the use case identifiers of each verification use case; and determining the target verification use case based on the matching use case identifier.

[0006] In one optional implementation, the number of target verification cases is multiple; the step of verifying the configuration change information based on the target verification cases to obtain the verification result of the configuration change information includes: obtaining multiple test case parameters of the target verification cases; determining test case parameters that match each target verification case from the multiple test case parameters; and verifying the configuration change information based on the matching test case parameters and the corresponding target verification cases to obtain the verification result.

[0007] In one optional implementation, determining the test case parameter that matches each target verification case from the plurality of test case parameters includes: determining a parameter label for each test case parameter to obtain a plurality of parameter labels; determining a target parameter label associated with each target verification case from the plurality of parameter labels; and determining the test case parameter corresponding to the target parameter label as the test case parameter that matches the target verification case.

[0008] In one optional implementation, the plurality of test case parameters include a first type of parameter and a second type of parameter of the target verification test case; wherein, the first type of parameter is a parameter determined based on the configuration change information, and the second type of parameter is a static parameter of the target verification test case that does not change during execution.

[0009] In one optional implementation, the step of verifying the configuration change information based on the target verification test case to obtain the verification result of the configuration change information includes: obtaining the target simulation environment of the configuration change information; and verifying the configuration change information in the target simulation environment based on the target verification test case to obtain the verification result.

[0010] In one optional implementation, obtaining the target simulation environment for the configuration change information includes: determining a preset simulation environment that matches the configuration change information; obtaining an environment call link for the preset simulation environment; and calling the preset simulation environment based on the environment call link to obtain the target simulation environment.

[0011] In an optional implementation, the method further includes: determining the configuration status of the configuration change information; and, if the configuration change information meets the verification requirements based on the configuration status, performing a step of determining a target verification test case corresponding to the business requirements of the service to be configured based on the mapping relationship.

[0012] Secondly, embodiments of this disclosure also provide a configuration change processing apparatus, comprising: an acquisition module, configured to acquire a service to be configured and determine configuration change information matching the service to be configured; a determination module, configured to determine a target verification test case corresponding to the service requirements of the service to be configured based on a mapping relationship; wherein the mapping relationship is used to indicate the mapping relationship between various types of service requirements and various verification test cases; and a verification module, configured to perform verification processing on the configuration change information based on the target verification test case to obtain a verification result of the configuration change information; wherein the verification result is used to indicate whether the configuration change information contains abnormal information.

[0013] Thirdly, embodiments of this disclosure also provide a computer device, including: a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the computer device is running, the processor communicates with the memory via the bus, and when the machine-readable instructions are executed by the processor, the steps of the first aspect above, or any possible implementation of the first aspect, are performed.

[0014] Fourthly, embodiments of this disclosure also provide a computer-readable storage medium storing a computer program that, when executed by a processor, performs the steps of the first aspect or any possible implementation of the first aspect.

[0015] In the above embodiments, after obtaining the service to be configured and determining its configuration change information, target verification test cases corresponding to the service requirements of the service to be configured can be determined based on the mapping relationship. This allows for automatic determination of target verification test cases, improving the efficiency of configuration change processing. Subsequently, the configuration change information can be verified based on the target verification test cases to obtain the verification result. Compared with manual verification, this improves the accuracy of configuration change information verification and avoids missed detections caused by manual verification. At this point, the verification result can be used to determine whether the configuration change information contains abnormal information. Therefore, the configuration change information can be verified before executing the service to be configured, preventing the application of abnormal information to the service and ensuring the quality of configuration changes.

[0016] To make the above-mentioned objects, features and advantages of this disclosure more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings used in the embodiments will be briefly described below. These drawings are incorporated in and constitute a part of this specification. They illustrate embodiments conforming to this disclosure and, together with the specification, serve to explain the technical solutions of this disclosure. It should be understood that the following drawings only show some embodiments of this disclosure and should not be considered as limiting the scope. Those skilled in the art can obtain other related drawings based on these drawings without creative effort.

[0018] Figure 1 A flowchart illustrating a configuration change processing method provided by an embodiment of this disclosure is shown;

[0019] Figure 2 A flowchart illustrating the process of obtaining multiple test case parameters of a target verification test case provided in an embodiment of this disclosure is shown.

[0020] Figure 3 A schematic diagram illustrating the application of the configuration change processing method provided in the embodiments of this disclosure is shown.

[0021] Figure 4 A schematic diagram of the framework structure of a target simulation environment provided in an embodiment of this disclosure is shown;

[0022] Figure 5 A schematic diagram of a configuration change processing apparatus provided in an embodiment of this disclosure is shown;

[0023] Figure 6 A schematic diagram of a computer device provided in an embodiment of this disclosure is shown. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this disclosure, and not all of them. The components of the embodiments of this disclosure described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this disclosure provided in the accompanying drawings is not intended to limit the scope of the claimed disclosure, but merely represents selected embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0025] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0026] In this document, the term "and / or" merely describes a relationship, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" in this document means any combination of at least two of any one or more elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0027] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0028] Research has revealed that current verification of configuration changes typically relies on manual checks. For example, configuration change work orders can be manually verified, or end-to-end (E2E) verification can be performed manually. However, these methods heavily depend on human experience and are prone to omissions, compromising the accuracy of configuration change verification and impacting the quality of configuration changes. Furthermore, this manual verification approach is inefficient, affecting the speed of configuration change deployment.

[0029] Based on the above research, this disclosure provides a method, apparatus, computer device, and storage medium for processing configuration changes. In the above embodiments, after obtaining the service to be configured and determining the configuration change information of the service to be configured, target verification test cases corresponding to the service requirements of the service to be configured are determined based on a mapping relationship. This allows for automatic determination of target verification test cases based on the mapping relationship, improving the processing efficiency of configuration changes. Subsequently, the configuration change information can be verified based on the target verification test cases to obtain the verification result. Compared with manual verification, this improves the accuracy of configuration change information verification and avoids missed detections caused by manual verification. At this point, the verification result can be used to determine whether the configuration change information contains abnormal information. Therefore, the configuration change information can be verified before executing the service to be configured based on the configuration change information, preventing the application of the configuration change information to the service to be configured if it contains abnormal information, thus avoiding affecting the normal operation of the service and ensuring the quality of configuration changes.

[0030] To facilitate understanding of this embodiment, a configuration change processing method disclosed in this disclosure will first be described in detail. The execution subject of the configuration change processing method provided in this disclosure is generally a computer device with a certain computing power. This computer device may include a configuration backend, and the configuration change processing method provided in this disclosure is applied within the configuration backend.

[0031] See Figure 1 The diagram shows a flowchart of a configuration change processing method provided in an embodiment of this disclosure. The method includes steps S101 to S105, wherein:

[0032] S101: Obtain the service to be configured and determine the configuration change information that matches the service to be configured.

[0033] In this embodiment of the disclosure, the service to be configured can be understood as a service for which configuration change information is determined based on business requirements, but which has not yet taken effect. In this case, the service to be configured can be a payment service, a sales service, a routing configuration service, etc.

[0034] In this embodiment of the disclosure, a service to be configured can be obtained, and configuration change information matching the service to be configured can be determined. In this case, the configuration change information can be understood as information generated based on the service requirements of the service to be configured.

[0035] S103: Determine the target verification test case corresponding to the business requirements of the service to be configured based on the mapping relationship; wherein, the mapping relationship is used to indicate the mapping relationship between each type of business requirement and each verification test case.

[0036] In this embodiment of the disclosure, a corresponding type label can be set for each type of business requirement and at least one verification case corresponding to that type of business requirement (at this time, the at least one verification case constitutes a verification case group), and a mapping relationship between each type of business requirement and each verification case can be established based on the type label.

[0037] At this point, the target verification test cases corresponding to the business requirements of the service to be configured can be determined based on this mapping relationship. The service to be configured can have one or more business requirements; therefore, the target verification test cases can correspond to one or more groups of verification test cases.

[0038] In this embodiment of the disclosure, each type of business requirement can correspond to multiple configuration change types. In this case, at least one sub-validation test case can be set for each configuration change type, and a mapping relationship between each configuration change type and the at least one sub-validation test case can be established. The configuration change type is used to indicate the configuration change items involved in the business requirement.

[0039] At this point, the configuration change types corresponding to the business requirements can be determined based on the business requirements, and the target verification case corresponding to the business requirements can be determined through the mapping relationship between the configuration change types and the at least one sub-verification case.

[0040] S105: Perform verification processing on the configuration change information based on the target verification case to obtain the verification result of the configuration change information; wherein, the verification result is used to indicate whether the configuration change information contains abnormal information.

[0041] In this embodiment of the disclosure, after determining the target verification test case corresponding to the business requirement, the target verification test case can be called to verify the configuration change information corresponding to the configuration requirement, and the verification result of the configuration change information can be obtained. The verification result can be that the verification passed, in which case it can be determined that the configuration change information does not contain abnormal information. Alternatively, the verification result can be that the verification failed, in which case it can be determined that the configuration change information contains abnormal information.

[0042] In addition, if the verification result is that the verification failed, the verification result may also include verification details and the reason for the failure.

[0043] In this embodiment of the disclosure, after obtaining the verification result of the configuration change information, the verification result can be sent to the personnel handling the configuration change according to the preset contact method. For example, the verification result can be sent to the personnel handling the configuration change via SMS or email, or the verification result can be sent to the device associated with the personnel handling the configuration change via a pop-up window. For example, the associated device can be a computer or a mobile phone.

[0044] In the above embodiments, after obtaining the service to be configured and determining its configuration change information, target verification test cases corresponding to the service requirements of the service to be configured can be determined based on the mapping relationship. This allows for automatic determination of target verification test cases, improving the efficiency of configuration change processing. Subsequently, the configuration change information can be verified based on the target verification test cases to obtain the verification result. Compared with manual verification, this improves the accuracy of configuration change information verification and avoids missed detections caused by manual verification. At this point, the verification result can be used to determine whether the configuration change information contains abnormal information. Therefore, the configuration change information can be verified before executing the service to be configured, preventing the application of abnormal information to the service and ensuring the quality of configuration changes.

[0045] In an optional implementation, after obtaining the service to be configured and determining the configuration change information that matches the service to be configured, the configuration status of the configuration change information can be determined, and if it is determined based on the configuration status that the configuration change information meets the verification requirements, the step of determining the target verification test case corresponding to the service requirements of the service to be configured based on the mapping relationship can be executed.

[0046] In the embodiments disclosed in this disclosure, the configuration change processing flow can be controlled by a state machine. In this case, the configuration status of the corresponding configuration change information can be determined by obtaining the configuration status of the configuration change in the state machine.

[0047] The configuration status of the configuration change information can be either unpublished or published.

[0048] In this embodiment of the disclosure, the fact that the configuration change information meets the verification requirements can be understood as: the configuration status of the configuration change information is an unpublished status.

[0049] At this point, if the configuration change information is determined to be in an unpublished state based on the configuration status of the configuration change information, the step of determining the target verification test case corresponding to the business requirements of the service to be configured based on the mapping relationship can be executed.

[0050] In the above embodiments, the configuration status of the configuration change information can be obtained to determine whether the configuration change information meets the verification requirements. The method of verifying the configuration change information only after determining that the configuration change information meets the verification requirements can improve the effectiveness of verifying the configuration change information and avoid wasting computing resources.

[0051] In an optional implementation, the mapping relationship includes an identifier mapping relationship. In this case, for the above S103: determining the target verification test case corresponding to the service requirements of the service to be configured based on the mapping relationship, specifically includes the following steps:

[0052] Step S21: Determine the service requirement identifier of the service to be configured;

[0053] Step S22: Determine the use case identifier that matches the business requirement identifier based on the identifier mapping relationship; wherein, the identifier mapping relationship is used to indicate the mapping relationship between the business requirement identifier of each type of business requirement and the use case identifier of each verification use case;

[0054] Step S23: Determine the target verification use case based on the matching use case identifier.

[0055] In this embodiment of the disclosure, the business requirement identifier can indicate the business requirement of the service to be configured. For example, if the business requirement of the service to be configured is a card binding requirement, then the business requirement identifier of the service to be configured is the card binding identifier. Alternatively, if the business requirement of the service to be configured is a merchant number configuration requirement, then the business requirement identifier of the service to be configured is the merchant configuration identifier, etc. The business requirement identifier of the service to be configured can be one or multiple.

[0056] In this embodiment of the disclosure, the identifier mapping relationship may include business requirement identifiers for various types of business requirements and use case identifiers corresponding to the business requirement identifiers. At this time, the use case identifier and the business requirement identifier may be the same. In this case, the use case identifier that matches the business requirement identifier of the business to be configured can be determined based on the identifier mapping relationship, and the target verification use case can be determined based on the matching use case identifier.

[0057] In one possible implementation, the number of test case identifiers for each verification test case can be one or more. In this case, the test case identifier tree formed by the test case identifiers corresponding to each verification test case can be determined according to the association relationship between the test case identifiers corresponding to each verification test case (e.g., inclusion relationship, hierarchical relationship, etc.).

[0058] At this point, the position of the use case identifier that matches the business requirement identifier in the use case identifier tree can be determined. Based on the identifier position, the use case identifier tree, and the verification use cases corresponding to each use case identifier in the use case identifier tree, the target verification use case corresponding to the business requirement of the business to be configured can be determined.

[0059] In the above implementation, the target verification case can be determined by identifying the service requirement identifier of the service to be configured and by determining the corresponding identifier mapping relationship between the service requirement identifier and the test case identifier of each verification test case. This can save time in determining the target verification case and improve the determination efficiency.

[0060] In an optional implementation, when there are multiple target verification cases, for S105: verifying the configuration change information based on the target verification cases to obtain the verification result of the configuration change information, specifically including the following steps:

[0061] Step S31: Obtain multiple test case parameters of the target verification test case;

[0062] Step S32: Determine the test case parameters that match each of the target verification test cases from the plurality of test case parameters;

[0063] Step S33: Based on the matching test case parameters and the corresponding target verification case, perform verification processing on the configuration change information to obtain the verification result.

[0064] In this embodiment of the disclosure, the multiple test case parameters of the target verification test case may include a first type of parameter and a second type of parameter; wherein, the first type of parameter is a parameter determined based on the configuration change information, and the second type of parameter is a static parameter that does not change during the execution of the target verification test case.

[0065] Here, the first type of parameter for the target validation test case can be configuration information from the configuration change information, such as a merchant number or a card number. Alternatively, the first type of parameter for the target validation test case can also be a dynamic parameter generated based on the configuration information from the configuration change information. For example, if the configuration information in the configuration change information is a card number, then the dynamic parameter generated based on that configuration information can be the account balance of the account corresponding to that card number.

[0066] In this embodiment of the disclosure, a corresponding parameter generation rule can be preset for each target verification test case, and the target verification test case can be executed according to the parameter generation rule to obtain the first type of parameter.

[0067] In this embodiment of the disclosure, the second type of parameter of the target verification test case is a static parameter that does not change during the execution of the target verification test case. In this case, the second type of parameter corresponding to the target verification test case can be determined by the parameter mapping relationship, wherein the parameter mapping relationship indicates the mapping relationship between each verification test case and each static parameter.

[0068] In this embodiment of the disclosure, the process of obtaining multiple test case parameters of the target verification test case can be described as follows: Figure 2 As shown.

[0069] Depend on Figure 2 It can be seen that after identifying the configuration change information that matches the service to be configured, the first type of parameters of the target verification test case can be determined based on the configuration information in the configuration change information, such as... Figure 2 The first type of parameter is 1. Afterwards, the parameter mapping relationship can be accessed, and the static parameters in the parameter mapping relationship can be obtained to get the second type of parameter corresponding to the target verification test case.

[0070] In this embodiment of the disclosure, after obtaining the first type of parameter 1 and the second type of parameter, the first type of parameter can be calculated based on the first type of parameter 1 and / or the second type of parameter according to the parameter generation rule, such as... Figure 2 The first type of parameter 2 in the text.

[0071] In this embodiment of the disclosure, after obtaining multiple test parameters of the target verification case, the test case parameter that matches each target verification case can be determined from the multiple test case parameters.

[0072] In practice, firstly, parameter labels for each test case parameter can be determined, resulting in multiple parameter labels. Then, target parameter labels associated with each target verification case can be identified from these multiple parameter labels. Next, the test case parameters corresponding to the target parameter labels can be determined as the test case parameters that match the target verification case.

[0073] In this embodiment of the disclosure, the parameter label of the test case parameter can correspond to the parameter name of the test case parameter. For example, if the parameter name corresponding to the test case parameter is A, the parameter label of the test case parameter can be set to A, or the parameter label of the test case parameter can be set to A'.

[0074] In this embodiment of the disclosure, after determining the parameter label corresponding to each test case parameter and obtaining multiple parameter labels, the target parameter label associated with each target verification case can be determined from the multiple parameter labels.

[0075] Specifically, the business execution mode corresponding to the business requirement of the target verification case can be determined. Then, the target parameter label associated with the target verification case can be determined according to the parameter name of the test parameter required by the business execution mode.

[0076] Then, the test case parameters corresponding to the target parameter label can be determined as test case parameters that match the target verification case.

[0077] In this embodiment of the disclosure, each target verification case may correspond to at least one test case parameter group, each test case parameter group may contain at least one test case parameter, and the test case parameters contained in different test case parameter groups may be the same or different.

[0078] At this time, as Figure 2 As shown, the configuration change information can be verified based on at least one test case parameter group and the corresponding target verification case to obtain the verification result of the configuration change information.

[0079] In the above implementation, the target parameter label associated with the target verification case can be determined from multiple parameter labels corresponding to each target verification case, and the test case parameter corresponding to the target parameter label can be determined as the test case parameter matching the target verification case. In this way, the test case parameter corresponding to the target verification case can be determined by the target parameter label, and accurate and comprehensive test case parameters matching the target verification case can be filtered from multiple test case parameters. This avoids parameter abnormality errors during the verification of configuration change information by the target verification case and improves the verification accuracy.

[0080] In an optional implementation, for S105: the configuration change information is validated based on the target validation case to obtain the validation result of the configuration change information, specifically including the following steps:

[0081] Step S41: Obtain the target simulation environment for the configuration change information;

[0082] Step S42: Based on the target verification case, the configuration change information is verified in the target simulation environment to obtain the verification result.

[0083] In this embodiment of the disclosure, the target simulation environment can be understood as a simulation environment corresponding to the production environment of the service to be configured. In this case, the overall deployment architecture of the target simulation environment is the same as that of the production environment of the service to be configured, and the functions to be implemented are the same.

[0084] In this embodiment of the disclosure, the target simulation environment for obtaining the configuration change information can be obtained in the following ways.

[0085] First, determine the preset simulation environment that matches the configuration change information.

[0086] Next, obtain the environment call link of the preset simulation environment.

[0087] Then, the preset simulation environment can be invoked based on the environment call link to obtain the target simulation environment.

[0088] In this embodiment of the disclosure, a simulation environment corresponding to the service to be configured can be determined based on the production environment of the service to be configured, and the simulation environment can be determined as the preset simulation environment for the configuration change information of the service to be configured.

[0089] In this embodiment of the disclosure, there can be multiple services to be configured. These multiple services to be configured can correspond to different production environments. At this time, a corresponding simulation environment can be pre-set for each production environment to obtain multiple preset simulation environments.

[0090] Then, a preset simulation environment that matches the configuration change information can be selected from these multiple preset simulation environments.

[0091] In this embodiment of the disclosure, after determining a preset simulation environment that matches the configuration change information, the environment call link corresponding to the preset simulation environment can be obtained, and the preset simulation environment can be called based on the environment call link to obtain the target simulation environment. Here, the environment call link of the preset simulation environment is different from the environment call link corresponding to the production environment.

[0092] Here, the environment call link of the preset simulation environment can be understood as the domain name and / or gateway corresponding to the preset simulation environment.

[0093] In this embodiment of the disclosure, after obtaining the target simulation environment of the configuration change information, the configuration change information can be verified in the target simulation environment based on the target verification test cases to obtain the verification result.

[0094] In practice, the databases of the target simulation environment and the corresponding production environment can be synchronized. Then, based on the target verification test cases, the data in the database of the target simulation environment after data synchronization can be called to verify the configuration change information and obtain the verification results.

[0095] In the above embodiments, the target simulation environment for configuration change information can be obtained, and the configuration change information can be verified in the target simulation environment based on the target verification test cases. This avoids the impact of the configuration change information verification process on the production environment, achieving non-intrusive verification of the production environment and improving the accuracy of configuration change information verification. Furthermore, verifying configuration change information through the target simulation environment enables automated verification, saving labor costs.

[0096] In an optional implementation, the application diagram of the configuration change processing method provided in this disclosure can be as follows: Figure 3 As shown.

[0097] Depend on Figure 3 As can be seen, after the configuration backend detects the business requirements of the business to be configured submitted by the demand backend, it can generate a configuration change work order corresponding to the business requirements. At this time, the configuration change work order can contain configuration change information.

[0098] Each business requirement can be associated with at least one configuration backend (e.g., Figure 3 In the configuration backend 1, ... configuration backend m), each configuration backend can generate configuration work orders for the associated business requirements.

[0099] Afterwards, all configuration work orders can be submitted to the target simulation environment for verification processing to obtain the verification results (that is, the configuration change information is verified in the target simulation environment).

[0100] In one possible implementation, when verifying configuration change information in the target simulation environment, the framework diagram of the target simulation environment can be as follows: Figure 4 As shown.

[0101] Depend on Figure 4 It can be seen that we can first determine the business requirement identifier corresponding to the business to be configured, and then determine the use case identifier that matches the business requirement identifier.

[0102] Assume that the business requirement identifier corresponding to business requirement 1 is as follows: Figure 4 The business requirement identifiers shown are as follows: "Business Requirement Identifier 1" and "Business Requirement 2" respectively. Figure 4 The “Business Requirement Identifier 2” shown here indicates that the use case identifier 1 that matches the “Business Requirement Identifier 1” is “Business Requirement Identifier 1”, and the use case identifier 2 that matches the “Business Requirement Identifier 2” is “Business Requirement Identifier 2”.

[0103] Then, based on this use case identifier, the target validation use case corresponding to the business requirements of the service to be configured can be determined, for example, such as Figure 4 As shown, the target verification case corresponding to business requirement 1 is "target verification case 1", and the target verification case corresponding to business requirement 2 is "target verification case 2".

[0104] Afterwards, the corresponding test case parameters can be called through the target validation test case (e.g., ...). Figure 4 The first and second types of parameters shown), API interface (e.g., ... Figure 4 The payment and transaction functions shown (e.g., payment, transaction, and functional modules) Figure 4 The configuration change information is verified using modules 1 and 2 shown, as well as data from the database, to obtain the verification result of the configuration change information.

[0105] In this embodiment of the disclosure, if it is determined from the verification results that the configuration change information contains abnormal information, an abnormality alert can be generated and sent to the target staff.

[0106] If the verification results determine that the configuration change information does not contain any abnormal information, a verification success message can be generated. At this time, the verification success message can be displayed, and the configuration change information can be sent to the configuration change release process.

[0107] Those skilled in the art will understand that, in the above-described method of the specific implementation, the order in which each step is written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0108] Based on the same inventive concept, this disclosure also provides a configuration change processing device corresponding to the configuration change processing method. Since the principle of the device in this disclosure for solving the problem is similar to the configuration change processing method described above in this disclosure, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0109] Reference Figure 5 The diagram shown is a schematic of a configuration change processing device provided in an embodiment of this disclosure. The device includes: an acquisition module 51, a determination module 52, and a verification module 53; wherein,

[0110] The acquisition module 51 is used to acquire the service to be configured and determine the configuration change information that matches the service to be configured.

[0111] The determination module 52 is used to determine the target verification test cases corresponding to the business requirements of the service to be configured based on the mapping relationship; wherein, the mapping relationship is used to indicate the mapping relationship between each type of business requirement and each verification test case;

[0112] The verification module 53 is used to perform verification processing on the configuration change information based on the target verification test case to obtain the verification result of the configuration change information; wherein, the verification result is used to indicate whether the configuration change information contains abnormal information.

[0113] In the above embodiments, after obtaining the service to be configured and determining its configuration change information, target verification test cases corresponding to the service requirements of the service to be configured can be determined based on the mapping relationship. This allows for automatic determination of target verification test cases, improving the efficiency of configuration change processing. Subsequently, the configuration change information can be verified based on the target verification test cases to obtain the verification result. Compared with manual verification, this improves the accuracy of configuration change information verification and avoids missed detections caused by manual verification. At this point, the verification result can be used to determine whether the configuration change information contains abnormal information. Therefore, the configuration change information can be verified before executing the service to be configured, preventing the application of abnormal information to the service and ensuring the quality of configuration changes.

[0114] In one possible implementation, the determining module 52 is further configured to: determine the service requirement identifier of the service to be configured when the mapping relationship includes an identifier mapping relationship; determine the use case identifier that matches the service requirement identifier based on the identifier mapping relationship; wherein the identifier mapping relationship is used to indicate the mapping relationship between the service requirement identifier of each type of service requirement and the use case identifier of each verification use case; and determine the target verification use case based on the matching use case identifier.

[0115] In one possible implementation, the verification module 53 is further configured to: when there are multiple target verification cases, obtain multiple test case parameters of the target verification cases; determine the test case parameters that match each target verification case from the multiple test case parameters; and perform verification processing on the configuration change information based on the matching test case parameters and the corresponding target verification cases to obtain the verification result.

[0116] In one possible implementation, the verification module 53 is further configured to: determine the parameter label of each of the test case parameters to obtain a plurality of parameter labels; determine the target parameter label associated with each of the target verification cases from the plurality of parameter labels; and determine the test case parameter corresponding to the target parameter label as the test case parameter that matches the target verification case.

[0117] In one possible implementation, the plurality of test case parameters include a first type of parameter and a second type of parameter of the target verification test case; wherein, the first type of parameter is a parameter determined based on the configuration change information, and the second type of parameter is a static parameter of the target verification test case that does not change during execution.

[0118] In one possible implementation, the verification module 53 is further configured to: obtain the target simulation environment of the configuration change information; perform verification processing on the configuration change information in the target simulation environment based on the target verification test case, and obtain the verification result.

[0119] In one possible implementation, the verification module 53 is further configured to: determine a preset simulation environment that matches the configuration change information; obtain an environment call link for the preset simulation environment; and call the preset simulation environment based on the environment call link to obtain the target simulation environment.

[0120] In one possible implementation, the device is further configured to: determine the configuration status of the configuration change information; and, if the configuration change information meets the verification requirements based on the configuration status, execute the step of determining a target verification case corresponding to the service requirements of the service to be configured based on the mapping relationship.

[0121] The processing flow of each module in the device and the interaction flow between each module can be referred to the relevant descriptions in the above method embodiments, and will not be detailed here.

[0122] Corresponding to Figure 1 In addition to the method for handling configuration changes, this disclosure also provides a computer device 600, such as... Figure 6 The diagram shown is a structural schematic of a computer device 600 provided in an embodiment of this disclosure, including:

[0123] The computer device 600 comprises a processor 61, a memory 62, and a bus 63. The memory 62 stores execution instructions and includes main memory 621 and external memory 622. Main memory 621, also called internal memory, temporarily stores computational data in the processor 61, as well as data exchanged with external memory such as a hard disk. The processor 61 exchanges data with external memory 622 through main memory 621. When the computer device 600 is running, the processor 61 communicates with the memory 62 through the bus 63, causing the processor 61 to execute the following instructions:

[0124] Obtain the service to be configured and determine the configuration change information that matches the service to be configured;

[0125] The target verification test cases corresponding to the business requirements of the service to be configured are determined based on the mapping relationship; wherein, the mapping relationship is used to indicate the mapping relationship between each type of business requirement and each verification test case;

[0126] The configuration change information is validated based on the target validation test case to obtain the validation result of the configuration change information; wherein, the validation result is used to indicate whether the configuration change information contains abnormal information.

[0127] This disclosure also provides a computer-readable storage medium storing a computer program that, when executed by a processor, performs the steps of the configuration change processing method described in the above-described method embodiments. The storage medium may be a volatile or non-volatile computer-readable storage medium.

[0128] This disclosure also provides a computer program product carrying program code. The program code includes instructions that can be used to execute the steps of the configuration change processing method described in the above method embodiments. For details, please refer to the above method embodiments, which will not be repeated here.

[0129] The aforementioned computer program product can be implemented through hardware, software, or a combination thereof. In one optional embodiment, the computer program product is specifically embodied in a computer storage medium; in another optional embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0130] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. In the several embodiments provided in this disclosure, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division; in actual implementation, there may be other division methods. Furthermore, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection may be through some communication interfaces; the indirect coupling or communication connection of devices or modules may be electrical, mechanical, or other forms.

[0131] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0132] In addition, the functional modules in the various embodiments of this disclosure can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module.

[0133] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0134] Finally, it should be noted that the above-described embodiments are merely specific implementations of this disclosure, used to illustrate the technical solutions of this disclosure, and not to limit it. The protection scope of this disclosure is not limited thereto. Although this disclosure has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this disclosure. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this disclosure, and should all be covered within the protection scope of this disclosure. Therefore, the protection scope of this disclosure should be determined by the protection scope of the claims.

Claims

1. A method for processing configuration changes, characterized in that, include: Obtain the service to be configured and determine the configuration change information that matches the service to be configured. The configuration change information includes information generated based on the service requirements of the service to be configured. The target verification test cases corresponding to the business requirements of the service to be configured are determined based on the mapping relationship; wherein, the mapping relationship is used to indicate the mapping relationship between each type of business requirement and each verification test case; The configuration change information is validated based on the target validation test case to obtain a validation result for the configuration change information; wherein, the validation result indicates whether the configuration change information contains abnormal information. The mapping relationship includes an identifier mapping relationship. Determining the target verification test case corresponding to the business requirements of the service to be configured based on the mapping relationship includes: Determine the service requirement identifier of the service to be configured; Based on the identifier mapping relationship, a use case identifier that matches the business requirement identifier is determined; wherein, the identifier mapping relationship is used to indicate the mapping relationship between the business requirement identifier of each type of business requirement and the use case identifier of each verification use case; The target validation use case is determined based on the matching use case identifier. The number of target verification cases is multiple; the verification processing of the configuration change information based on the target verification cases to obtain the verification result of the configuration change information includes: Obtain multiple test case parameters for the target verification test case; Among the plurality of test case parameters, determine the test case parameters that match each of the target verification cases; Based on the matching test case parameters and the corresponding target verification test cases, the configuration change information is verified to obtain the verification result; Verifying the configuration change information based on the target verification test case includes verifying the configuration change information in the target simulation environment based on the target verification test case.

2. The method according to claim 1, characterized in that, The step of determining the test case parameters that match each target verification test case from the plurality of test case parameters includes: Determine the parameter label for each of the test case parameters to obtain multiple parameter labels; Determine the target parameter label associated with each of the target verification test cases from the plurality of parameter labels; The test case parameters corresponding to the target parameter label are determined as test case parameters that match the target verification test case.

3. The method according to claim 1, characterized in that, The multiple test case parameters include a first type of parameter and a second type of parameter of the target verification test case; wherein, the first type of parameter is a parameter determined based on the configuration change information, and the second type of parameter is a static parameter of the target verification test case that does not change during execution.

4. The method according to claim 1, characterized in that, The step of verifying the configuration change information based on the target verification test case to obtain the verification result of the configuration change information includes: The target simulation environment for obtaining the configuration change information; Based on the target verification test case, the configuration change information is verified in the target simulation environment to obtain the verification result.

5. The method according to claim 4, characterized in that, The target simulation environment for obtaining the configuration change information includes: Determine a preset simulation environment that matches the configuration change information; Obtain the environment call link of the preset simulation environment; The target simulation environment is obtained by calling the preset simulation environment based on the environment call link.

6. The method according to claim 1, characterized in that, The method further includes: Determine the configuration status of the configuration change information; If, based on the configuration status, it is determined that the configuration change information meets the verification requirements, the step of determining the target verification test case corresponding to the business requirements of the service to be configured is executed based on the mapping relationship.

7. A configuration change processing apparatus, characterized in that, include: The acquisition module is used to acquire the service to be configured and determine the configuration change information that matches the service to be configured. The configuration change information includes information generated based on the service requirements of the service to be configured. The determination module is used to determine the target verification test cases corresponding to the business requirements of the service to be configured based on the mapping relationship; wherein, the mapping relationship is used to indicate the mapping relationship between each type of business requirement and each verification test case; The verification module is used to perform verification processing on the configuration change information based on the target verification test case, and obtain the verification result of the configuration change information; wherein, the verification result is used to indicate whether the configuration change information contains abnormal information. The mapping relationship includes an identifier mapping relationship. Determining the target verification test case corresponding to the business requirements of the service to be configured based on the mapping relationship includes: Determine the service requirement identifier of the service to be configured; Based on the identifier mapping relationship, a use case identifier that matches the business requirement identifier is determined; wherein, the identifier mapping relationship is used to indicate the mapping relationship between the business requirement identifier of each type of business requirement and the use case identifier of each verification use case; The target validation use case is determined based on the matching use case identifier. The number of target verification cases is multiple; the verification processing of the configuration change information based on the target verification cases to obtain the verification result of the configuration change information includes: Obtain multiple test case parameters for the target verification test case; Among the plurality of test case parameters, determine the test case parameters that match each of the target verification cases; Based on the matching test case parameters and the corresponding target verification test cases, the configuration change information is verified to obtain the verification result; Verifying the configuration change information based on the target verification test case includes verifying the configuration change information in the target simulation environment based on the target verification test case.

8. A computer device, characterized in that, include: The computer device includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the computer device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, the steps of the configuration change processing method as described in any one of claims 1 to 6 are performed.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the configuration change processing method as described in any one of claims 1 to 6.

Images