CN114911706A

CN114911706A - Use case recommendation method, device, equipment and storage medium

Info

Publication number: CN114911706A
Application number: CN202210566923.8A
Authority: CN
Inventors: 卢艳梅; 蒋剑琴
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2022-05-23
Filing date: 2022-05-23
Publication date: 2022-08-16

Abstract

The application discloses a use case recommendation method, a use case recommendation device, use case recommendation equipment and a storage medium, and belongs to the technical field of computers and the Internet. The method comprises the following steps: acquiring a first code of a target application program; determining a change function according to the first code; determining a first call chain from at least one call chain contained in the target application program based on the change function; and determining the use case corresponding to the first call chain as a recommended use case to be tested according to the corresponding relation between the use cases and the call chains. According to the method and the device, the determination efficiency of the recommended case is improved, the efficiency of the whole regression test is improved, the accuracy of the determined recommended case is improved, the whole regression test is pointed, and the accuracy of the whole regression test is improved.

Description

Use case recommendation method, device, equipment and storage medium

Technical Field

The present application relates to the field of computer and internet technologies, and in particular, to a method, an apparatus, a device, and a storage medium for use case recommendation.

Background

As the target application programs are business tuned, the software systems often need to make changes to the code to accommodate the business tuning.

Currently, after detecting a change to a code, a comprehensive test is performed on each use case of a target application program to detect whether the changed code affects an existing use case of the target application program, and then the affected use case is subsequently adjusted or modified.

However, in the related art, each case of the target application is detected, and the whole regression test is inefficient and lacks pertinence.

Disclosure of Invention

The embodiment of the application provides a case recommendation method, a case recommendation device, case recommendation equipment and a storage medium, and improves the efficiency of the whole regression test, so that the whole regression test has pertinence. The technical scheme is as follows.

According to an aspect of the embodiments of the present application, there is provided a use case recommendation method, including the steps of:

acquiring new task data which is not learned based on the sustainable learning model;

acquiring a first code of a target application program, wherein the first code is a code updated in the target application program;

determining a change function according to the first code;

determining a first call chain from at least one call chain contained in the target application program based on the change function, wherein the first call chain refers to a call chain associated with the change function;

and determining the use case corresponding to the first call chain as a recommended use case to be tested according to the corresponding relation between the use case and the call chain.

According to an aspect of the embodiments of the present application, there is provided a use case recommendation apparatus, including:

the code acquisition module is used for acquiring a first code of a target application program, wherein the first code is a code which is updated in the target application program;

a function determining module, configured to determine a change function according to the first code;

a call chain determining module, configured to determine, based on the change function, a first call chain from at least one call chain included in the target application, where the first call chain is a call chain associated with the change function;

and the case determining module is used for determining the case corresponding to the first call chain as the recommended case to be tested according to the corresponding relation between the case and the call chain.

According to an aspect of an embodiment of the present application, an embodiment of the present application provides a computer device, where the computer device includes a processor and a memory, where the memory stores at least one program, and the at least one program is loaded and executed by the processor to implement the use case recommendation method described above.

According to an aspect of the embodiments of the present application, a computer-readable storage medium is provided, in which at least one program is stored, and the at least one program is loaded and executed by a processor to implement the use case recommendation method described above.

According to an aspect of embodiments herein, there is provided 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 executes the computer instructions, so that the computer device executes the use case recommendation method.

The technical scheme provided by the embodiment of the application can bring the following beneficial effects:

the method comprises the steps of determining a call chain corresponding to a change function through the change function corresponding to a code, and further taking the use case corresponding to the call chain as a recommended use case to be tested according to the corresponding relation between the use case and the call chain, on one hand, after the code of a target application program is updated, the recommended use case to be tested can be determined without detecting the whole number of use cases of the target application program, the determination efficiency of the recommended use case is improved, and the efficiency of the whole regression test is improved.

Drawings

FIG. 1 is a schematic diagram of an architecture of a use case recommendation platform provided by an embodiment of the present application;

FIG. 2 illustrates a schematic diagram of a use case recommendation system;

FIG. 3 is a flowchart of a use case recommendation method according to an embodiment of the present application;

FIG. 4 is a flowchart illustrating a method for obtaining correspondence between use cases and call chains;

FIG. 5 is a flow chart illustrating a method of obtaining correspondence between code and call chains;

FIG. 6 is a diagram illustrating a flow of a use case recommendation method;

fig. 7 is a block diagram of a use case recommendation apparatus according to an embodiment of the present application;

fig. 8 is a block diagram of a use case recommendation apparatus according to another embodiment of the present application;

fig. 9 is a block diagram of a computer device according to an embodiment of the present application.

Detailed Description

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.

Referring to fig. 1, a schematic diagram of an architecture of a use case recommendation platform according to an embodiment of the present application is shown. The use case recommendation platform may include a presentation layer 10, a logic layer 20, a storage layer 30, and a base services layer 40.

