CN116452208B - Method, device, equipment and medium for determining change transaction code - Google Patents

Method, device, equipment and medium for determining change transaction code Download PDF

Info

Publication number
CN116452208B
CN116452208B CN202310731057.8A CN202310731057A CN116452208B CN 116452208 B CN116452208 B CN 116452208B CN 202310731057 A CN202310731057 A CN 202310731057A CN 116452208 B CN116452208 B CN 116452208B
Authority
CN
China
Prior art keywords
transaction code
change
determining
calling
target transaction
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202310731057.8A
Other languages
Chinese (zh)
Other versions
CN116452208A (en
Inventor
刘永昆
谢仁伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
CCB Finetech Co Ltd
Original Assignee
CCB Finetech Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by CCB Finetech Co Ltd filed Critical CCB Finetech Co Ltd
Priority to CN202310731057.8A priority Critical patent/CN116452208B/en
Publication of CN116452208A publication Critical patent/CN116452208A/en
Application granted granted Critical
Publication of CN116452208B publication Critical patent/CN116452208B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401Transaction verification
    • G06Q20/4012Verifying personal identification numbers [PIN]
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405Establishing or using transaction specific rules
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Computer Security & Cryptography (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Stored Programmes (AREA)

Abstract

The invention provides a method, a device, equipment and a medium for determining a change transaction code, which can be applied to the technical fields of computers and finance. The method comprises the following steps: determining a deployment package corresponding to the check point, wherein the deployment package comprises a dependency package; obtaining compiling file information according to the deployment package and the dependency package; obtaining a calling relation corresponding to the check point according to the compiling class file information; matching a calling method corresponding to a target transaction code with a calling relation to generate a transaction code calling chain, wherein the target transaction code is determined according to a deployment package; determining a change call chain occurring in a preset time period based on the transaction code call chain; and determining a change transaction code based on the change call chain. The method solves the difficult problem of transaction code change identification, is not limited by new and old versions, can quickly, accurately and effectively identify the change transaction code, is beneficial to realizing complete coverage of transaction code change and reduces the occurrence of production events.

Description

Method, device, equipment and medium for determining change transaction code
Technical Field
The present invention relates to the field of computer and financial technologies, and in particular, to a method, apparatus, device, and medium for determining a change transaction code.
Background
The transaction code is commonly used for managing business transaction, and the back of the transaction code comprises application logic and downstream business interface calling logic, so that the identification and influence analysis of the transaction code change are used as the identification of a test range, the verification of an upstream interface and a downstream interface and the influence analysis of a high-risk scene are important bases, and the transaction code change identification becomes a basic work in development test for realizing the safety management and control of a financial level.
In the process of implementing the invention, it is found that, based on the configuration change, the transaction code change is identified, and not all codes contained in the configuration library are necessarily applied, and the important business logic is possibly encapsulated in a dependent package or a dependent library, so that the transaction code change cannot be accurately identified. Based on the new version package and the old version package, the modification is identified, and the modification is influenced by the compiling version and the compiling environment, so that high misjudgment exists, the identified modification range is enlarged, and the identification result cannot be used.
Disclosure of Invention
In view of the above, the present invention provides a method, apparatus, device and medium for determining a change transaction code.
According to a first aspect of the present invention, there is provided a method of determining a change transaction code, comprising:
Determining a deployment package corresponding to the check point, wherein the deployment package comprises a dependency package;
obtaining compiling file information according to the deployment package and the dependency package;
obtaining a calling relation corresponding to the check point according to the compiling class file information;
matching a calling method corresponding to a target transaction code with a calling relation to generate a transaction code calling chain, wherein the target transaction code is determined according to a deployment package;
determining a change call chain occurring in a preset time period based on the transaction code call chain; and
based on the change call chain, a change transaction code is determined.
According to an embodiment of the present invention, a calling method corresponding to a target transaction code is matched with a calling relationship to generate a transaction code calling chain, including:
obtaining an entry method corresponding to the target transaction code according to the target transaction code;
executing a first query operation in the call relation to obtain an entry call method called by the entry method;
executing a second query operation according to the entry calling method to obtain a next method called by the entry calling method; and
and repeatedly executing the query operation until the next method cannot be queried, and obtaining a transaction code call chain.
According to an embodiment of the present invention, an entry method corresponding to a target transaction code is obtained according to the target transaction code, including:
Under the condition that the target transaction code is determined to be configured in the configuration file, obtaining an entry method corresponding to the target transaction code through the configuration file; and
and under the condition that the target transaction code is confirmed to be annotated on the entry method, intercepting and obtaining the entry method corresponding to the target transaction code through an annotation interceptor.
According to the embodiment of the invention, according to the deployment package and the dependency package, compiling class file information is obtained, and the method comprises the following steps:
and respectively carrying out decompression operation on the deployment package and the dependency package to a class level to obtain compiled class file information.
According to an embodiment of the present invention, further comprising:
and determining the target transaction code according to the configuration file or the annotation mark in the deployment package.
According to an embodiment of the present invention, determining a change call chain occurring within a preset period of time based on a transaction code call chain includes:
acquiring change content occurring in a preset time period from a configuration library;
identifying change content to obtain a change class and a method list; and
and determining the corresponding transaction code call chain as a change call chain when the change class and the method in the method list are determined to exist in the transaction code call chain.
According to an embodiment of the present invention, obtaining, from a configuration library, content of a change occurring in a preset period of time includes:
Determining a checked point according to the checked point and a preset time period; and
and according to the check point and the checked point, performing query operation on the configuration library to obtain change contents.
A second aspect of the present invention provides a device for determining a change transaction code, including:
the first determining module is used for determining a deployment package corresponding to the check point, wherein the deployment package comprises a dependency package;
the information acquisition module is used for acquiring compiling file information according to the deployment package and the dependence package;
the calling relation acquisition module is used for acquiring a calling relation corresponding to the check point according to the compiling class file information;
the generation module is used for matching a calling method corresponding to the target transaction code with a calling relation to generate a transaction code calling chain, wherein the target transaction code is determined according to the deployment package;
the second determining module is used for determining a change call chain which occurs in a preset time period based on the transaction code call chain; and
and the third determining module is used for determining the changed transaction code based on the changed call chain.
A third aspect of the present invention provides an electronic device comprising: one or more processors; and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of determining the altered transaction code described above.
The fourth aspect of the present invention also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-described method of determining a change transaction code.
The fifth aspect of the present invention also provides a computer program product comprising a computer program which when executed by a processor implements the method of determining a modified transaction code as described above.
According to the embodiment of the invention, compared with the method which is completely based on configuration change, the method which is used for identifying transaction code change can accurately identify class and method packaged in a dependent package or library by matching the calling method corresponding to the target transaction code with the calling relation, establish a complete transaction code calling chain, improve the identification rate and identify the transaction code calling chain; and determining a change call chain based on the transaction code call chain, and further identifying the change transaction code. The method solves the difficult problem of transaction code change identification, is not limited by new and old versions, can quickly, accurately and effectively identify the change transaction code, is beneficial to realizing complete coverage of transaction code change and reduces the occurrence of production events.
Drawings
The foregoing and other objects, features and advantages of the invention will be apparent from the following description of embodiments of the invention with reference to the accompanying drawings, in which:
FIG. 1 is an application scenario diagram illustrating a method of determining a change transaction code according to an embodiment of the present invention;
FIG. 2 is a flow chart illustrating a method of determining a change transaction code according to an embodiment of the invention;
FIG. 3 illustrates a method flow diagram for matching a calling method corresponding to a target transaction code with a calling relationship to generate a transaction code call chain in accordance with an embodiment of the invention;
FIG. 4 illustrates a flow chart of a method for determining a change call chain that occurs within a preset time period based on a transaction code call chain, in accordance with an embodiment of the present invention;
FIG. 5 is a flowchart of a method for acquiring changed content occurring within a preset time period from a configuration library according to an embodiment of the present invention;
FIG. 6 is a block diagram showing the construction of a device for determining a change transaction code according to an embodiment of the present invention; and
fig. 7 shows a block diagram of an electronic device adapted to implement a method of determining a change transaction code according to an embodiment of the invention.
Detailed Description
Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. It should be understood that the description is only illustrative and is not intended to limit the scope of the invention. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the invention. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the present invention.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.
Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
In the technical scheme of the invention, the related data (such as including but not limited to personal information of a user) are collected, stored, used, processed, transmitted, provided, invented, applied and the like, and all the processing accords with the regulations of related laws and regulations and does not violate the popular regulations of the public order.
In the technical scheme of the embodiment of the invention, the authorization or the consent of the user is obtained before the personal information of the user is obtained or acquired.
In the process of implementing the invention, the development and submission code change is found in the application development process, and a tester verifies the service case according to the requirement, but the identification of the code change influence range of the developer is a difficult problem, for example, a method is called by two transaction services, and the two transactions are necessarily influenced by adjusting the method, so that the two transactions are required to be further verified. Particularly in complex business systems, if there is no effective technical means to control the changes, defects are introduced into the production version, and the risk is further exposed, thus bringing loss to actual production and operation.
In the traditional transaction code change identification method, a demand analysis person identifies a change transaction code in a demand analysis link so as to determine an influence test range. Based on the configuration change identification transaction code change, from the engineering point of view, not all codes contained in the configuration library are necessarily applied, and the important business logic is possibly packaged in a dependent package or a dependent library, so that the transaction code change cannot be accurately identified. The modification is identified based on the new version package and the old version package, and because the modification is influenced by the compiling version and the compiling environment, high misjudgment exists, so that the identified modification range is enlarged, and the identification result cannot be used.
The embodiment of the invention provides a method for determining a change transaction code, which comprises the following steps: determining a deployment package corresponding to the check point, wherein the deployment package comprises a dependency package; obtaining compiling file information according to the deployment package and the dependency package; obtaining a calling relation corresponding to the check point according to the compiling class file information; matching a calling method corresponding to a target transaction code with a calling relation to generate a transaction code calling chain, wherein the target transaction code is determined according to a deployment package; determining a change call chain occurring in a preset time period based on the transaction code call chain; and determining a change transaction code based on the change call chain.
Fig. 1 shows an application scenario diagram of a method for determining a change transaction code according to an embodiment of the present invention.
As shown in fig. 1, the application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 is a medium used to provide a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The user may interact with the server 105 through the network 104 using at least one of the first terminal device 101, the second terminal device 102, the third terminal device 103, to receive or send messages, etc. Various communication client applications, such as a shopping class application, a web browser application, a search class application, an instant messaging tool, a mailbox client, social platform software, etc. (by way of example only) may be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103.
The first terminal device 101, the second terminal device 102, the third terminal device 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 105 may be a server providing various services, such as a background management server (by way of example only) providing support for websites browsed by the user using the first terminal device 101, the second terminal device 102, and the third terminal device 103. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.
It should be noted that the method for determining the change transaction code according to the embodiment of the present invention may be generally performed by the server 105. Accordingly, the device for determining the change transaction code according to the embodiment of the present invention may be generally disposed in the server 105. The method for determining the change transaction code provided by the embodiment of the present invention may also be performed by a server or a server cluster which is different from the server 105 and is capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103 and/or the server 105. Accordingly, the determination device for changing the transaction code provided by the embodiment of the present invention may be provided in a server or a server cluster that is different from the server 105 and is capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and/or the server 105.
It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
The following will describe a method for determining the change transaction code according to an embodiment of the present invention in detail with reference to fig. 2 to 5 based on the scenario described in fig. 1.
FIG. 2 is a flow chart illustrating a method of determining a change transaction code according to an embodiment of the invention.
As shown in FIG. 2, the method 200 for determining a modified transaction code in this embodiment includes operations S210-S260.
In operation S210, a deployment package corresponding to the checkpoint is determined, wherein the deployment package includes a dependency package.
According to the embodiment of the invention, the deployment package can be a source program code compiling result, a manually compiled packaging result or a pipeline automatic packaging result, and is not limited in the example. The deployment package corresponding to the checkpoint may be consistent with the configuration code corresponding to the checkpoint, i.e., no code changes are made in the middle. If a plurality of branches exist on the configuration, the configuration library codes of the deployment package and the corresponding check points are kept consistent according to whether the codes are consistent.
In operation S220, compiled class file information is obtained from the deployment package and the dependency package.
According to the embodiment of the invention, the compiling class file information can be obtained according to the configuration codes in the deployment package and the dependency package. And the decompression operation can be carried out on the deployment package and the dependency package to the class level to obtain the compiled class file information.
In operation S230, a calling relationship corresponding to the checkpoint is obtained according to the compiled class file information.
According to an embodiment of the present invention, the call relationship may be a one-to-one relationship. And obtaining the calling relation corresponding to the check point according to the class in the compiled class file information.
According to the embodiment of the invention, the method for establishing the call relationship can be realized by using byte codes or regularization and other technologies in the practical application process, and the method is not particularly limited in the embodiment.
For example, the call relationship can be established in two steps, the call relationship between the method and the method is established first, and then the global call relationship is established, so as to improve the efficiency of establishing the call relationship.
In operation S240, a calling method corresponding to the target transaction code is matched with the calling relationship, and a transaction code calling chain is generated, wherein the target transaction code is determined according to the deployment package.
According to the embodiment of the invention, the deployment package can further comprise: class, configuration file, etc. The target transaction code may be determined based on the profile information in the deployment package. The calling method corresponding to the target transaction code can be identified, and the transaction code calling chain is formed by matching the calling relation corresponding to the check point according to the calling method.
For example, a transaction code call chain may include transaction codes, classes, and call relationships between method elements and elements.
In operation S250, a change call chain occurring within a preset period of time is determined based on the transaction code call chain.
According to an embodiment of the present invention, the preset time period may be a time period between a checkpoint and a checkpointed. The checkpoints and the checked points may be version packing time points of the new version and the old version, or may be any two time points in sequence, which is not particularly limited in this embodiment.
For example, when automatically checking through a pipeline, the current time of the automatic check may be taken as a checked point, and the time when the automatic check submitted last time is completed may be taken as a checked point.
According to the embodiment of the invention, the method or class in the transaction code call chain can be compared and identified according to the change method or class in the preset time period, and if the change method or class in the preset time period exists in the transaction code call chain, the transaction code call chain can be used as the change call chain.
In operation S260, a modified transaction code is determined based on the change call chain.
According to the embodiment of the invention, the changed transaction code can be obtained according to the change call chain identification.
According to the embodiment of the invention, compared with the method which is completely based on configuration change, the method which is used for identifying transaction code change can accurately identify class and method packaged in a dependent package or library by matching the calling method corresponding to the target transaction code with the calling relation, establish a complete transaction code calling chain, improve the identification rate and identify the transaction code calling chain; and determining a change call chain based on the transaction code call chain, and further identifying the change transaction code. The method solves the difficult problem of transaction code change identification, is not limited by new and old versions, can quickly, accurately and effectively identify the change transaction code, is beneficial to realizing complete coverage of transaction code change and reduces the occurrence of production events.
According to the embodiment of the invention, the change call chain is determined, in the change transaction code is determined, the change can be identified through the call chain association and the code, the transaction code range influenced by each code submission or combination request can be accurately identified, the limitation of iteration version or product synchronization is avoided, the front-end input of the automatic test is applicable, and the method is not in the description range of the embodiment and is not further described.
FIG. 3 illustrates a method flow diagram for matching a calling method corresponding to a target transaction code with a calling relationship to generate a transaction code call chain, according to an embodiment of the invention.
As shown in fig. 3, the method 340 for generating the transaction code call chain according to the embodiment, which matches the call method corresponding to the target transaction code with the call relationship, may include operations S341 to S344.
In operation S341, an entry method corresponding to the target transaction code is obtained according to the target transaction code.
According to the embodiment of the invention, the entry method corresponding to the target transaction code can be obtained according to the configuration of the target transaction code.
For example, if the target transaction code is configured in the configuration file, the target transaction code may be directly read from the configuration file or the frame container instance, and the entry method corresponding to the target transaction code may be identified. If the transaction code is marked on the entry method through annotation, the entry method corresponding to the target transaction code can be obtained through interception by configuring a corresponding annotation interceptor and reading the transaction code from the initialization of the application container.
For example, in a container no-service (service) scenario, the transaction code or the entry method corresponding to the transaction code may be further identified by a flow arrangement configuration file through flow arrangement, and in an embodiment, the identification of the entry method corresponding to the transaction code is not limited.
In operation S342, a first query operation is performed in the call relationship, resulting in an entry call method called by the entry method.
According to the embodiment of the invention, the entry calling method called by the entry method can be obtained by inquiring the calling method in the calling relation.
In operation S343, according to the entry calling method, a second query operation is performed to obtain the next method called by the entry calling method.
According to the embodiment of the invention, the next method called by the entry calling method can be obtained by inquiring the entry calling method again in the calling relation.
In operation S344, the query operation is repeatedly performed until the next method cannot be queried, resulting in a transaction code call chain.
According to an embodiment of the present invention, the transaction code call chain may be expressed as: transaction code entry method 1 entry calling method 2 … entry calling method invokes the next method N. The calling method in the transaction code calling chain can be expressed as: class + connector + method.
According to the embodiment of the invention, the calling methods corresponding to all the target transaction codes determined according to the deployment package can be matched with the calling relations, and a transaction code calling chain is generated for the subsequent transaction code change identification. The calling relationship may represent an association relationship between calling methods.
For example, the calling method corresponding to the target transaction code may include method 1. The call relationship may be that method 1 calls method 2, method 2 calls method 4, method 4 calls method 3, and so on. The transaction code call chain may be expressed as: target transaction code method 1 method 2 method 4 method 3.
According to the embodiment of the invention, the class and the method encapsulated in the dependent package or library can be accurately identified by matching the calling method corresponding to the target transaction code with the calling relation, a complete transaction code calling chain is established, the identification rate is improved, and the quick, accurate and effective identification of the changed transaction code is facilitated.
According to an embodiment of the present invention, according to a target transaction code, an entry method corresponding to the target transaction code may include:
under the condition that the target transaction code is determined to be configured in the configuration file, obtaining an entry method corresponding to the target transaction code through the configuration file; and under the condition that the target transaction code is determined to be on the method corresponding to the target transaction code through the annotation mark, obtaining the entry method corresponding to the target transaction code through configuring the corresponding annotation interceptor.
According to the embodiment of the invention, under the condition that the target transaction code is determined to be configured in the configuration file, the identification of the corresponding relation between the target transaction code and the entry function can be completed through direct reading of the configuration file, and the entry method corresponding to the target transaction code is obtained. Under the condition that the target transaction code is determined to be on the method corresponding to the target transaction code through the annotation mark, the corresponding annotation interceptor is configured to read in when the application container is initialized, the identification of the corresponding relation between the target transaction code and the entry function is completed, and the entry method corresponding to the target transaction code is obtained.
For example, if the target transaction code is newly added, the entry function pair relationship corresponding to the target transaction code is newly added, and the change is also identified in the call chain, so as to identify the changed transaction code.
According to the embodiment of the invention, the entry method corresponding to the target transaction code is determined according to the configuration condition of the target transaction code, so that the subsequent query of the calling method through the entry method is facilitated, and a calling chain is further obtained. Compared with the traditional manual interpretation, the invention realizes automatic judgment of the change of the transaction code based on the call chain, and improves the efficiency and the recognition accuracy.
According to an embodiment of the present invention, obtaining compiled class file information according to a deployment package and a dependency package may include:
And respectively carrying out decompression operation on the deployment package and the dependency package to a class level to obtain compiled class file information.
According to an embodiment of the invention, the decompression operation may comprise a recursive decompression operation. The dependency package may be a dependency package of a business class, for which decompression is operated to class level, i.e. full-scale expansion to class level, for a call chain of full-scale methods.
According to an embodiment of the present invention, the deployment package may further include: class, configuration file, etc. In a byte code interpreted class language represented by Java, a file extension is expressed as war or jar.
According to the embodiment of the invention, the class and the method encapsulated in the dependent package or library can be accurately identified by operating the decompression operation of the deployment package and the dependent package to the class level, a complete transaction code call chain is established, and the identification rate is improved.
According to another embodiment of the present invention, the method for determining the change transaction code may further include, in addition to the operations S210 to S260, the steps of:
and determining the target transaction code according to the configuration file or the annotation mark in the deployment package.
According to the embodiment of the invention, the configuration file can comprise a configured code file, the configured code file contains transaction codes, and the transaction codes in the configured code file can be used as target transaction codes. The annotation mark can be marked on the method, and the target transaction code can be determined according to the transaction code of the annotation mark on the method.
According to the embodiment of the invention, the calling method corresponding to the target transaction code can be determined according to the configuration file or the annotation mark in the deployment package, and then the transaction code calling chain is finally obtained according to the matching calling relation of the calling method, so that the change calling chain can be accurately identified from the transaction code calling chain, and the quick identification of the change transaction code is facilitated.
FIG. 4 illustrates a flowchart of a method for determining a change call chain that occurs within a preset time period based on a transaction code call chain, according to an embodiment of the invention.
As shown in fig. 4, a method 450 for determining a change call chain occurring in a preset period of time based on a transaction code call chain in this embodiment includes operations S451 to S453.
In operation S451, the change content occurring in the preset period is acquired from the configuration library.
According to an embodiment of the invention, the preset time period may be a time period between a checkpoint and a checkpointed. The checkpoints and the checked points may be the packing time points of the new version and the old version, or may be any two time points in sequence, which is not particularly limited in this embodiment.
According to an embodiment of the invention, the configuration library may be a code hosting repository for code management. In this embodiment, the change content generated in the preset time period may be based on the change content between two time points, or may be the change content between two version points, or may be the change content of a certain time in the development process compared with the previous version point, which is not specifically limited in this example.
According to the embodiment of the invention, the change content can be positioned to the granularity of the method in the class, and the method is represented by: class + connector + method. The use of class prefixes may prevent the method from repeating.
The connector may be null and is consistent with the call chain of the subsequent transaction code, which is not specifically limited in this embodiment.
In operation S452, the change content is identified, and a change class and method list is obtained.
According to embodiments of the present invention, altering content may include adding, modifying, deleting code lines, and the like.
According to the embodiment of the invention, the change content can be further processed and represented by a class+connector+method, and the change class and method can be identified. The change class and method comprises a new adding method, a modification method and a deletion method.
According to the embodiment of the invention, the change content is identified, and a change class and a method list are obtained and used for identifying a change call chain.
In operation S453, in the case where it is determined that the change class and the method in the method list exist in the transaction code call chain, the corresponding transaction code call chain is determined as the change call chain.
According to the embodiment of the present invention, the change class and the method list obtained in operation S452 may be traversed to determine whether a method exists in the transaction code call chain list one by one. If the transaction code call chain exists in a certain transaction code call chain, the transaction code call chain is identified as a change call chain. Because transaction codes exist in the change call chain, changed transaction codes can be obtained, and a full change transaction code list can be obtained after combination.
According to the embodiment of the invention, the change call chain is determined, or the transaction code call chain can be traversed first, then the change method is matched, the same result can be obtained, and the improper limitation to the embodiment is not constituted in concrete implementation.
According to the embodiment of the invention, based on the transaction code call chain, the change call chain generated in the preset time period is determined, so that the change transaction code is obtained, and compared with the method for identifying the change based on the new version package and the old version package, the method is not influenced by the compiled version and the environment, the method change range can be accurately identified, and the identification result is more accurate. The method solves the difficult problem of changing and identifying the transaction code, is not limited by new and old versions, and can quickly, accurately and effectively identify the changed transaction code.
Fig. 5 shows a flowchart of a method for acquiring changed content occurring within a preset time period from a configuration library according to an embodiment of the present invention.
As shown in fig. 5, the method 5510 of obtaining the change content occurring in the preset time period from the configuration library in this embodiment may include operations S5511 to S5512.
In operation S5511, a checkpointed is determined according to the checkpointed and the preset period.
In operation S5512, a query operation is performed on the configuration library according to the checkpoints and the checkpoints, and changed contents are obtained.
According to the embodiment of the invention, the change content can be obtained through the configuration command. Wherein, the change content can comprise adding, modifying, deleting code lines and the like. The modification content may also be obtained by regularization. In view of the differences in code configuration inventory, no specific limitation is made in the embodiment of the present invention.
According to an embodiment of the invention, a query instruction may be sent to a configuration library. The instruction content of the query instruction may include: configuration library information, start time, end time from checkpoints and checkpoints. The instruction content of the query instruction may further include: code branches, submits, or requests information to further define the scope of the change.
According to the embodiment of the invention, the changing content generated in the preset time period is acquired from the configuration library, so that when the changing transaction code is determined, the changing class and the method list are identified through the changing content, and further, the changing call chain is determined, and the quick, accurate and effective identification of the changing transaction code is facilitated.
According to the embodiment of the invention, the modification content identified by the configuration library comprises the transaction code contained in the code, and the obtained modification content is used for modifying the part.
In the implementation process, transaction codes corresponding to a single application deployment package can be distributed in different configuration libraries, and the change transaction codes identified in the embodiment of the invention need to be further aggregated to obtain the total change transaction codes of the application deployment package.
Based on the method for determining the changed transaction code, the invention also provides a device for determining the changed transaction code. The device will be described in detail below in connection with fig. 6.
Fig. 6 is a block diagram showing a configuration of a device for determining a change transaction code according to an embodiment of the present invention.
As shown in fig. 6, the determining apparatus 600 for changing a transaction code of this embodiment includes a first determining module 610, an information acquiring module 620, a calling relationship acquiring module 630, a generating module 640, a second determining module 650, and a third determining module 660.
The first determining module 610 is configured to determine a deployment package corresponding to the checkpoint, where the deployment package includes a dependency package. In an embodiment, the first determining module 610 may be configured to perform the operation S210 described above, which is not described herein.
The information obtaining module 620 is configured to obtain compiled class file information according to the deployment package and the dependency package. In an embodiment, the information obtaining module 620 may be configured to perform the operation S220 described above, which is not described herein.
The call relation obtaining module 630 is configured to obtain a call relation corresponding to the checkpoint according to the compiled class file information. In an embodiment, the call relationship obtaining module 630 may be configured to perform the operation S230 described above, which is not described herein.
The generating module 640 is configured to match a calling method corresponding to a target transaction code with a calling relationship, and generate a transaction code calling chain, where the target transaction code is determined according to the deployment package. In an embodiment, the generating module 640 may be configured to perform the operation S240 described above, which is not described herein.
The second determining module 650 is configured to determine, based on the transaction code call chain, a change call chain that occurs within a preset time period. In an embodiment, the second determining module 650 may be configured to perform the operation S250 described above, which is not described herein.
The third determining module 660 is configured to determine the modified transaction code based on the modified call chain. In an embodiment, the third determining module 660 may be configured to perform the operation S260 described above, which is not described herein.
According to an embodiment of the present invention, the generating module 640 includes a first sub-generating unit, a second sub-generating unit, a third sub-generating unit, and a fourth sub-generating unit.
The first sub-generation unit is used for obtaining an entry method corresponding to the target transaction code according to the target transaction code.
The second sub-generating unit is used for executing the first query operation in the calling relation to obtain an entry calling method called by the entry method.
And the third sub-generating unit is used for executing a second query operation according to the entry calling method to obtain the next method called by the entry calling method.
The fourth sub-generating unit is used for repeatedly executing the query operation until the next method cannot be queried, and obtaining a transaction code call chain.
The means 600 for determining a change transaction code may further comprise a fourth determining module according to an embodiment of the present invention.
The fourth determining module is used for determining the target transaction code according to the configuration file or the annotation mark in the deployment package.
According to an embodiment of the present invention, the second determining module 650 may include an acquire change content unit, an acquire change class, a method list unit, and a change call chain determining unit.
The change content acquisition unit is used for acquiring the change content generated in the preset time period from the configuration library.
The change class and method list acquisition unit is used for identifying change contents and obtaining a change class and method list.
The change call chain determining unit is used for determining the corresponding transaction code call chain as a change call chain when determining that the change class and the method in the method list exist in the transaction code call chain.
According to an embodiment of the present invention, the get change content unit may include a first subunit and a second subunit.
The first subunit is configured to determine a checked point according to the check point and a preset time period.
And the second subunit is used for executing query operation on the configuration library according to the check point and the checked point to obtain the change content.
Any of the first determination module 610, the information acquisition module 620, the call relationship acquisition module 630, the generation module 640, the second determination module 650, and the third determination module 660 may be combined in one module to be implemented, or any of the modules may be split into a plurality of modules, according to an embodiment of the present invention. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module. According to embodiments of the present invention, at least one of the first determination module 610, the information acquisition module 620, the call relationship acquisition module 630, the generation module 640, the second determination module 650, and the third determination module 660 may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-substrate, a system-on-package, an Application Specific Integrated Circuit (ASIC), or as hardware or firmware in any other reasonable manner of integrating or packaging the circuits, or as any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, at least one of the first determination module 610, the information acquisition module 620, the call relationship acquisition module 630, the generation module 640, the second determination module 650, and the third determination module 660 may be at least partially implemented as computer program modules, which when executed, may perform the respective functions.
According to the embodiment of the invention, compared with the method for identifying the transaction code change based on the configuration change, the method can accurately identify the class and the method packaged in the dependency package or the library by matching the calling method corresponding to the target transaction code with the calling relation, establish a complete transaction code calling chain, improve the identification rate and identify the transaction code calling chain; and determining a change call chain based on the transaction code call chain, and further identifying the change transaction code. The method solves the difficult problem of transaction code change identification, is not limited by new and old versions, can quickly, accurately and effectively identify the change transaction code, is beneficial to realizing complete coverage of transaction code change and reduces the occurrence of production events.
Fig. 7 shows a block diagram of an electronic device adapted to implement a method of determining a change transaction code according to an embodiment of the invention.
As shown in fig. 7, an electronic device 700 according to an embodiment of the present invention includes a processor 701 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. The processor 701 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. The processor 701 may also include on-board memory for caching purposes. The processor 701 may comprise a single processing unit or a plurality of processing units for performing different actions of the method flow according to an embodiment of the invention.
In the RAM 703, various programs and data necessary for the operation of the electronic apparatus 700 are stored. The processor 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. The processor 701 performs various operations of the method flow according to an embodiment of the present invention by executing programs in the ROM 702 and/or the RAM 703. Note that the program may be stored in one or more memories other than the ROM 702 and the RAM 703. The processor 701 may also perform various operations of the method flow according to embodiments of the present invention by executing programs stored in the one or more memories.
According to an embodiment of the invention, the electronic device 700 may further comprise an input/output (I/O) interface 705, the input/output (I/O) interface 705 also being connected to the bus 704. The electronic device 700 may also include one or more of the following components connected to the I/O interface 705: an input section 706 including a keyboard, a mouse, and the like; an output portion 707 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 708 including a hard disk or the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. The drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read therefrom is mounted into the storage section 708 as necessary.
The present invention also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present invention.
According to embodiments of the present invention, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to an embodiment of the invention, the computer-readable storage medium may include ROM 702 and/or RAM 703 and/or one or more memories other than ROM 702 and RAM 703 described above.
Embodiments of the present invention also include a computer program product comprising a computer program containing program code for performing the method shown in the flowcharts. The program code means for causing a computer system to carry out the methods provided by embodiments of the present invention when the computer program product is run on the computer system.
The above-described functions defined in the system/apparatus of the embodiment of the present invention are performed when the computer program is executed by the processor 701. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the invention.
In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed over a network medium in the form of signals, downloaded and installed via the communication section 709, and/or installed from the removable medium 711. The computer program may include program code that may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 709, and/or installed from the removable medium 711. The above-described functions defined in the system of the embodiment of the present invention are performed when the computer program is executed by the processor 701. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the invention.
According to embodiments of the present invention, program code for carrying out computer programs provided by embodiments of the present invention may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or in assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that the features recited in the various embodiments of the invention and/or in the claims may be combined in various combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the invention. In particular, the features recited in the various embodiments of the invention and/or in the claims can be combined in various combinations and/or combinations without departing from the spirit and teachings of the invention. All such combinations and/or combinations fall within the scope of the invention.
The embodiments of the present invention are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present invention. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the invention is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the invention, and such alternatives and modifications are intended to fall within the scope of the invention.

Claims (7)

1. A method of determining a change transaction code, the method comprising:
determining a deployment package corresponding to the check point, wherein the deployment package comprises a dependent package;
obtaining compiling file information according to the deployment package and the dependency package;
obtaining a calling relation corresponding to the check point according to the compiling class file information;
matching a calling method corresponding to a target transaction code with the calling relation to generate a transaction code calling chain, wherein the target transaction code is determined according to the deployment package;
determining a change call chain occurring in a preset time period based on the transaction code call chain; and
Determining a change transaction code based on the change call chain;
the determining, based on the transaction code call chain, a change call chain that occurs in a preset time period includes:
acquiring the changed content occurring in the preset time period from a configuration library;
identifying the change content to obtain a change class and a method list; and
determining the corresponding transaction code call chain as the change call chain under the condition that the change class and the method in the method list exist in the transaction code call chain;
the obtaining, from a configuration library, the change content that occurs in the preset time period includes:
determining a checked point according to the check point and the preset time period, wherein the check point comprises a new version packing time point, and the checked point comprises an old version packing time point; and
according to the check point and the checked point, query operation is carried out on the configuration library to obtain the change content; the configuration library is a code hosting warehouse and is used for code management, the inquiring operation comprises sending an inquiring instruction, and the instruction content of the inquiring instruction comprises: configuring library information, and obtaining starting time and ending time according to the check point and the checked point;
Wherein, the matching the calling method corresponding to the target transaction code with the calling relation to generate a transaction code calling chain comprises:
obtaining an entry method corresponding to the target transaction code according to the target transaction code;
executing a first query operation in the call relation to obtain an entry call method called by the entry method;
executing a second query operation according to the entry calling method to obtain a next method called by the entry calling method; and
repeatedly executing the query operation until the next method cannot be queried, and obtaining the transaction code call chain;
the method for obtaining the entry corresponding to the target transaction code according to the target transaction code comprises the following steps:
and under the condition that the target transaction code is confirmed to be annotated on the entrance method, intercepting the entrance method corresponding to the target transaction code by an annotation interceptor.
2. The method of claim 1, wherein the obtaining the entry method corresponding to the target transaction code according to the target transaction code further comprises:
in the case that the target transaction code is determined to be configured in a configuration file, the entry method corresponding to the target transaction code is obtained through the configuration file.
3. The method according to claim 1, wherein the obtaining compiled class file information from the deployment package and the dependency package includes:
and respectively carrying out decompression operation on the deployment package and the dependency package to a class level to obtain the compiled class file information.
4. The method according to claim 1, wherein the method further comprises:
and determining the target transaction code according to the configuration file or the annotation mark in the deployment package.
5. A device for determining a change transaction code, the device comprising:
the first determining module is used for determining a deployment package corresponding to the check point, wherein the deployment package comprises a dependent package;
the information acquisition module is used for acquiring compiling file information according to the deployment package and the dependency package;
the calling relation acquisition module is used for acquiring a calling relation corresponding to the check point according to the compiling class file information;
the generation module is used for matching a calling method corresponding to a target transaction code with the calling relation to generate a transaction code calling chain, wherein the target transaction code is determined according to the deployment package;
The second determining module is used for determining a change call chain which occurs in a preset time period based on the transaction code call chain; and
the third determining module is used for determining a modified transaction code based on the modified call chain;
the second determining module comprises an acquisition change content unit, an acquisition change class, a method list unit and a change call chain determining unit, wherein the acquisition change content unit is used for acquiring change content occurring in the preset time period from a configuration library, the acquisition change class and the method list unit are used for identifying the change content to obtain a change class and a method list, and the change call chain determining unit is used for determining a corresponding transaction code call chain as the change call chain when determining that a method in the change class and the method list exists in the transaction code call chain;
the method comprises the steps that a change content unit is obtained, wherein the change content unit comprises a first subunit and a second subunit, a checked point is determined according to the check point and the preset time period, the check point comprises a new version packing time point, the checked point comprises an old version packing time point, and the second subunit is used for executing query operation on the configuration library according to the check point and the checked point to obtain the change content; the configuration library is a code hosting warehouse and is used for code management, the inquiring operation comprises sending an inquiring instruction, and the instruction content of the inquiring instruction comprises: configuring library information, and obtaining starting time and ending time according to the check point and the checked point;
Wherein, the matching the calling method corresponding to the target transaction code with the calling relation to generate a transaction code calling chain comprises: obtaining an entry method corresponding to the target transaction code according to the target transaction code; executing a first query operation in the call relation to obtain an entry call method called by the entry method; executing a second query operation according to the entry calling method to obtain a next method called by the entry calling method; repeatedly executing the query operation until the next method cannot be queried, and obtaining the transaction code call chain;
the method for obtaining the entry corresponding to the target transaction code according to the target transaction code comprises the following steps: and under the condition that the target transaction code is confirmed to be annotated on the entrance method, intercepting the entrance method corresponding to the target transaction code by an annotation interceptor.
6. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-4.
7. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method according to any of claims 1-4.
CN202310731057.8A 2023-06-20 2023-06-20 Method, device, equipment and medium for determining change transaction code Active CN116452208B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310731057.8A CN116452208B (en) 2023-06-20 2023-06-20 Method, device, equipment and medium for determining change transaction code

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310731057.8A CN116452208B (en) 2023-06-20 2023-06-20 Method, device, equipment and medium for determining change transaction code

Publications (2)

Publication Number Publication Date
CN116452208A CN116452208A (en) 2023-07-18
CN116452208B true CN116452208B (en) 2023-09-22

Family

ID=87136063

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310731057.8A Active CN116452208B (en) 2023-06-20 2023-06-20 Method, device, equipment and medium for determining change transaction code

Country Status (1)

Country Link
CN (1) CN116452208B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112235128A (en) * 2020-09-23 2021-01-15 建信金融科技有限责任公司 Transaction path analysis method, device, server and storage medium
CN112559024A (en) * 2020-12-14 2021-03-26 建信金融科技有限责任公司 Method and device for generating transaction code change list
CN114049122A (en) * 2021-11-30 2022-02-15 中国建设银行股份有限公司 Service processing method and system
CN114706827A (en) * 2022-04-19 2022-07-05 中国银行股份有限公司 Automatic generation method and device for transaction link topology
CN114721943A (en) * 2022-03-28 2022-07-08 中国建设银行股份有限公司 Method and device for determining test range
CN114816971A (en) * 2021-01-19 2022-07-29 腾讯科技(深圳)有限公司 Data processing method, related equipment and storage medium

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140032345A1 (en) * 2012-07-30 2014-01-30 Bank Of America Corporation Authentication Using Transaction Codes on a Mobile Device

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112235128A (en) * 2020-09-23 2021-01-15 建信金融科技有限责任公司 Transaction path analysis method, device, server and storage medium
CN112559024A (en) * 2020-12-14 2021-03-26 建信金融科技有限责任公司 Method and device for generating transaction code change list
CN114816971A (en) * 2021-01-19 2022-07-29 腾讯科技(深圳)有限公司 Data processing method, related equipment and storage medium
CN114049122A (en) * 2021-11-30 2022-02-15 中国建设银行股份有限公司 Service processing method and system
CN114721943A (en) * 2022-03-28 2022-07-08 中国建设银行股份有限公司 Method and device for determining test range
CN114706827A (en) * 2022-04-19 2022-07-05 中国银行股份有限公司 Automatic generation method and device for transaction link topology

Also Published As

Publication number Publication date
CN116452208A (en) 2023-07-18

Similar Documents

Publication Publication Date Title
US11550599B2 (en) Method and apparatus for running applet
CN112463729B (en) Data file warehousing method and device, electronic equipment and medium
CN110865889B (en) Method and device for transmitting event between components
CN112799940A (en) Regression testing method, device, computer system and computer readable storage medium
CN110795331A (en) Software testing method and device
CN112559024A (en) Method and device for generating transaction code change list
CN116452208B (en) Method, device, equipment and medium for determining change transaction code
CN115982491A (en) Page updating method and device, electronic equipment and computer readable storage medium
CN112506781B (en) Test monitoring method, device, electronic equipment, storage medium and program product
CN113918525A (en) Data exchange scheduling method, system, electronic device, medium, and program product
CN112783903B (en) Method and device for generating update log
CN114253599A (en) Version deployment method, version deployment device, electronic device and storage medium
CN113032256A (en) Automatic test method, device, computer system and readable storage medium
CN113419740A (en) Program data stream analysis method and device, electronic device and readable storage medium
CN111859403A (en) Method and device for determining dependency vulnerability, electronic equipment and storage medium
CN114840429A (en) Method, apparatus, device, medium and program product for identifying version conflicts
CN115421738A (en) Version deployment method and device, electronic equipment and storage medium
CN114266547A (en) Method, device, equipment, medium and program product for identifying business processing strategy
CN116680184A (en) Code scanning method, device, electronic equipment and medium
CN116820565A (en) Source code processing method, device, electronic equipment and medium
CN115421779A (en) Object storage method and device, electronic equipment and computer readable storage medium
CN116450416A (en) Redundancy check method and device for software test cases, electronic equipment and medium
CN116702150A (en) Code scanning method, apparatus, device, storage medium, and program product
CN117472410A (en) Method, device and equipment for updating development tool in componentized development project
CN115016827A (en) Method, device, electronic equipment and medium for deploying JAVA application

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant