CN112363927A - Code testing method and device, computer equipment and storage medium - Google Patents

Abstract

The application relates to a code testing method, a code testing device, computer equipment and a storage medium. According to the method, a first performance parameter difference value and a second performance parameter difference value are obtained, the problem troubleshooting range is continuously and rapidly narrowed through a mode of comparing the difference values with a preset threshold value, and when the second performance parameter difference value is larger than the preset threshold value and the installation package to be verified and the reference installation package are adjacent installation packages according to the updating sequence, the fact that the code loopholes exist in the installation package to be verified is determined. By adopting the method, the efficiency and the accuracy of code vulnerability positioning can be improved on the whole.

Description

Code testing method and device, computer equipment and storage medium

Technical Field

The present application relates to the field of software testing technologies, and in particular, to a code testing method and apparatus, a computer device, and a storage medium.

Background

In the software development process, the iterative updating speed of the software version is extremely high, and even a certain functional module of a certain version of software can update the code for many times in one day.

Because the situation that a certain code installation package is vulnerable to updating is difficult to avoid in the code updating process, the existing solution is to test the new version software after the software version is updated in a manual mode, and when a problem exists in a certain functional module, massive installation package submission records and contents related to the functional module are screened one by one in a manual mode, and finally the problem existing in the installation package submitted in a certain time can be found.

The existing code problem positioning mode needs to consume a large amount of time for manual screening, and manual operation easily causes errors, so that the code vulnerability positioning accuracy is influenced.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a code testing method, apparatus, computer device, and storage medium capable of improving efficiency and accuracy of code vulnerability location.

A code testing method, comprising: acquiring a first performance parameter difference value, wherein the first performance parameter difference value is a difference value of performance parameter test values of a latest installation package and a reference installation package; when the first performance parameter difference value is larger than a preset threshold value and the latest installation package and the reference installation package are not adjacent installation packages according to the updating sequence, taking one installation package between the latest installation package and the reference installation package as an installation package to be verified; acquiring a second performance parameter difference value, wherein the second performance parameter difference value is a difference value of the performance parameter test values of the installation package to be verified and the reference installation package; when the second performance parameter difference is smaller than the preset threshold value, taking the installation package to be verified as a new reference installation package, and returning to the step of obtaining the first performance parameter difference; when the second performance parameter difference is larger than the preset threshold value and the to-be-verified installation package and the reference installation package are not adjacent installation packages according to the updating sequence, taking one installation package between the to-be-verified installation package and the reference installation package as a new to-be-verified installation package, and returning to the step of obtaining the second performance parameter difference; and when the second performance parameter difference value is larger than the preset threshold value and the installation package to be verified and the reference installation package are adjacent installation packages according to the updating sequence, determining that the installation package to be verified has a code bug.

In one embodiment, the method further comprises: when the first performance parameter difference value is not greater than a preset threshold value, storing a performance parameter test value of a latest installation package of the code test, and taking the latest installation package as a reference installation package of the next code test;

and/or

And after the installation package to be verified is taken as a new reference installation package, storing the performance parameter test value of the new reference installation package.

In one embodiment, the method further comprises: before the first performance parameter difference value is obtained, a code test instruction is obtained; obtaining the update information of the latest installation package of the code test according to the code test instruction; wherein the update information comprises at least one of an update time and an update specification; sending a performance test instruction to an automatic test module according to the update information to obtain a performance parameter test value of the latest installation package correspondingly returned by the automatic test module; and sending an information acquisition request to a storage module according to the code test instruction, and acquiring a performance parameter test value of the reference installation package correspondingly returned by the storage module.

In one embodiment, the taking one installation package between the latest installation package and the reference installation package as an installation package to be verified includes: and according to the updating sequence, updating the corresponding installation package of the primary code at the middle as the installation package to be verified.

In one embodiment, the taking one installation package between the latest installation package and the reference installation package as an installation package to be verified includes: determining an installation package from the series of installation packages as the installation package to be verified according to the attribute information of the series of installation packages; wherein the series of installation packages includes all installation packages whose update sequence is after the benchmark installation package and before the latest installation package;

in one embodiment, the attribute information includes one or more of a code line number, an update subject, and a development team of the installation package.

In one embodiment, the performance parameter test values include test values of one or more of fluency, physical memory actually used, and usage flow rate.

In one embodiment, the performance parameter test value is a fluency test value, the performance parameter difference value is a difference between the fluency test values of the latest installation package and the reference installation package, and the preset threshold value is 1%.

In one embodiment, the method further comprises: and generating a code problem report after the code vulnerability of the installation package to be verified is determined.

In one embodiment, the method further comprises: and sending the code problem report to a specified mailbox.

A code testing apparatus comprising: the first difference acquisition module is used for acquiring a first performance parameter difference; the first performance parameter difference value is a difference value of performance parameter test values of the latest installation package and the reference installation package; the first processing module is used for taking one installation package between the latest installation package and the reference installation package as an installation package to be verified when the first performance parameter difference value is larger than a preset threshold value and the latest installation package and the reference installation package are not adjacent installation packages according to the updating sequence; a second difference obtaining module, configured to obtain a second performance parameter difference, where the second performance parameter difference is a difference between the performance parameter test values of the to-be-verified installation package and the reference installation package; the second processing module is used for taking the installation package to be verified as a new reference installation package when the second performance parameter difference value is smaller than the preset threshold value, and returning to the step of obtaining the first performance parameter difference value; a third processing module, configured to, when the second performance parameter difference is greater than the preset threshold and the to-be-verified installation package and the reference installation package are not adjacent installation packages according to the update sequence, take an installation package between the to-be-verified installation package and the reference installation package as a new to-be-verified installation package, and return to the step of obtaining the second performance parameter difference; and the fourth processing module is used for determining that the installation package to be verified has a code bug when the second performance parameter difference is greater than the preset threshold value and the installation package to be verified and the reference installation package are adjacent installation packages according to the updating sequence.

A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the code testing method when executing the computer program.

A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the code testing method.

According to the code testing method, the device, the computer equipment and the storage medium, whether code bugs exist in the latest installation package and the benchmark installation package is judged by using the computer firstly, the problem is rapidly checked in a large range, then a new installation package to be verified can be set according to the comparison result of the performance parameter difference and the preset threshold, the problem is rapidly checked in a reduced range, and finally the installation package with the bugs is accurately determined.

Drawings

FIG. 1 is a diagram of an application environment of a code testing method in one embodiment;

FIG. 2 is a flow diagram illustrating a code testing method according to one embodiment;

FIG. 3 is a schematic flow chart of a code testing method in one embodiment;

FIG. 4 is a flow chart illustrating steps involved in performing the first performance parameter difference according to the magnitude of the first performance parameter difference, according to an embodiment;

FIG. 5 is a diagram illustrating some of the steps involved prior to obtaining a first performance parameter difference, in one embodiment;

FIG. 6 is a block diagram of a code testing apparatus according to an embodiment;

FIG. 7 is a diagram illustrating an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The code testing method provided by the application can be applied to the application environment shown in FIG. 1. The server 101 may communicate with the terminal 102 via a network, so as to obtain test data (including at least one performance parameter test value of at least one installation package) of the software installation package from the terminal 102. The server 101 may be implemented by an independent server or a server cluster composed of a plurality of servers; the terminal 102 may be, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices.

As shown in fig. 2, the present application provides a code testing method, which is described by taking the application of the method to the server 101 in fig. 1 as an example, and includes the following steps:

step S201, obtaining a first performance parameter difference value, wherein the first performance parameter difference value is a difference value of performance parameter test values of a latest installation package and a reference installation package;

step S202, when the first performance parameter difference value is larger than a preset threshold value and the latest installation package and the reference installation package are not adjacent installation packages according to the updating sequence, taking one installation package between the latest installation package and the reference installation package as an installation package to be verified;

step S203, obtaining a second performance parameter difference value, wherein the second performance parameter difference value is a difference value of performance parameter test values of the installation package to be verified and the reference installation package;

step S204, when the second performance parameter difference is not larger than the preset threshold, taking the installation package to be verified as a new reference installation package, and returning to execute the step S201;

step S205, when the second performance parameter difference is greater than the preset threshold and the installation package to be verified and the reference installation package are not adjacent installation packages according to the updating sequence, taking one installation package between the installation package to be verified and the reference installation package as a new installation package to be verified, and returning to execute the step S203;

and step S206, when the second performance parameter difference is larger than a preset threshold value and the installation package to be verified and the reference installation package are adjacent installation packages according to the updating sequence, determining that the installation package to be verified has a code bug.

The code testing method can be applied to one or more times of code testing requirements. Generally, in software development, for a certain functional module, a plurality of code updates may be completed every time period (for example, one day), accordingly, a plurality of installation packages (including but not limited to application packages suitable for android or apple operating systems) may be produced in an update sequence, accordingly, a code test may be performed for each such time period (for example, one day), and thus, a code test may be performed to determine whether the installation packages produced in the time period have a code vulnerability related to a certain performance parameter (for example, fluency). If a certain installation package has a code bug in the installation packages output in a certain time period, the relevant workers can know that the installation package is the reference installation package after the workers carry out bug fixing on the code bug of the installation package, and then the next code test is executed for the next time period. Each time period may have a fixed time length therebetween, or may have a different time length depending on actual settings, and is not particularly limited herein.

In addition, the updating sequence mentioned herein corresponds to the development sequence between installation packages. In essence, the update sequence represents a version iteration sequence between different installation packages, for example, a developer adds, deletes or modifies a code based on the content of the first installation package to obtain/output the second installation package, and if the update sequence is represented, the update time corresponding to the second installation package may be regarded as being later than the update time of the first installation package. In some examples, the order of the outputs of the series of installation packages may be regarded as an update order, and information (e.g., time information or sorting information) of the order of the outputs may be used as information of the update order; in some examples, when the computer system stores or uploads each installation package to a specified server or terminal in turn according to the development sequence, the information stored or uploaded in turn can be used as the information of the update sequence; in some examples, after the developers check the preliminary contents of the installation packages, the developers set related flag information for the installation packages according to the edition iteration order of the installation packages, and the flag information can also be used as update sequence information. In some flows, when related data processing is performed according to an update sequence, a step that information of the update sequence needs to be acquired may be implied, but according to some examples in the foregoing paragraph, the update sequence may be embodied as various types of sequences in different implementation occasions as long as the sequences are consistent with the sequence of development of the installation package. The present application does not particularly limit what means is required to obtain the information of the update sequence, and does not particularly limit the specific format and form of the information of the update sequence.

In step S201, the latest installation package refers to an installation package with the latest update time within a certain time period, and may also be understood as an installation package with the latest version within the time period. The reference installation package can be understood as the installation package with the oldest version in a certain time period. In fact, the corresponding latest installation package and the reference installation package may also change when the selected time period is different. In some cases, the latest installation package in the current time slot may sometimes be regarded as the reference installation package in the next time slot, as long as the version of the aforementioned latest installation package in the current time slot in the next time slot is the oldest in the installation packages of the series corresponding to the next time slot.

In step S201, the first performance parameter difference is a difference between a performance parameter test value of the latest installation package and a performance parameter test value of the reference installation package. Specifically, the obtaining of the first performance parameter difference may include: the server 101 may perform all or part of the steps of performing code testing on the reference installation package and the latest installation package, obtaining the performance parameter test value, and obtaining the phase difference value of the performance parameter test value, or even the server 101 may instruct other servers or terminals to perform all or part of the steps by a command. Generally, the performance parameter test value of the benchmark installation package is obtained and stored in the last code test, and can be obtained from the storage information; the server 101 may send the latest installation package to a test terminal (e.g., the terminal 102), or instruct another server to send the latest installation package to the test terminal, or the test terminal automatically downloads the latest installation package from the server 101 or another server, and after the test terminal installs the latest installation package, automatically perform a performance test on the latest installation package, and return the obtained performance parameter test value of the latest installation package to the server 101; the server 101 obtains a first performance parameter difference value according to the performance parameter test value of the latest installation package and the performance parameter test value of the reference installation package, where the first performance parameter difference value may be an absolute difference value, for example, a difference value obtained by subtracting the performance parameter test value of the reference installation package from the performance parameter test value of the latest installation package, and the first performance parameter difference value may be a relative difference value, for example, a reduction rate or an increase rate of the performance parameter test value of the latest installation package relative to the performance parameter test value of the reference installation package. In addition, the process executed by the test terminal may also be executed by an automatic test script installed on the terminal, where the automatic test script may be a script dedicated to testing a certain performance parameter, for example, a fluency automatic test script, or a script that may be used to test various performance parameters.

The first performance parameter difference obtained by the server 101 may relate to one performance parameter or more performance parameters. In some examples, the first performance parameter difference obtained by the server 101 is a difference of a performance parameter test value, for example, a difference of a fluency test value. In other examples, the first performance parameter difference may relate to two performance parameters, such as fluency and physical memory actually used. Of course, the first performance parameter difference may relate to more performance parameters. Correspondingly, the preset threshold value in step S202 may be different according to the number of terms of the performance parameter.

The preset threshold in step S202 may be the same value or different values in each code test, and may be specifically adjusted according to actual requirements. In some cases, this may also be the case: in the previous code test, if the first performance parameter difference is the difference between the fluency test values, the preset threshold is the preset threshold in the fluency aspect, and in the present code test, the first performance parameter difference is set as the difference between the actually used physical memory test values, and the preset threshold may be correspondingly set as the preset threshold in the actually used physical memory aspect. The specific numerical value of the preset threshold value can be set according to actual needs, for example, when the performance parameter is the fluency, if it is determined that the difference value between the fluency test value corresponding to the current installation package and the fluency test value corresponding to the previous installation package exceeds 1%, which is a condition that the software development requirement is not met, the preset threshold value can be set to 1%.

The adjacent installation packages in step S202 mean that no other installation packages exist between two installation packages in the update sequence. When the first performance parameter difference is larger than the preset threshold, the requirement of software development can be considered not to be met, namely, a code bug exists in the adjacent installation package. Generally, if the reference installation package is an installation package meeting the software development requirement, it may be determined whether the latest installation package meets the software development requirement, that is, whether a code bug exists, according to a difference between the first performance parameter difference and a preset threshold value. When the latest installation package and the reference installation package are not adjacent installation packages according to the updating sequence, the installation package with the code bugs is probably a middle installation package, and at the moment, if the installation packages are respectively checked one by one, the efficiency is low.

In step S203, the obtained second performance parameter difference is basically consistent with the obtained first performance parameter difference in principle, and is not expanded too much here. The difference is that the second performance parameter difference is a difference between the performance parameter test values of the to-be-verified installation package and the reference installation package.

Step S204 shows that if the second performance parameter difference is not larger than the preset threshold, the installation package between the reference installation package and the installation package to be verified does not have a code bug; at this time, it may be determined that the installation package between the installation package to be verified and the latest installation package (including the latest installation package) has a code bug, so that the installation package to be verified is used as a new reference installation package, and then step S201 is performed. Depending on the result of the re-execution of step S201, step S204, step S205 or step S206 may be correspondingly performed subsequently.

In step S204, after the installation package to be verified is used as a new reference installation package, the performance parameter test value of the new reference installation package may be saved. In this way, when step S201 is executed again, the performance parameter test value of the new benchmark installation package can be quickly acquired.

Step S205 indicates that, if the second performance parameter difference is greater than the preset threshold and the to-be-verified installation package and the reference installation package are not adjacent installation packages according to the update sequence, code bugs exist in the installation package (including the to-be-verified installation package) between the reference installation package and the to-be-verified installation package, at this time, an installation package between the to-be-verified installation package and the reference installation package needs to be used as a new to-be-verified installation package, and the inspection for further reducing the range is performed. The difference value between the performance parameter test value of the new installation package to be verified and the performance parameter test value of the reference installation package is the new second performance parameter difference value obtained in the step S203; step S204, step S205 or step S206 is then correspondingly performed according to the new second performance parameter difference.

Step S206 indicates that at least one of the installation packages is located with a code bug after the step is executed. Generally, after discovering that the installation package has a code bug, a developer may modify the code content of the installation package, and other installation packages developed based on the installation package content may also be modified accordingly.

In step S206, the mode of determining that the to-be-verified installation package has the code bug may be various, for example, text prompt information may be generated, where the text prompt information is used to prompt that the to-be-verified installation package has the code bug. Other types of presentation information such as symbols and graphics may be generated, and are not particularly limited.

According to the code testing method, whether code bugs exist in the latest installation package and the benchmark installation package or not is judged, the problem is rapidly checked in a large range, then a new installation package to be verified can be set according to the comparison result of the performance parameter difference and the preset threshold, the problem is rapidly checked in a reduced range, and finally the installation package with the bugs is accurately determined.

In an embodiment, as shown in fig. 3, after starting, M is obtained first, where M is a first performance parameter difference, and then a size relationship between M and L is determined, where L is a preset threshold.

When M is larger than L, judging whether the reference installation package and the latest installation package are adjacent installation packages, if so, determining that a code bug exists, and particularly determining that the latest installation package has the code bug; if not, determining the installation package to be verified from the installation packages between the reference installation package and the latest installation package, and then obtaining N, wherein N is the second performance parameter difference.

And judging the size relationship between N and L.

When N is larger than L, judging whether the reference installation package and the installation package to be verified are adjacent installation packages, and if so, determining that a code bug exists; and if not, returning to the step of determining the installation package to be verified, specifically taking one installation package between the current installation package to be verified and the reference installation package as a new installation package to be verified.

And when N is less than or equal to L, determining a new reference installation package, specifically, taking the current installation package to be verified as the new reference installation package, and then returning to the step of obtaining M.

And when M is less than or equal to L, ending, and taking the latest installation package of the code test as the reference installation package of the next code test.

In some embodiments, as shown in fig. 4, the code testing method further includes: and step S207, when the first performance parameter difference value is not greater than the preset threshold value, storing the performance parameter test value of the latest installation package of the current code test, and taking the latest installation package as the reference installation package of the next code test. Therefore, when the next code test is carried out, the performance parameter test value of the latest installation package of the current code test can be directly read as the performance parameter test value of the benchmark installation package of the next code test.

In some embodiments, as shown in fig. 4, the code testing method further includes: and S208, when the first performance parameter difference value is larger than a preset threshold value and the reference installation package and the latest installation package are adjacent installation packages, determining that the latest installation package has a code bug.

In some embodiments, as shown in fig. 5, the code testing method further includes:

step S101, before obtaining a first performance parameter difference value, obtaining a code test instruction;

step S102, obtaining the update information of the latest installation package of the code test according to the code test instruction; wherein the update information includes at least one of an update time and an update specification;

step S103, sending a performance test instruction to the automatic test module according to the update information to obtain a performance parameter test value of the latest installation package correspondingly returned by the automatic test module;

and step S104, sending an information acquisition request to the storage module according to the code test instruction, and acquiring a performance parameter test value of the reference installation package correspondingly returned by the storage module.

In step S101, the code test instruction is used to instruct the server 101 to perform code vulnerability screening for a certain time period or for a certain series of installation packages at the present time. Steps S101 to S104 are steps executed for the present code test instruction, and in an actual situation, the next code test instruction may also be obtained, and the foregoing steps are implemented according to the same principle. Generally, the code test instructions may be issued periodically or by manual confirmation, and the server 101 may start to perform the code test one time after acquiring the code test instructions.

In step S102, the update information corresponds to the installation package, so that the update order between the installation package and the installation package can be determined by the update information. The update time may refer to the output time of the installation package, or may refer to the time marked after the installation package passes through some auditing or confirmation processes, and is not particularly limited, and the update time may reflect the update sequence corresponding to the installation package. The update description is generally used for explaining the difference of a certain installation package in content compared with the last installation package, or for explaining the update subject, the development team and the like related to a certain installation package.

The hardware of the automatic test module and the storage module in steps S103 and S104 may exist in the terminal 102, or may exist in other devices (e.g., a server). In the field of software testing, when performance parameters of an installation package need to be acquired, developers generally develop an automatic test script and run the automatic test script to acquire corresponding performance parameters, which are the prior art and are not developed. Similarly, the automatic test module of the present application is configured to test the specified installation package according to the performance test instruction, and obtain a performance parameter test value of the installation package.

The storage module is used for storing some data generated in the code testing process, for example, the performance parameter testing value of the latest installation package in the last code testing process can be stored, the reference installation package of the code testing can be used as the reference installation package by the latest installation package of the last code testing, and the performance parameter testing value of the latest installation package of the code testing is obtained as the performance parameter testing value of the reference installation package of the code testing by sending a data obtaining request to the storage module.