The presentation layer 10 is used to display information to present the information to a user. In the embodiment of the present application, the presentation layer 10 may display a recommended case list, a full use case list, a recorded use case list, an influence call chain list, call chain detail data, recording details, and the like. The recommended use case list comprises recommended use cases, wherein the recommended use cases refer to use cases which can be influenced by codes after the codes of the target application program are updated; the full use case class table refers to a full use case contained in the target application program; the recorded use case list comprises a run use case, the run use case refers to a run use case, and a call chain corresponding to the use case can be determined by the run use case; the list of the affected call chains comprises the affected call chains, wherein the affected call chains refer to the call chains which can be affected by the codes of the target application program after the codes are updated; the call chain detail data refers to the call relation among functions contained in the call chain; the recording details refer to recorded data of the use case running process, and the recorded data are, for example, screenshots or videos of the use case running process. In some embodiments, the users include developers and testers. Wherein, the code of the target application program is updated by the developer; and carrying out case testing on the recommended cases by a tester according to the recommended case list so as to detect whether the case is influenced after the codes are updated. It should be noted that the above description of the content displayed by the display layer 10 is only exemplary and explanatory, and in an exemplary embodiment, the content displayed by the display layer 10 can be flexibly set and adjusted according to actual situations; illustratively, only the full use case list is displayed when the code of the target application program is not updated, and the recommended use case list is displayed when the code of the target application program is updated.

The logic layer 20 is used for data processing. In the embodiment of the present application, the logic layer 20 includes a recommended use case determining section, an influence call chain determining section, a use case aggregation section, a normalization section, and a recording data processing section. The recommended use case determining block is used for determining use cases which are possibly influenced after codes of the target application program are updated and used as candidate use cases; the influence call chain determining block is used for determining a call chain which is possibly influenced after the code of the target application program is updated; the case aggregation version block is used for determining a recommended case from the candidate cases; the normalization version block is used for processing the data format so as to keep the data format uniform; the recording data processing block is used for determining recording details.

The storage layer 30 is used to store data. In the embodiment of the present application, the storage layer 30 stores data including: the calling chain of the target application program, the use case of the target application program, the code of the target application program, the corresponding relation between the code of the target application program and the calling chain, the corresponding relation between the use case of the target application program and the calling chain and the like. In some embodiments, the data stored in the storage layer 30 is obtained by the logic layer 20 and processed to obtain the content to be presented by the presentation layer 10. Illustratively, the logic layer 20 determines a recommended use case list based on the correspondence between the use cases and the call chains of the target application stored in the storage layer 30, and the recommended use case list is then presented by the presentation layer 10.

The basic service layer 40 is used for providing a bottom layer service for the use case recommendation platform. In the embodiment of the present application, the basic service layer 40 can provide a static call chain acquisition service and a dynamic call chain acquisition service for the use case recommendation platform. The static calling chain obtaining service is used for obtaining a static calling chain, and the static calling chain is used for representing the corresponding relation between codes of the target application program and the calling chain; the dynamic call chain obtaining service is used for obtaining a dynamic call chain, and the dynamic call chain is used for representing the corresponding relation between the use case and the call chain of the target application program.

It should be noted that, the above is an introduction of the use case recommendation platform by taking the target application as an example, in an exemplary embodiment, the use case recommendation platform is also applicable to other applications, and the embodiment of the present application does not limit this.

Optionally, the use case recommendation platform may be applied to a use case recommendation system. Illustratively, as shown in fig. 2, the use case recommendation system includes a terminal device 50 and a server 60.

The terminal device 50 may be an electronic device such as a tablet Computer, a PC (Personal Computer), and the like, which is not limited in the embodiment of the present application. In some embodiments, the terminal device 50 includes a client of the use case recommendation platform.

The server 60 is used to provide background services for the terminal device 50. The server 60 may be a server, a server cluster composed of a plurality of servers, or a cloud computing service center. Alternatively, the server 60 may be a background server of a client of the use case recommendation platform. In the exemplary embodiment, server 60 provides a background service for clients of the use case recommendation platform among the plurality of terminal devices 50.

The terminal device 50 and the server 60 perform data transmission via a network.

In some embodiments, the terminal device 50 includes a first terminal device and a second terminal device, where the first terminal device is a terminal device used by a developer, and the second terminal device is a terminal device used by a tester. In the embodiment of the application, a developer submits an updated code through a first terminal device, a server determines a recommended case based on the updated code, and the recommended case is displayed to the recommended case through a second terminal device. It should be noted that the above descriptions of the terminal device 50 and the server 60 are only exemplary and explanatory, and in an exemplary embodiment, the functions of the terminal device 50 and the server 60 can be flexibly set and adjusted; illustratively, the load capacity and the data processing capacity of the terminal device 50 are strong, and the recommended use case is determined by the terminal device 50 based on the updated code.

Please refer to fig. 3, which illustrates a flowchart of a use case recommendation method according to an embodiment of the present application. The steps of the method may be performed by the terminal device 50 and/or the server 60 (hereinafter collectively referred to as "computer devices") of fig. 2 described above. The method may comprise at least one of the following steps (301-304):

step 301, a first code of a target application program is obtained.

The target application may be any application, such as an instant messaging application, a social contact application, a game application, a reading application, and the like, which is not limited in this embodiment of the present application. In some embodiments, the target application may be an application that requires download installation, or may be a point-and-play applet.

In the embodiment of the application, the target application program comprises a use case and code. The use case is used for describing the function of the target application program, and the code refers to the basis for supporting the correct execution of the function of the target application program. In the exemplary embodiment, during the running process of the target application program, the functions described in the corresponding use case are realized by executing the corresponding codes. It should be noted that the use case and the code of the target application program may be stored in the computer device, or may be stored in another computer device.

