CN117271360A

CN117271360A - Front-end and back-end joint debugging method, device, equipment, medium and program product

Info

Publication number: CN117271360A
Application number: CN202311332759.5A
Authority: CN
Inventors: 徐蕾; 张双亮
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2023-10-16
Filing date: 2023-10-16
Publication date: 2023-12-22

Abstract

The present disclosure provides a front-and-back joint debugging method, which may be applied to the technical field of information security. The front-end and back-end joint debugging method comprises the following steps: receiving error messages uploaded from a user terminal, wherein the error messages comprise query information and problem description; acquiring link data in a database based on the query information, wherein the link data is logic link data from front end to back end of a function where the query information is located, and the link data comprises code development data and version development data; extracting the code development data and the version development data to obtain N responsible persons related to front-end joint debugging and back-end joint debugging, wherein N is a positive integer; and distributing the problem description and the link data to the N responsible persons. The present disclosure also provides a front-end and back-end joint debugging apparatus, device, storage medium, and program product.

Description

Front-end and back-end joint debugging method, device, equipment, medium and program product

Technical Field

The present disclosure relates to the field of information security technologies, and in particular, to a front-end and back-end joint debugging method, apparatus, device, medium, and program product.

Background

In the age of rapid development of the Internet, the colorful software of the mobile terminal and the PC terminal becomes an indispensable living tool in the hands of people, the software updating and iteration speed is continuously accelerated, the detail requirements of people on the software are also higher and higher, and the requirements on the period and quality of software development are higher. Because the product is on-line in a shorter period, the time for testing and checking the product is more intense. In this case, the test is also affected by long data links, unclear problem responsibility, difficulty in tracking problems, etc., resulting in insufficient execution of the test, low control over details of the data and User Interface (UI), and affecting customer experience.

Disclosure of Invention

In view of the foregoing, the present disclosure provides front-end and back-end joint debugging methods, apparatuses, devices, media, and program products that improve the efficiency of front-end and back-end joint debugging.

According to a first aspect of the present disclosure, there is provided a front-end and back-end joint debugging method, including: receiving error messages uploaded from a user terminal, wherein the error messages comprise query information and problem description; acquiring link data in a database based on the query information, wherein the link data is logic link data from front end to back end of a function where the query information is located, and the link data comprises code development data and version development data; extracting the code development data and the version development data to obtain N responsible persons related to front-end joint debugging and back-end joint debugging, wherein N is a positive integer; and distributing the problem description and the link data to the N responsible persons.

According to an embodiment of the present disclosure, after the distributing the problem description and the link data to the N responsible persons, the method further includes: receiving problem feedback from responsible persons; and maintaining a joint debugging task based on the received problem feedback, the joint debugging task being generated in response to the error message.

According to an embodiment of the present disclosure, the code development data includes code table values, and the maintaining joint debugging tasks based on the received problem feedback includes: classifying the received problem feedback to obtain a problem feedback category, wherein the problem feedback category comprises that the related code of the current responsible person has a problem and the related code of the current responsible person does not have a problem; judging whether the problem can be solved within a preset period or not under the condition that the related code of the responsible person has the problem; extracting a change code in the problem feedback under the condition that the problem can be solved within a preset period; acquiring a data table in the database based on the code table value; and modifying the data table based on the modification code.

According to an embodiment of the present disclosure, after the determining whether the problem can be solved within the preset period, the method further includes: under the condition that the problem can be solved within a preset period, the error message and the link data are put into a summarizing task; and timing up the error message and the link data by the summarizing task.

According to an embodiment of the present disclosure, after the classifying the received problem feedback to obtain a problem feedback category, the method further includes: under the condition that the relevant codes of the responsible person have no problem, the error message and the link data are put into a summarizing task; and timing up the error message and the link data by the summarizing task.

According to an embodiment of the present disclosure, the N responsible persons include a total responsible person, and the sending, by the summary task, the error message and the link data at regular time includes: and uploading the error message and the link data to the total responsible person.

According to the embodiment of the disclosure, M error messages and link data corresponding to the M error messages are maintained in the summarizing task, and M is a positive integer.

According to an embodiment of the disclosure, the query information includes a control number of the front end.