Of course, the performance parameter test value of the reference installation package of the code test may also be manually set in advance and stored in the storage module in advance.

In some embodiments, in step S202, taking one installation package between the latest installation package and the reference installation package as the installation package to be verified, includes: and according to the updating sequence, updating the corresponding installation package with the code at the middle most as the installation package to be verified. For example, after a period of time, 4 new installation packages are produced, whether the installation packages have code bugs or not in the code test needs to be checked, at this time, the latest installation package of the previous code test can be used as the reference installation package of the code test, in this way, the first performance parameters corresponding to the reference installation package and the latest installation package of the code test are compared with a preset threshold, when the difference value of the first performance parameters is greater than the preset threshold, 3 installation packages are arranged between the reference installation package and the latest installation package of the code test, if the reference installation package is regarded as the first installation package according to the updating sequence, the 4 installation packages are regarded as the second installation package, the third installation package, the fourth installation package and the fifth installation package respectively, and at this time, the third installation package is selected as the installation package to be verified. The next step S203 is to obtain the difference value between the performance parameter test values of the third installation package and the reference installation package. In other cases, when the number of installation packages including the reference installation package is an even number, there are two installation packages at the middle, and in these cases, the installation package with the update sequence being earlier or later (i.e., updated) in the two installation packages may be used as the installation package to be verified; for example, when the reference installation package is the first installation package and the latest installation package is the eighth installation package, the fourth installation package or the fifth installation package may be used as the installation package to be verified. In any case, according to the updating sequence, the mode that the installation package corresponding to the code updating in the middle is taken as the installation package to be verified has important significance for quickly reducing the code vulnerability investigation range.

In some other embodiments, taking one of the latest installation package and the benchmark installation package as the installation package to be verified includes: determining an installation package from the series of installation packages as an installation package to be verified according to the attribute information of the series of installation packages; the installation packages of the series comprise all installation packages which are positioned after the reference installation package and before the latest installation package in the updating sequence. Generally, the attribute information includes one or more of the number of code lines of the installation package, an update subject and a development group to which the update subject belongs, and the attribute information can embody some characteristics of the installation package, including the importance degree of a certain installation package, the workload (such as the number of code lines traversed) required for performing a performance test on a certain installation package to obtain a performance parameter test value, and the like.

The mode of determining the installation package to be verified according to the attribute information of the installation package can reduce the investigation range in a more targeted manner according to the characteristics of the generated installation package.

Specifically, the installation package to be verified may be determined according to the number of code lines of the installation package as the attribute information, and the specific manner may also be various, including but not limited to:

(1) and taking the installation package with the most obvious change compared with the last version (the previous installation package) in the number of certain code lines between the reference installation package and the latest installation package as the installation package to be verified. For example, there are five installation packages, the reference installation package is regarded as the first installation package, and the other installation packages are regarded as the second, third, fourth, and fifth installation packages according to the update sequence (in the following description, when the five installation packages are used for various examples, such a distinction is also adopted, and the description is not repeated). At this moment, the number of code lines of the second installation package is increased by 1 thousand lines compared with that of the first installation package, the number of code lines of the third installation package is increased by 1 thousand lines compared with that of the second installation package, the number of code lines of the fourth installation package is increased by 2 thousand lines compared with that of the third installation package, the number of code lines of the fifth installation package is increased by 3 thousand lines compared with that of the fourth installation package, and at this moment, the number of code lines of the fourth installation package is changed most obviously compared with that of the previous version among the second installation package, the third installation package and the fourth installation package, so that the fourth installation package is selected as the installation package to be verified. The range to be further checked determined by the method contains the installation package with the most obvious code line number change, and the efficiency of positioning problems is improved to a certain extent.

(2) And determining the increment of the code line number from the reference installation package to the latest installation package, and taking the installation package corresponding to the median of the increment as the installation package to be verified. For example, there are five installation packages, the number of code lines of the second installation package is increased by 1 thousand lines compared with the first installation package, the number of code lines of the third installation package is increased by 1 thousand lines compared with the second installation package, the number of code lines of the fourth installation package is increased by 2 thousand lines compared with the third installation package, the number of code lines of the fifth installation package is increased by 3 thousand lines compared with the fourth installation package, the increment from the reference installation package to the latest installation package is 7 thousand lines, the median of the 7 thousand lines is 3.5 thousand lines, the installation package corresponding to the median (i.e., the installation package to which the code of the newly added 3.5 thousand lines belongs) is the fourth installation package, and the fourth installation package is taken as the installation package to be verified. In the mode, the range to be further checked is set to be about half of the total amount of the newly added codes through the number of the codes, so that the range to be checked is objectively ensured not to be too large or too small.

In other embodiments, the installation package to be verified may be determined according to the update topic or the development group to which the installation package belongs, for example, different weights may be set for different update topics or different development groups to which the installation package belongs, and installation packages corresponding to update topics or development groups which are more important or relate to more complex code content have higher weights. At this time, if there are five installation packages, the installation package with the highest weight value can be selected from the second, third and fourth installation packages as the installation package to be verified.

In some embodiments, the performance parameter test values include test values for one or more of fluency, physical memory actually used, and usage flow. Of course, in other embodiments, the performance parameter test value may also be a parameter of other code aspects.