In one possible implementation, the use cases correspond to different scenarios, and the code executed by the use cases is different in different scenarios. Taking a use case for describing a data transmission function as an example, for a smooth data transmission scene, the code executed by the use case includes: the system comprises a login related code, a data uploading related code, a data sending related code and a first response received related code, wherein the first response is used for indicating that data are smoothly transmitted to target equipment; for a data transfer interrupt scenario, the code executed by the use case includes: the system comprises a log-in related code, a data upload related code, a data sending related code and a second response received related code, wherein the second response is used for indicating that the data is not transmitted to the target equipment.

In another possible implementation, the use case corresponds to one scenario, that is, the codes corresponding to different use cases are different. Illustratively, if a use case is used to describe the login function, the code executed by the use case includes: a code associated with the login; if the use case is used for describing the account switching function, the code executed by the use case comprises the following steps: the related code of logging in and the related code of logging out.

In some embodiments, the code of the target application changes as the business is adjusted. In the embodiment of the application, in order to determine whether the changed code has an influence on a use case of the target application, the computer device obtains a first code of the target application, where the first code is a code updated in the target application. Wherein the updating of the code includes, but is not limited to, at least one of: submission of new code, modification of code, deletion of code, etc.

In some embodiments, the first code may be automatically obtained by the computer device or submitted by the user. In one possible implementation, the first code is automatically obtained by the computer device. The computer device detects the difference between the history code and the object code of the object application program, further determines that the updated code does not exist in the object application program under the condition that the history code is not different from the object code, and correspondingly determines that the updated code exists in the object application program under the condition that the history code is different from the object code, thereby acquiring the first code. It should be noted that, in this case, the computer device may directly determine the code having the difference as the first code; alternatively, the computer device may select a completely compiled code as the first code by centering on the differentiated code. In another possible embodiment, the first code is submitted by a user. The computer device determines the code as the first code when detecting the code submitted by the user.

Step 302, determining a change function according to the first code.

The code of the target application includes a function. In the embodiment of the present application, after acquiring the first code, the computer device determines the change function according to the first code. Wherein, the change function refers to a function which is changed and updated in the target application program, and the updating of the function includes but is not limited to at least one of the following items: addition of new functions, modification of functions, deletion of functions, etc. It should be noted that the number of the alteration functions determined according to the first code may be one or more, and the embodiment of the present application does not limit this.

In some embodiments, the computer device, when determining the alter function, obtains a code modification location of the first code, and further determines the alter function based on the code modification location. Wherein, the code modification position refers to a position in the first code where the code update occurs.

In some embodiments, the first code corresponds to the active code, i.e. the first code is modified on the basis of the source code.

In one possible embodiment, the computer device determines the code modification location based on a difference between the first code and the source code. In some embodiments, the computer device determines the code modification location based on a difference between the first code and the source code after obtaining the first code. Wherein the modification comprises adding code, changing code and deleting code. Illustratively, if the first code is obtained by adding code on the basis of the source code, the computer device determines that the difference between the first code and the source code is newly added code, and further determines the position of the newly added code in the first code as the code modification position; if the first code is obtained by changing the code on the basis of the source code, the computer equipment determines that the difference between the first code and the source code is changed code, and determines the position of the changed code in the first code as the code modification position; if the first code is obtained by deleting the code on the basis of the source code, the computer device determines that the difference between the first code and the source code is the deleted code, and further determines the position of the deleted code in the source code as the code modification position.

In another possible implementation, the computer device determines the code modification position according to a modification operation of the user on the source code. In some embodiments, a detection probe is disposed in the source code, and upon determining that the source code is modified, the detection probe records a code modification location and provides the code modification location to the computer device. Wherein the detection probe is inserted into the code at the time of compilation of the code. Wherein, the modification operation comprises a code adding operation, a code changing operation and a code deleting operation. Illustratively, if the first code is obtained by adding codes on the basis of the source code, the detection probe records the position of the newly added code in the first code and determines the position as the code modification position; if the first code is obtained by changing the code on the basis of the source code, the detection probe records the position of the changed code in the first code and determines the position as the code modification position; if the first code is obtained by deleting the code on the basis of the source code, the detection probe records the position of the deleted code in the source code and determines the position as the code modification position.

Of course, in another possible implementation manner, the code modification position may be reported to the computer device by a user, which is not limited in this embodiment of the application.

In some embodiments, the first code does not correspond to the active code, that is, the first code is a code newly submitted by a developer for the target application, and in this case, the position of the first code in the full-scale code of the target application is determined as the code modification position.

In some embodiments, when determining the alteration function based on the code modification position, the computer device may determine all functions included in the code modification position as the alteration function; alternatively, when determining a change function based on the code modification position, the computer device detects a function for determining that an update has occurred from the code modification position as the change function. In addition, if the first code is a code newly submitted by a developer for a target application, all functions included in the first code are the change function.

Step 303, determining a first call chain from at least one call chain included in the target application program based on the change function.

In an embodiment of the present application, after determining the change function, the computer device determines a first call chain from at least one call chain included in the target application based on the change function. Wherein the first call chain refers to a call chain associated with a change function.

