CN115629961A - Method and device for determining debugging result, storage medium and electronic device - Google Patents
Method and device for determining debugging result, storage medium and electronic device Download PDFInfo
- Publication number
- CN115629961A CN115629961A CN202211145880.2A CN202211145880A CN115629961A CN 115629961 A CN115629961 A CN 115629961A CN 202211145880 A CN202211145880 A CN 202211145880A CN 115629961 A CN115629961 A CN 115629961A
- Authority
- CN
- China
- Prior art keywords
- debugging
- case
- target
- test
- determining
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a method and a device for determining a debugging result, a storage medium and an electronic device, which relate to the technical field of smart families, wherein the method for determining the debugging result comprises the following steps: acquiring a first test result when the test cases in the test case table are tested; determining a target debugging case with an abnormal test result from the first test result; responding to a debugging instruction of a first object, and debugging the target debugging case by using target login information corresponding to the target debugging case and debugging information corresponding to the target debugging case to obtain a debugging result of the target debugging case.
Description
Technical Field
The application relates to the technical field of smart homes, in particular to a method and a device for determining a debugging result, a storage medium and an electronic device.
Background
At present, generally, after a test operation of an interface case is executed, an error case may occur, and then, for the error case, manual troubleshooting is required to be performed to debug the error interface case. However, the existing framework can only manually find the corresponding use case from the use case management page and then debug the use case after recording the use case with errors, the process is complicated, and the debugging efficiency is very low. Therefore, the related art has a problem that debugging efficiency for an error case is low.
Aiming at the problem that the debugging efficiency of the error case is low in the related technology, an effective solution is not provided yet.
Disclosure of Invention
The embodiment of the application provides a method and a device for determining a debugging result, a storage medium and an electronic device, so as to at least solve the problem that the debugging efficiency of an error case is low in the related art.
According to an embodiment of the present application, there is provided a method for determining a debugging result, including: acquiring a first test result when the test cases in the test case table are tested; determining a target debugging case with an abnormal test result from the first test result; responding to a debugging instruction of a first object, and debugging the target debugging case by using target login information corresponding to the target debugging case and debugging information corresponding to the target debugging case to obtain a debugging result of the target debugging case.
In an exemplary embodiment, determining a target test case with an abnormal test result from the first test result includes: determining a second test result preset for the test case in the test case table; and comparing the second test result with the first test result, and determining the test case inconsistent with the second test result in the first test result as the target test case of the test result.
In an exemplary embodiment, the debugging the target debugging use case by using the target login information corresponding to the target debugging use case and the debugging information corresponding to the target debugging use case includes: determining debugging parameters of the test case from case parameters of the test case in the test case table; determining debugging information of the target debugging case based on the debugging parameters; and under the condition that the target login information corresponding to the target debugging case is not empty, executing login operation of the target debugging case by using the target login information, and debugging the target debugging case by using the debugging information of the target debugging case.
In an exemplary embodiment, before debugging the target debug use case using the target login information corresponding to the target debug use case and the debug information corresponding to the target debug use case, the method further includes: and responding to the selection instruction of the first object, and determining the target login information from pre-provided login information to be selected, wherein the pre-provided login information to be selected represents login information of all test cases containing preset words in the test case table.
In an exemplary embodiment, after determining the target login information from the pre-provided login information to be selected in response to the selection instruction of the first object, the method further includes: determining login priority corresponding to the login information to be selected under the condition that the target debugging case is failed to log in based on the target login information; determining standby login information corresponding to the highest login priority from the multiple pieces of login information to be selected; logging in the target debugging case based on the standby logging information; wherein the login priority is determined by one of: the selection frequency of the information to be selected and the selection time of the information to be selected and logged in.
In one exemplary embodiment, the method further comprises: under the condition that target login information corresponding to the target debugging use case is empty, determining whether the target debugging use case supports a function of debugging in a non-login state; if the target debugging case is determined to support the function of debugging in the non-login state, determining the corresponding general debugging information of the target debugging case in the non-login state, and debugging the target debugging case by using the general debugging information; the universal debugging information is used for debugging a target debugging use case in a non-login state and a target debugging use case in a login state; and if the target debugging case is determined not to support the function of debugging in the non-login state, sending prompt information to the first object, wherein the prompt information is used for prompting that the target debugging case cannot be debugged.
In an exemplary embodiment, after obtaining the debugging result of the target debugging use case, the method further includes: determining debugging parameters of the target debugging case from the debugging result; sending a parameter updating request to a first object, wherein the parameter updating request represents a request for updating the test cases in the test case table by using the debugging parameters; and under the condition that an updating instruction fed back by the first object based on the parameter updating request is received, responding to the updating instruction, and updating the request of the test case in the test case table by using the debugging parameter.
According to another embodiment of the present application, there is also provided a device for determining a debugging result, including: the acquisition module is used for acquiring a first test result when the test cases in the test case table are tested; the determining module is used for determining a target test case with an abnormal test result from the first test result; and the obtaining module is used for responding to a debugging instruction of the first object, and debugging the target debugging case by using the target login information corresponding to the target debugging case and the debugging information corresponding to the target debugging case to obtain a debugging result of the target debugging case.
According to another aspect of the embodiments of the present application, there is further provided a computer-readable storage medium, in which a computer program is stored, where the computer program is configured to execute the method for determining a debugging result when the computer program runs.
According to another aspect of the embodiments of the present application, there is also provided an electronic apparatus, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the method for determining the debugging result through the computer program.
In the embodiment of the application, a first test result when the test cases in the test case table are tested is obtained; determining a target test case with an abnormal test result from the first test result; responding to a debugging instruction of a first object, and debugging the target debugging use by using target login information corresponding to the target debugging use and debugging information corresponding to the target debugging use to obtain a debugging result of the target debugging use; by adopting the technical scheme, the problem of low debugging efficiency of the wrong case is solved, and the debugging efficiency is further improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art to obtain other drawings without inventive exercise.
Fig. 1 is a schematic diagram of a hardware environment of a method for determining a debugging result according to an embodiment of the present application;
FIG. 2 is a flow chart of a method of determining debug results according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a method for determining debugging results according to an embodiment of the present application;
fig. 4 is a flowchart illustrating a method for determining a debugging result according to an embodiment of the present application (i);
fig. 5 is a flowchart illustrating a method for determining a debugging result according to an embodiment of the present application (ii);
fig. 6 is a block diagram of a device for determining a debugging result according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the accompanying drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
According to an aspect of an embodiment of the present application, a method for determining a debugging result is provided. The method for determining the debugging result is widely applied to full-House intelligent digital control application scenes such as intelligent homes (Smart Home), intelligent homes, intelligent Home equipment ecology, intelligent House (Intelligent House) ecology and the like. Alternatively, in this embodiment, the method for determining the debugging result may be applied to a hardware environment formed by the terminal device 102 and the server 104 as shown in fig. 1. As shown in fig. 1, the server 104 is connected to the terminal device 102 through a network, and may be configured to provide a service (e.g., an application service) for the terminal or a client installed on the terminal, set a database on the server or independent of the server, and provide a data storage service for the server 104, and configure a cloud computing and/or edge computing service on the server or independent of the server, and provide a data operation service for the server 104.
The network may include, but is not limited to, at least one of: wired network, wireless network. The wired network may include, but is not limited to, at least one of: wide area networks, metropolitan area networks, local area networks, which may include, but are not limited to, at least one of the following: WIFI (Wireless Fidelity), bluetooth. Terminal equipment 102 can be but not limited to be PC, the cell-phone, the panel computer, intelligent air conditioner, intelligent cigarette machine, intelligent refrigerator, intelligent oven, intelligent kitchen range, intelligent washing machine, intelligent water heater, intelligent washing equipment, intelligent dish washer, intelligent projection equipment, intelligent TV, intelligent clothes hanger, intelligent (window) curtain, intelligence audio-visual, smart jack, intelligent stereo set, intelligent audio amplifier, intelligent new trend equipment, intelligent kitchen guarding equipment, intelligent bathroom equipment, intelligence robot of sweeping the floor, intelligence robot of wiping the window, intelligence robot of mopping the ground, intelligent air purification equipment, intelligent steam ager, intelligent microwave oven, intelligent kitchen is precious, intelligent clarifier, intelligent water dispenser, intelligent lock etc..
In this embodiment, a method for determining a debugging result is provided, and is applied to the computer terminal, and fig. 2 is a flowchart of the method for determining a debugging result according to the embodiment of the present application, where the flowchart includes the following steps:
step S202, a first test result when the test cases in the test case table are tested is obtained;
the test cases in the test case table may include a group of test cases for performing testing simultaneously. The test case may be in the form of, for example, "1 (case ID), test log-in interface (case description), first case group (case group), user name (test parameters), xxx.com (url), http request (request mode), < head >. </head >, < body >. </body >, (body)". For example, a test case a, a test case B, and a test case C that are in the same group in the test case table are obtained, and a first test result of testing the test case a, the test case B, and the test case C is obtained. For example, as shown in fig. 5, the structure of the first test result is, for example, the "result table" of fig. 5. In FIG. 5, the results table may include a use case ID, a use case group, a use case specification, a url, a request style, a header, a body, and a result.
Step S204, determining a target test case with an abnormal test result from the first test result;
it should be noted that the target test case with the abnormal test result may include a test case that fails to be executed due to poor network and the like. For example, if it is determined that the target test case with an abnormal test result in the first test results of the tests performed on the test case a, the test case B, and the test case C is the test case B, the test case B may be determined as the target debug case.
Step S206, responding to the debugging instruction of the first object, and debugging the target debugging case by using the target login information corresponding to the target debugging case and the debugging information corresponding to the target debugging case to obtain the debugging result of the target debugging case.
The first object may include, but is not limited to, a human or a robot.
It should be noted that the debugging information corresponding to the target debugging case includes general debugging information and login debugging information, the general debugging information is used for debugging the target debugging case in the unregistered state and the target debugging case in the logged state, and the login debugging information is used for debugging the target debugging case in the logged state.
Through the steps, a first test result when the test cases in the test case table are tested is obtained; determining a target test case with an abnormal test result from the first test result; responding to a debugging instruction of a first object, debugging the target debugging case by using target login information corresponding to the target debugging case and debugging information corresponding to the target debugging case to obtain a debugging result of the target debugging case, solving the problem of low debugging efficiency of an error case in the related technology, and further improving the debugging efficiency.
In an exemplary embodiment, how to determine the process of the target test case with abnormal test result from the first test result in step S204 is described based on the following technical solution, and the specific steps include: determining a second test result preset for the test case in the test case table; and comparing the second test result with the first test result, and determining the test case inconsistent with the second test result in the first test result as the target test case of the test result.
It should be noted that the second test result may be set in advance by the first object, or the historical test result may be analyzed to obtain the historical test result with the highest frequency, and the second test result may be determined according to the historical test result with the highest frequency.
In an exemplary embodiment, in order to better understand the process of debugging the target debug case by using the target login information corresponding to the target debug case and the debug information corresponding to the target debug case in step S206, a technical solution is provided, which includes the specific steps of: determining debugging parameters of the test case from case parameters of the test case in the test case table; determining debugging information of the target debugging case based on the debugging parameters; and under the condition that the target login information corresponding to the target debugging use case is not empty, executing the login operation of the target debugging use case by using the target login information, and debugging the target debugging use case by using the debugging information of the target debugging use case.
It should be noted that the use case parameters of the test cases in the test case table may include a use case ID, a use case group, a use case specification, parameters, url, a request mode, a header, a body, an assertion, and the like. Wherein, url, header and body can be set as debugging parameters of the debugging use case.
As shown in FIG. 3, url is "Https:// www.haigeek.com/queryNoticeInfo", header is { "Content-Type": application/json "," nonces ": 1660200712279", "timesmamp": 1660200712279"," Language ": zh-CN", "Accept-Language": zh-CN, zh-CN; q =0.9"," anti ReplaySign ": 111" } ", and body is" { "currPage": 1"," limit ":2}".
In an exemplary embodiment, further, before debugging the target debug case by using the target login information corresponding to the target debug case and the debug information corresponding to the target debug case, the following steps need to be performed: and responding to the selection instruction of the first object, and determining the target login information from pre-provided login information to be selected, wherein the pre-provided login information to be selected represents login information of all test cases containing preset words in the test case table.
It should be noted that the "preset word" may include, for example, "login," logic, "and the like, and the test case in the test case table that includes the preset word may include, for example," login "or a case list whose interface address includes" logic.
In an exemplary embodiment, optionally, after determining the target login information from pre-provided login information to be selected in response to the selection instruction of the first object, determining a login priority corresponding to the login information to be selected when logging in the target debugging use case based on the target login information fails; determining standby login information corresponding to the highest login priority from the multiple pieces of login information to be selected; logging in the target debugging case based on the standby login information; wherein the login priority is determined by one of: the selection frequency of the to-be-selected login information and the selection time of the to-be-selected login information.
Optionally, in another embodiment, determining the login priority according to the selection frequency of the to-be-selected login information includes: and determining the highest login priority corresponding to the login information to be selected with the highest selection frequency.
Optionally, in other embodiments, determining the login priority according to the selection time of the to-be-selected login information includes: and determining that the latest login information to be selected at the selection moment corresponds to the highest login priority. Or determining that the login information to be selected with the longest debugging time period corresponds to the highest login priority.
Or, in an embodiment, when logging in the target debugging case based on the target login information fails, sending a plurality of pieces of the login information to be selected to a first object, determining, by the first object, a login priority corresponding to the login information to be selected, and determining, from the plurality of pieces of the login information to be selected, backup login information corresponding to a highest login priority.
In an exemplary embodiment, when the target login information corresponding to the target debugging use case is empty, it may be determined whether the target debugging use case supports a function of debugging in a non-login state; if the target debugging case is determined to support the function of debugging in the non-login state, determining the corresponding general debugging information of the target debugging case in the non-login state, and debugging the target debugging case by using the general debugging information; the universal debugging information is used for debugging a target debugging use case in a non-login state and a target debugging use case in a login state; and if the target debugging case is determined not to support the function of debugging in the non-login state, sending prompt information to the first object, wherein the prompt information is used for prompting that the target debugging case cannot be debugged.
In an exemplary embodiment, after obtaining the debugging result of the target debugging use case, parameter updating may also be implemented, and a specific process includes: determining debugging parameters of the target debugging case from the debugging result; sending a parameter updating request to a first object, wherein the parameter updating request represents a request for updating the test cases in the test case table by using the debugging parameters; and under the condition that an updating instruction fed back by the first object based on the parameter updating request is received, responding to the updating instruction, and updating the request of the test cases in the test case table by using the debugging parameters.
It should be noted that, after receiving a parameter update instruction replied by the first object based on the parameter update request, the test case in the test case table may be updated using the debug parameter.
In order to better understand the process of the method for determining the debugging result, the following describes a flow of the method for determining the debugging result with reference to an optional embodiment, but is not limited to the technical solution of the embodiment of the present application.
Fig. 4 is a flowchart illustrating a method for determining a debugging result according to an embodiment of the present application (i), as shown in fig. 4, the following steps are specifically performed:
step S402, determining a test case group;
step S404, displaying the case result of the execution case;
step S406, click "send execution" on the use case result corresponding to the target use case in the result list, and enter the page of online test, where the online test page is as shown in fig. 3, and includes "interface address", "sent message header", "sent message body", and the like, where the interface address is, for example, "https:// www.haigeek.com/querynotinfo", and the sent message body is, for example, "{ currPage:1, limit:2}".
Step S408, sending a use case result corresponding to the target use case to a debugging page; fig. 3 is a diagram illustrating a debugging page, where fig. 3 is a schematic diagram illustrating a method for determining a debugging result according to an embodiment of the present application. The debugging page includes a "select login case," such as "extra-sea login," a "request method and address," such as "Header" and "Body," and the like, and the request method and address are, for example, "POST.
Step S410, determining whether a login use case exists in front of the target use case; if yes, go to step S412, otherwise go to step S420.
Step S412, a login case is selected in a pull-down mode, and the nearest case is selected by default;
step S414, displaying the target use case so that a user can edit the target use case conveniently;
step S416, clicking to execute, and debugging;
step S418, displaying the test result;
and step S420, directly clicking the editing case and directly executing.
In one embodiment, after the test case is executed, the results of the test case are displayed line by line, wherein each line of results is provided with a button for checking the details of the case; clicking to check the details of the case, displaying the information of the case through a popup window, and displaying an 'online test' button; and clicking an online test button to send the case information to a page of a single debugging case, so that the case information can be edited. And a pull-down menu is displayed at the upper end of the page, a use case list with all titles containing 'login' or interface addresses containing 'login' in front of the current use case is displayed, and the closest use case of the current use case is selected by default. And clicking an execution button, executing the selected login case, executing the current case, and displaying a detailed execution result and execution time.
Fig. 5 is a flowchart illustrating a method for determining a debugging result according to an embodiment of the present application (ii); as shown in fig. 5, the following steps are specifically performed:
step S502, a use case table and a result table are set;
the use case table may include the following attributes: use case ID (unique value), use case description, use case group, parameter, URL, request mode, header, body and assertion;
the following attributes may be included in the results table: example ID, example description, example group, URL (actual transmission after parameter replacement), request method (actual transmission after parameter replacement), header (actual transmission after parameter replacement), body (actual transmission after parameter replacement), result (execution result).
Step S504, click and carry out alone;
step S506-1, extracting actually sent url, header and body from the library according to the use case ID;
step S506-2, obtaining a case containing 'login' in the result set according to the case description;
step S508, selecting whether to perform login; if yes, go to step S512, otherwise go to step S510;
step S510, the login case is empty;
step S512, selecting a login case;
step S514, the url, the header and the body can be modified;
step S516, clicking and executing;
step S518, the login case is executed firstly (if the login case exists), and then the main case is executed;
step S520, a result is obtained and displayed to a page.
The structure of the use case table is shown in fig. 3, and includes: the method comprises the following steps of using a case ID (unique value), a module to which the case belongs, a case description, parameters, including parameters such as Url, body and header, wherein the case description is used for briefly describing the function of the case, and if the case is a login case, the description needs to contain a 'login' two-character, so that the case is convenient to view, and a data basis is provided for selecting the login case later.
After the use case is executed, relevant information including use case id, use case description, use case group, actually sent url, body, header and the like is recorded in the result table. When a use case is selected to be executed independently, the system searches all use case lists containing 'login' or interface addresses containing 'login' in the set of use cases, and asks the user to select the correct login use case. When the target use case is executed, the login use case is executed firstly, then the current use case is executed, and the test result is returned.
Through the steps, the wrong interface can be directly sent to the interface test page on the result page for debugging, and the corresponding login interface is automatically executed, so that the efficiency of interface debugging is greatly improved.
Through the description of the foregoing embodiments, it is clear to those skilled in the art that the method according to the foregoing embodiments may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present application or portions thereof that contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (such as a ROM/RAM, a magnetic disk, and an optical disk), and includes several instructions for enabling a terminal device (which may be a mobile phone, a computer, a server, or a network device) to execute the method of the embodiments of the present application.
Fig. 6 is a block diagram of a debugging result determination apparatus according to an embodiment of the present application; as shown in fig. 4, includes:
an obtaining module 62, configured to obtain a first test result when testing the test case in the test case table;
the test cases in the test case table may include a group of test cases for performing testing simultaneously. The test case may be in the form of, for example, "1 (case ID), test log-in interface (case description), first case group (case group), user name (test parameters), xxx.com (url), http request (request mode), < head >. </head >, < body >. </body >, (body)". For example, a test case a, a test case B, and a test case C of the same group in the test case table are obtained, and a first test result of testing the test case a, the test case B, and the test case C is obtained. For example, as shown in fig. 5, the structure of the first test result is, for example, the "result table" of fig. 5. In FIG. 5, the results table may include a use case ID, a use case group, a use case specification, a url, a request style, a header, a body, and a result.
A determining module 64, configured to determine, from the first test result, a target test case with an abnormal test result;
it should be noted that the target test case with the abnormal test result may include a test case that fails to be executed due to poor network and the like. For example, if it is determined that the target test case with an abnormal test result in the first test results of the tests performed on the test case a, the test case B, and the test case C is the test case B, the test case B may be determined as the target debug case.
An obtaining module 66, configured to respond to a debugging instruction of the first object, and debug the target debugging case by using the target login information corresponding to the target debugging case and the debugging information corresponding to the target debugging case, so as to obtain a debugging result of the target debugging case.
The first object may include, but is not limited to, a human or a robot.
Acquiring a first test result when the test cases in the test case table are tested by the device; determining a target test case with an abnormal test result from the first test result; responding to a debugging instruction of a first object, and debugging the target debugging case by using target login information corresponding to the target debugging case and debugging information corresponding to the target debugging case to obtain a debugging result of the target debugging case, so that the problem of low debugging efficiency of a wrong case in the related technology is solved, and the debugging efficiency is improved.
In an exemplary embodiment, the determining module 64 is further configured to determine a second test result preset for the test case in the test case table; and comparing the second test result with the first test result, and determining the test case inconsistent with the second test result in the first test result as the target test case of the test result.
It should be noted that the second test result may be set in advance by the first object, or the historical test result may be analyzed to obtain the historical test result with the highest frequency, and the second test result may be determined according to the historical test result with the highest frequency.
In an exemplary embodiment, the obtaining module 66 is further configured to determine debugging parameters of the test case from case parameters of the test case in the test case table; determining debugging information of the target debugging case based on the debugging parameters; and under the condition that the target login information corresponding to the target debugging case is not empty, executing login operation of the target debugging case by using the target login information, and debugging the target debugging case by using the debugging information of the target debugging case.
It should be noted that the use case parameters of the test cases in the test case table may include a use case ID, a use case group, a use case specification, parameters, url, a request mode, a header, a body, an assertion, and the like. The url, the header, and the body may be set as debugging parameters of the debugging use case.
In an exemplary embodiment, the apparatus for determining a debugging result further includes a first target login information determining module, configured to determine, in response to the selection instruction of the first object, the target login information from pre-provided login information to be selected, where the pre-provided login information to be selected represents login information of all test cases containing preset words in the test case table.
It should be noted that the "preset word" may include, for example, "login," logic, "and the like, and the test case in the test case table that includes the preset word may include, for example," login "or a case list whose interface address includes" logic.
In an exemplary embodiment, the apparatus for determining the debugging result further includes a second target login information determining module, configured to determine a login priority corresponding to the login information to be selected; determining standby login information corresponding to the highest login priority from the multiple pieces of login information to be selected; logging in the target debugging case based on the standby login information; wherein the login priority is determined by one of: the selection frequency of the to-be-selected login information and the selection time of the to-be-selected login information.
Optionally, in another embodiment, determining the login priority according to the selection frequency of the to-be-selected login information includes: and determining the highest login priority corresponding to the login information to be selected with the highest selection frequency.
Optionally, in another embodiment, determining the login priority according to the selection time of the login information to be selected includes: and determining the highest login priority corresponding to the latest login information to be selected at the selection moment. Or determining that the login information to be selected with the longest debugging time period corresponds to the highest login priority.
Or, in an embodiment, when logging in the target debugging case based on the target login information fails, sending a plurality of pieces of the login information to be selected to a first object, determining, by the first object, a login priority corresponding to the login information to be selected, and determining, from the plurality of pieces of the login information to be selected, backup login information corresponding to a highest login priority.
In an exemplary embodiment, the apparatus for determining a debugging result further includes a debugging module, configured to, when target login information corresponding to the target debugging case is empty, determine whether the target debugging case supports a function of performing debugging in a non-login state; if the target debugging case is determined to support the function of debugging in the non-login state, determining the corresponding general debugging information of the target debugging case in the non-login state, and debugging the target debugging case by using the general debugging information; the universal debugging information is used for debugging a target debugging use case in a non-login state and a target debugging use case in a login state; and if the target debugging case is determined not to support the function of debugging in the non-login state, sending prompt information to the first object, wherein the prompt information is used for prompting that the target debugging case cannot be debugged.
In an exemplary embodiment, the apparatus for determining a debugging result further includes an updating module, configured to determine, from the debugging result, a debugging parameter of the target debugging case after the debugging result of the target debugging case is obtained; sending a parameter updating request to a first object, wherein the parameter updating request represents a request for updating the test cases in the test case table by using the debugging parameters; and under the condition that an updating instruction fed back by the first object based on the parameter updating request is received, responding to the updating instruction, and updating the request of the test case in the test case table by using the debugging parameter.
It should be noted that, after receiving a parameter update instruction replied by the first object based on the parameter update request, the test case in the test case table may be updated using the debug parameter.
Embodiments of the present application also provide a storage medium including a stored program, where the program performs any one of the methods described above when executed.
Alternatively, in the present embodiment, the storage medium may be configured to store program codes for performing the following steps:
s1, obtaining a first test result when testing a test case in a test case table;
s2, determining a target test case with an abnormal test result from the first test result;
s3, responding to a debugging instruction of the first object, and debugging the target debugging case by using the target login information corresponding to the target debugging case and the debugging information corresponding to the target debugging case to obtain a debugging result of the target debugging case.
Embodiments of the present application further provide an electronic device, comprising a memory in which a computer program is stored and a processor configured to execute the computer program to perform the steps in any of the method embodiments described above.
Optionally, the electronic apparatus may further include a transmission device and an input/output device, wherein the transmission device is connected to the processor, and the input/output device is connected to the processor.
Optionally, in this embodiment, the processor may be configured to execute the following steps by a computer program:
s1, obtaining a first test result when testing cases in a test case table;
s2, determining a target test case with an abnormal test result from the first test result;
s3, responding to a debugging instruction of the first object, and debugging the target debugging case by using the target login information corresponding to the target debugging case and the debugging information corresponding to the target debugging case to obtain a debugging result of the target debugging case.
Optionally, in this embodiment, the storage medium may include, but is not limited to: various media capable of storing program codes, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.
Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation manners, and this embodiment is not described herein again.
It will be apparent to those skilled in the art that the modules or steps of the present application described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a memory device and executed by a computing device, and in some cases, the steps shown or described may be executed out of order, or separately as integrated circuit modules, or multiple modules or steps thereof may be implemented as a single integrated circuit module. Thus, the present application is not limited to any specific combination of hardware and software.
The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.
Claims (10)
1. A method for determining a debugging result is characterized by comprising the following steps:
acquiring a first test result when the test cases in the test case table are tested;
determining a target debugging case with an abnormal test result from the first test result;
responding to a debugging instruction of a first object, and debugging the target debugging case by using target login information corresponding to the target debugging case and debugging information corresponding to the target debugging case to obtain a debugging result of the target debugging case.
2. The method for determining the debugging result according to claim 1, wherein determining the target debugging case with abnormal testing result from the first testing result comprises:
determining a second test result preset for the test case in the test case table;
and comparing the second test result with the first test result, and determining a test case inconsistent with the second test result in the first test result as the target debugging case.
3. The method for determining the debugging result according to claim 1, wherein the debugging the target debugging use case using the target login information corresponding to the target debugging use case and the debugging information corresponding to the target debugging use case comprises:
determining debugging parameters of the test case from case parameters of the test case in the test case table;
determining debugging information of the target debugging case based on the debugging parameters;
and under the condition that the target login information corresponding to the target debugging case is not empty, executing login operation of the target debugging case by using the target login information, and debugging the target debugging case by using the debugging information of the target debugging case.
4. The method for determining the debugging result according to any one of claims 1 to 3, wherein before the target debugging use is debugged using the target login information corresponding to the target debugging use and the debugging information corresponding to the target debugging use, the method further comprises:
and responding to the selection instruction of the first object, and determining the target login information from pre-provided login information to be selected, wherein the pre-provided login information to be selected represents login information of all test cases containing preset words in the test case table.
5. The method for determining debugging results according to claim 4, wherein after determining the target login information from the login information to be selected provided in advance in response to the instruction for selecting the first object, the method further comprises:
determining login priority corresponding to the login information to be selected under the condition that the target debugging case is failed to be logged in based on the target login information;
determining standby login information corresponding to the highest login priority from the multiple pieces of login information to be selected;
logging in the target debugging case based on the standby login information;
wherein the login priority is determined by one of: the selection frequency of the to-be-selected login information and the selection time of the to-be-selected login information.
6. The method of determining debug results of claim 4, wherein said method further comprises:
under the condition that target login information corresponding to the target debugging use case is empty, determining whether the target debugging use case supports a function of debugging in a non-login state;
if the target debugging case is determined to support the function of debugging in the non-login state, determining the corresponding general debugging information of the target debugging case in the non-login state, and debugging the target debugging case by using the general debugging information; the universal debugging information is used for debugging a target debugging use case in a non-login state and a target debugging use case in a login state;
and if the target debugging case is determined not to support the function of debugging in the non-login state, sending prompt information to the first object, wherein the prompt information is used for prompting that the target debugging case cannot be debugged.
7. The method for determining the debugging result according to claim 1, wherein after obtaining the debugging result of the target debugging case, the method further comprises:
determining debugging parameters of the target debugging case from the debugging result;
sending a parameter updating request to a first object, wherein the parameter updating request represents a request for updating the test cases in the test case table by using the debugging parameters;
and under the condition that an updating instruction fed back by the first object based on the parameter updating request is received, responding to the updating instruction, and updating the request of the test case in the test case table by using the debugging parameter.
8. An apparatus for determining a debug result, comprising:
the acquisition module is used for acquiring a first test result when the test cases in the test case table are tested;
the determining module is used for determining a target debugging case with an abnormal test result from the first test result;
and the obtaining module is used for responding to a debugging instruction of the first object, and debugging the target debugging case by using the target login information corresponding to the target debugging case and the debugging information corresponding to the target debugging case to obtain a debugging result of the target debugging case.
9. A computer-readable storage medium, comprising a stored program, wherein the program is operable to perform the method of any one of claims 1 to 7.
10. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method of any of claims 1 to 7 by means of the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211145880.2A CN115629961A (en) | 2022-09-20 | 2022-09-20 | Method and device for determining debugging result, storage medium and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211145880.2A CN115629961A (en) | 2022-09-20 | 2022-09-20 | Method and device for determining debugging result, storage medium and electronic device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115629961A true CN115629961A (en) | 2023-01-20 |
Family
ID=84902178
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211145880.2A Pending CN115629961A (en) | 2022-09-20 | 2022-09-20 | Method and device for determining debugging result, storage medium and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115629961A (en) |
-
2022
- 2022-09-20 CN CN202211145880.2A patent/CN115629961A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107749813B (en) | Account management method, device, storage medium, equipment, server and terminal | |
| CN114896003A (en) | Page configuration method and device, storage medium and electronic device | |
| CN117573320A (en) | Task node execution method and device, storage medium and electronic device | |
| CN115629961A (en) | Method and device for determining debugging result, storage medium and electronic device | |
| CN109725884A (en) | Air control ' In System Reconfiguration Method, device, equipment and readable storage medium storing program for executing | |
| CN115934523A (en) | Target test data generation method and device, storage medium and electronic device | |
| CN115499333A (en) | Method, system, storage medium and electronic device for determining association relationship | |
| CN116361155A (en) | Method and device for testing software development kit, storage medium and electronic device | |
| CN115454851A (en) | Interface regression testing method and device, storage medium and electronic device | |
| CN115065508A (en) | Method and apparatus for processing device twin data, storage medium, and electronic apparatus | |
| CN115345225A (en) | Method and device for determining recommended scene, storage medium and electronic device | |
| US9490995B1 (en) | Simulation system for network devices in a network | |
| CN115687349A (en) | Database table generation method and device, storage medium and electronic device | |
| CN115834435A (en) | Interface test method and device, storage medium and electronic device | |
| CN105051776A (en) | Information processing device, information processing system, and information processing method | |
| CN115357446A (en) | Device testing method and device, storage medium and electronic device | |
| CN114760235B (en) | Method and device for executing dial testing task, storage medium and electronic device | |
| CN112463183A (en) | Display control card aging detection method, device and system and computer readable medium | |
| CN114999494A (en) | Voice interaction function testing method and device, storage medium and electronic device | |
| CN115733879A (en) | Target page pushing method and device, storage medium and electronic device | |
| CN115167163A (en) | Scene execution method and device, storage medium and electronic device | |
| CN115865650A (en) | Service deployment method and device, storage medium and electronic device | |
| CN114826899A (en) | Debugging method and device of equipment control service, storage medium and electronic device | |
| CN115460117A (en) | Device testing method and apparatus, storage medium, and electronic apparatus | |
| CN115550214A (en) | Task monitoring method and device, storage medium and electronic device |
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 |