CN112115046B - Software fault positioning method, device and terminal - Google Patents
Software fault positioning method, device and terminal Download PDFInfo
- Publication number
- CN112115046B CN112115046B CN202010866121.XA CN202010866121A CN112115046B CN 112115046 B CN112115046 B CN 112115046B CN 202010866121 A CN202010866121 A CN 202010866121A CN 112115046 B CN112115046 B CN 112115046B
- Authority
- CN
- China
- Prior art keywords
- software
- sub
- construction
- project
- code warehouse
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000010276 construction Methods 0.000 claims abstract description 165
- 230000010354 integration Effects 0.000 claims abstract description 67
- 238000004590 computer program Methods 0.000 claims description 20
- 230000008569 process Effects 0.000 description 19
- 238000011161 development Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 7
- 239000000243 solution Substances 0.000 description 6
- 239000000872 buffer Substances 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000001514 detection method Methods 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000002347 injection Methods 0.000 description 1
- 239000007924 injection Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000002459 sustained effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application is applicable to the technical field of continuous software integration, and provides a software fault positioning method, a device and a terminal, wherein the method comprises the following steps: acquiring a version number of software corresponding to the software fault information; determining a construction integrated information file corresponding to the software according to the version number; the construction data of each sub-project code warehouse contained in the software is integrated in the construction integrated information file, and the software comprises at least one sub-project code warehouse; and according to the software fault information and the construction data, locating and obtaining a target sub-project code warehouse with fault occurrence from at least one sub-project code warehouse. The scheme can improve the convenience and accuracy of software fault positioning.
Description
Technical Field
The application belongs to the technical field of continuous software integration, and particularly relates to a software fault positioning method, device and terminal.
Background
Currently, terminal devices generally enrich their functions by installing software having various functions, for example, a variety of android applications (software in a smart phone is also called an application) can be installed on a mobile phone of an android system.
In software development, many software (applications) are developed in team cooperation requiring multiple persons, i.e., team development members need to integrate their work often, which also means that multiple integration may occur during the software development process.
With the increasing complexity of the existing software project, which means that the software structure is more and more complex and the scale is larger and larger, a product is usually divided into a plurality of development modules, even more than ten development modules, for development and integration, different development modules correspond to different project code warehouses, and each development module is divided into several stages for carrying out: code synchronization, code compilation, build packaging, injection compilation, test compilation, unit testing, etc., and each development module for each product is frequently integrated multiple times per day. The more integration times are more progress nodes representing the software project, the more software project versions are generated, which leads to that when the software fault problem occurs, the sub project code warehouse needs to be traversed in different software versions to locate the sub project code warehouse where the fault occurs, and the specific fault of the software code is difficult to be quickly and accurately located.
Disclosure of Invention
The embodiment of the application provides a software fault positioning method, a device and a terminal, which are used for solving the problem that when the problem of software faults occurs in the existing software continuous integration, the sub-project code warehouse needs to be traversed in different software versions to position the specific faults of the software codes in which sub-project code warehouse the faults occur, and the specific faults of the software codes are difficult to position quickly and accurately.
A first aspect of an embodiment of the present application provides a software fault locating method, including:
acquiring a version number of software corresponding to the software fault information;
determining a construction integrated information file corresponding to the software according to the version number; the construction data of each sub-project code warehouse contained in the software is integrated in the construction integrated information file, and the software comprises at least one sub-project code warehouse;
and according to the software fault information and the construction data, locating and obtaining a target sub-project code warehouse with fault occurrence from at least one sub-project code warehouse.
A second aspect of the embodiments of the present application provides a software fault locating device, including:
the first acquisition module is used for acquiring the version number of the software corresponding to the software fault information;
the determining module is used for determining a construction integrated information file corresponding to the software according to the version number; the construction data of each sub-project code warehouse contained in the software is integrated in the construction integrated information file, and the software comprises at least one sub-project code warehouse;
and the fault positioning module is used for positioning and obtaining a target sub-project code warehouse with faults from at least one sub-project code warehouse according to the software fault information and the construction data.
A third aspect of the embodiments of the present application provides a terminal comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method according to the first aspect when executing the computer program.
A fourth aspect of the embodiments of the present application provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements the steps of the method according to the first aspect.
A fifth aspect of the present application provides a computer program product for causing a terminal to carry out the steps of the method of the first aspect described above when the computer program product is run on the terminal.
As can be seen from the above, in the embodiment of the present application, by acquiring the version number of the software corresponding to the software fault information, according to the version number, the construction integration information file corresponding to the software and integrating the construction data of each sub-project code warehouse included in the software is determined, so that the target sub-project code warehouse with the fault is located from the sub-project code warehouses according to the software fault information and the construction data. According to the scheme, when a fault occurs, the software version number is utilized to find out the construction data of the sub-project code warehouse corresponding to the current version number, and further, according to the construction data and fault information, the target sub-project code warehouse with the fault is found out, so that the convenience and accuracy of fault location are improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following description will briefly introduce the drawings that are needed in the embodiments or the description of the prior art, it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart I of a software fault location method according to an embodiment of the present application;
FIG. 2 is a second flowchart of a software fault location method according to an embodiment of the present disclosure;
FIG. 3 is a framework structure diagram of a multi-project build integration provided by an embodiment of the present application;
FIG. 4 is a block diagram of a software fault locating device according to an embodiment of the present application;
fig. 5 is a block diagram of a terminal according to an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system configurations, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".
It should be understood that the sequence number of each step in this embodiment does not mean the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.
In order to illustrate the technical solutions described in the present application, the following description is made by specific examples.
Referring to fig. 1, fig. 1 is a flowchart of a software fault locating method according to an embodiment of the present application. As shown in fig. 1, a software fault locating method includes the following steps:
step 101, the version number of the software corresponding to the software fault information is obtained.
The development of a piece of software is often accompanied by continuous code integration operations. When the software is continuously integrated once, a corresponding version number is generated, and the software with different version numbers corresponds to different software development progress nodes.
When the software fault information is detected, the version number of the software corresponding to the software fault information can be judged according to the description information of the software fault. The method can be to acquire all version numbers of the software one by one, or to extract and interpret key information in the software fault information and match the related version numbers so as to acquire the version numbers of the software corresponding to the software fault information.
The sub-project code warehouses corresponding to the software with different version numbers are different from each other. The different types of the sub-project code warehouses include different record contents in the sub-project code warehouses corresponding to the software with different version numbers, different numbers of the sub-project code warehouses corresponding to the software with different version numbers, different ID addresses of the sub-project code warehouses corresponding to the software with different version numbers, and the like.
And 102, determining a construction integration information file corresponding to the software according to the version number.
Wherein, the construction data of each sub-project code warehouse contained in the software is integrated in the construction integrated information file. At least one sub-item code repository is included in the software.
The software may be a system software or an application software. A software can arrange different functional module settings to different personnel to implement development work to form different sub-project code warehouses, and programming codes of one sub-project module in the whole software are recorded in one sub-project code warehouse.
The construction data is specifically obtained by constructing each sub-project code warehouse contained in the software according to a continuous integration task.
Sustained integration refers to the integration of code into the backbone frequently (multiple times a day). Continuous integration is a software development practice, i.e. team development members often integrate their work, usually at least once a day per member, meaning that multiple integration may occur per day.
The version number is a unique number and is correspondingly generated along with each item integration of the software.
An automated build process includes automated compiling, distributing, deploying, testing, and the like. Each version of software is built from different sub-project code warehouses, and the code nodes, the built input parameters and the built environment of the sub-project code warehouses are different.
Here, a version number is associated with a construction integration information file, and construction data of sub-project code warehouses of software in each project integration process are summarized in the construction integration information file, so that recording and summarizing of construction information of the sub-project code warehouses in the project integration process are realized.
In the step, the acquisition of the construction integrated information file recorded with the construction data corresponding to the software of the version number is realized through the version number of the software, so that the construction data of the target version of the software can be traced, and the judgment and the positioning of the software faults are realized.
And step 103, positioning and obtaining a target sub-project code warehouse with faults from at least one sub-project code warehouse according to the software fault information and the construction data.
Here, the construction data includes identification information of sub-item code warehouses to be constructed, construction site information, node information of codes in different sub-item code warehouses, and the like.
The construction condition of each sub-project code warehouse in the software of the current software version can be traced back according to the construction data. The construction condition of each sub-project code warehouse is acquired, so that the target sub-project code warehouse with faults is further determined by combining software fault information.
The construction situation comprises a construction state, a construction process description and the like, wherein the construction state is for example construction success or construction failure, and the construction process description can be specifically information of the number of times of trying to construct, construction time, problems occurring in construction and the like; this is illustrative only and not limiting.
In the process, the checking and determining of each sub-project code warehouse with the construction problem in the software of the current software version are realized through the software fault information and the construction data, and the confirmation of the construction state of the sub-project code warehouse of the current version is jointly realized through the two information, so that when the software problem occurs, related software codes can be rapidly and accurately positioned, the positioning speed of the specific fault problem is improved, the fault solving efficiency is improved, and the reverse positioning function of the fault of the software release version is realized.
As an alternative embodiment, the locating and obtaining the target sub-project code warehouse with fault from at least one sub-project code warehouse according to the software fault information and the construction data includes:
determining a related sub-project code warehouse of the software fault information from at least one sub-project code warehouse according to the software fault information; acquiring the construction state of the related sub-project code warehouse according to the construction data; and locating and obtaining a target sub-item code warehouse with faults from the related sub-item code warehouses according to the construction state.
The construction state may be a state of successful construction, a state of failed construction, or a state of delayed construction process.
The related sub-project code warehouse is one or more sub-project code warehouses pointed by the software fault information; more specifically, the related sub-item code repository is a sub-item code repository in which a software failure may occur, which is preliminarily determined according to the software failure information.
In a specific application process, when a fault occurs, determining a software version sequence number of the software with the fault, determining a construction integrated information file according to the version sequence number, determining a corresponding construction state according to construction data in the construction integrated information file and a sub-item code warehouse individual possibly related to the software fault, and finally analyzing and positioning a cause of the fault to complete a reverse analysis process from the whole software version fault to an integrated sub-item.
Through the implementation process, a software developer can quickly and accurately perform reverse positioning analysis, the construction state of the sub-item can be reversely restored when any software version fails, and the software version failure solving speed, the working efficiency of the software developer and the software version iteration speed are fully improved.
According to the method and the device, the corresponding relation between the integrated information file and the software version number is built through integration in advance, so that when faults occur, the built data of the sub-project code warehouse corresponding to the current version number can be searched through the software version number, the built data can be combined based on the fault information, the target sub-project code warehouse with the faults can be searched, and convenience and accuracy of fault location are improved.
Different implementations of a software fault locating method are also provided in the embodiments of the present application.
Referring to fig. 2, fig. 2 is a flowchart second of a software fault locating method according to an embodiment of the present application. As shown in fig. 2, a software fault locating method includes the following steps:
step 201, obtaining construction data for constructing each sub-project code warehouse contained in the software according to the continuous integration task.
The continuous integration task can be configured according to the current project progress, and specifically can configure a construction environment, construction input parameters, construction objects and the like.
The acquisition of the build data may be the acquisition of build configuration data prior to the start of the build, or the acquisition of build information data during the build process.
As an alternative embodiment, the building each sub-item code repository included in the software according to the continuous integration task includes:
dividing at least one sub-project code warehouse contained in the software into different construction project groups according to the set commonality information, and determining a continuous integration task corresponding to each construction project group; and constructing sub-project code warehouses contained in each constructed project group according to the continuous integration task.
The common information may be common information in information such as construction input parameters and warehouse configuration.
The software of an output version can be specifically constructed corresponding to dozens of sub-item warehouses, the sub-item warehouses are often divided into a plurality of constructed item groups according to the information of input parameters, warehouse configuration and the like, and the sub-item code warehouses in each group are constructed according to the groups.
And after each sub-item code warehouse is successfully constructed, outputting a result to be stored in a construction cache, and preparing for final version integration.
And 202, summarizing the construction data under the condition of carrying out project integration on each sub-project code warehouse after construction is completed, and obtaining a construction integration information file.
Wherein, after the construction of each sub-project code warehouse is completed, project integration is required for each sub-project code warehouse of which construction is completed.
Specifically, after constructing the sub-project code warehouse included in each construction project group according to the continuous integration task, it further includes: outputting a construction result of each construction project group; the project integration is carried out on each sub project code warehouse which is built, and the project integration comprises the following steps: integrating the construction result of each construction project group.
In specific implementation, the construction result of each construction project group and the construction data corresponding to each sub project code warehouse can be output to a construction output buffer together.
In connection with fig. 3, when the continuous integration task of the software is executed, different construction project groups may be constructed sequentially, the sub-project code warehouse included in each construction project group is constructed through the construction unit, the construction result is stored in the construction output buffer, and in the project integration stage, the construction result of each construction project group is integrated, and meanwhile, the construction data in the construction output buffer is integrated, so as to obtain the construction integration information file.
And 203, storing the version numbers of the software integrated with the project by associating the constructed integrated information file.
When the construction data is summarized, the construction data can be uniformly formatted and stored and issued together with the software version, so that key information such as construction integration sites and environments of each sub-project code warehouse corresponding to the target software version is uniformly formatted and stored and issued together with the software version, and the fault reverse positioning function of the software release version can be realized.
Wherein a software version contains a unique build integration information file that will be available for reverse fault locating operations based on the software version.
And (3) uniformly adding key information recording actions such as construction parameters, on-site states and the like in each construction unit, outputting the key information recording actions to a construction output buffer along with construction results, automatically gathering information of all sub-project construction buffers by a construction script in a project integration stage, and formatting and storing the information in a uniform file.
All sub-projects to be integrated are traversed, and the construction information of each sub-project is summarized and output to a designated file in a unified way, so that any software version contains a unique construction integrated information file which can be used for carrying out reverse operation on the software version.
In the process, when the software product version is constructed and output, key information such as a construction integration site, a construction environment and the like of each sub-project code warehouse are recorded and managed effectively in a standardized manner, so that when the software problem occurs in the output and release version, the state of the sub-project code warehouse in the software version is confirmed quickly, and the specific problem of the software code is positioned quickly and accurately.
Step 204, the version number of the software corresponding to the software fault information is obtained.
The implementation manner of this step is the same as that of step 101 in the foregoing implementation, and will not be repeated here.
And step 205, determining a construction integration information file corresponding to the software according to the version number.
The build integration information file integrates build data for each sub-item code repository contained in the software. At least one sub-item code repository is included in the software.
The implementation manner of this step is the same as that of step 102 in the foregoing implementation, and will not be repeated here.
And 206, positioning and obtaining a target sub-project code warehouse with faults from at least one sub-project code warehouse according to the software fault information and the construction data.
The implementation manner of this step is the same as that of step 103 in the foregoing implementation, and will not be repeated here.
In the embodiment of the application, by acquiring construction data for constructing each sub-project code warehouse included in software according to a continuous integration task, under the condition that project integration is carried out on each sub-project code warehouse after construction is completed, the construction data is summarized to obtain a construction integration information file, the construction integration information file is associated with the version number of the software after project integration, under the condition that software fault information is detected, the version number of the software corresponding to the software fault information is acquired, and according to the version number, the construction integration information file of the construction data of each sub-project code warehouse included in the integrated software corresponding to the software is determined, so that a target sub-project code warehouse with fault occurrence is positioned from the sub-project code warehouses according to the software fault information and the construction data. According to the scheme, in the continuous integration process of the software project, the construction data are recorded and summarized to obtain the construction integrated information file, and the corresponding relation between the construction integrated information file and the software version number is established, so that when a fault occurs, the construction data of the sub-project code warehouse corresponding to the current version number can be searched by utilizing the software version number, and further, according to the fault information and the construction data, the target sub-project code warehouse with the fault is searched, and the convenience and accuracy of fault positioning are improved.
Referring to fig. 4, fig. 4 is a block diagram of a software fault locating device according to an embodiment of the present application, and for convenience of explanation, only a portion related to the embodiment of the present application is shown.
The software fault location apparatus 400 includes:
a first obtaining module 401, configured to obtain a version number of software corresponding to the software failure information;
a determining module 402, configured to determine a build integrated information file corresponding to the software according to the version number; the construction data of each sub-project code warehouse contained in the software is integrated in the construction integrated information file, and the software comprises at least one sub-project code warehouse;
and the fault positioning module 403 is configured to position and obtain a target sub-project code warehouse in which a fault occurs from at least one sub-project code warehouse according to the software fault information and the construction data.
The fault location module 403 is specifically configured to:
determining a related sub-project code warehouse of the software fault information from at least one sub-project code warehouse according to the software fault information;
acquiring the construction state of the related sub-project code warehouse according to the construction data;
and according to the construction state, locating the target sub-item code warehouse with the fault from the related sub-item code warehouse.
Wherein the apparatus further comprises:
the second acquisition module is used for acquiring construction data for constructing each sub-project code warehouse contained in the software according to the continuous integration task;
the integration module is used for summarizing the construction data under the condition of carrying out project integration on each sub-project code warehouse after construction is completed, so as to obtain a construction integrated information file;
and the association storage module is used for carrying out association storage on the constructed integrated information file and the version number of the software after project integration.
Wherein the apparatus further comprises:
the construction module is used for dividing at least one sub-project code warehouse contained in the software into different construction project groups according to the set commonality information and determining continuous integration tasks corresponding to each construction project group; and constructing sub-project code warehouses contained in each constructed project group according to the continuous integration task.
The apparatus further comprises: the output module is used for outputting the construction result of each construction project group; correspondingly, the integration module is specifically configured to integrate the construction result of each construction project group.
The software fault locating device provided by the embodiment of the application can realize each process of the embodiment of the software fault locating method, and can achieve the same technical effect, and in order to avoid repetition, the description is omitted here.
Fig. 5 is a block diagram of a terminal according to an embodiment of the present application. As shown in the figure, the terminal 5 of this embodiment includes: at least one processor 50 (only one is shown in fig. 5), a memory 51 and a computer program 52 stored in the memory 51 and executable on the at least one processor 50, the processor 50 implementing the steps in any of the various method embodiments described above when executing the computer program 52.
The terminal 5 may be a computing device such as a desktop computer, a notebook computer, a palm computer, a cloud server, etc. The terminal 5 may include, but is not limited to, a processor 50, a memory 51. It will be appreciated by those skilled in the art that fig. 5 is merely an example of the terminal 5 and is not limiting of the terminal 5, and may include more or fewer components than shown, or may combine some components, or different components, e.g., the terminal may further include input and output devices, network access devices, buses, etc.
The processor 50 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The storage 51 may be an internal storage unit of the terminal 5, such as a hard disk or a memory of the terminal 5. The memory 51 may be an external storage device of the terminal 5, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the terminal 5. Further, the memory 51 may also include both an internal storage unit and an external storage device of the terminal 5. The memory 51 is used for storing the computer program as well as other programs and data required by the terminal. The memory 51 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal and method may be implemented in other manners. For example, the apparatus/terminal embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each method embodiment described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium contains content that can be appropriately scaled according to the requirements of jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is subject to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.
The present application may implement all or part of the procedures in the methods of the above embodiments, and may also be implemented by a computer program product, which when run on a terminal causes the terminal to implement steps in the embodiments of the methods described above.
The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.
Claims (8)
1. A method for locating a software fault, comprising:
acquiring a version number of software corresponding to the software fault information;
determining a construction integrated information file corresponding to the software according to the version number; the construction data of each sub-project code warehouse contained in the software is integrated in the construction integrated information file, and the software comprises at least one sub-project code warehouse;
according to the software fault information and the construction data, a target sub-project code warehouse with fault occurrence is obtained from at least one sub-project code warehouse in a positioning mode;
before the software version number corresponding to the software fault information is obtained, the method further comprises the following steps:
acquiring construction data for constructing each sub-project code warehouse contained in the software according to the continuous integration task;
under the condition of carrying out project integration on each sub-project code warehouse after construction, summarizing the construction data to obtain a construction integrated information file;
and storing the build integrated information file and the version number of the software integrated by the project in an associated mode.
2. The software fault locating method according to claim 1, wherein said locating a fault occurring target sub-item code repository from at least one of said sub-item code repositories based on said software fault information and said build data comprises:
determining a related sub-project code warehouse of the software fault information from at least one sub-project code warehouse according to the software fault information;
acquiring the construction state of the related sub-project code warehouse according to the construction data;
and according to the construction state, locating the target sub-item code warehouse with the fault from the related sub-item code warehouse.
3. The software fault locating method according to claim 1, wherein said constructing each sub-item code repository included in the software according to the continuous integration task includes:
dividing at least one sub-project code warehouse contained in the software into different construction project groups according to set commonality information, and determining a continuous integration task corresponding to each construction project group;
and constructing sub-project code warehouses contained in each constructed project group according to the continuous integration task.
4. A software fault locating method according to claim 3, wherein after said constructing sub-project code warehouses included in each of said constructed project groups according to said continuous integration task, further comprising:
outputting a construction result of each construction project group;
the project integration of each sub-project code warehouse after construction is completed comprises the following steps:
integrating the construction result of each construction project group.
5. A software fault locating device, comprising:
the first acquisition module is used for acquiring the version number of the software corresponding to the software fault information;
the determining module is used for determining a construction integrated information file corresponding to the software according to the version number; the construction data of each sub-project code warehouse contained in the software is integrated in the construction integrated information file, and the software comprises at least one sub-project code warehouse;
the fault positioning module is used for positioning and obtaining a target sub-project code warehouse with faults from at least one sub-project code warehouse according to the software fault information and the construction data;
the apparatus further comprises:
the second acquisition module is used for acquiring construction data for constructing each sub-project code warehouse contained in the software according to the continuous integration task;
the integration module is used for summarizing the construction data under the condition of carrying out project integration on each sub-project code warehouse after construction is completed, so as to obtain a construction integrated information file;
and the association storage module is used for carrying out association storage on the constructed integrated information file and the version number of the software after project integration.
6. The software fault location device of claim 5, wherein the fault location module is specifically configured to:
determining a related sub-project code warehouse of the software fault information from at least one sub-project code warehouse according to the software fault information;
acquiring the construction state of the related sub-project code warehouse according to the construction data;
and according to the construction state, locating the target sub-item code warehouse with the fault from the related sub-item code warehouse.
7. A terminal comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 4 when the computer program is executed.
8. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the steps of the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010866121.XA CN112115046B (en) | 2020-08-25 | 2020-08-25 | Software fault positioning method, device and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010866121.XA CN112115046B (en) | 2020-08-25 | 2020-08-25 | Software fault positioning method, device and terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112115046A CN112115046A (en) | 2020-12-22 |
| CN112115046B true CN112115046B (en) | 2023-12-29 |
Family
ID=73803703
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010866121.XA Active CN112115046B (en) | 2020-08-25 | 2020-08-25 | Software fault positioning method, device and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112115046B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107729258A (en) * | 2017-11-30 | 2018-02-23 | 扬州大学 | A kind of program mal localization method of software-oriented version problem |
| CN110830284A (en) * | 2018-08-14 | 2020-02-21 | 杭州达乎科技有限公司 | SDN network-based service fault monitoring method and device |
| CN111144839A (en) * | 2019-12-17 | 2020-05-12 | 深圳市优必选科技股份有限公司 | Project construction method, continuous integration system and terminal equipment |
-
2020
- 2020-08-25 CN CN202010866121.XA patent/CN112115046B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107729258A (en) * | 2017-11-30 | 2018-02-23 | 扬州大学 | A kind of program mal localization method of software-oriented version problem |
| CN110830284A (en) * | 2018-08-14 | 2020-02-21 | 杭州达乎科技有限公司 | SDN network-based service fault monitoring method and device |
| CN111144839A (en) * | 2019-12-17 | 2020-05-12 | 深圳市优必选科技股份有限公司 | Project construction method, continuous integration system and terminal equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112115046A (en) | 2020-12-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107273286B (en) | Scene automatic test platform and method for task application | |
| CN106951364B (en) | Test method and device | |
| CN111144839B (en) | Project construction method, continuous integration system and terminal equipment | |
| CN109783346B (en) | Keyword-driven automatic testing method and device and terminal equipment | |
| CN108111364B (en) | Service system testing method and device | |
| CN111190551B (en) | Redis data migration system, migration method, migration device and terminal | |
| CN111181805B (en) | Micro-service test baffle generation method and system based on test case | |
| US8661414B2 (en) | Method and system for testing an order management system | |
| CN112650688A (en) | Automated regression testing method, associated device and computer program product | |
| CN112948233A (en) | Interface testing method, device, terminal equipment and medium | |
| CN109284331A (en) | Accreditation information acquisition method, terminal device and medium based on business datum resource | |
| CN117493188A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN112115046B (en) | Software fault positioning method, device and terminal | |
| CN116738091A (en) | Page monitoring method and device, electronic equipment and storage medium | |
| CN113468058B (en) | Regression testing method and device for software as service platform and electronic equipment | |
| CN113868137A (en) | Method, device and system for processing buried point data and server | |
| CN113342600A (en) | Method and device for monitoring program dependent plug-in | |
| CN112631905A (en) | Execution process data management method and device, computer equipment and storage medium | |
| CN112632174A (en) | Data inspection method, device and system | |
| CN111274143A (en) | Buried point testing method, device, equipment and storage medium | |
| CN117688564B (en) | Detection method, device and storage medium for intelligent contract event log | |
| CN115250231B (en) | Application configuration method and device | |
| CN115545677B (en) | Online process specification detection method and system based on automatic case execution condition | |
| CN109446166B (en) | Method for detecting file directory, computer readable storage medium and terminal device | |
| CN113419738A (en) | Interface document generation method and device and interface management equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |