CN114860566A - Source code testing method and device, electronic equipment and storage medium - Google Patents

Source code testing method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN114860566A
CN114860566A CN202110157643.7A CN202110157643A CN114860566A CN 114860566 A CN114860566 A CN 114860566A CN 202110157643 A CN202110157643 A CN 202110157643A CN 114860566 A CN114860566 A CN 114860566A
Authority
CN
China
Prior art keywords
test
source code
code data
tested
function
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.)
Pending
Application number
CN202110157643.7A
Other languages
Chinese (zh)
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.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen 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 Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN202110157643.7A priority Critical patent/CN114860566A/en
Publication of CN114860566A publication Critical patent/CN114860566A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3684Test management for test design, e.g. generating new test cases

Abstract

The embodiment of the application provides a source code testing method and device, electronic equipment and a storage medium, and relates to the technical field of big data and cloud. The method comprises the following steps: acquiring source code data to be tested, wherein the source code data comprises a source code to be tested and test management information corresponding to the source code to be tested, the test management information is annotation information of the source code to be tested, and the test management information comprises at least one of test indication information or contact information of a target person; generating a corresponding test case based on the source code data; if the test management information comprises test indication information, testing the test case according to the test indication information to obtain a test result; and if the test management information comprises the contact information of the target person, sending the test result to the electronic equipment of the target person based on the contact information of the target person. The embodiment of the application can improve the testing efficiency.

Description