In one embodiment, the performance parameter test value is a fluency test value, the performance parameter difference value is a difference between fluency test values of the latest installation package and the reference installation package, and the preset threshold value is 1%.

In some embodiments, the code testing method further comprises: and generating a code problem report after determining that the installation package to be verified has the code bug. Furthermore, the server 101 may also send a code problem report to a designated mailbox, so that the relevant personnel can know the problem of the code test in time.

It should be understood that although the various steps in the flow charts of fig. 2-5 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 described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-5 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.

In one embodiment, as shown in FIG. 6, there is provided a code testing apparatus 600 comprising: a first difference obtaining module 601, a first processing module 602, a second difference obtaining module 603, a second processing module 604, a third processing module 605 and a fourth processing module 606, wherein:

a first difference obtaining module 601, configured to obtain a first performance parameter difference; the first performance parameter difference value is a difference value of performance parameter test values of the latest installation package and the reference installation package;

a first processing module 602, configured to, when the first performance parameter difference is greater than a preset threshold and the latest installation package and the reference installation package are not adjacent installation packages according to the update sequence, use one installation package between the latest installation package and the reference installation package as an installation package to be verified;

a second difference obtaining module 603, configured to obtain a second performance parameter difference, where the second performance parameter difference is a difference between the performance parameter test values of the to-be-verified installation package and the reference installation package;

the second processing module 604 is configured to, when the second performance parameter difference is not greater than the preset threshold, use the installation package to be verified as a new reference installation package, and return to the step of obtaining the first performance parameter difference;

a third processing module 605, configured to, when the second performance parameter difference is greater than the preset threshold and the to-be-verified installation package and the reference installation package are not adjacent installation packages according to the update sequence, take an installation package between the to-be-verified installation package and the reference installation package as a new to-be-verified installation package, and return to the step of obtaining the second performance parameter difference;

the fourth processing module 606 is configured to determine that a code bug exists in the to-be-verified installation package when the second performance parameter difference is greater than the preset threshold and the to-be-verified installation package and the reference installation package are adjacent installation packages according to the update sequence.

In one embodiment, the code testing apparatus further comprises:

a storage module (not shown) configured to store a performance parameter test value of a latest installation package of the current code test when the first performance parameter difference is not greater than a preset threshold, and use the latest installation package as a reference installation package of a next code test;

the storage module can also be used for storing the performance parameter test value of the new benchmark installation package after the installation package to be verified is used as the new benchmark installation package.

In one embodiment, the code testing apparatus further comprises:

a test instruction obtaining module (not shown) configured to obtain a code test instruction before obtaining the first performance parameter difference;

an update information obtaining module (not shown) configured to obtain, according to the code test instruction, update information of a latest installation package of the code test; wherein the update information includes at least one of an update time and an update specification;

a latest value obtaining module (not shown) for sending a performance test instruction to the automatic test module according to the update information to obtain a performance parameter test value of the latest installation package correspondingly returned by the automatic test module;

and a reference value obtaining module (not shown) for sending an information obtaining request to the storage module according to the code test instruction, and obtaining a performance parameter test value of the reference installation package correspondingly returned by the storage module.

In one embodiment, the first processing module is configured to use one installation package between the latest installation package and the reference installation package as the installation package to be verified, and includes: and according to the updating sequence, updating the corresponding installation package with the code at the middle most as the installation package to be verified.

In one embodiment, the first processing module is configured to use one installation package between the latest installation package and the reference installation package as the installation package to be verified, and includes: determining an installation package from the series of installation packages as an installation package to be verified according to the attribute information of the series of installation packages; the installation packages of the series comprise all installation packages which are positioned after the reference installation package and before the latest installation package in the updating sequence. The attribute information may include one or more of the number of code lines of the installation package, the subject of the update, and the development group to which the update belongs.

In one embodiment, the code testing device performs data processing, and the related performance parameter test values include test values of one or more of fluency, physical memory actually used, and usage flow. In one embodiment, the performance parameter test value is a fluency test value, the performance parameter difference value is a difference between fluency test values of the latest installation package and the reference installation package, and the preset threshold value is 1%.

In one embodiment, the code testing apparatus further comprises: and a report generation module (not shown) for generating a code problem report after determining that the installation package to be verified has the code bug.

The code testing apparatus may further include: and a report sending module (not shown) for sending the code problem report to a designated mailbox.

For the specific definition of the code testing device, reference may be made to the above definition of the code testing method, which is not described herein again. The modules in the code testing device can be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 7. The computer device comprises a processor, a memory and a network interface which are connected through a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The nonvolatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. Which computer program is executed by a processor to implement the aforementioned code testing method.

Those skilled in the art will appreciate that the architecture shown in fig. 7 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program: acquiring a first performance parameter difference value, wherein the first performance parameter difference value is a difference value of performance parameter test values of a latest installation package and a reference installation package; when the first performance parameter difference value is larger than a preset threshold value and the latest installation package and the reference installation package are not adjacent installation packages according to the updating sequence, taking one installation package between the latest installation package and the reference installation package as an installation package to be verified; acquiring a second performance parameter difference value, wherein the second performance parameter difference value is a difference value of the performance parameter test values of the installation package to be verified and the reference installation package; when the second performance parameter difference is not larger than the preset threshold value, taking the installation package to be verified as a new reference installation package, and returning to the step of obtaining the first performance parameter difference; when the second performance parameter difference is larger than the preset threshold value and the installation package to be verified and the reference installation package are not adjacent installation packages according to the updating sequence, taking one installation package between the installation package to be verified and the reference installation package as a new installation package to be verified, and returning to the step of obtaining the second performance parameter difference; and when the second performance parameter difference value is larger than a preset threshold value and the installation package to be verified and the reference installation package are adjacent installation packages according to the updating sequence, determining that the installation package to be verified has a code bug.

In one embodiment, the processor, when executing the computer program, further performs the steps of: when the first performance parameter difference value is not greater than a preset threshold value, storing a performance parameter test value of the latest installation package of the code test, and taking the latest installation package as a reference installation package of the next code test; and after the installation package to be verified is taken as a new reference installation package, the performance parameter test value of the new reference installation package can be stored.

In one embodiment, the processor, when executing the computer program, further performs the steps of: before the first performance parameter difference value is obtained, a code test instruction is obtained; according to the code test instruction, obtaining the update information of the latest installation package of the code test; wherein the update information includes at least one of an update time and an update specification; sending a performance test instruction to the automatic test module according to the update information to obtain a performance parameter test value of the latest installation package correspondingly returned by the automatic test module; and sending an information acquisition request to the storage module according to the code test instruction, and acquiring a performance parameter test value of the reference installation package correspondingly returned by the storage module.

In one embodiment, when the processor executes the computer program, taking one installation package between the latest installation package and the benchmark installation package as the installation package to be verified, and the method comprises the following steps: and according to the updating sequence, updating the corresponding installation package with the code at the middle most as the installation package to be verified.

In one embodiment, when the processor executes the computer program, taking one installation package between the latest installation package and the benchmark installation package as the installation package to be verified, and the method comprises the following steps: determining an installation package from the series of installation packages as an installation package to be verified according to the attribute information of the series of installation packages; the serial installation packages comprise all installation packages of which the updating sequence is positioned after the reference installation package and before the latest installation package; the attribute information may include one or more of the number of code lines of the installation package, the subject of the update, and the development group to which the update belongs.

In one embodiment, the performance parameter test values involved in the execution of the computer program by the processor include test values for one or more of fluency, physical memory actually used, and usage flow.

In one embodiment, when the processor executes the computer program, the performance parameter test value involved is a fluency test value, the performance parameter difference value is a difference between fluency test values of the latest installation package and the benchmark installation package, and the preset threshold value is 1%.

In one embodiment, the processor, when executing the computer program, further performs the steps of: after determining that the installation package to be verified has a code bug, generating a code problem report; further, the following steps may also be implemented: and sending the code problem report to a specified mailbox.

In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: acquiring a first performance parameter difference value, wherein the first performance parameter difference value is a difference value of performance parameter test values of a latest installation package and a reference installation package; when the first performance parameter difference value is larger than a preset threshold value and the latest installation package and the reference installation package are not adjacent installation packages according to the updating sequence, taking one installation package between the latest installation package and the reference installation package as an installation package to be verified; acquiring a second performance parameter difference value, wherein the second performance parameter difference value is a difference value of the performance parameter test values of the installation package to be verified and the reference installation package; when the second performance parameter difference is not larger than the preset threshold value, taking the installation package to be verified as a new reference installation package, and returning to the step of obtaining the first performance parameter difference; when the second performance parameter difference is larger than the preset threshold value and the installation package to be verified and the reference installation package are not adjacent installation packages according to the updating sequence, taking one installation package between the installation package to be verified and the reference installation package as a new installation package to be verified, and returning to the step of obtaining the second performance parameter difference; and when the second performance parameter difference value is larger than a preset threshold value and the installation package to be verified and the reference installation package are adjacent installation packages according to the updating sequence, determining that the installation package to be verified has a code bug.

In one embodiment, the computer program when executed by the processor further performs the steps of: when the first performance parameter difference value is not greater than a preset threshold value, storing a performance parameter test value of the latest installation package of the code test, and taking the latest installation package as a reference installation package of the next code test; and after the installation package to be verified is taken as a new reference installation package, the performance parameter test value of the new reference installation package can be stored.

In one embodiment, the computer program when executed by the processor further performs the steps of: before the first performance parameter difference value is obtained, a code test instruction is obtained; according to the code test instruction, obtaining the update information of the latest installation package of the code test; wherein the update information includes at least one of an update time and an update specification; sending a performance test instruction to the automatic test module according to the update information to obtain a performance parameter test value of the latest installation package correspondingly returned by the automatic test module; and sending an information acquisition request to the storage module according to the code test instruction, and acquiring a performance parameter test value of the reference installation package correspondingly returned by the storage module.

In one embodiment, a computer program, when executed by a processor, for defining an installation package between a latest installation package and a reference installation package as an installation package to be verified, includes: and according to the updating sequence, updating the corresponding installation package with the code at the middle most as the installation package to be verified.

In one embodiment, a computer program, when executed by a processor, for defining an installation package between a latest installation package and a reference installation package as an installation package to be verified, includes: determining an installation package from the series of installation packages as an installation package to be verified according to the attribute information of the series of installation packages; the serial installation packages comprise all installation packages of which the updating sequence is positioned after the reference installation package and before the latest installation package; the attribute information may include one or more of the number of code lines of the installation package, the subject of the update, and the development group to which the update belongs.

