CN111698123A - Method and device for positioning exception of incoming system, computer equipment and storage medium - Google Patents
Method and device for positioning exception of incoming system, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111698123A CN111698123A CN202010584922.7A CN202010584922A CN111698123A CN 111698123 A CN111698123 A CN 111698123A CN 202010584922 A CN202010584922 A CN 202010584922A CN 111698123 A CN111698123 A CN 111698123A
- Authority
- CN
- China
- Prior art keywords
- interface
- information
- request
- link
- calling
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000003860 storage Methods 0.000 title claims abstract description 20
- 238000012360 testing method Methods 0.000 claims abstract description 164
- 238000004519 manufacturing process Methods 0.000 claims abstract description 123
- 238000011161 development Methods 0.000 claims abstract description 41
- 238000004590 computer program Methods 0.000 claims description 16
- 239000000945 filler Substances 0.000 claims description 9
- 230000005856 abnormality Effects 0.000 claims description 8
- 238000012544 monitoring process Methods 0.000 claims description 6
- 230000002159 abnormal effect Effects 0.000 claims description 2
- 230000006872 improvement Effects 0.000 abstract description 4
- 230000009467 reduction Effects 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 230000008439 repair process Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 238000004458 analytical method Methods 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000009826 distribution Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method and a device for positioning exception of a system for entering a part, computer equipment and a storage medium, which relate to test management, wherein if the link information of the system for entering the part is a system test link, a corresponding calling interface is requested according to a test request parameter; acquiring a target system interface which does not send a request result according to the test request parameters, generating corresponding first-kind interface fault prompt information according to development information of the target system interface and a first system error prompt template, and sending the first-kind interface fault prompt information to an H5 page; if the system link information of the incoming part is a system production link, requesting a corresponding calling interface according to the production request parameter; and acquiring the current target system interface which does not send the request result according to the production request parameters, generating corresponding second-type interface fault prompt information according to the second system error prompt template, and sending the second-type interface fault prompt information to an H5 page. The method realizes the reduction of time consumption and the improvement of efficiency of positioning the fault interface of the associated side server, and has high accuracy of acquiring the positioning information of the fault interface.
Description
Technical Field
The invention relates to the technical field of test management, in particular to a method and a device for positioning an exception of a workpiece feeding system, computer equipment and a storage medium.
Background
The incoming system is a system at the top of the incoming flow, plays a role of starting and stopping, and can conveniently extend an interface of an associated system called by an H5 page (H5 is a language description mode for constructing Web content) through the incoming system. That is, generally, the H5 page initiates the incoming flow to call the interface of the incoming system, so that the interface of the incoming system calls the interface of the corresponding associated server. Because the number of the associated parties of the incoming system is large, the incoming system is affected by the abnormality of all the servers of the associated parties.
At present, when a system composed of a pickup system, an associated server and an H5 page is joint-tuned and tested, when there is an abnormality in an interface of the associated server, a tester on the H5 page generally contacts a pickup system developer, and then the pickup system developer contacts a manager on the associated server. The method for positioning the fault interface of the associated server not only has long time consumption and low efficiency, but also has low accuracy of acquiring the positioning information of the fault interface.
Disclosure of Invention
The embodiment of the invention provides a method, a device, computer equipment and a storage medium for positioning an exception of a piece feeding system, and aims to solve the problems that in the prior art, when a system consisting of the piece feeding system, an associated party server and an H5 page is subjected to joint debugging and testing, when an interface of the associated party server is abnormal, a tester of an H5 page generally contacts a piece feeding system developer, and then the piece feeding system developer contacts a manager of the associated party server, so that the positioning of a fault interface of the associated party server is not only long in time consumption and low in efficiency, but also the accuracy of the positioning information acquisition of the fault interface is low.
In a first aspect, an embodiment of the present invention provides an anomaly positioning method for a workpiece feeding system, including:
acquiring current link information of a piece feeding system;
judging whether the part feeding system link information is a system testing link or a system production link;
if the system link information of the incoming part is a system test link, calling an interface corresponding to a test request parameter request sent by a received H5 page;
acquiring a target system interface which does not send a request result according to the test request parameters, generating corresponding first-kind interface fault prompt information according to development information of the target system interface and a pre-stored first system error prompt template, and sending the first-kind interface fault prompt information to an H5 page;
if the part feeding system link information is a system production link, calling an interface corresponding to a production request parameter request sent by a received H5 page; and
and acquiring the current target system interface which does not send the request result according to the production request parameters, generating corresponding second-type interface fault prompt information according to a pre-stored second system error prompt template, and sending the second-type interface fault prompt information to an H5 page.
In a second aspect, an embodiment of the present invention provides an anomaly positioning device for a workpiece feeding system, including:
the system comprises a pickup information acquisition unit, a pickup information acquisition unit and a pickup information acquisition unit, wherein the pickup information acquisition unit is used for acquiring the current pickup system link information;
the link judging unit is used for judging whether the link information of the workpiece feeding system is a system testing link or a system production link;
the first interface calling unit is used for calling an interface corresponding to a test request parameter request sent by a received H5 page if the piece feeding system link information is a system test link;
the first fault prompting unit is used for acquiring a target system interface which does not send a request result according to the test request parameter, generating corresponding first-kind interface fault prompting information according to development information of the target system interface and a pre-stored first system error prompting template, and sending the first-kind interface fault prompting information to an H5 page;
the second interface calling unit is used for calling an interface corresponding to a production request parameter request sent by the received H5 page if the piece feeding system link information is a system production link; and
and the second fault prompting unit is used for acquiring the current target system interface which does not send the request result according to the production request parameters, generating corresponding second-type interface fault prompting information according to a prestored second system error prompting template and sending the second-type interface fault prompting information to an H5 page.
In a third aspect, an embodiment of the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor, when executing the computer program, implements the method for locating an exception in a pickup system according to the first aspect.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and the computer program, when executed by a processor, causes the processor to execute the incoming system exception locating method according to the first aspect.
The embodiment of the invention provides a method and a device for positioning exception of a piece feeding system, computer equipment and a storage medium, wherein the method comprises the steps of acquiring link information of the current piece feeding system; judging whether the part feeding system link information is a system testing link or a system production link; if the system link information of the incoming part is a system test link, calling an interface corresponding to a test request parameter request sent by a received H5 page; acquiring a target system interface which does not send a request result according to the test request parameters, generating corresponding first-kind interface fault prompt information according to development information of the target system interface and a pre-stored first system error prompt template, and sending the first-kind interface fault prompt information to an H5 page; if the part feeding system link information is a system production link, calling an interface corresponding to a production request parameter request sent by a received H5 page; and acquiring the current target system interface which does not send the request result according to the production request parameters, generating corresponding second-type interface fault prompt information according to a pre-stored second system error prompt template, and sending the second-type interface fault prompt information to an H5 page. The method realizes the reduction of time consumption and the improvement of efficiency of positioning the fault interface of the associated side server, and has high accuracy of acquiring the positioning information of the fault interface.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic view of an application scenario of the method for locating an exception in a system for entering a package according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart illustrating a method for locating an exception in a system for entering parts according to an embodiment of the present invention;
FIG. 3 is a sub-flowchart of a method for locating an exception in a system for entering a package according to an embodiment of the present invention;
FIG. 4 is a schematic view of another sub-flow chart of the method for locating an exception in a system for entering a package according to an embodiment of the present invention;
FIG. 5 is a schematic block diagram of an anomaly locating device of the incoming system according to the embodiment of the present invention;
FIG. 6 is a schematic block diagram of a sub-unit of an anomaly locating device of a feeding system according to an embodiment of the present invention;
FIG. 7 is a schematic block diagram of another subunit of an anomaly locating apparatus of a feeding system according to an embodiment of the present invention;
FIG. 8 is a schematic block diagram of a computer device provided by an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It will 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 invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention 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 and includes any and all possible combinations of one or more of the associated listed items.
Referring to fig. 1 and fig. 2, fig. 1 is a schematic view of an application scenario of a method for locating an exception in a system for entering a package according to an embodiment of the present invention; fig. 2 is a schematic flow chart of a method for locating an exception in a pickup system according to an embodiment of the present invention, where the method is applied to a pickup system server and is executed by application software installed in the pickup system server.
As shown in fig. 2, the method includes steps S110 to S160.
And S110, acquiring the current link information of the system for feeding the parts.
In this embodiment, in order to more clearly understand the technical solution, a detailed description is given below of a terminal related to a specific implementation scenario. The invention describes the technical scheme in the aspect of a workpiece feeding system.
The first is an association system, the association system comprises a plurality of associator servers, each associator server provides an interface for the incoming system to call, and the incoming system can forward request parameters sent by a front-end H5 page to the association system. For example, in a banking application scenario, the associated server is a bank product management system, an identity authentication system, a wind control label system, a product order system, or the like.
The second is a system for entering a package (which can be understood as a system server for entering a package, and is abbreviated as a server), and the system for entering a package is a system located at the forefront of the process flow, and plays a role in starting and stopping. It is located between the association system and the H5 page and serves as an intermediate bridge for the H5 call to the association system. Through the system of the incoming files, the interface of the related system called by the H5 page can be conveniently expanded without any modification on the code of the H5 page.
And thirdly, a host APP (namely, a native application) installed on the user terminal, wherein the host APP is embedded with an SDK (namely, a software development kit), and codes between the host APP and the H5 page can be mutually called so as to mutually borrow corresponding functions.
Fourthly, H5 page (H5 page is that HTML5 constructs Web content, and HTML5 is that hypertext 5.0 standard) on the user terminal, H5 page is a way that request can be directly sent to the incoming system, so as to call the interface of the associated system through the incoming system; the H5 page is another way, that is, the H5 page needs to call some functions of the host APP before initiating a request to the system-in-progress, and then can initiate a request to the system-in-progress.
When the complete system consisting of the association system, the incoming system and the H5 page (including the host APP if necessary) is used for joint debugging and testing, the fault in the association system can be quickly located through the incoming system.
The complete system generally goes through two stages, namely a system test stage and a system production stage. In a system testing link, the testing environment is generally in a testing environment, the testing environment branch is generally a develop branch, and the testing environment branch is deployed on a private server or a local area network server of a company and is mainly used for testing whether bugs exist or not, generally, the bugs cannot be seen by users and other people, and the testing environment is similar to a production environment as much as possible. In a system production link, the system is generally in a production environment, the production environment refers to a production environment which formally provides external services, an error report is generally closed, an error log is generally opened, and the production environment is the most important environment, and a deployment branch of the production environment is generally a master branch. Therefore, in order to more accurately judge the link where the part feeding system is located at the moment, the current part feeding system link information needs to be acquired. The system comprises a system test link, a system production link and a system loading system link, wherein the system test link and the system loading system link have only two values.
And S120, judging whether the part feeding system link information is a system testing link or a system production link.
In this embodiment, in order to realize that the complete system is in a testing link or a production link, once a fault occurs, the specific prompt contents displayed on the H5 page are different, and at this time, it is necessary to first determine that the piece feeding system link information is a system testing link or a system production link.
And S130, if the piece feeding system link information is a system testing link, requesting a corresponding calling interface according to the received testing request parameter sent by the H5 page.
In this embodiment, in a testing link, a user who faces the testing system is a tester, and in order to visually prompt a target system interface that does not send a request result according to a test request parameter on an H5 page, at this time, a piece feeding system needs to first call an interface corresponding to the test request parameter request sent by the H5 page to determine whether there is a target system interface that does not send a request result according to the test request parameter. The target system interfaces which do not send the request result according to the test request parameters are more likely to be interfaces with faults or exceptions, and the faults need to be checked in time.
In one embodiment, as shown in fig. 3, step S130 includes:
s131, obtaining corresponding calling interfaces according to the test request parameters to form a test link calling interface list;
s132, obtaining test request sub-parameters in the test request parameters, wherein the test request sub-parameters correspond to the calling interfaces in the test link calling interface list respectively;
and S133, sending the test request sub-parameters respectively corresponding to the calling interfaces in the test link calling interface list to corresponding target system interfaces.
In this embodiment, when the system component entering link information corresponding to the component entering system is a system testing link, which indicates that the complete system is in a testing link, a tester generally sends various testing request parameters continuously on page H5, and the testing request parameters are forwarded to the associated system through the component entering system, so as to invoke an interface of the associated system, and determine whether the component entering system can invoke the interface of the associated system, and then return a corresponding correct result (also called system finding BUG).
If the test request parameter is directly sent to the incoming system by the H5 page, the test request parameter is directly sent to the incoming system without calling the code of the host APP.
If the H5 page is the code calling the host APP first and then the test request parameter is sent to the system for incoming calls, the specific steps at this time are as follows:
the H5 page sends a test request parameter to the host APP;
the host APP intercepts a test request parameter request sent by an H5 page to generate a return parameter;
calling a callback function in an H5 page by a host APP so as to send a return parameter to an H5 page;
the H5 page sends the return parameters corresponding to the test request parameters to a mail feeding system;
that is, after the test request parameter sent by H5 needs to be intercepted by the host APP to generate a return parameter, the return parameter converted from the test request parameter is sent to the incoming system, so as to implement the call of the interface in the association system.
In the testing link, after the test request parameters sent by the H5 page are analyzed by the incoming system, it is possible to know which interfaces of the associated system need to be called, that is, to obtain the test link calling interface list. After the analysis of the test request parameters is completed, it is generally known which sub-parameters are used to call which interface of the associated system, that is, the test request sub-parameters corresponding to each call interface in the test request parameters are obtained.
The test request parameters generally clearly indicate which interface is called to obtain which returned result, and at this time, the interface keywords in the request parameters are retrieved to obtain which interfaces need to be called and also obtain the test request sub-parameters corresponding to each interface.
After the test request sub-parameters respectively corresponding to each calling interface are obtained, the test request sub-parameters respectively corresponding to each calling interface can be sent to the calling interface (which can also be understood as a target system interface) corresponding to the associated system, so that the request parameters can be accurately distributed.
S140, acquiring a target system interface which does not send a request result according to the test request parameter, generating corresponding first-kind interface fault prompt information according to development information of the target system interface and a pre-stored first system error prompt template, and sending the first-kind interface fault prompt information to an H5 page.
In this embodiment, if it is detected in the incoming system that the target system interface does not send the corresponding request result according to the test request sub-parameter, indicating that the target system interface does not feed back the corresponding request result to the H5 page according to the corresponding test request sub-parameter, the incoming system can accurately know which target system interfaces fail.
In one embodiment, step S140 includes:
judging whether a target system interface sends a corresponding request result according to the test request subparameter or not;
if a target system interface does not send a corresponding request result according to the test request subparameter, acquiring development information of the corresponding target system interface;
and generating corresponding first-kind interface fault prompt information according to the development information and a pre-stored first system error prompt template, and sending the first-kind interface fault prompt information to an H5 page.
In this embodiment, the component feeding system group is a first system error prompt template which stores development information of interface pairs of each associated server in the associated system (that is, information such as names, contact mailboxes, telephone numbers and the like of developers who know the interfaces of each associated server), and at this time, the component feeding system also stores a first system error prompt template which is not filled with any information item blank template, and at this time, the development information is correspondingly filled into the first system error prompt template, so that the first type of interface fault prompt information can be generated. And then, sending the first-kind interface fault prompt information to an H5 page to realize visual prompt of the tester. At this time, the tester directly obtains which interface of the associated server has a fault, and can directly contact the corresponding developer according to the first-kind interface fault prompt information to solve the problem of the interface fault.
In an embodiment, the generating, according to the development information and a first system error prompt template stored in advance, corresponding first-class interface fault prompt information, and sending the first-class interface fault prompt information to an H5 page includes:
acquiring a developer name filling item, a contact mailbox filling item and a telephone number filling item which are included in the first system error prompt template; wherein the initial values of the developer name filler, the contact mailbox filler and the telephone number filler are all null values;
filling a developer name in the development information into a developer name filling item, filling a contact mailbox into a contact mailbox filling item, filling a telephone number into a telephone number filling item, generating corresponding first-kind interface fault prompting information, and sending the first-kind interface fault prompting information to an H5 page.
In this embodiment, for example, there are 3 entries to be filled in the first system error prompt template, which are a developer name entry, a contact mailbox entry, and a phone number entry, respectively, and the initial values of the 3 entries to be filled are all null values. After the development information of the target system interface with the fault is obtained, filling information corresponding to the development information can be filled into the item to be filled corresponding to the first system error prompt template.
For example, the developer name in the development information is populated into the developer name fill, the contact mailbox is populated into the contact mailbox fill, and the telephone number is populated into the telephone number fill. And finally, the first-kind interface fault prompt information displayed on the H5 page comprises the following steps: "you call [ bank product management system ] interface report error, please contact product management responsible person-XX, its phone number is-123 XXXXXXXX, contact mailbox is-XX @ xx.com".
S150, if the part feeding system link information is a system production link, calling an interface corresponding to a production request parameter request sent by the received H5 page.
In this embodiment, in a production link, the targeted users are general users, and in order to display a current target system interface which does not send a request result according to a test request parameter on an H5 page instead of directly, and to flexibly prompt that a current system has a fault and is in fault emergency repair, at this time, corresponding second-type interface fault prompt information is generated according to a second system fault prompt template stored in advance, and is sent to an H5 page.
In one embodiment, as shown in fig. 4, step S150 includes:
s151, obtaining corresponding calling interfaces according to the production request parameters to form a production link calling interface list;
s152, obtaining production request sub-parameters in the production request parameters, wherein the production request sub-parameters correspond to all calling interfaces in the production link calling interface list;
and S153, sending the production request sub-parameters respectively corresponding to each calling interface of the production link calling interface list to the corresponding current target system interface.
In this embodiment, in the production link, generally, a user continuously sends out actual production request parameters on a page H5, and the production request parameters are forwarded to the association system through the incoming system to call the interface of the association system, so as to determine whether the incoming system can call the interface of the association system and return a corresponding actually required result.
After the incoming system analyzes the production request parameters sent by the H5 page, it can obtain which interfaces of the associated system need to be called, that is, obtain the list of production link calling interfaces. After the analysis of the production request parameters is completed, it is generally known which sub-parameters are to call which interface of the associated system, that is, the production request sub-parameters corresponding to each call interface in the production request parameters are obtained.
The production request parameters generally clearly indicate which interface is called to obtain which returned result, and at this time, the interface keywords in the production request parameters are retrieved to obtain which interfaces need to be called and also obtain the production request sub-parameters corresponding to each interface.
After the production request sub-parameters respectively corresponding to each calling interface are obtained, the production request sub-parameters respectively corresponding to each calling interface can be sent to the calling interface (which can also be understood as a target system interface) corresponding to the associated system, so that accurate distribution of the production request parameters is realized.
And S160, acquiring the current target system interface which does not send the request result according to the production request parameters, generating corresponding second-type interface fault prompt information according to a pre-stored second system error prompt template, and sending the second-type interface fault prompt information to an H5 page.
In this embodiment, since the production request sub-parameters respectively corresponding to each calling interface in the production link calling interface list are distributed, at this time, it can be determined in the component feeding system whether there is a target system interface that does not send a corresponding request result according to the production request sub-parameters according to the received feedback data from the association system, and it can be known whether there is a failure of an interface of an association server in the association system through this determination.
If it is detected in the incoming system that the target system interface does not send the corresponding request result according to the production request sub-parameter, it indicates that the target system interface does not feed back the corresponding request result to the page H5 according to the corresponding production request sub-parameter, and at this time, the incoming system can accurately know which target system interfaces fail. However, the ordinary user does not need to accurately know how to solve the problem of the interface fault like a tester, and at the moment, only needs to prompt that the fault exists and the emergency repair fault is being notified on the H5 page of the user.
At this time, when the corresponding second-type interface fault prompt information is generated according to the prestored second system error prompt template, the second system error prompt template is directly called to be directly used as the second-type interface fault prompt information without acquiring the development information of the interface. For example, the second system error prompt template is set as "system error reporting, the programmer brother is trying to rescue … …, the error reporting information is directly returned to the receiving terminal of the joint debugging and testing personnel, the programmer brother can directly see the abnormality and find the corresponding developer to process, please patiently wait", the user is prompted by the graceful prompt mode, and the timely interaction with the user is realized.
In an embodiment, step S160 is followed by:
and acquiring development information corresponding to each current target system interface according to the current target system interface which does not send the corresponding request result according to the production request subparameter, and sending the development information corresponding to each current target system interface to the corresponding monitoring terminal.
In this embodiment, in a production link of a complete system, once a user is prompted on a page H5 that a calling interface of an associated system has a fault, operation and maintenance personnel of an incoming system needs to timely obtain which calling interfaces have the fault and notify corresponding interface developers to perform fault first-aid repair, and at this time, development information corresponding to each current target system interface is sent to a monitoring terminal (for example, a smart phone) correspondingly used by the operation and maintenance personnel of the incoming system.
The method realizes the reduction of time consumption and the improvement of efficiency of positioning the fault interface of the associated side server, and has high accuracy of acquiring the positioning information of the fault interface.
The embodiment of the invention also provides a device for positioning the abnormality of the workpiece feeding system, which is used for executing any embodiment of the method for positioning the abnormality of the workpiece feeding system. Specifically, referring to fig. 5, fig. 5 is a schematic block diagram of an anomaly positioning device of a workpiece entering system according to an embodiment of the present invention. The incoming system anomaly locating device 100 can be configured in an incoming system server.
As shown in fig. 5, the device 100 for locating an abnormality of an incoming article system includes: the system comprises a pickup information acquisition unit 110, a link judgment unit 120, a first interface calling unit 130, a first failure prompting unit 140, a second interface calling unit 150 and a second failure prompting unit 160.
A file information acquiring unit 110, configured to acquire current file system link information.
In this embodiment, the complete system generally undergoes two stages, namely, a system testing stage and a system production stage. In a system testing link, the testing environment is generally in a testing environment, the testing environment branch is generally a develop branch, and the testing environment branch is deployed on a private server or a local area network server of a company and is mainly used for testing whether bugs exist or not, generally, the bugs cannot be seen by users and other people, and the testing environment is similar to a production environment as much as possible. In a system production link, the system is generally in a production environment, the production environment refers to a production environment which formally provides external services, an error report is generally closed, an error log is generally opened, and the production environment is the most important environment, and a deployment branch of the production environment is generally a master branch. Therefore, in order to more accurately judge the link where the part feeding system is located at the moment, the current part feeding system link information needs to be acquired. The system comprises a system test link, a system production link and a system loading system link, wherein the system test link and the system loading system link have only two values.
A link determining unit 120, configured to determine that the piece feeding system link information is a system testing link or a system production link.
In this embodiment, in order to realize that the complete system is in a testing link or a production link, once a fault occurs, the specific prompt contents displayed on the H5 page are different, and at this time, it is necessary to first determine that the piece feeding system link information is a system testing link or a system production link.
The first interface invoking unit 130 is configured to, if the piece-entering system link information is a system test link, request a corresponding invoking interface according to the received test request parameter sent by the H5 page.
In this embodiment, in a testing link, a user who faces the testing system is a tester, and in order to visually prompt a target system interface that does not send a request result according to a test request parameter on an H5 page, at this time, a piece feeding system needs to first call an interface corresponding to the test request parameter request sent by the H5 page to determine whether there is a target system interface that does not send a request result according to the test request parameter. The target system interfaces which do not send the request result according to the test request parameters are more likely to be interfaces with faults or exceptions, and the faults need to be checked in time.
In one embodiment, as shown in fig. 6, the first interface calling unit 130 includes:
a first interface list obtaining unit 131, configured to obtain a corresponding calling interface according to the test request parameter to form a test link calling interface list;
a first test request subparameter obtaining unit 132, configured to obtain test request subparameters in the test request parameters, where the test request subparameters correspond to the call interfaces in the test link call interface list, respectively;
a first request parameter sending unit 133, configured to send the test request sub-parameters corresponding to each calling interface in the test link calling interface list to the corresponding target system interface.
In this embodiment, when the system component entering link information corresponding to the component entering system is a system testing link, which indicates that the complete system is in a testing link, a tester generally sends various testing request parameters continuously on page H5, and the testing request parameters are forwarded to the associated system through the component entering system, so as to invoke an interface of the associated system, and determine whether the component entering system can invoke the interface of the associated system, and then return a corresponding correct result (also called system finding BUG).
If the test request parameter is directly sent to the incoming system by the H5 page, the test request parameter is directly sent to the incoming system without calling the code of the host APP.
If the H5 page is the code calling the host APP first and then the test request parameter is sent to the system for incoming calls, the specific steps at this time are as follows:
the H5 page sends a test request parameter to the host APP;
the host APP intercepts a test request parameter request sent by an H5 page to generate a return parameter;
calling a callback function in an H5 page by a host APP so as to send a return parameter to an H5 page;
the H5 page sends the return parameters corresponding to the test request parameters to a mail feeding system;
that is, after the test request parameter sent by H5 needs to be intercepted by the host APP to generate a return parameter, the return parameter converted from the test request parameter is sent to the incoming system, so as to implement the call of the interface in the association system.
In the testing link, after the test request parameters sent by the H5 page are analyzed by the incoming system, it is possible to know which interfaces of the associated system need to be called, that is, to obtain the test link calling interface list. After the analysis of the test request parameters is completed, it is generally known which sub-parameters are used to call which interface of the associated system, that is, the test request sub-parameters corresponding to each call interface in the test request parameters are obtained.
The test request parameters generally clearly indicate which interface is called to obtain which returned result, and at this time, the interface keywords in the request parameters are retrieved to obtain which interfaces need to be called and also obtain the test request sub-parameters corresponding to each interface.
After the test request sub-parameters respectively corresponding to each calling interface are obtained, the test request sub-parameters respectively corresponding to each calling interface can be sent to the calling interface (which can also be understood as a target system interface) corresponding to the associated system, so that the request parameters can be accurately distributed.
The first fault prompting unit 140 is configured to acquire a target system interface that does not send a request result according to the test request parameter, generate corresponding first-class interface fault prompting information according to development information of the target system interface and a first system error prompting template stored in advance, and send the first-class interface fault prompting information to an H5 page.
In this embodiment, if it is detected in the incoming system that the target system interface does not send the corresponding request result according to the test request sub-parameter, indicating that the target system interface does not feed back the corresponding request result to the H5 page according to the corresponding test request sub-parameter, the incoming system can accurately know which target system interfaces fail.
In one embodiment, the first fault notification unit 140 includes:
the first request result screening unit is used for judging whether a target system interface sends a corresponding request result according to the test request subparameter or not;
the first development information acquisition unit is used for acquiring development information of a corresponding target system interface if the target system interface does not send a corresponding request result according to the test request subparameter;
and the first fault prompt information generating unit is used for generating corresponding first type interface fault prompt information according to the development information and a pre-stored first system error prompt template, and sending the first type interface fault prompt information to an H5 page.
In this embodiment, the component feeding system group is a first system error prompt template which stores development information of interface pairs of each associated server in the associated system (that is, information such as names, contact mailboxes, telephone numbers and the like of developers who know the interfaces of each associated server), and at this time, the component feeding system also stores a first system error prompt template which is not filled with any information item blank template, and at this time, the development information is correspondingly filled into the first system error prompt template, so that the first type of interface fault prompt information can be generated. And then, sending the first-kind interface fault prompt information to an H5 page to realize visual prompt of the tester. At this time, the tester directly obtains which interface of the associated server has a fault, and can directly contact the corresponding developer according to the first-kind interface fault prompt information to solve the problem of the interface fault.
In an embodiment, the first failure indication information generating unit includes:
the first template acquisition unit is used for acquiring a developer name filling item, a contact mailbox filling item and a telephone number filling item which are included in the first system error prompt template; wherein the initial values of the developer name filler, the contact mailbox filler and the telephone number filler are all null values;
the first filling unit is used for filling the developer name in the development information into a developer name filling item, filling the contact mailbox into a contact mailbox filling item, filling the telephone number into a telephone number filling item, generating corresponding first-kind interface fault prompting information, and sending the first-kind interface fault prompting information to an H5 page.
In this embodiment, for example, there are 3 entries to be filled in the first system error prompt template, which are a developer name entry, a contact mailbox entry, and a phone number entry, respectively, and the initial values of the 3 entries to be filled are all null values. After the development information of the target system interface with the fault is obtained, filling information corresponding to the development information can be filled into the item to be filled corresponding to the first system error prompt template.
For example, the developer name in the development information is populated into the developer name fill, the contact mailbox is populated into the contact mailbox fill, and the telephone number is populated into the telephone number fill. And finally, the first-kind interface fault prompt information displayed on the H5 page comprises the following steps: "you call [ bank product management system ] interface report error, please contact product management responsible person-XX, its phone number is-123 XXXXXXXX, contact mailbox is-XX @ xx.com".
A second interface calling unit 150, configured to, if the piece-in system link information is a system production link, request a corresponding calling interface according to a received production request parameter sent from the H5 page.
In this embodiment, in a production link, the targeted users are general users, and in order to display a current target system interface which does not send a request result according to a test request parameter on an H5 page instead of directly, and to flexibly prompt that a current system has a fault and is in fault emergency repair, at this time, corresponding second-type interface fault prompt information is generated according to a second system fault prompt template stored in advance, and is sent to an H5 page.
In one embodiment, as shown in fig. 7, the second interface calling unit 150 includes:
a second interface list obtaining unit 151, configured to obtain, according to the production request parameter, a corresponding calling interface to form a production link calling interface list;
a second test request sub-parameter obtaining unit 152, configured to obtain production request sub-parameters in the production request parameters, where the production request sub-parameters correspond to each calling interface in the production link calling interface list;
a second request parameter sending unit 153, configured to send the production request sub-parameters corresponding to each calling interface in the production link calling interface list to the corresponding current target system interface.
In this embodiment, in the production link, generally, a user continuously sends out actual production request parameters on a page H5, and the production request parameters are forwarded to the association system through the incoming system to call the interface of the association system, so as to determine whether the incoming system can call the interface of the association system and return a corresponding actually required result.
After the incoming system analyzes the production request parameters sent by the H5 page, it can obtain which interfaces of the associated system need to be called, that is, obtain the list of production link calling interfaces. After the analysis of the production request parameters is completed, it is generally known which sub-parameters are to call which interface of the associated system, that is, the production request sub-parameters corresponding to each call interface in the production request parameters are obtained.
The production request parameters generally clearly indicate which interface is called to obtain which returned result, and at this time, the interface keywords in the production request parameters are retrieved to obtain which interfaces need to be called and also obtain the production request sub-parameters corresponding to each interface.
After the production request sub-parameters respectively corresponding to each calling interface are obtained, the production request sub-parameters respectively corresponding to each calling interface can be sent to the calling interface (which can also be understood as a target system interface) corresponding to the associated system, so that accurate distribution of the production request parameters is realized.
And the second fault prompting unit 160 is configured to acquire a current target system interface that does not send a request result according to the production request parameter, generate corresponding second-class interface fault prompting information according to a second system error prompting template stored in advance, and send the second-class interface fault prompting information to the H5 page.
In this embodiment, since the production request sub-parameters respectively corresponding to each calling interface in the production link calling interface list are distributed, at this time, it can be determined in the component feeding system whether there is a target system interface that does not send a corresponding request result according to the production request sub-parameters according to the received feedback data from the association system, and it can be known whether there is a failure of an interface of an association server in the association system through this determination.
If it is detected in the incoming system that the target system interface does not send the corresponding request result according to the production request sub-parameter, it indicates that the target system interface does not feed back the corresponding request result to the page H5 according to the corresponding production request sub-parameter, and at this time, the incoming system can accurately know which target system interfaces fail. However, the ordinary user does not need to accurately know how to solve the problem of the interface fault like a tester, and at the moment, only needs to prompt that the fault exists and the emergency repair fault is being notified on the H5 page of the user.
At this time, when the corresponding second-type interface fault prompt information is generated according to the prestored second system error prompt template, the second system error prompt template is directly called to be directly used as the second-type interface fault prompt information without acquiring the development information of the interface. For example, the second system error prompt template is set as "system error reporting, the programmer brother is trying to rescue … …, the error reporting information is directly returned to the receiving terminal of the joint debugging and testing personnel, the programmer brother can directly see the abnormality and find the corresponding developer to process, please patiently wait", the user is prompted by the graceful prompt mode, and the timely interaction with the user is realized.
In one embodiment, the device 100 for locating an anomaly in a workpiece feeding system further comprises:
and the monitoring terminal notification unit is used for acquiring development information corresponding to each current target system interface according to the current target system interface which does not send the corresponding request result according to the production request subparameter, and sending the development information corresponding to each current target system interface to the corresponding monitoring terminal.
In this embodiment, in a production link of a complete system, once a user is prompted on a page H5 that a calling interface of an associated system has a fault, operation and maintenance personnel of an incoming system needs to timely obtain which calling interfaces have the fault and notify corresponding interface developers to perform fault first-aid repair, and at this time, development information corresponding to each current target system interface is sent to a monitoring terminal (for example, a smart phone) correspondingly used by the operation and maintenance personnel of the incoming system.
The device realizes the reduction of time consumption and the improvement of efficiency of the fault interface of the positioning related party server, and the accuracy rate of obtaining the fault interface positioning information is high.
The above-mentioned anomaly locating device of the incoming system can be implemented in the form of a computer program, and the computer program can be run on a computer device as shown in fig. 8.
Referring to fig. 8, fig. 8 is a schematic block diagram of a computer device according to an embodiment of the present invention. The computer device 500 is a server, and the server may be an independent server or a server cluster composed of a plurality of servers.
Referring to fig. 8, the computer device 500 includes a processor 502, memory, and a network interface 505 connected by a system bus 501, where the memory may include a non-volatile storage medium 503 and an internal memory 504.
The non-volatile storage medium 503 may store an operating system 5031 and a computer program 5032. The computer program 5032, when executed, causes the processor 502 to perform a firmware system exception location method.
The processor 502 is used to provide computing and control capabilities that support the operation of the overall computer device 500.
The internal memory 504 provides an environment for the operation of the computer program 5032 in the non-volatile storage medium 503, and when the computer program 5032 is executed by the processor 502, the processor 502 can execute the firmware system exception location method.
The network interface 505 is used for network communication, such as providing transmission of data information. Those skilled in the art will appreciate that the configuration shown in fig. 8 is a block diagram of only a portion of the configuration associated with aspects of the present invention and is not intended to limit the computing device 500 to which aspects of the present invention may be applied, and that a particular computing device 500 may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
The processor 502 is configured to run the computer program 5032 stored in the memory, so as to implement the method for locating an exception in a pickup system disclosed in the embodiment of the present invention.
Those skilled in the art will appreciate that the embodiment of a computer device illustrated in fig. 8 does not constitute a limitation on the specific construction of the computer device, and that in other embodiments a computer device may include more or fewer components than those illustrated, or some components may be combined, or a different arrangement of components. For example, in some embodiments, the computer device may only include a memory and a processor, and in such embodiments, the structures and functions of the memory and the processor are consistent with those of the embodiment shown in fig. 8, and are not described herein again.
It should be understood that, in the embodiment of the present invention, the Processor 502 may be a Central Processing Unit (CPU), and the Processor 502 may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable gate arrays (FPGAs) or other Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. Wherein a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
In another embodiment of the invention, a computer-readable storage medium is provided. The computer readable storage medium may be a non-volatile computer readable storage medium. The computer readable storage medium stores a computer program, wherein the computer program, when executed by the processor, implements the method for locating an exception in a system for incoming calls disclosed in the embodiments of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses, devices and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. 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 invention.
In the embodiments provided by the present invention, it should be understood that the disclosed apparatus, device and method can be implemented in other ways. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only a logical division, and there may be other divisions when the actual implementation is performed, or units having the same function may be grouped into one unit, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may also be an electric, mechanical or other form of connection.
The units described as separate parts may or may not be physically separate, and parts displayed 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 can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a storage medium. Based on such understanding, the technical solution of the present invention essentially or partially contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk.
While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A method for positioning abnormality of a workpiece feeding system is characterized by comprising the following steps:
acquiring current link information of a piece feeding system;
judging whether the part feeding system link information is a system testing link or a system production link;
if the system link information of the incoming part is a system test link, calling an interface corresponding to a test request parameter request sent by a received H5 page;
acquiring a target system interface which does not send a request result according to the test request parameters, generating corresponding first-kind interface fault prompt information according to development information of the target system interface and a pre-stored first system error prompt template, and sending the first-kind interface fault prompt information to an H5 page;
if the part feeding system link information is a system production link, calling an interface corresponding to a production request parameter request sent by a received H5 page; and
and acquiring the current target system interface which does not send the request result according to the production request parameters, generating corresponding second-type interface fault prompt information according to a pre-stored second system error prompt template, and sending the second-type interface fault prompt information to an H5 page.
2. The incoming system exception positioning method according to claim 1, wherein the requesting a corresponding call interface according to the received test request parameter sent from the H5 page includes:
acquiring corresponding calling interfaces according to the test request parameters to form a test link calling interface list;
acquiring test request sub-parameters in the test request parameters, which correspond to the calling interfaces in the test link calling interface list respectively;
and sending the test request sub-parameters respectively corresponding to each calling interface in the test link calling interface list to the corresponding target system interface.
3. The incoming system exception positioning method according to claim 2, wherein the obtaining of the target system interface that does not send the request result according to the test request parameter to generate corresponding first-kind interface fault prompting information according to development information of the target system interface and a first system error prompting template stored in advance and send the first-kind interface fault prompting information to an H5 page includes:
judging whether a target system interface sends a corresponding request result according to the test request subparameter or not;
if a target system interface does not send a corresponding request result according to the test request subparameter, acquiring development information of the corresponding target system interface;
and generating corresponding first-kind interface fault prompt information according to the development information and a pre-stored first system error prompt template, and sending the first-kind interface fault prompt information to an H5 page.
4. The incoming system exception positioning method according to claim 3, wherein the generating of the corresponding first-kind interface failure prompt information according to the development information and a first system error prompt template stored in advance and the sending of the first-kind interface failure prompt information to an H5 page includes:
acquiring a developer name filling item, a contact mailbox filling item and a telephone number filling item which are included in the first system error prompt template; wherein the initial values of the developer name filler, the contact mailbox filler and the telephone number filler are all null values;
filling a developer name in the development information into a developer name filling item, filling a contact mailbox into a contact mailbox filling item, filling a telephone number into a telephone number filling item, generating corresponding first-kind interface fault prompting information, and sending the first-kind interface fault prompting information to an H5 page.
5. The incoming system exception positioning method according to claim 1, wherein the calling interface corresponding to the request for the production request parameter sent according to the received H5 page comprises:
acquiring corresponding calling interfaces according to the production request parameters to form a production link calling interface list;
acquiring production request sub-parameters in the production request parameters, which correspond to the calling interfaces in the production link calling interface list respectively;
and sending the production request sub-parameters respectively corresponding to each calling interface of the production link calling interface list to the corresponding current target system interface.
6. The incoming system exception positioning method according to claim 5, wherein after acquiring a current target system interface that does not send a request result according to a production request parameter, to generate corresponding second-type interface fault prompting information according to a second system error prompting template stored in advance and send the second-type interface fault prompting information to an H5 page, the method further comprises:
and acquiring development information corresponding to each current target system interface according to the current target system interface which does not send the corresponding request result according to the production request subparameter, and sending the development information corresponding to each current target system interface to the corresponding monitoring terminal.
7. An abnormal positioning device for a workpiece feeding system, which is characterized by comprising:
the system comprises a pickup information acquisition unit, a pickup information acquisition unit and a pickup information acquisition unit, wherein the pickup information acquisition unit is used for acquiring the current pickup system link information;
the link judging unit is used for judging whether the link information of the workpiece feeding system is a system testing link or a system production link;
the first interface calling unit is used for calling an interface corresponding to a test request parameter request sent by a received H5 page if the piece feeding system link information is a system test link;
the first fault prompting unit is used for acquiring a target system interface which does not send a request result according to the test request parameter, generating corresponding first-kind interface fault prompting information according to development information of the target system interface and a pre-stored first system error prompting template, and sending the first-kind interface fault prompting information to an H5 page;
the second interface calling unit is used for calling an interface corresponding to a production request parameter request sent by the received H5 page if the piece feeding system link information is a system production link; and
and the second fault prompting unit is used for acquiring the current target system interface which does not send the request result according to the production request parameters, generating corresponding second-type interface fault prompting information according to a prestored second system error prompting template and sending the second-type interface fault prompting information to an H5 page.
8. The incoming system exception positioning device of claim 7, wherein the first interface call unit comprises:
a first interface list obtaining unit, configured to obtain a corresponding calling interface according to the test request parameter to form a test link calling interface list;
a first test request subparameter obtaining unit, configured to obtain test request subparameters, in the test request parameters, corresponding to the call interfaces in the test link call interface list, respectively;
and the first request parameter sending unit is used for sending the test request sub-parameters respectively corresponding to each calling interface in the test link calling interface list to the corresponding target system interface.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method for incoming system exception location according to any one of claims 1 to 6 when executing the computer program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, causes the processor to carry out the incoming item system anomaly locating method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010584922.7A CN111698123A (en) | 2020-06-23 | 2020-06-23 | Method and device for positioning exception of incoming system, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010584922.7A CN111698123A (en) | 2020-06-23 | 2020-06-23 | Method and device for positioning exception of incoming system, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111698123A true CN111698123A (en) | 2020-09-22 |
Family
ID=72483674
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010584922.7A Pending CN111698123A (en) | 2020-06-23 | 2020-06-23 | Method and device for positioning exception of incoming system, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111698123A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114461302A (en) * | 2022-02-09 | 2022-05-10 | 北京理房通支付科技有限公司 | Parameter checking method, checking template generating method and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150074367A1 (en) * | 2013-09-09 | 2015-03-12 | International Business Machines Corporation | Method and apparatus for faulty memory utilization |
| CN107864066A (en) * | 2017-08-24 | 2018-03-30 | 平安普惠企业管理有限公司 | Offline H5 pages monitoring method, device, equipment and readable storage medium storing program for executing |
| CN110198247A (en) * | 2018-02-26 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Interface test method and system |
| CN110515829A (en) * | 2019-07-10 | 2019-11-29 | 平安普惠企业管理有限公司 | Application testing method, device, equipment and computer readable storage medium |
| CN110688285A (en) * | 2019-09-30 | 2020-01-14 | 深圳前海环融联易信息科技服务有限公司 | Method and device for processing abnormal classification of business system, computer equipment and storage medium |
-
2020
- 2020-06-23 CN CN202010584922.7A patent/CN111698123A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150074367A1 (en) * | 2013-09-09 | 2015-03-12 | International Business Machines Corporation | Method and apparatus for faulty memory utilization |
| CN107864066A (en) * | 2017-08-24 | 2018-03-30 | 平安普惠企业管理有限公司 | Offline H5 pages monitoring method, device, equipment and readable storage medium storing program for executing |
| CN110198247A (en) * | 2018-02-26 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Interface test method and system |
| CN110515829A (en) * | 2019-07-10 | 2019-11-29 | 平安普惠企业管理有限公司 | Application testing method, device, equipment and computer readable storage medium |
| CN110688285A (en) * | 2019-09-30 | 2020-01-14 | 深圳前海环融联易信息科技服务有限公司 | Method and device for processing abnormal classification of business system, computer equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 陈锦富;卢炎生;谢晓东;游亮;温贤鑫;: "一个组件安全自动化测试平台的设计与实现", 计算机科学, no. 12 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114461302A (en) * | 2022-02-09 | 2022-05-10 | 北京理房通支付科技有限公司 | Parameter checking method, checking template generating method and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10346282B2 (en) | Multi-data analysis based proactive defect detection and resolution | |
| CN107992409B (en) | Test case generation method and device, computer equipment and storage medium | |
| US10824521B2 (en) | Generating predictive diagnostics via package update manager | |
| US9824002B2 (en) | Tracking of code base and defect diagnostic coupling with automated triage | |
| US8832658B2 (en) | Verification framework for business objects | |
| US20110214021A1 (en) | Systems and methods for initiating software repairs in conjunction with software package updates | |
| CN108134708B (en) | Method and device for monitoring third-party interface | |
| CN109815111A (en) | Gray scale test method, device, computer equipment and storage medium | |
| US8667333B2 (en) | Extensible testing system | |
| US10331439B2 (en) | Source code transfer control method, computer program therefor, and recording medium therefor | |
| CN106547687A (en) | Application testing method, apparatus and system | |
| US20230259436A1 (en) | Systems and methods for monitoring application health in a distributed architecture | |
| CN111259403A (en) | Penetration testing method and device, computer equipment and storage medium | |
| CN111290806A (en) | Calling method and device of application program interface, computer equipment and storage medium | |
| CN111221727B (en) | Test method, test device, electronic equipment and computer readable medium | |
| CN110688285A (en) | Method and device for processing abnormal classification of business system, computer equipment and storage medium | |
| US20200012479A1 (en) | Intelligent checking engine | |
| US7617462B2 (en) | Graphical user interface (GUI) for displaying software component availability as determined by a messaging infrastructure | |
| CN112100078A (en) | Method, device and equipment for generating interface test case | |
| CN111698123A (en) | Method and device for positioning exception of incoming system, computer equipment and storage medium | |
| CN111061637B (en) | Interface testing method, interface testing device and storage medium | |
| JP5006824B2 (en) | Test program management system | |
| US20110153538A1 (en) | Rule-based Processing in Different Layers | |
| US7734763B2 (en) | Application for testing the availability of software components | |
| US20210382764A1 (en) | Comparisons of application programming interface interactions to determine compatibilities |
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 |