Source code testing method and device, electronic equipment and storage medium
Technical Field
The application relates to the technical field of big data and cloud, in particular to a source code testing method and device, electronic equipment and a storage medium.
Background
The unit test is to perform function-level test on the program code unit, and can complete verification of the minimum software design unit. In the front-end project, unit testing is also indispensable, and the unit testing in the front-end project can guarantee the correctness of the project, and avoids finding problems after the project is online.
The current unit testing framework at the front end is provided with mocha, jest and the like, so that the environment required by testing, data required by simulation testing, collection and operation of the compiled test case and judgment of the correctness of the execution of the test case can be provided. In the actual use process, the efficiency of testing the test case by adopting front-end unit test frames such as Jest, mocha and the like is low.
Disclosure of Invention
The application provides a source code testing method and device, electronic equipment and a storage medium, which can improve testing efficiency.
In one aspect, a source code testing method is provided, and the method includes:
acquiring source code data to be tested, wherein the source code data comprises a source code to be tested and test management information corresponding to the source code to be tested, the test management information is annotation information of the source code to be tested, and the test management information comprises at least one of test indication information or contact information of a target person;
generating a corresponding test case based on the source code data;
if the test management information comprises test indication information, testing the test case according to the test indication information to obtain a test result;
and if the test management information comprises the contact information of the target person, sending the test result to the electronic equipment of the target person based on the contact information of the target person.
In another aspect, there is provided a source code testing apparatus, including:
the code data acquisition module is used for acquiring source code data to be tested, wherein the source code data comprises a source code to be tested and test management information corresponding to the source code to be tested, the test management information is annotation information of the source code to be tested, and the test management information comprises at least one of test instruction information or contact information of a target person;
the test case generation module is used for generating a corresponding test case based on the source code data;
the test case testing module is used for testing the test case according to the test instruction information to obtain a test result when the test management information comprises the test instruction information;
and the test result sending module is used for sending the test result to the electronic equipment of the target person based on the contact information of the target person when the test management information comprises the contact information of the target person.
In one possible implementation manner, the source code data includes at least two source codes to be tested, and the test instruction information includes test priority information between the at least two source codes to be tested;
when the test case testing module tests the test case according to the test instruction information, the test case testing module is specifically configured to:
and testing the test cases corresponding to the source code data in sequence according to the test priority information between at least two source codes to be tested.
In one possible implementation manner, the source code data includes at least two source codes to be tested, the test management information further includes a test type of each source code to be tested, and the source code testing apparatus further includes:
and the test passing rate determining module is used for counting the test results of each test type and determining the test passing rate corresponding to each test type based on the test results of each test type.
In a possible implementation manner, the test case generation module is specifically configured to:
converting source code data into an abstract syntax tree, wherein each node on the abstract syntax tree corresponds to each function in the source code to be tested respectively, and the connection relation between the nodes corresponds to the inclusion relation between the functions;
and generating a corresponding test case according to the abstract syntax tree and the source code data.
In a possible implementation manner, when the test case generation module generates a corresponding test case according to the abstract syntax tree and the source code data, the test case generation module is specifically configured to:
determining nodes of a target structure by traversing the abstract syntax tree, wherein the target structure comprises a function calling structure;
if the corresponding content of the node of the target structure in the abstract syntax tree contains a calling function, determining the node of the target structure as a target node;
and obtaining a test case based on the corresponding content of each target node in the source code data.
In a possible implementation manner, when the test case generation module obtains a test case based on the content corresponding to each target node in the source code data, the test case generation module is specifically configured to:
generating each first test case set according to the corresponding content of each calling function in the source code data, wherein the test cases comprise each first test case set;
for any calling function, if the content of the calling function corresponding to the source code data comprises the called function of the calling function, generating a second test case set according to the content of the called function corresponding to the source code data, and merging the second test case set into the first test case set.
In one possible implementation, the calling function is a descriptor function, and the called function is an it function.
In yet another aspect, an electronic device is provided, comprising a memory and a processor, wherein the memory has stored therein a computer program; when running the computer program, the processor executes the source code testing method provided in any of the alternative embodiments of the present application.
In yet another aspect, a computer-readable storage medium is provided, in which a computer program is stored, and the computer program, when executed by a processor, implements the source code testing method provided in any of the alternative embodiments of the present application.
The technical scheme provided by the application brings the beneficial effects that:
compared with the prior art, the source code testing method, the source code testing device, the electronic equipment and the storage medium can generate the corresponding test case based on the source code data, the source code data can contain the test instruction information, the test case can be tested according to the test instruction information, the test instruction information can effectively indicate the test process of the test case, the test efficiency can be improved, the source code data can also contain the contact information of the target personnel, when the test case is tested to obtain the test result, the test result can be sent to the electronic equipment of the target person based on the contact information of the target person, so that the source code related person can be quickly positioned, the test result of the source code can be quickly informed to the related person, subsequent processing can be conveniently carried out, and the test efficiency can be effectively improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments of the present application will be briefly described below.
Fig. 1 is a schematic flowchart of a method for generating a test case according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a source code testing method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a source code testing apparatus according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present application.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
The embodiment of the application provides a source code testing method, which can generate a corresponding test case based on source code data, wherein the source code data can contain test indication information, the test case can be tested according to the test indication information, the test indication information can effectively indicate the testing process of the test case, the testing efficiency can be improved, the source code data can also contain contact information of target personnel, when the test case is tested to obtain a testing result, the testing result can be sent to electronic equipment of the target personnel based on the contact information of the target personnel, the quick positioning of relevant personnel of the source code is realized, the testing result of the source code can be conveniently and quickly informed to the relevant personnel, so that subsequent processing can be conveniently carried out, and the testing efficiency can be effectively improved.
The data involved in the various alternative embodiments provided herein may be implemented based on cloud technology, the data processing/data computing involved in implementation of the solution may be implemented based on cloud computing,
cloud technology refers to a hosting technology for unifying serial resources such as hardware, software, network and the like in a wide area network or a local area network to realize calculation, storage, processing and sharing of data. Cloud technology (Cloud technology) is based on a general term of network technology, information technology, integration technology, management platform technology, application technology and the like applied in a Cloud computing business model, can form a resource pool, is used as required, and is flexible and convenient. Cloud computing technology will become an important support. Background services of the technical network system require a large amount of computing and storage resources, such as video websites, picture-like websites and more web portals. With the high development and application of the internet industry, each article may have its own identification mark and needs to be transmitted to a background system for logic processing, data in different levels are processed separately, and various industrial data need strong system background support and can only be realized through cloud computing.
Cloud computing (cloud computing) is a computing model that distributes computing tasks over a pool of resources formed by a large number of computers, enabling various application systems to obtain computing power, storage space, and information services as needed. The network that provides the resources is referred to as the "cloud". Resources in the "cloud" appear to the user as being infinitely expandable and available at any time, available on demand, expandable at any time, and paid for on-demand.
As a basic capability provider of cloud computing, a cloud computing resource pool (called as an ifas (Infrastructure as a Service) platform for short is established, and multiple types of virtual resources are deployed in the resource pool and are selectively used by external clients.
According to the logic function division, a PaaS (Platform as a Service) layer can be deployed on an IaaS (Infrastructure as a Service) layer, a SaaS (Software as a Service) layer is deployed on the PaaS layer, and the SaaS can be directly deployed on the IaaS. PaaS is a platform on which software runs, such as a database, a web container, etc. SaaS is a variety of business software, such as web portal, sms, and mass texting. Generally speaking, SaaS and PaaS are upper layers relative to IaaS.
Cloud computing (cloud computing) refers to a delivery and use mode of an IT infrastructure, and refers to obtaining required resources in an on-demand and easily-extensible manner through a network; the generalized cloud computing refers to a delivery and use mode of a service, and refers to obtaining a required service in an on-demand and easily-extensible manner through a network. Such services may be IT and software, internet related, or other services. Cloud Computing is a product of development and fusion of traditional computers and Network Technologies, such as Grid Computing (Grid Computing), distributed Computing (distributed Computing), Parallel Computing (Parallel Computing), Utility Computing (Utility Computing), Network Storage (Network Storage Technologies), Virtualization (Virtualization), Load balancing (Load Balance), and the like.
With the development of diversification of internet, real-time data stream and connecting equipment and the promotion of demands of search service, social network, mobile commerce, open collaboration and the like, cloud computing is rapidly developed. Different from the prior parallel distributed computing, the generation of cloud computing can promote the revolutionary change of the whole internet mode and the enterprise management mode in concept.
The optional embodiments of the present application can also be implemented based on Big data, which refers to a data set that cannot be captured, managed, and processed by a conventional software tool within a certain time range, and is a massive, high-growth-rate, and diversified information asset that needs a new processing mode to have stronger decision-making power, insight discovery power, and process optimization capability. With the advent of the cloud era, big data has attracted more and more attention, and the big data needs special technology to effectively process a large amount of data within a tolerance elapsed time. The method is suitable for the technology of big data, and comprises a large-scale parallel processing database, data mining, a distributed file system, a distributed database, a cloud computing platform, the Internet and an extensible storage system.
The source code testing method provided by the embodiment of the application can be applied to any application scene related to source code testing, for example, can be applied to a front-end source code testing scene. Each optional embodiment of the present application may be executed by a test device, where the test device may be a terminal device, a server, or a server cluster, where the server cluster includes at least two servers, and the server may be a physical server or the aforementioned cloud server.
The front-end source code test comprises unit test, wherein the unit test is to perform function-level test on a program code unit and is to complete verification work on a minimum software design unit. Unit testing is mainly performed from 4 aspects of unit function, unit interface, data structure and statement branch coverage.
The test of the unit function is to ensure that the unit module has the function of completing the design requirement; the test of the unit interface is to ensure that the data flow in and out of the program unit is correct during the test; the test of the data structure is to ensure the integrity of the stored global data and local data in the process of executing the algorithm; the test for sentence branch coverage is to ensure that each sentence and each branch of the function can be correctly executed by the unit function under the limit boundary condition, and eliminate useless codes. The unit function is a program code composed of various statements, and the design of test cases of various statements is the key of unit test.
In front-end projects, unit testing is also indispensable. The unit test in the front-end project can ensure the correctness of the project, avoids finding problems after the project is online, can realize automatic test, can greatly improve the efficiency compared with manual test, can drive development, and needs to pay attention to the design of an interface in the development stage in order to ensure the testability of codes.
The unit test also has explanatory property, the test case is an explanation on how to use the interface, and the good test case can enable other people to understand the use mode of the interface through the test case, so that the time for reading documents is saved. The unit test can also ensure the reconstruction of the project, the project is difficult to avoid the problem of reconstruction, and the basic power of the project is reconstructed only when the complete unit test is available.
According to the method and the device for testing the source code, annotation information can be added to the source code to be tested, and the source code data to be tested is obtained, wherein the annotation information is testing management information, and includes but is not limited to contact information, testing instruction information and testing types of target personnel. For convenience of description, in the embodiment of the present application, the contact information of the target person is represented by a writer, and the test instruction information includes, but is not limited to, a test priority of the source code to be tested.
In the embodiment of the application, the corresponding test case can be generated based on the source code data to be tested, and after the test case is executed by the test equipment, the test case can be collected, so that the management of the test behavior is realized.
To facilitate understanding and description of the embodiments of the present application, terms referred to in the embodiments of the present application will be explained and explained below.
Test case: a set of test inputs, execution conditions, and expected results tailored for a particular objective are used to verify that a particular software requirement is met.
A decoration device: the method is essentially a TS (TypeScript) function, can add extra functions to other functions without any code change, and the return value of the TS (TypeScript) function is also a function object, wherein the TypeScript function is a computer programming language.
Abstract Syntax Tree (AST): an abstract representation of the syntax structure of the source code represents the syntax structure of the programming language in the form of a tree, each node on the tree representing a structure in the source code.
JSDoc: and a tool for generating Application Programming Interface (API) documents of JavaScript Application programs or libraries and modules according to the annotation information in the JavaScript (JS) file, wherein the JavaScript is a high-level Programming language.
descriptor function: also referred to as test set functions or test suite functions. The descriptor function is a global function for creating a test suite, which can be understood as a set of test cases. The descriptor function accepts two parameters, namely a character string and a callback function, the character string is the name or title of the test suite and is usually used for describing the tested content, and the callback function is a code block for realizing the test suite and is also called a descriptor block.
The it function: also referred to as test item functions or test case functions. The it function is also a global function used for creating a test case in the descriptor block, the it function receives two parameters, which are divided into a character string and a callback function, the character string is the name or title of the test case, and the callback function is a code block for realizing the test case, which is also called the it block.
In the embodiment of the present application, a standard for writing source code data is provided, where the source code data includes an annotation portion and a logic implementation portion, the annotation portion is the test management information mentioned below, and the logic implementation portion is the source code to be tested mentioned below. The following describes the source code data provided by the embodiment in detail, taking an example that the source code to be tested can implement 1+2 equal to 3. Specifically, the source code data of the embodiment of the present application is denoted as source code data a1, and the source code data a1 may be as follows:
/**
@ author someone// writer
Priority P0// test priority
Type of @ casetype unit// test
The notation part is the symbol// the logic implementation part is the following
describe(‘test sum’,()=>{
it(‘add test’,function(){
expect (sum (1,2)). toBe (3); // achieving 1+2 equals 3
});
});
The source code data A1 can also be called testbase, is written in a JSDoc annotation form, integrates elegance of styles and convenience of writing, and can be combined with a front-end unit test framework in a non-invasive mode. The source code data a1 includes an annotation part and a logic implementation part, wherein the annotation part is inserted into the writer, the test priority and the test type in the form of annotation, and does not need to change the logic of the original code (i.e. the logic implementation part), thereby facilitating the migration of stock code and the access of new projects.
In the embodiment of the present application, the source code data a1 may be used to generate a corresponding test case, as shown in fig. 1, where fig. 1 is a flowchart illustrating a method for generating a test case according to the embodiment of the present application. Specifically, the source code data a1 may be converted into a corresponding abstract syntax tree, and each node on the abstract syntax tree is sequentially traversed and processed accordingly.
The abstract syntax tree corresponding to the source code data a1 includes an abstract syntax tree code B1 and an abstract syntax tree code B2, which are shown below.
Abstract syntax tree code B1:
Figure BDA0002934382380000091
Figure BDA0002934382380000101
abstract syntax tree code B2:
Figure BDA0002934382380000102
Figure BDA0002934382380000111
Figure BDA0002934382380000121
in the embodiment of the application, each node on the abstract syntax tree is traversed in sequence and corresponding processing is performed, and for the currently traversed node, corresponding processing can be performed in the following manner. For convenience of understanding and explanation, the manner will be described below in the form of steps, which may include steps S11 through S17, and it should be noted that the size of the step number does not limit the execution order of the steps.
Step S11, determine whether the current node is a node corresponding to the function call structure, if yes, execute step S12, otherwise execute step S16.
In the embodiment of the present application, the function call structure is an expressonstatable, where (enum number) ts.syntaxkind.expressonstatable ═ 226, that is, kind ═ 226, so if the corresponding content of the current node in the abstract syntax tree includes "kind: 226 ", it may be determined that the node is the node corresponding to the function call structure. In the embodiments of the present application and the following embodiments, the content of any node corresponding to the abstract syntax tree may also be referred to as an abstract syntax tree portion corresponding to the node.
Step S12, determining whether the content of the current node corresponding to the abstract syntax tree includes a descriptor, if yes, performing step S13, and if no, performing step S16.
In the embodiment of the present application, if the corresponding content of the current node in the source code data includes the descriptor function, the corresponding content of the current node in the abstract syntax tree includes "escapedText: 'descriptor'. Whether the content of the current node in the abstract syntax tree includes the descriptor, i.e., the descriptor function, can be determined by determining whether the content of the current node in the abstract syntax tree includes "escapedText: 'descriptor'.
In step S13, whether the descriptor includes it in the corresponding content of the source code data is determined, if yes, step S14 is executed, and if no, step S15 is executed. In the embodiments of the present application and the following embodiments, the content of any function corresponding to the source code data may also be referred to as a source code data portion corresponding to the function.
In this embodiment, if the content of the descriptor corresponding to the source code data includes it, that is, the descriptor function includes it function, the content of the node connected to the current node corresponding to the abstract syntax tree includes "escapedText: 'it'. In the actual application process, whether the content of the descriptor corresponding to the source code data includes an it, namely an it function, can be determined by judging whether the content of the node connected with the current node corresponding to the abstract syntax tree includes "escapedText: 'it'.
It should be noted that the abstract syntax tree is a tree structure, each node on the abstract syntax tree corresponds to each function in the source code to be tested, and the connection relationship between the nodes corresponds to the inclusion relationship between the functions. If the descriptor function includes the it function, the content of the descriptor corresponding to the source code data includes the it function, that is, the content of the descriptor corresponding to the source code data includes the content of the it corresponding to the source code data, and the node corresponding to the descriptor function is connected to the node corresponding to the it function included in the descriptor function.
And step S14, generating a first test case set by using the content corresponding to the descriptor in the source code data, and merging a second test case set into the first test case set by using a second test case set generated by using the content corresponding to the it in the source code data.
In the embodiment of the application, if the content of the descriptor corresponding to the it in the source code data includes the it, the content of the descriptor corresponding to the source code data is used to generate a first test case set, and the first test case set includes a second test case set generated by using the content of the it corresponding to the source code data.
For example, the above-mentioned source code data a1 is:
/**
@ author someone// writer
Priority P0// test priority
Type of @ casetype unit// test
The notation part is the symbol// the logic implementation part is the following
describe(‘test sum’,()=>{
it(‘add test’,function(){
expect (sum (1,2)). toBe (3); // achieving 1+2 equals 3
});
});
The source code data a1 may be regarded as content of a descriptor corresponding to the source code data, where the descriptor function includes an it function, and the first test case set generated by using the source code data a1 is as follows:
cases:[
Suite{
name:‘test sum’,
type:‘normal’,
meta: [ object ],/corresponds to writer, test priority, test type
parent:[Circular],
cases [ Array ],// second test case set
}]
Wherein "meta: [ object ]" corresponds to an annotation section including, but not limited to, writer, test priority, test type, "cases: [ Array ]" is a second set of test cases generated with it's corresponding content in the source code data, i.e., with "it (' add test ', function () { expect (sum (1,2)). toBe (3))); "the generated second test case suite.
Step S15, generating a first test case set by using the corresponding content of the descriptor in the source code data.
In the embodiment of the application, if the content of the descriptor corresponding to the source code data does not include the it, the content of the descriptor corresponding to the source code data is used for generating the first test case set, and the first test case set does not include the second test case set.
For example, if the descriptor function of the source code data a1 does not include the it function, that is, if the source code data a1 is as follows:
/**
@ author someone// writer
Priority P0// test priority
Type of @ casetype unit// test
The notation part is the symbol// the logic implementation part is the following
describe(‘test sum’,()=>{
});
The generated first set of test cases may be as follows:
cases:[
Suite{
name:‘test sum’,
type:‘normal’,
meta [ object ],// corresponds to writer, test priority, test type parent [ Circular ],
}]
it should be noted that the content of the descriptor function in this embodiment is empty, which is only for distinguishing from the embodiment in which the descriptor function includes the it function, and in practical application, the descriptor function may include the it function and/or other functions and/or other information besides the it function, and the number of the it function and other functions is not limited in this embodiment.
Step S16, determine whether the current node is the last node, if yes, end the process, otherwise, execute step S17.
In step S17, the next node is used as the current node.
In this embodiment, if the current node is not the last node, the next node is taken as the current node, and step S11 and the following steps are executed. That is, steps S11-S17 may be performed in a loop multiple times. And finally, when the loop is ended, obtaining the test case corresponding to the source code data.
For example, at the end of the loop, for source code data A1, a test case may be obtained as follows:
console.dir
the test case part corresponding to the Suite {// root node is equivalent to a folder
name:‘root’,
type:‘normal’,
meta:null,
parent:null,
cases [// descriptor function corresponding test case part, i.e. first test case set
Suite{
name:‘test sum’,
type:‘normal’,
meta: [ object ],/corresponds to writer, test priority, test type
parent:[Circular],
cases [ Array ],// it function corresponding test case part, i.e. second test case set
}]}
It should be noted that the source code data may include at least one descriptor function, and for each descriptor function, may include at least one it function, and/or at least one function other than the it function. The test case corresponding to the source code data comprises a test case part corresponding to the root node, the test case part corresponding to the root node comprises a test case part corresponding to each descriptor function, and for each descriptor function, the corresponding test case part comprises a test case part corresponding to each it function.
The embodiment of the application further provides two types of source code data to be tested, which are respectively marked as source code data a2 and source code data A3, wherein the source code data a2 and the source code data A3 are both obtained by inserting test management information into a logic implementation portion, and the source code data has a large modification amount. Still taking the example that the source code to be tested can realize 1+2 being equal to 3, the source code data a2 and the source code data A3 provided by the embodiment of the present application are described in detail.
The source code data a2 is as follows:
export function sum(a:number,b:number):number{
return a+b;
}
@ suite ('test sum', 'sound', priority.high, type.Unit)// corresponding to writer, test priority, test type
class Suite1{
@test
‘adds 1+2to equal 3’(){
expect (sum (1,2)). toBe (3); // achieving 1+2 equals 3
}
}
Among them, the source code data a2 is written by a decorator, which is advantageous in that the manner in which information is collected is relatively elegant, "'someone' corresponds to the writer," priority. In the embodiment of the application, the source code data a2 can be directly converted into the corresponding test case.
The source code data a3 is as follows:
export function sum(a:number,b:number):number{
return a+b;
}
describe(testBase(‘test sum’,‘someone’,Priority.High,Type.Unit),()=>{
// corresponding to writer, test priority, test type
it(‘adds 1+2to equal 3’,()=>{
expect (sum (1,2)). toBe (3); // achieving 1+2 equals 3
});
});
The source code data A3 is to inject the test management information in a form of injecting a function (function) into the descriptor function, so that the manner is not elegant enough, "'sound' corresponds to the writer," priority.high "corresponds to the test priority," type.unit "corresponds to the test type, and the source code data A3 can be directly converted into a corresponding test case.
In the embodiment of the application, the source code data to be tested can be written in a mode shown by any one of the source code data A1-A3, the writing mode of the source code data is unified, and a writer, a test priority and a test type of each source code data can be clear at a glance.
In the embodiment of the application, a test case (which may be a test case corresponding to any one of source code data a 1-A3) corresponding to source code data may be tested to obtain a test result, and the test result is sent to the electronic device of the writer.
In the actual test, a plurality of test cases can be tested, the test cases with high priority are preferentially tested according to the test priority corresponding to each test case, the test results of the test cases with high priority are preferentially sent to the corresponding electronic equipment of the writer according to the priority corresponding to each test case after the test is finished, and the test results of the test cases with high priority can be preferentially analyzed and processed after the test is finished.
After the test is completed, the test result corresponding to each test type can be counted, the test passing rate of each test type is determined, and the effect of the test is determined based on the test passing rate of each test type.
While the source code testing method is specifically described above from the perspective of specific embodiments, the source code testing method of the embodiments of the present application will be described in detail below from the perspective of method steps, which may be executed by a testing device, specifically, as shown in fig. 2, the method includes step S21 and step S24.
Step S21, obtaining source code data to be tested, where the source code data includes a source code to be tested and test management information corresponding to the source code to be tested, where the test management information is comment information of the source code to be tested, and the test management information includes at least one of test instruction information or contact information of a target person.
In the embodiment of the present application, the number of source codes to be tested may be as shown in the above-mentioned source code data a1, the source codes to be tested may be as shown in the above-mentioned logic implementation part, the test management information may be as shown in the above-mentioned comment part, the test indication information includes, but is not limited to, the above-mentioned test priority, and the contact information of the target person includes, but is not limited to, the above-mentioned writer.
The contact information of the target person may be at least one of a mailbox of the target person, identification information of an instant messaging application program, a phone number, and the like, which is not limited in this embodiment of the application.
And step S22, generating a corresponding test case based on the source code data.
In this embodiment of the application, in step S22, generating a corresponding test case based on the source code data may specifically include:
converting source code data into an abstract syntax tree, wherein each node on the abstract syntax tree corresponds to each function in the source code to be tested respectively, and the connection relation between the nodes corresponds to the inclusion relation between the functions; and generating a corresponding test case according to the abstract syntax tree and the source code data.
In the embodiment of the present application, the source code data may be converted into the abstract syntax tree, and the conversion manner is not limited, for example, a compiler may be used to convert the source code data into the abstract syntax tree.
In this embodiment of the application, there may be a containment relationship between functions in the source code data, for example, the descriptor function may include an it function, which may be specifically seen in the logic implementation part in the foregoing source code data a 1.
Each node on the abstract syntax tree corresponds to each function in the source code to be tested, and the connection relationship between the nodes corresponds to the inclusion relationship between the functions, for example, the descriptor function and the it function in the source code data a1 correspond to two nodes on the abstract syntax tree, and the connection between the two nodes indicates that the descriptor function includes the it function.
Generating a corresponding test case according to the abstract syntax tree and the source code data, which specifically includes:
determining nodes of a target structure by traversing the abstract syntax tree, wherein the target structure comprises a function calling structure; if the corresponding content of the node of the target structure in the abstract syntax tree contains a calling function, determining the node of the target structure as a target node; and obtaining a test case based on the corresponding content of each target node in the source code data.
In the embodiment of the present application, the Traversal manner of the abstract syntax tree is not limited, for example, the Traversal manner may be post Traversal (LRD), that is, first traverse the left sub-tree, then traverse the right sub-tree, and finally access the root node.
For the current node traversed, it may be determined whether the current node is a node of a target structure, including but not limited to a function call structure. If the corresponding content of the current node in the abstract syntax tree comprises "kid: 226 ", the node may be determined to be the node corresponding to the function call structure, as described in the foregoing.
If the corresponding content of the node of the target structure in the abstract syntax tree includes a calling function, the node of the target structure is determined as the target node, where the calling function includes but is not limited to a descriptor function, and for convenience of description, the following description will take the calling function as the descriptor function as an example.
Whether the content of the current node in the abstract syntax tree includes the descriptor function can be determined by determining whether the content of the current node in the abstract syntax tree includes "escapedText:" descriptor' ", as described in detail above.
In the embodiment of the present application, obtaining a test case based on the content of each target node corresponding to the source code data may specifically include:
generating each first test case set according to the corresponding content of each calling function in the source code data, wherein the test cases comprise each first test case set; for any calling function, if the content of the calling function corresponding to the source code data comprises the called function of the calling function, generating a second test case set according to the content of the called function corresponding to the source code data, and merging the second test case set into the first test case set.
For convenience of description, the following description will take the calling function as the descriptor function and the called function as the it function as an example.
For each calling function, a first test case set can be generated by using the corresponding content of the descriptor function in the source code data. If the content of the descriptor function corresponding to the source code data comprises the it function, generating a first test case set by using the content of the descriptor function corresponding to the source code data, and generating a second test case set by using the content of the it function corresponding to the source code data in the first test case set; if the content of the descriptor function corresponding to the source code data does not include the it function, the content of the descriptor function corresponding to the source code data is utilized to generate a first test case set, and the first test case set does not include a second test case set, which can be seen in the foregoing description.
And step S23, if the test management information includes the test instruction information, testing the test case according to the test instruction information to obtain a test result.
In the embodiment of the application, the annotation information of the source code data may include test instruction information, so as to test the test case according to the test instruction information. The test indication information includes, but is not limited to, a test priority, and for convenience of description, the test indication information is taken as the test priority as an example for description.
The source code data comprises at least two source codes to be tested, and the test indication information comprises test priority information between the at least two source codes to be tested; in step S23, the testing the test case according to the test instruction information may specifically include:
and testing the test cases corresponding to the source code data in sequence according to the test priority information between at least two source codes to be tested.
In one possible implementation, the source code data may be at least two, and each source code data may include a source code to be tested and corresponding test management information, including but not limited to test instruction information or contact information of a target person. The test indication information may be a test priority of the source code to be tested, in other words, the test indication information is test priority information between at least two source codes to be tested, that is, the test indication information is test priority information between at least two source code data.
In the embodiment of the application, the test instruction information includes test priority information between at least two source codes to be tested, and the test cases corresponding to the source code data can be tested sequentially in the order of priority from high to low according to the test priority information between the at least two source codes to be tested.
For example, if the test priority of source code to be tested C1 is higher than that of source code to be tested C2, source code data corresponding to source code to be tested C1 is tested first, and then source code data corresponding to source code to be tested C2 is tested.
In actual execution, the test results corresponding to the source code data may also be sequentially processed in a sequence from high to low in priority according to test priority information between at least two source codes to be tested, where the processing manner includes, but is not limited to, analyzing the test results, and sending the test results to electronic devices of corresponding target persons.
For example, if the test priority of the source code to be tested C1 is higher than that of the source code to be tested C2, after the source code data corresponding to the source codes to be tested C1 and C2 are respectively tested, the test result corresponding to the source code to be tested C1 is preferentially sent to the electronic device of the corresponding target person, and then the test result corresponding to the source code to be tested C2 is sent to the electronic device of the corresponding target person.
And step S24, if the test management information includes the contact information of the target person, sending the test result to the electronic equipment of the target person based on the contact information of the target person.
In the embodiment of the application, the test management information may include contact information of the target person, and the test result may be sent to the electronic device of the target person based on the contact information of the target person. The contact information of the target person may be at least one of a mailbox of the target person, identification information of the instant messaging application program, a telephone number, and the like.
For example, if the contact information of the target person is the mailbox of the target person, the test result may be sent to the mailbox of the target person, and the target person logs in the mailbox of the target person through the electronic device to receive and view the test result.
In the embodiment of the application, for each source code data, the source code data includes a source code to be tested and test management information corresponding to the source code to be tested, and the test management information includes contact information of a target person, that is, contact information of the target person corresponding to each source code data exists in each source code data. Therefore, after the test case corresponding to the source code data is tested, the test result can be sent to the electronic device of the target person corresponding to the source code data based on the contact information of the target person corresponding to the source code data.
In this embodiment of the present application, the source code data includes at least two source codes to be tested, the test management information further includes a test type of each source code to be tested, and the method may further include:
counting the test results of each test type; and determining the test passing rate corresponding to each test type based on the test result of each test type.
In this embodiment of the application, for each source code data, the source code data includes a source code to be tested and test management information corresponding to the source code to be tested, and the test management information includes a test type of the source code to be tested, that is, each source code data has a test type corresponding to the source code data, and the test types corresponding to any two source code data may be the same or different, which is not limited herein.
After testing the test cases corresponding to the source code data, the test results of each test type can be counted, the test result of any test type includes at least one test result, the test passing rate corresponding to each test type can be determined through the test results of each test type, and the test passing rate corresponding to each test type is directly displayed in the current test equipment, or sent to the electronic equipment of preset personnel, or sent to the electronic equipment of target personnel.
Since each source code data may have the contact information and the test type of the target person corresponding to the source code data, a corresponding relationship may also exist between the target person and the test type. After the test passing rates corresponding to the test types are counted, the test passing rates of the test types corresponding to the target person can be sent to the electronic device of the target person.
In actual execution, for each test type, the test passing rate of the test type may be directly sent to the electronic device of the target person corresponding to the test type, or the test passing rate of the test type may be added to the test result corresponding to the test type, and the test result with the test passing rate added thereto is sent to the electronic device of the corresponding target person.
Compared with the prior art, the source code testing method has the advantages that the corresponding test cases can be generated based on the source code data, the source code data can contain the test indication information, the test cases can be tested according to the test indication information, the test indication information can effectively indicate the testing process of the test cases, the testing efficiency can be improved, the source code data can also contain the contact information of target personnel, when the test cases are tested to obtain the testing results, the testing results can be sent to the electronic equipment of the target personnel based on the contact information of the target personnel, the quick positioning of the source code relevant personnel is achieved, the testing results of the source codes can be conveniently and quickly informed to the relevant personnel, the subsequent processing is convenient, and the testing efficiency can be effectively improved.
The source code testing method is specifically described from the perspective of the method steps, and a source code testing device is introduced from the perspective of a virtual module as follows:
an embodiment of the present application provides a source code testing apparatus, as shown in fig. 3, the source code testing apparatus 30 may include: a code data acquisition module 301, a test case generation module 302, a test case test model 303, and a test result transmission module 304, wherein,
the code data acquiring module 301 is configured to acquire source code data to be tested, where the source code data includes a source code to be tested and test management information corresponding to the source code to be tested, where the test management information is comment information of the source code to be tested, and the test management information includes at least one of test instruction information or contact information of a target person;
a test case generation module 302, configured to generate a corresponding test case based on the source code data;
the test case testing module 303 is configured to test the test case according to the test instruction information when the test management information includes the test instruction information, so as to obtain a test result;
and a test result sending module 304, configured to send the test result to the electronic device of the target person based on the contact information of the target person when the test management information includes the contact information of the target person.
In one possible implementation manner, the source code data includes at least two source codes to be tested, and the test instruction information includes test priority information between the at least two source codes to be tested;
when the test case testing module 303 tests the test case according to the test instruction information, it is specifically configured to:
and testing the test cases corresponding to the source code data in sequence according to the test priority information between at least two source codes to be tested.
In a possible implementation manner, the source code data includes at least two source codes to be tested, the test management information further includes a test type of each source code to be tested, and the source code testing apparatus 30 further includes:
and the test passing rate determining module is used for counting the test results of each test type and determining the test passing rate corresponding to each test type based on the test results of each test type.
In a possible implementation manner, the test case generation module 302 is specifically configured to:
converting source code data into an abstract syntax tree, wherein each node on the abstract syntax tree corresponds to each function in the source code to be tested respectively, and the connection relation between the nodes corresponds to the inclusion relation between the functions;
and generating a corresponding test case according to the abstract syntax tree and the source code data.
In a possible implementation manner, when the test case generation module 302 generates a corresponding test case according to the abstract syntax tree and the source code data, it is specifically configured to:
determining nodes of a target structure by traversing the abstract syntax tree, wherein the target structure comprises a function calling structure;
if the corresponding content of the node of the target structure in the abstract syntax tree contains a calling function, determining the node of the target structure as a target node;
and obtaining a test case based on the corresponding content of each target node in the source code data.
In a possible implementation manner, when the test case generation module 302 obtains a test case based on corresponding content of each target node in the source code data, it is specifically configured to:
generating each first test case set according to the corresponding content of each calling function in the source code data, wherein the test cases comprise each first test case set;
for any calling function, if the content of the calling function corresponding to the source code data comprises the called function of the calling function, generating a second test case set according to the content of the called function corresponding to the source code data, and merging the second test case set into the first test case set.
In one possible implementation, the calling function is a descriptor function, and the called function is an it function.
The source code testing apparatus of this embodiment can execute the source code testing method shown in any of the above embodiments of this application, and its implementation principles are similar, and are not described herein again.
The source code testing device may be a computer program (including program code) running in a computer apparatus, for example the source code testing device is an application software; the apparatus may be used to perform the corresponding steps in the methods provided by the embodiments of the present application.
In some embodiments, the source code testing apparatus provided in the embodiments of the present Application may be implemented by a combination of hardware and software, and by way of example, the source code testing apparatus provided in the embodiments of the present Application may be a processor in the form of a hardware decoding processor, which is programmed to execute the source code testing method provided in the embodiments of the present Application, for example, the processor in the form of the hardware decoding processor may be implemented by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), Complex Programmable Logic Devices (CPLDs), Field Programmable Gate Arrays (FPGAs), or other electronic components.
In other embodiments, the source code testing apparatus provided in the embodiments of the present application may be implemented in a software manner, and the source code testing apparatus stored in the memory may be software in the form of a program, a plug-in, and the like, and includes a series of modules, including a code data obtaining module 301, a test case generating module 302, a test case testing model 303, a test result sending module 304, and a test passing rate determining module; the code data obtaining module 301, the test case generating module 302, the test case testing model 303, the test result sending module 304, and the test passing rate determining module are used to implement the source code testing method provided by the embodiment of the present application.
The embodiment of the application provides a source code testing device, compared with the prior art, the embodiment of the application can generate a corresponding test case based on source code data, the source code data can contain test indication information, the test case can be tested according to the test indication information, the test indication information can effectively indicate the test process of the test case, the test efficiency can be improved, the source code data can also contain contact information of target personnel, when the test case is tested to obtain a test result, the test result can be sent to electronic equipment of the target personnel based on the contact information of the target personnel, the quick positioning of the source code relevant personnel is realized, the test result of the source code can be rapidly informed to the relevant personnel, the subsequent processing is convenient, and the test efficiency can be effectively improved.
The source code testing apparatus of the present application is described above from the perspective of a virtual module, and the electronic device of the present application is described below from the perspective of a physical apparatus.
An embodiment of the present application provides an electronic device, as shown in fig. 4, an electronic device 4000 shown in fig. 4 includes: a processor 4001 and a memory 4003. Processor 4001 is coupled to memory 4003, such as via bus 4002. Optionally, the electronic device 4000 may further comprise a transceiver 4004. In addition, the transceiver 4004 is not limited to one in practical applications, and the structure of the electronic device 4000 is not limited to the embodiment of the present application.
Processor 4001 may be a CPU, general purpose processor, DSP, ASIC, FPGA or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor 4001 may also be a combination that performs a computational function, including, for example, a combination of one or more microprocessors, a combination of a DSP and a microprocessor, or the like.
Bus 4002 may include a path that carries information between the aforementioned components. Bus 4002 may be a PCI bus, EISA bus, or the like. The bus 4002 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 4, but this does not indicate only one bus or one type of bus.
Memory 4003 may be, but is not limited to, a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an EEPROM, a CD-ROM or other optical disk storage, an optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
The memory 4003 is used for storing computer programs for executing the present scheme, and is controlled by the processor 4001 for execution. Processor 4001 is configured to execute a computer program stored in memory 4003 to implement what is shown in any of the foregoing method embodiments.
The embodiment of the application provides electronic equipment, which comprises a memory and a processor, wherein the memory is stored with a computer program; the processor, when running the computer program, performs the source code testing method shown in any of the embodiments described above.
The electronic device of the present application is described above from the perspective of a physical device, and the computer-readable storage medium of the present application is described below from the perspective of a storage medium.
The embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the source code testing method shown in any one of the above embodiments is implemented.
Embodiments of the present application also provide a computer program product or computer program comprising computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the method provided in the various alternative implementations to which the above-described method embodiments relate.
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
The foregoing is only a partial embodiment of the present application, and it should be noted that, for those skilled in the art, several modifications and decorations can be made without departing from the principle of the present application, and these modifications and decorations should also be regarded as the protection scope of the present application.

Claims (10)

1. A source code testing method, comprising:
acquiring source code data to be tested, wherein the source code data comprises a source code to be tested and test management information corresponding to the source code to be tested, the test management information is comment information of the source code to be tested, and the test management information comprises at least one of test instruction information or contact information of a target person;
generating a corresponding test case based on the source code data;
if the test management information comprises the test instruction information, testing the test case according to the test instruction information to obtain a test result;
and if the test management information comprises the contact information of the target person, sending the test result to the electronic equipment of the target person based on the contact information of the target person.
2. The method of claim 1, wherein the source code data comprises at least two source codes to be tested, and the test indication information comprises test priority information between the at least two source codes to be tested;
the testing the test case according to the test indication information includes:
and sequentially testing the test cases corresponding to the source code data according to the test priority information between at least two source codes to be tested.
3. The method of claim 1, wherein the source code data includes at least two source codes to be tested, wherein the test management information further includes a test type of each of the source codes to be tested, and wherein the method further comprises:
counting the test result of each test type;
and determining the test passing rate corresponding to each test type based on the test result of each test type.
4. The method according to any one of claims 1-3, wherein generating the corresponding test case based on the source code data comprises:
converting the source code data into an abstract syntax tree, wherein each node on the abstract syntax tree corresponds to each function in the source code to be tested respectively, and the connection relation between the nodes corresponds to the inclusion relation between the functions;
and generating a corresponding test case according to the abstract syntax tree and the source code data.
5. The method of claim 4, wherein generating the corresponding test case according to the abstract syntax tree and the source code data comprises:
determining nodes of a target structure by traversing the abstract syntax tree, wherein the target structure comprises a function calling structure;
if the corresponding content of the node of the target structure in the abstract syntax tree contains a calling function, determining the node of the target structure as a target node;
and obtaining the test case based on the corresponding content of each target node in the source code data.
6. The method of claim 5, wherein obtaining the test case based on the corresponding content of each of the target nodes in the source code data comprises:
generating each first test case set according to the corresponding content of each calling function in the source code data, wherein the test cases comprise each first test case set;
for any calling function, if the content of the calling function in the source code data includes the called function of the calling function, generating a second test case set according to the content of the called function in the source code data, and merging the second test case set into the first test case set.
7. The method of claim 6, wherein the calling function is a descriptor function and the called function is an it function.
8. A source code testing apparatus, comprising:
the system comprises a code data acquisition module, a data processing module and a data processing module, wherein the code data acquisition module is used for acquiring source code data to be tested, the source code data comprises a source code to be tested and test management information corresponding to the source code to be tested, the test management information is comment information of the source code to be tested, and the test management information comprises at least one of test instruction information or contact information of target personnel;
the test case generation module is used for generating a corresponding test case based on the source code data;
the test case testing module is used for testing the test case according to the test indication information to obtain a test result when the test management information comprises the test indication information;
and the test result sending module is used for sending the test result to the electronic equipment of the target person based on the contact information of the target person when the test management information comprises the contact information of the target person.
9. An electronic device, comprising a memory and a processor, wherein the memory has stored therein a computer program; the processor, when executing the computer program, performs the method of any of claims 1 to 7.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method of any one of claims 1 to 7.
CN202110157643.7A 2021-02-04 2021-02-04 Source code testing method and device, electronic equipment and storage medium Pending CN114860566A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110157643.7A CN114860566A (en) 2021-02-04 2021-02-04 Source code testing method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110157643.7A CN114860566A (en) 2021-02-04 2021-02-04 Source code testing method and device, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN114860566A true CN114860566A (en) 2022-08-05

Family

ID=82622738

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110157643.7A Pending CN114860566A (en) 2021-02-04 2021-02-04 Source code testing method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114860566A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117724988A (en) * 2024-02-18 2024-03-19 杭州玳数科技有限公司 UI component Library Testing method based on Testing Library, storage medium and electronic equipment

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117724988A (en) * 2024-02-18 2024-03-19 杭州玳数科技有限公司 UI component Library Testing method based on Testing Library, storage medium and electronic equipment

Similar Documents

Publication Publication Date Title
CN111382174B (en) Multi-party data joint query method, device, server and storage medium
Varga et al. An overview of the OMNeT++ simulation environment
CN110543297B (en) Method and apparatus for generating source code
US9823991B2 (en) Concurrent workload simulation for application performance testing
CN106657192B (en) Method and equipment for presenting service calling information
CN110442330A (en) List element conversion method, device, electronic equipment and storage medium
CN114116065B (en) Method and device for acquiring topological graph data object and electronic equipment
EP3279816A1 (en) Data analysis processing method, apparatus, computer device, and storage medium
CN113238740B (en) Code generation method, code generation device, storage medium and electronic device
CN111400170A (en) Data permission testing method and device
CN111309317A (en) Code automation method and device for realizing data visualization
CN113419789A (en) Method and device for generating data model script
CN111694561A (en) Interface management method, device, equipment and storage medium
CN115599347A (en) Automatic code development implementation method and system
CN115599359A (en) Code generation method, device, equipment and medium
CN111078573A (en) Test message generation method and device
CN114860566A (en) Source code testing method and device, electronic equipment and storage medium
CN112395339B (en) Intersystem data admission verification method, device, computer equipment and storage medium
CN108243238B (en) Method and device for acquiring performance data
US8607201B2 (en) Augmenting visualization of a call stack
CN111124541A (en) Configuration file generation method, device, equipment and medium
Petriu et al. Software performance models from system scenarios
CN116431668A (en) Metadata acquisition-based data blood-edge analysis method and device and electronic equipment
CN114265846A (en) Data operation method and device, electronic equipment and storage medium
CN113672674A (en) Method, electronic device and storage medium for automatically arranging service flow

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