It should be noted that, since there is a call relationship between functions in the code of the target application program, the first call chain may include a change function or a call function having a call relationship with the change function. The specific manner of acquiring the first call chain is described below and will not be described herein.

And 304, determining the use case corresponding to the first call chain as the recommended use case to be tested according to the corresponding relation between the use cases and the call chains.

In the embodiment of the application, after determining the first call chain, the computer device determines, according to the correspondence between the use cases and the call chain, the use case corresponding to the first call chain as the recommended use case to be tested. In some embodiments, in order to improve the determination efficiency of the recommended use case, the correspondence between the use case and the call chain may be pre-stored. If the correspondence between the use case and the call chain can be stored in the computer device in advance, the correspondence can also be stored in other computer devices to reduce the storage load of the computer device.

In a possible implementation manner, when the computer device obtains the recommended use case, the computer device determines the full use cases corresponding to the first call chain according to the corresponding relationship between the use cases and the call chains, and all the full use cases are used as the recommended use cases to be tested.

In another possible implementation, because one call chain may correspond to multiple use cases, when the computer device obtains the recommended use case, according to a corresponding relationship between the use cases and the call chain, a total number of use cases corresponding to the first call chain is determined, and the total number of use cases is aggregated to screen and determine the recommended use case to be tested, which is specifically described below and is not described herein again.

To sum up, in the technical solution provided in the embodiment of the present application, the call chain corresponding to the change function is determined by the change function corresponding to the code, and then the use case corresponding to the call chain is used as the recommended use case to be tested according to the corresponding relationship between the use case and the call chain, on one hand, after the code of the target application program is updated, the recommended use case to be tested can be determined without detecting the whole number of use cases of the target application program, so as to improve the determination efficiency of the recommended use case and improve the efficiency of the whole regression test, on the other hand, the update of the code is locked to the change of the finer function to determine the change function, the change function is associated with the call chain, the recommended use case is further determined according to the corresponding relationship between the use case and the call chain, so as to improve the accuracy of the determined recommended use case, so that the whole regression test has pertinence, and the accuracy of the whole regression test is improved.

In addition, the change function is determined based on the code modification position, namely the change function is determined based on the position of code updating of the code, functions in the whole code do not need to be traversed to determine the change function, the accuracy of the change function is improved, the determination efficiency of the change function is improved, and the efficiency of the whole regression test is further improved.

Next, a description is given of an acquisition mode of the first call chain.

In an exemplary embodiment, the step 303 includes at least one of the following steps:

1. and determining a calling function with a calling relationship with the changing function.

In the embodiment of the application, after obtaining the change function, the computer device determines a call function having a call relationship with the change function. The calling relation comprises calling and called. In some embodiments, if the call relationship between the change function and the call function is a call, the change function calls the call function in the code; if the calling relationship between the changing function and the calling function is called, the changing function is called by the calling function in the code. The call comprises a direct call and an indirect call. In some embodiments, if the calling relationship between the change function and the call function is direct call, the change function directly calls the call function in the code, that is, no other function exists between the change function and the call function in the code execution process; if the calling relationship between the changing function and the calling function is indirect calling, the changing function indirectly calls the calling function in the code, namely other functions exist between the changing function and the calling function in the code execution process. Similarly, invoked includes direct invoked and indirect invoked.

In a possible implementation, when determining the calling function, the computer device determines a second calling chain from at least one calling chain included in the target application, where the second calling chain is a calling chain including the modifying function and a calling function having a calling relationship with the modifying function, and further determines the calling function having a calling relationship with the modifying function based on the second calling chain. In some embodiments, the computer device determines, from at least one call chain included in the target application, a call chain including the alteration function as a second call chain with reference to the alteration function, and further determines, from the second call chain, a function having a call relationship with the alteration function as the call function.

In another possible implementation, when determining the calling function, the computer device performs instrumentation and compilation on the first code, and determines the calling function having a calling relationship with the changing function. In some embodiments, the computer device performs instrumentation and compilation on the first code to obtain at least one call chain corresponding to the first code, determines a call chain including a change function from the at least one call chain corresponding to the first code, and determines a function having a call relationship with the change function from the call chain including the change function as the call function. Of course, in other embodiments, since the relationship between the functions may be determined during instrumentation compilation, after the instrumentation compilation is performed on the first code, the calling function having a calling relationship with the changed function is directly determined, and at least one calling chain corresponding to the first code is obtained. Wherein, the instrumentation compiling refers to inserting a detection probe in the code compiling process.

Of course, in another possible implementation, when determining the call function, the computer device determines a second call chain from at least one call chain included in the target application, where the second call chain is a call chain including the alteration function and a call function having a call relationship with the alteration function, and further determines a call function having a call relationship with the alteration function based on the second call chain; and performing instrumentation and compilation on the first code, and determining a calling function having a calling relationship with the change function. In this case, the above-mentioned calling functions include a calling function determined from the second calling chain, and a calling function compiled by instrumentation.

It should be noted that the above-mentioned obtaining of the calling function is only exemplary and explanatory, and in an exemplary embodiment, the computer device may flexibly select a suitable manner to obtain the calling function according to actual situations. Exemplarily, if the changed function is a newly added function and the changed function does not appear in the code of the target application before, it is determined that the changed function is not included in the existing call chain of the target application program, and the call function is determined by instrumentation and compilation of the first code; if the changed function is a newly added function and the changed function appears in the code of the target application before, determining that the calling chain containing the changed function exists in the target application program, and further determining the calling function through instrumentation compiling of the first code and the second calling chain; and if the change function is obtained based on the modification of the existing function, determining the calling function through the second calling chain under the condition that the use case corresponding to the first code normally runs.