In one embodiment, the computer program, when executed by the processor, is configured to relate test values of performance parameters including test values of one or more of fluency, physical memory actually used, and usage flow.

In one embodiment, when the computer program is executed by the processor, the performance parameter test value involved is a fluency test value, the performance parameter difference value is a difference between fluency test values of the latest installation package and the benchmark installation package, and the preset threshold value is 1%.

In one embodiment, the computer program when executed by the processor further performs the steps of: after determining that the installation package to be verified has a code bug, generating a code problem report; further, the following steps may also be implemented: and sending the code problem report to a specified mailbox.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (10)

1. A method for code testing, the method comprising:

acquiring a first performance parameter difference value, wherein the first performance parameter difference value is a difference value of performance parameter test values of a latest installation package and a reference installation package;

when the first performance parameter difference value is larger than a preset threshold value and the latest installation package and the reference installation package are not adjacent installation packages according to the updating sequence, taking one installation package between the latest installation package and the reference installation package as an installation package to be verified;

acquiring a second performance parameter difference value, wherein the second performance parameter difference value is a difference value of the performance parameter test values of the installation package to be verified and the reference installation package;

when the second performance parameter difference is smaller than the preset threshold value, taking the installation package to be verified as a new reference installation package, and returning to the step of obtaining the first performance parameter difference;

when the second performance parameter difference is larger than the preset threshold value and the to-be-verified installation package and the reference installation package are not adjacent installation packages according to the updating sequence, taking one installation package between the to-be-verified installation package and the reference installation package as a new to-be-verified installation package, and returning to the step of obtaining the second performance parameter difference;

and when the second performance parameter difference value is larger than the preset threshold value and the installation package to be verified and the reference installation package are adjacent installation packages according to the updating sequence, determining that the installation package to be verified has a code bug.

2. The method of claim 1, further comprising:

when the first performance parameter difference value is not greater than a preset threshold value, storing a performance parameter test value of a latest installation package of the code test, and taking the latest installation package as a reference installation package of the next code test;

and/or

And after the installation package to be verified is taken as a new reference installation package, storing the performance parameter test value of the new reference installation package.

3. The method of claim 1, further comprising:

before the first performance parameter difference value is obtained, a code test instruction is obtained;

obtaining the update information of the latest installation package of the code test according to the code test instruction; wherein the update information comprises at least one of an update time and an update specification;

sending a performance test instruction to an automatic test module according to the update information to obtain a performance parameter test value of the latest installation package correspondingly returned by the automatic test module;

and sending an information acquisition request to a storage module according to the code test instruction, and acquiring a performance parameter test value of the reference installation package correspondingly returned by the storage module.

4. The method according to claims 1 to 3, wherein the taking one installation package between the latest installation package and the benchmark installation package as the installation package to be verified comprises:

and according to the updating sequence, updating the corresponding installation package of the primary code at the middle as the installation package to be verified.

5. The method according to claims 1 to 3,

taking one installation package between the latest installation package and the reference installation package as an installation package to be verified, including: determining an installation package from the series of installation packages as the installation package to be verified according to the attribute information of the series of installation packages; wherein the series of installation packages includes all installation packages whose update sequence is after the benchmark installation package and before the latest installation package;

preferably, the attribute information includes one or more of the number of code lines of the installation package, the subject of the update, and the development group to which the update belongs.

6. The method of claim 1,

the performance parameter test value comprises one or more test values of fluency, actually used physical memory and used flow;

preferably, the performance parameter test value is a fluency test value, the performance parameter difference value is a difference between the fluency test values of the latest installation package and the reference installation package, and the preset threshold value is 1%.

7. The method of claim 1,

the method further comprises the following steps: generating a code problem report after the installation package to be verified has the code bug;

preferably, the method further comprises: and sending the code problem report to a specified mailbox.

8. A code testing apparatus, characterized in that the apparatus comprises:

the first difference acquisition module is used for acquiring a first performance parameter difference; the first performance parameter difference value is a difference value of performance parameter test values of the latest installation package and the reference installation package;

the first processing module is used for taking one installation package between the latest installation package and the reference installation package as an installation package to be verified when the first performance parameter difference value is larger than a preset threshold value and the latest installation package and the reference installation package are not adjacent installation packages according to the updating sequence;

a second difference obtaining module, configured to obtain a second performance parameter difference, where the second performance parameter difference is a difference between the performance parameter test values of the to-be-verified installation package and the reference installation package;

the second processing module is used for taking the installation package to be verified as a new reference installation package when the second performance parameter difference value is smaller than the preset threshold value, and returning to the step of obtaining the first performance parameter difference value;

a third processing module, configured to, when the second performance parameter difference is greater than the preset threshold and the to-be-verified installation package and the reference installation package are not adjacent installation packages according to the update sequence, take an installation package between the to-be-verified installation package and the reference installation package as a new to-be-verified installation package, and return to the step of obtaining the second performance parameter difference;

and the fourth processing module is used for determining that the installation package to be verified has a code bug when the second performance parameter difference is greater than the preset threshold value and the installation package to be verified and the reference installation package are adjacent installation packages according to the updating sequence.

9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 7 are implemented when the computer program is executed by the processor.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.

Images