A second aspect of the present disclosure provides a front-end and back-end joint debugging device, including: the first receiving module is used for receiving error messages uploaded by the user terminal, wherein the error messages comprise query information and problem description; the query module is used for acquiring link data in a database based on the query information, wherein the link data is logic link data from front end to back end of a function where the query information is located, and the link data comprises code development data and version development data; the data extraction module is used for extracting the code development data and the version development data to obtain N responsible persons related to front and back end joint debugging, wherein N is a positive integer; and the distribution module is used for distributing the problem description and the link data to the N responsible persons.

According to an embodiment of the disclosure, the apparatus further comprises: the system comprises a second receiving module and a maintenance module, wherein the second receiving module is used for receiving problem feedback from a responsible person; and the maintenance module is used for maintaining joint debugging tasks based on the received problem feedback, wherein the joint debugging tasks are generated in response to the error message.

According to the embodiment of the disclosure, the code development data comprises code table values, and the maintenance module is used for classifying received problem feedback to obtain a problem feedback category, wherein the problem feedback category comprises that a problem exists in a relevant code of a current responsible person and a problem does not exist in a relevant code of the current responsible person; judging whether the problem can be solved within a preset period or not under the condition that the related code of the responsible person has the problem; extracting a change code in the problem feedback under the condition that the problem can be solved within a preset period; acquiring a data table in the database based on the code table value; and modifying the data table based on the modification code.

According to an embodiment of the disclosure, the maintenance module is configured to put the error message and the link data into a summary task when the problem can be solved within a preset period; and timing up the error message and the link data by the summarizing task.

According to the embodiment of the disclosure, the maintenance module is configured to put the error message and the link data into a summary task when the relevant code of the responsible person has no problem; and timing up the error message and the link data by the summarizing task.

A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the front-end and back-end joint debugging method described above.

A fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the front-end and back-end joint debugging method described above.

The fifth aspect of the present disclosure also provides a computer program product comprising a computer program which, when executed by a processor, implements the front-end and back-end joint debugging method described above.

In the embodiment of the disclosure, in order to solve the technical problem that the joint debugging efficiency is too low due to the adoption of the step-by-step front-and-back joint debugging process in the prior art, the data related to each end in the process of developing functions are integrated, a data link is laid out in advance, a problem investigation database is established, one-key positioning problem analysis personnel and timing summarizing problem solving conditions improve the working efficiency of development and test, help to quickly position a problem code block, improve the problem submitting speed and quickly assist in problem positioning.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be more apparent from the following description of embodiments of the disclosure with reference to the accompanying drawings, in which:

FIG. 1 schematically illustrates an application scenario diagram of a front-end and back-end joint debugging method according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow chart of a front-end and back-end joint debugging method in accordance with an embodiment of the present disclosure;

FIG. 3 schematically illustrates a flow chart of another front-end and back-end joint debugging method in accordance with an embodiment of the present disclosure;

FIG. 4 schematically illustrates a flow chart of a method of maintaining tasks according to an embodiment of the disclosure;

FIG. 5 schematically illustrates a flow chart of another maintenance task method according to an embodiment of the disclosure;

FIG. 6 schematically illustrates a flow chart of another maintenance task method according to an embodiment of the disclosure;

FIG. 7 schematically illustrates a flow diagram of a front-end and back-end joint debugging system in accordance with an embodiment of the present disclosure;

FIG. 8 schematically illustrates a block diagram of a front-end and back-end joint debugging device according to an embodiment of the present disclosure; and

fig. 9 schematically illustrates a block diagram of an electronic device adapted to implement a front-end and back-end joint debugging method in accordance with an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.

Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

In a typical scenario, taking a scenario number function in an APP as an example, the scenario number function is embedded in a main APP in an SDK manner, and page presentation data is acquired by the following two aspects: the official account in the scene number is obtained by the SDK, APP login user data are required to be obtained from the APP, different applications are managed in different development teams, and the data sources are more.

When a tester finds that the problem exists in the data display, the tester can directly find a front-end developer writing the page, the front-end searches a data source through a tracking code, possibly an interface or a local database or initializes incoming information, the data with the problem is fed back to the previous level, the data source of the previous level is required to be further checked upwards until the problem root is located, and finally a responsible person feeds back the problem after the problem is solved, and in the process, the tester needs to sequentially perform the problem verification test. Even without being affected by network environment, printing, etc., it is extremely time consuming, which greatly affects the on-line planning of the product.

Moreover, most of the company testers currently find problems, namely the problem is changed, and the retest flow is long and complex, so that the product quality improvement efficiency is low.

Therefore, a front-end and back-end joint debugging method capable of improving the problem verification efficiency in the soft-start development process is urgently needed.

In order to solve the technical problems in the prior art, an embodiment of the present disclosure provides a front-end and back-end joint debugging method, which receives an error message uploaded from a user terminal, where the error message includes query information and problem description; acquiring link data in a database based on the query information, wherein the link data is logic link data from front end to back end of a function where the query information is located, and the link data comprises code development data and version development data; extracting the code development data and the version development data to obtain N responsible persons related to front-end joint debugging and back-end joint debugging, wherein N is a positive integer; and distributing the problem description and the link data to the N responsible persons.

Fig. 1 schematically illustrates an application scenario diagram of a front-end and back-end joint debugging method according to an embodiment of the present disclosure.

As shown in fig. 1, an application scenario 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user may interact with the server 105 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. Various communication client applications, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only) may be installed on the terminal devices 101, 102, 103.

The terminal devices 101, 102, 103 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (by way of example only) providing support for websites browsed by users using the terminal devices 101, 102, 103. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that the front-end and back-end joint debugging method provided in the embodiments of the present disclosure may be generally performed by the server 105. Accordingly, the front-end and back-end joint debugging device provided in the embodiments of the present disclosure may be generally disposed in the server 105. The front-end and back-end joint debugging method provided by the embodiments of the present disclosure may also be performed by a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 1, 103 and/or the server 105. Accordingly, the front-end and back-end joint debugging device provided by the embodiments of the present disclosure may also be provided in a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105.

It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

The front-rear joint debugging method of the disclosed embodiment will be described in detail below with reference to fig. 2 to 7 based on the scenario described in fig. 1.

Fig. 2 schematically illustrates a flow chart of a front-end and back-end joint debugging method according to an embodiment of the present disclosure.

As shown in fig. 2, the front-end and back-end joint debugging method of this embodiment includes operations S210 to S230, which can be performed by the server 105.

In operation S210, an error message uploaded from the user terminal is received, where the error message includes query information and a problem description.

Specifically, in a typical scenario, a developer performs a software test on a software program in an application that is not online, where the software program is a software program related to front-end and back-end, and in general, the test of the software program related to front-end and back-end can be understood as follows: and testing corresponding code data from a front-end User Interface (UI) page to a back-end for realizing a function in an application, wherein in the testing process, one function is jointly realized and developed by a plurality of developers of different types, so that different link data from the front end to the back end can be formed according to different working contents, the link data comprises a plurality of nodes, and at least one associated responsible person corresponds to each link node. The error message is then targeted by the tester, and the query information may be any information that can locate the link data. The information can be a node description in the link data, can locate the whole link, and can also be other information capable of representing the whole link; accordingly, the problem description describes the problem encountered by the tester when testing the function.

It should be noted that, the problem found by the tester is most intuitive in UI display, so in order to ensure timeliness of error uploading, it is most convenient to query corresponding logic through UI control IDs, for example, the query information UI control IDs are usually a unique identifier formed by front end page codes and the order in which the page controls are located.

In operation S220, link data in the database is acquired based on the query information, the link data being front-end to back-end logical link data of a function in which the query information is located, the link data including code development data and version development data.

Specifically, the database is established in advance, and the database mainly stores the data link of a certain function in the software development process, and the corresponding developer and key information of each node. Generally speaking, data is taken from a database according to a code table, and is packaged into an interface, and the front end acquires corresponding data by calling the interface and displays the corresponding data at a corresponding position, so that the information is required to be acquired and corresponds to each other on a link for checking problems. The link data includes necessary code development data and necessary version development data, wherein the code development data (also referred to as code query information) includes: front-end developer name (or ID), front-end UI control ID, data source (such as field Key) filled in control, interface number of data source, back-end development of the interface personnel name (or ID), corresponding code table value of database searched by the interface; version development data (also referred to as version development information) includes: the term is the name (or ID) of the person responsible for the term and the current UI date of change. Further, the code development data and the version development data are connected together to form a key information database.

For example, the link data is shown in table one below:

control ID

Development 1

Field key

Interface number

Development 2

Code table value

…

10000888

Zhang San

title

IO299

Li Si

E0002

…

List one

As shown in the above table one, in the case that the query information in the received error execution is "1000088", the database is queried through the query information to obtain the above table one, and in this function, development 1 is "Zhang san", in other words, "Zhang san" as a node, and the Key information on the node includes a field Key of "Title" and an interface number of "IO299"; accordingly, the key information corresponding to the node "Li four" includes a code table value "E0002".

In operation S230, the code development data and the version development data are extracted to obtain N responsible persons related to the front-end and back-end joint debugging, where N is a positive integer.

Specifically, only necessary data such as the first type of the above-described code development data and version development data are retained, and N responsible persons related to N nodes are obtained from the code development data and version development data.

In operation S240, the problem description and the link data are distributed to the N responsible persons.

Specifically, after the query result set in the database is automatically queried in the form of Shell script, the query result set is split, and only a tester is required to describe the problem phenomenon, other series of information is queried through the test input control ID, so that the corresponding problem list can be summarized, and the content of a front-end developer is as follows: the XXX developer is friendly, has a problem related to XXX control, the phenomenon is XXX, the data to be searched is derived from XXX, the back end relates to the developer to be XXX, please check as soon as possible-! Content for backend developers is as follows: the XXX developer is friendly, the phenomenon is XXX, the related interface is XXX, the related field is XXX, the related database code table value is XXX, the front end relates to the developer as XXX, please check-! The method can divide the problems to developers of different nodes on the data link simultaneously, and synchronously check and improve the efficiency.

After the problems are distributed to developers of different nodes, the problems are examined and examined through links which are respectively responsible, the examination results are fed back, and a server receives the examination results and executes certain processing logic to ensure joint debugging efficiency. The method is specifically as follows:

fig. 3 schematically illustrates a flow chart of another front-end and back-end joint debugging method according to an embodiment of the present disclosure.

As shown in fig. 3, another front-end and back-end joint debugging method of the embodiment includes operations S310 to S320, where operations S310 to S320 are performed after operation S240.

In operation S310, a question feedback from a responsible person is received.

In operation S320, a joint debugging task is maintained based on the received problem feedback, the joint debugging task being generated in response to the error message.

Specifically, the problem feedback of each responsible person is continuously received, the problem feedback comprises several types of standardized results, and by identifying the standardized results, corresponding processing logic can be executed to continuously maintain the joint debugging task, wherein the joint debugging task refers to: the time effect of the problem fed back by each responsible person is different to a certain extent, so that unified communication task maintenance logic is set for different N responsible persons under the same function, and maintenance is not carried out on one responsible person only.

Hereinafter, the joint debugging maintenance logic of the present disclosure will be disclosed in detail as follows:

fig. 4 schematically illustrates a flow chart of a maintenance task method according to an embodiment of the disclosure.

As shown in fig. 4, a maintenance task method of this embodiment includes operations S410 to S450, and operations S410 to S450 may at least partially perform operation S320 described above.

According to an embodiment of the present disclosure, the code development data includes a code table value.

In operation S410, the received question feedback is classified to obtain a question feedback category including that the relevant code of the current responsible person has a question and the relevant code of the current responsible person does not have a question.

In operation S420, in case that there is a problem with the code of the responsible person, it is determined whether the problem can be solved within a preset period.

In operation S430, in case the problem can be solved within a preset period, a change code in the problem feedback is extracted.

In operation S440, a data table in the database is acquired based on the code table value.

In operation S450, the data table is modified based on the modification code.

Fig. 5 schematically illustrates a flow chart of another maintenance task method according to an embodiment of the disclosure.

As shown in fig. 5, another maintenance task method of this embodiment includes operations S510 to S520, and the operations S510 to S520 are performed after the operation S420.

In operation S510, in case that the problem can be solved within a preset period, the error message and the link data are put into a summary task.

In operation S520, the error message and the link data are sent up at regular time by the summary task.

The general responsible person is, for example, an item responsible person/leader, through which the data table in the database can be re-established.

Specifically, the error reporting condition of a plurality of functions can be maintained in one summarizing task, so that the reasonable utilization of resources is ensured.

Fig. 6 schematically illustrates a flow chart of another maintenance task method according to an embodiment of the disclosure.

As shown in fig. 6, another maintenance task method of this embodiment includes operations S610 to S620, and the operations S610 to S620 are performed after the operation S410.

In operation S610, in the case that the code related to the responsible person has no problem, the error message and the link data are put into a summary task.

In operation S620, the error message and the link data are sent up in timing by the summary task.

Fig. 7 schematically illustrates a flow chart of a front-end and back-end joint debugging system according to an embodiment of the present disclosure.

As shown in fig. 7, the front-end and back-end joint debugging system of this embodiment includes a key information database and a problem management system,

wherein,

firstly, in a key information database, acquiring the functional version development information and key information of each data node by a system design/project leader; based on the front-end control ID as a unique identifier, a table is built by combining the key information and is stored in a database.

Secondly, in the problem management system, a tester finds that the UI shows abnormality (of course, the problem description can be other), the tester inputs the control ID, the server receives the control ID, and queries the corresponding key information in the database, wherein the key information exists in the form of a table; generating problem order content through the key data and distributing the problem order content to each developer; each developer checks the relevant codes to determine whether problems exist; under the condition that no problem exists, marking that the link is finished, waiting for other developers to check, summarizing problem solving conditions through summarizing tasks, sending related conditions to a database, and presenting the related conditions to a project responsible person; in the case of a problem, judging whether the problem can be solved on the same day; under the condition that the problem can be solved on the same day, the problem can be solved by changing the code, and meanwhile, the maintenance data table is updated in the key information database; if the problem can not be solved on the same day, other matching conditions are needed, the problem solving conditions are summarized through the summarizing task, and related conditions are sent to the database and presented to the project responsible person.

Based on the front-rear end joint debugging method, the present disclosure also provides a front-rear end joint debugging device. The device will be described in detail below in connection with fig. 8.

Fig. 8 schematically illustrates a block diagram of a front-end and back-end joint debugging device according to an embodiment of the present disclosure.

As shown in fig. 8, the front-end and back-end joint debugging device 800 of this embodiment includes a first receiving module 810, a querying module 820, a data extracting module 830, and a distributing module 840.

The first receiving module 810 is configured to receive an error message uploaded from a user terminal, where the error message includes query information and a problem description. In an embodiment, the first receiving module 810 may be configured to perform the operation S210 described above, which is not described herein.

The query module 820 is configured to obtain link data in a database based on the query information, where the link data is front-end to back-end logic link data of a function where the query information is located, and the link data includes code development data and version development data. In an embodiment, the query module 820 may be used to perform the operation S220 described above, which is not described herein.

The data extraction module 830 is configured to extract the code development data and the version development data to obtain N responsible persons related to the front-end joint debugging and the back-end joint debugging, where N is a positive integer. In an embodiment, the data extraction module 830 may be configured to perform the operation S230 described above, which is not described herein.

The distribution module 840 is configured to distribute the problem description and the link data to the N responsible persons. In an embodiment, the distributing module 840 may be configured to perform the operation S240 described above, which is not described herein.

Any of the first receiving module 810, the querying module 820, the data extracting module 830, and the distributing module 840 may be combined in one module to be implemented, or any of the modules may be split into a plurality of modules according to an embodiment of the present disclosure. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module. According to embodiments of the present disclosure, at least one of the first receiving module 810, the querying module 820, the data extracting module 830, and the distributing module 840 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable way of integrating or packaging the circuitry, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, at least one of the first receiving module 810, the querying module 820, the data extracting module 830, and the distributing module 840 may be at least partially implemented as computer program modules, which when executed, may perform the respective functions.

As shown in fig. 9, an electronic device 900 according to an embodiment of the present disclosure includes a processor 901 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 902 or a program loaded from a storage portion 908 into a Random Access Memory (RAM) 903. The processor 901 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. Processor 901 may also include on-board memory for caching purposes. Processor 901 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the present disclosure.

In the RAM 903, various programs and data necessary for the operation of the electronic device 900 are stored. The processor 901, the ROM 902, and the RAM 903 are connected to each other by a bus 904. The processor 901 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 902 and/or the RAM 903. Note that the program may be stored in one or more memories other than the ROM 902 and the RAM 903. The processor 901 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in the one or more memories.

According to an embodiment of the disclosure, the electronic device 900 may also include an input/output (I/O) interface 905, the input/output (I/O) interface 905 also being connected to the bus 904. The electronic device 900 may also include one or more of the following components connected to the I/O interface 905: an input section 906 including a keyboard, a mouse, and the like; an output portion 907 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage portion 908 including a hard disk or the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as needed. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on the drive 910 so that a computer program read out therefrom is installed into the storage section 908 as needed.

The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, the computer-readable storage medium may include ROM 902 and/or RAM 903 and/or one or more memories other than ROM 902 and RAM 903 described above.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowcharts. The program code, when executed in a computer system, causes the computer system to implement the item recommendation method provided by embodiments of the present disclosure.

The above-described functions defined in the system/apparatus of the embodiments of the present disclosure are performed when the computer program is executed by the processor 901. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed, and downloaded and installed in the form of a signal on a network medium, via communication portion 909, and/or installed from removable medium 911. The computer program may include program code that may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 909 and/or installed from the removable medium 911. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 901. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

According to embodiments of the present disclosure, program code for performing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be provided in a variety of combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.

The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.

Claims

1. A front-to-back joint debugging method comprising:

receiving error messages uploaded from a user terminal, wherein the error messages comprise query information and problem description;

Acquiring link data in a database based on the query information, wherein the link data is logic link data from front end to back end of a function where the query information is located, and the link data comprises code development data and version development data;

extracting the code development data and the version development data to obtain N responsible persons related to front-end joint debugging and back-end joint debugging, wherein N is a positive integer; and

and distributing the problem description and the link data to the N responsible persons.

2. The method of claim 1, wherein after said distributing said problem description and said link data to said N responsible persons, further comprising:

receiving problem feedback from responsible persons; and

based on the received problem feedback, a joint debugging task is maintained, the joint debugging task being generated in response to the error message.

3. The method of claim 2, wherein the code development data comprises code table values,

based on the received problem feedback, maintaining joint debugging tasks includes:

classifying the received problem feedback to obtain a problem feedback category, wherein the problem feedback category comprises that the related code of the current responsible person has a problem and the related code of the current responsible person does not have a problem;

Judging whether the problem can be solved within a preset period or not under the condition that the related code of the responsible person has the problem;

extracting a change code in the problem feedback under the condition that the problem can be solved within a preset period;

acquiring a data table in the database based on the code table value; and

altering the data table based on the altering code.

4. A method according to claim 3, wherein after said determining if the problem can be resolved within a preset time period, further comprising:

under the condition that the problem can be solved within a preset period, the error message and the link data are put into a summarizing task; and

and the summarizing task sends the error message and the link data at regular time.

5. The method of claim 4, wherein after classifying the received problem feedback to obtain a problem feedback category, further comprising:

under the condition that the relevant codes of the responsible person have no problem, the error message and the link data are put into a summarizing task; and

6. The method of claim 5, wherein the N responsible persons include a total responsible person,

the step of sending the error message and the link data by the summarizing task at regular time comprises the following steps:

and uploading the error message and the link data to the total responsible person.

7. The method according to any one of claims 4 to 6, wherein M error messages and link data corresponding to the M error messages are maintained in the summary task, and M is a positive integer.

8. The method of any of claims 1-6, wherein the query information includes a control number of a front end.

9. A front-to-back joint debugging device comprising:

the first receiving module is used for receiving error messages uploaded by the user terminal, wherein the error messages comprise query information and problem description;

the query module is used for acquiring link data in a database based on the query information, wherein the link data is logic link data from front end to back end of a function where the query information is located, and the link data comprises code development data and version development data;

the data extraction module is used for extracting the code development data and the version development data to obtain N responsible persons related to front and back end joint debugging, wherein N is a positive integer; and

And the distribution module is used for distributing the problem description and the link data to the N responsible persons.

10. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-8.

11. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method according to any of claims 1-8.

12. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 8.