2. Selecting a call chain containing a change function or a call function from at least one call chain contained in the target application program as a first call chain.

In an embodiment of the application, after determining the calling function and the modifying function, the computer device selects, as the first calling chain, a calling chain including the modifying function or the calling function from at least one calling chain included in the target application. That is, only the change function is included in the first call chain; or, the first call chain only contains call functions; alternatively, the first call chain includes a change function and a call function. The number of the first call chains may be one or more, and the embodiment of the present application is not limited thereto.

In summary, in the technical scheme provided in the embodiment of the present application, the first call chain is determined by the change function and the call function having a call relationship with the change function, where the call function belongs to the function affected by the change function, and the first call chain includes the call chain affected by the change function, the call chain affected by the call function, and the call chain affected by both the change function and the call function, so that the determined first call chain is more comprehensive, and the determination accuracy of the first call chain is improved.

In addition, when the change function is determined, on one hand, the call function with the call relation with the change function is determined from the existing call chain of the target application program, namely, the call function is determined according to the existing call relation of the target application program, and on the other hand, the first code is instrumented and compiled to determine the call function with the call relation with the change function, namely, the call function is determined according to the updated code, so that the determined first call chain is more comprehensive and accurate, and the determination accuracy of the subsequent first call chain is improved.

Next, a description will be given of a method of determining the recommended example.

In an exemplary embodiment, the step 304 includes at least one of:

1. determining a plurality of use cases corresponding to the first call chain as a candidate use case set according to the corresponding relation between the use cases and the call chain;

2. taking one candidate use case from the candidate use case set as a reserved use case, and adding the candidate use case into the reserved use case set;

3. judging whether the candidate use cases which are not taken out exist in the candidate use case set or not;

4. if the candidate use case set has the candidate use case which is not taken out, taking out a target candidate use case from the candidate use case set and carrying out coverage comparison on each reserved use case in the reserved use case set;

5. and if the candidate use case set does not have the candidate use case which is not taken out, taking the reserved use case in the reserved use case set as the recommended use case.

In the embodiment of the application, after determining the first call chain, the computer device determines, according to the correspondence between the use cases and the call chain, a plurality of use cases corresponding to the first call chain as a candidate use case set. The multiple use cases may be full use cases corresponding to the first call chain. And then, the computer equipment takes one candidate use case from the candidate use case set as a reserved use case and adds the reserved use case to the reserved use case set. The reserved use case may be randomly selected from a candidate use case set.

In the embodiment of the application, under the condition that the computer equipment determines that the reserved use case exists in the reserved use case set, judging whether the candidate use case which is not taken out exists in the candidate use case set or not; further, if the candidate use case set has a candidate use case which is not taken out, taking out a target candidate use case from the candidate use case set and carrying out coverage comparison with each reserved use case in the reserved use case set.

In a possible implementation manner, in the coverage comparison process, if a first reserved use case with a function covering the target candidate use case exists in the reserved use case set, the target candidate use case is eliminated, and execution is started again from the step of judging whether the candidate use case which is not taken out exists in the candidate use case set.

In another possible implementation manner, in the coverage comparison process, if a second reserved use case which is functionally covered by the target candidate use case exists in the reserved use case set, the second reserved use case is removed from the reserved use case set, the target candidate use case is added to the reserved use case set, and the step of judging whether the candidate use case which is not taken out exists in the candidate use case set is performed again.

In yet another possible implementation manner, in the coverage comparison process, if the first reserved use case does not exist in the reserved use case set and the second reserved use case does not exist, the target candidate use case is added to the reserved use case set, and execution is started again from the step of judging whether the candidate use case which is not taken out exists in the candidate use case set.

In the embodiment of the application, if no candidate use case which is not taken out exists in the candidate use case set, the reserved use case in the reserved use case set is used as the recommended use case.

In summary, in the technical scheme provided by the embodiment of the application, the recommended cases are determined by screening the candidate cases, and under the condition that one call chain corresponds to a plurality of cases, the problem that the number of the candidate cases preliminarily determined according to the first call chain is too large is considered, the candidate cases are screened based on the function coverage relation among the cases to obtain the final recommended cases, so that the number of the recommended cases is reduced, and the efficiency of the whole regression test is improved.

Next, the corresponding relationship between the use case and the call chain and the manner of obtaining the corresponding relationship between the code and the call chain are introduced.

Referring to fig. 4, a flowchart of a method for acquiring a correspondence between a use case and a call chain according to an embodiment of the present application is shown. The steps of the method may be performed by the terminal device 50 and/or the server 60 (hereinafter collectively referred to as "computer devices") of fig. 2 described above. The method may comprise at least one of the following steps (401-403):

step 401, responding to an operation instruction for any use case in the target application program, and operating the use case.

The run instruction is used to control the running of the use case. The operation instruction may be an instruction initiated by the computer device automatically or an instruction initiated by the user, which is not limited in this embodiment of the application. In the embodiment of the application, the computer device executes any use case in the target application program under the condition that the execution instruction for the use case is detected.

In some embodiments, in order to record the use case running process, the computer device runs the use case and starts recording the use case running process when detecting a running instruction for any use case in the target application program, and then stops running the use case and stops recording the use case running process when detecting a stopping instruction for the use case, and generates a video file for recording the use case running process.

In some embodiments, after obtaining the video file, the computer device may directly store the video file as recorded data for the use case; alternatively, the computer device may perform framing processing on the video file to obtain video image frames, and store the video image frames as recording data for the use case.

Of course, in an exemplary embodiment, a computer device may also run multiple use cases. In a possible implementation, the execution instruction is used for controlling the execution of a plurality of use cases. After detecting the operation instruction, the computer device operates the multiple use cases based on the execution sequence of the operation instruction, and records the operation process of the multiple use cases. And then, stopping running the use case when a stop instruction is detected, and generating a video file for recording a plurality of use case running processes. In some embodiments, after acquiring the video file, the computer device may extract, from the video file, each use case that corresponds to the video file for storage; or, the computer device may also extract the video files corresponding to the respective use cases from the video file, perform framing processing on the video files corresponding to the respective use cases to obtain video image frames corresponding to the respective use cases, and store the video image frames as recording data.

Step 402, acquiring a second code executed in the target application program in the process of running the use case.

In the embodiment of the application, in the process of running the use case, the computer device acquires the second code executed in the target application program in the process of running the use case.

Step 403, determining the call chain corresponding to the second code as the call chain corresponding to the use case based on the corresponding relationship between the codes and the call chain, and recording the corresponding relationship between the use case and the call chain.

In the embodiment of the application, after the computer device obtains the second code, based on the corresponding relationship between the code and the call chain, the call chain corresponding to the second code is determined as the call chain corresponding to the use case, and the corresponding relationship between the use case and the call chain is recorded.

If the correspondence between the code and the call chain may be stored in the computer device in advance, or may be stored in other computer devices to reduce the storage load of the computer device, which is not limited in the embodiment of the present application.

In summary, in the technical scheme provided in the embodiment of the present application, in the process of running a use case, a code is used as a link, and according to the code required by the running use case and the corresponding relationship between the code and the call chain, the corresponding relationship between the use case and the call chain is determined, and the use case and the call chain are directly associated, so that a recommended use case to be tested is determined according to the call chain associated with the change function in the subsequent process, the management performance for the use case is optimized, and the efficiency of the whole regression test is improved.

Referring to fig. 5, a flowchart of a method for obtaining a correspondence between code and a call chain according to an embodiment of the present application is shown. The steps of the method may be performed by the terminal device 50 and/or the server 60 (hereinafter collectively referred to as "computer devices") of fig. 2 described above. The method can comprise at least one of the following steps (501-503):

step 501, performing instrumentation and compiling on any code included in the target application program to obtain a target function included in the code.

Instrumentation compilation refers to inserting instrumentation pointers during code compilation. In the embodiment of the application, after detecting any code included in the target application program submitted by a user, the computer device performs instrumentation and compilation on the code to obtain the target function included in the code. The objective function may be any function in the code, which is not limited in the embodiment of the present application.

Step 502, obtaining other functions having a calling relationship with the target function, and obtaining a calling chain corresponding to the target function.

In this embodiment of the application, after obtaining the target function, the computer device obtains, from the code, another function having a call relationship with the target function, and obtains a call chain corresponding to the target function. In some embodiments, the computer device obtains a calling function called by the target function in the presence of the calling function in the target function, determines the calling function called by the target function as a new target function, and starts executing the step of obtaining the calling function called by the target function in the presence of the calling function in the target function until the calling function does not exist in the target function; and further, obtaining a call chain corresponding to the target function based on the call relation between the target function and other functions in the code.

Step 503, taking the call chain corresponding to the target function as the call chain corresponding to the code, and recording the corresponding relationship between the code and the call chain.

In the embodiment of the application, after obtaining the call chain corresponding to the target function, the computer device takes the call chain corresponding to the target function as the call chain corresponding to the code, and records the corresponding relationship between the code and the call chain.

In some embodiments, the code corresponds to multiple call chains. After obtaining the call chain corresponding to the target function, the computer device obtains a function without a call relation with the target function from the code, repeats the steps by taking the function as a new target function, so as to obtain the call chain corresponding to the new target function, and so on until no function other than the call chain exists in the code.

In summary, in the technical solution provided in the embodiment of the present application, the call chain corresponding to the code is obtained through instrumentation and compilation of the code, the management performance for the code and the call chain is optimized, and subsequently, the code can be used as a link to determine the correspondence between the use case and the call chain according to the code required by running the use case and the correspondence between the code and the call chain.

In addition, referring to fig. 6, a complete description is given of a case recommendation method in the present application. The method comprises the following specific steps:

at step 601, the developer submits the code of the target application program to the computer device.

Step 602, the computer device performs instrumentation coding on the code of the target application program through the compiling plug-in, and obtains a code compiling result.

Step 603, the background service of the use case recommendation platform in the computer device determines and stores the corresponding relationship between the code and the call chain according to the code compiling result.

Step 604, the tester initiates an operation instruction for the use case to the computer device.

Step 605, the computer device runs the use case and records the use case running process.

And 606, determining the call chain corresponding to the use case by the computer equipment according to the code corresponding to the use case and the call chain corresponding to the code.

In step 607, the tester sends a stop instruction for the use case to the computer device.

At step 608, the computer device stops running the use case.

Step 609, the computer device reports the recorded data to the background service of the use case recommendation platform through the reporting interface.

Step 610, the background service of the use case recommendation platform analyzes the recorded data to determine and record the corresponding relationship between the use case and the call chain, and the recorded data of the use case.

At step 611, the developer submits the first code to the computer device.

Step 612, calculating a change function of the first code by using the background service of the case recommendation platform.

Step 613, the background service of the use case recommendation platform calculates a first call chain according to the change function.

And 614, determining the recommended use case to be tested according to the corresponding relation between the use case and the call chain by the background service of the use case recommendation platform.

And 615, displaying a recommended case list to a developer through a recommended case interface by a client of the case recommendation platform.

In some embodiments, further comprising the steps of:

in step 616, the client of the use case recommendation platform displays the first call chain list to the developer by influencing the call chain interface.

The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.

Referring to fig. 7, a block diagram of a use case recommendation apparatus according to an embodiment of the present application is shown. The device has the function of realizing the use case recommendation method, and the function can be realized by hardware or by hardware executing corresponding software. The device can be computer equipment, and can also be arranged in the computer equipment. The apparatus 700 may include: a code acquisition module 710, a function determination module 720, a call chain determination module 730, and a use case determination module 740.

The code obtaining module 710 is configured to obtain a first code of a target application, where the first code is a code that is updated in the target application.

A function determining module 720, configured to determine a change function according to the first code.

A call chain determining module 730, configured to determine, based on the change function, a first call chain from at least one call chain included in the target application, where the first call chain refers to a call chain associated with the change function.

The use case determining module 740 is configured to determine, according to a corresponding relationship between the use case and the call chain, the use case corresponding to the first call chain as the recommended use case to be tested.

In an exemplary embodiment, the call chain determining module 730 is further configured to determine a calling function having a calling relationship with the change function; selecting a call chain including the alteration function or the call function from at least one call chain included in the target application program as the first call chain.

In an exemplary embodiment, the call chain determining module 730 is further configured to determine a second call chain from at least one call chain included in the target application, where the second call chain is a call chain including the change function and a call function having a call relationship with the change function; determining the calling function based on the second call chain.

In an exemplary embodiment, the call chain determining module 730 is further configured to perform instrumentation compilation on the first code, and determine a call function having a call relationship with the change function.

In an exemplary embodiment, the use case determining module 740 is further configured to:

determining a plurality of use cases corresponding to the first call chain as a candidate use case set according to the corresponding relation between the use cases and the call chain;

taking one candidate use case from the candidate use case set as a reserved use case, and adding the candidate use case into the reserved use case set;

judging whether the candidate use case set has a candidate use case which is not taken out or not;

if the candidate use case set has the candidate use case which is not taken out, taking out a target candidate use case from the candidate use case set and carrying out coverage comparison on each reserved use case in the reserved use case set;

if a first reserved case which functionally covers the target candidate case exists in the reserved case set, the target candidate case is removed, and the step of judging whether the candidate case set has the candidate case which is not taken out is executed again;

if a second reserved use case which is functionally covered by the target candidate use case exists in the reserved use case set, removing the second reserved use case from the reserved use case set, adding the target candidate use case to the reserved use case set, and executing from the step of judging whether the candidate use case set has the candidate use case which is not taken out again;

if the first reserved use case does not exist in the reserved use case set and the second reserved use case does not exist, adding the target candidate use case to the reserved use case set, and executing from the step of judging whether the candidate use case which is not taken out exists in the candidate use case set again;

and if the candidate use case set does not have the candidate use case which is not taken out, taking the reserved use case in the reserved use case set as the recommended use case.

In an exemplary embodiment, the function determining module 720 is further configured to:

acquiring a code modification position of the first code, wherein the code modification position refers to a position where code updating occurs in the first code;

determining the alteration function based on the code modification location.

In an exemplary embodiment, as shown in fig. 8, the apparatus 700 further comprises:

a use case running module 750, configured to respond to a running instruction for any use case in the target application program, and run the use case.

A first recording module 760, configured to acquire a second code executed in the target application program in the process of running the use case; and determining the call chain corresponding to the second code as the call chain corresponding to the use case based on the corresponding relation between the codes and the call chain, and recording the corresponding relation between the use case and the call chain.

a code compiling module 770, configured to perform instrumentation and compiling on any code included in the target application program to obtain an object function included in the code.

The second recording module 780 is configured to obtain other functions having a call relationship with the target function, and obtain a call chain corresponding to the target function; and taking the call chain corresponding to the target function as the call chain corresponding to the code, and recording the corresponding relation between the code and the call chain.

It should be noted that, when the apparatus provided in the foregoing embodiment implements the functions thereof, only the division of the functional modules is illustrated, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the apparatus may be divided into different functional modules to implement all or part of the functions described above. In addition, the apparatus and method embodiments provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.

Referring to fig. 9, a block diagram of a computer device according to an embodiment of the present application is shown. The computer equipment can be used for realizing the functions of the use case recommendation method. Specifically, the method comprises the following steps:

the computer apparatus 900 includes a Central Processing Unit (CPU) 901, a system Memory 904 including a Random Access Memory (RAM) 902 and a Read Only Memory (ROM) 903, and a system bus 905 connecting the system Memory 904 and the CPU 901. The computer device 900 also includes a basic Input/Output system (I/O system) 906 for facilitating information transfer between devices within the computer, and a mass storage device 907 for storing an operating system 913, application programs 914, and other program modules 915.

The basic input/output system 906 includes a display 908 for displaying information and an input device 909 such as a mouse, keyboard, etc. for user input of information. Wherein a display 908 and an input device 909 are connected to the central processing unit 901 through an input-output controller 910 connected to the system bus 905. The basic input/output system 906 may also include an input/output controller 910 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, input-output controller 910 also provides output to a display screen, a printer, or other type of output device.

The mass storage device 907 is connected to the central processing unit 901 through a mass storage controller (not shown) connected to the system bus 905. The mass storage device 907 and its associated computer-readable media provide non-volatile storage for the computer device 900. That is, the mass storage device 907 may include a computer-readable medium (not shown) such as a hard disk or a CD-ROM (Compact disk Read-Only Memory) drive.

Without loss of generality, computer readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash Memory or other solid state Memory, CD-ROM, DVD (Digital Video Disc) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that computer storage media is not limited to the foregoing. The system memory 904 and mass storage device 907 described above may be collectively referred to as memory.

According to various embodiments of the present application, the computer device 900 may also operate as a remote computer connected to a network via a network, such as the Internet. That is, the computer device 900 may be connected to the network 912 through the network interface unit 911 on the system bus 905, or may be connected to another type of network or remote computer system (not shown) using the network interface unit 911.

The memory also includes a computer program stored in the memory and configured to be executed by the one or more processors to implement the use case recommendation method described above.

In an exemplary embodiment, a computer readable storage medium is also provided, in which at least one instruction, at least one program, a set of codes, or a set of instructions is stored, which when executed by a processor, implements the above-mentioned use case recommendation method.

Optionally, the computer-readable storage medium may include: ROM (Read Only Memory), RAM (Random Access Memory), SSD (Solid State drive), or optical disc. The Random Access Memory may include a ReRAM (resistive Random Access Memory) and a DRAM (Dynamic Random Access Memory).

In an exemplary embodiment, a computer program product or computer program is also provided, the 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 executes the computer instructions, so that the computer device executes the use case recommendation method.

It should be understood that reference to "a plurality" herein means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. In addition, the step numbers described herein only exemplarily show one possible execution sequence among the steps, and in some other embodiments, the steps may also be executed out of the numbering sequence, for example, two steps with different numbers are executed simultaneously, or two steps with different numbers are executed in a reverse order to the order shown in the figure, which is not limited by the embodiment of the present application.

The above description is only exemplary of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like that are made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A use case recommendation method, the method comprising:

determining a change function according to the first code;

2. The method according to claim 1, wherein said determining a first call chain from at least one call chain included in the target application based on the change function comprises:

determining a calling function having a calling relationship with the changing function;

and selecting a call chain containing the change function or the call function from at least one call chain contained in the target application program as the first call chain.

3. The method of claim 2, wherein determining the calling function having a calling relationship with the altering function comprises at least one of:

determining a second call chain from at least one call chain contained in the target application program, wherein the second call chain is a call chain containing the change function and a call function with a call relation with the change function; determining the calling function based on the second calling chain;

and performing instrumentation and compiling on the first code, and determining a calling function having a calling relationship with the change function.

4. The method according to claim 1, wherein the determining, according to the correspondence between the use cases and the call chains, the use case corresponding to the first call chain as the recommended use case to be tested comprises:

if a second reserved use case which is functionally covered by the target candidate use case exists in the reserved use case set, removing the second reserved use case from the reserved use case set, adding the target candidate use case into the reserved use case set, and executing from the step of judging whether the candidate use case set has the candidate use case which is not taken out again;

5. The method of claim 1, wherein determining a change function based on the first code comprises:

determining the alteration function based on the code modification location.

6. The method according to any one of claims 1 to 5, further comprising:

responding to an operation instruction aiming at any use case in the target application program, and operating the use case;

acquiring a second code executed in the target application program in the process of running the use case;

and determining the call chain corresponding to the second code as the call chain corresponding to the use case based on the corresponding relation between the codes and the call chain, and recording the corresponding relation between the use case and the call chain.

7. The method of claim 6, further comprising:

performing instrumentation and compiling on any code contained in the target application program to obtain a target function contained in the code;

acquiring other functions having a calling relation with the target function to obtain a calling chain corresponding to the target function;

and taking the call chain corresponding to the target function as the call chain corresponding to the code, and recording the corresponding relation between the code and the call chain.

8. A use case recommendation apparatus, the apparatus comprising:

and the use case determining module is used for determining the use case corresponding to the first call chain as the recommended use case to be tested according to the corresponding relation between the use case and the call chain.

9. A computer device, characterized in that the computer device comprises a processor and a memory, wherein at least one program is stored in the memory, and the at least one program is loaded and executed by the processor to implement the use case recommendation method according to any one of claims 1 to 7.

10. A computer-readable storage medium, wherein at least one program is stored in the storage medium, and the at least one program is loaded and executed by a processor to implement the use case recommendation method according to any one of claims 1 to 7.