CN113485880A - Test method and device - Google Patents
Test method and device Download PDFInfo
- Publication number
- CN113485880A CN113485880A CN202110785962.2A CN202110785962A CN113485880A CN 113485880 A CN113485880 A CN 113485880A CN 202110785962 A CN202110785962 A CN 202110785962A CN 113485880 A CN113485880 A CN 113485880A
- Authority
- CN
- China
- Prior art keywords
- test
- task
- tested
- page element
- data
- 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
- 238000010998 test method Methods 0.000 title claims abstract description 15
- 238000012360 testing method Methods 0.000 claims abstract description 605
- 238000000034 method Methods 0.000 claims description 54
- 238000012545 processing Methods 0.000 claims description 33
- 230000001960 triggered effect Effects 0.000 claims description 16
- 230000009471 action Effects 0.000 claims description 11
- 238000001514 detection method Methods 0.000 claims description 6
- 230000008569 process Effects 0.000 description 46
- 238000010586 diagram Methods 0.000 description 15
- 230000004044 response Effects 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 238000001545 Page's trend test Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000012216 screening Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2273—Test methods
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
- G06F11/221—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested to test buses, lines or interfaces, e.g. stuck-at or open line faults
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the specification provides a test method and a test device, wherein the test method comprises the following steps: responding to a test instruction of a task to be tested, determining a task link corresponding to the task to be tested according to a task identifier of the task to be tested, generating a test case corresponding to a page element test node in the task link, taking the task identifier as a calling parameter, calling a data query interface of a back-end server to perform data query, obtaining log data associated with the task to be tested, operating the test case, testing the page element test node according to the log data, triggering the back-end server based on the task identifier to test the data test node in the task link according to the log data, and generating and displaying a corresponding test result.
Description
Technical Field
The embodiment of the specification relates to the technical field of computers, in particular to a testing method. One or more embodiments of the present description also relate to a testing apparatus, a computing device, and a computer-readable storage medium.
Background
User interface testing (UI testing for short) is generally used for testing whether an object on a User interface can complete an expected function, so as to ensure good User experience and provide a corresponding function for a User to ensure that the User interface can normally provide the User, and in practical application, a back-end server for processing an interface access request of the User needs to update configuration information frequently, so as to ensure that the access request of the User can be accurately scheduled to the back-end server which normally works; therefore, the backend server needs to be tested while the user interface is tested.
However, in the current testing process, the testing process of the user interface and the testing process of the back-end server are often mutually independent, and the two independent testing processes need to be triggered manually by developers respectively, so that the testing process needs to consume much time, and the testing efficiency is low, and therefore, an effective method is urgently needed to solve the problems.
Disclosure of Invention
In view of this, the embodiments of the present disclosure provide a testing method. One or more embodiments of the present disclosure are also directed to a testing apparatus, a computing device, and a computer-readable storage medium, which solve the technical problems of the prior art.
According to a first aspect of embodiments herein, there is provided a test method comprising:
responding to a test instruction of a task to be tested, determining a task link corresponding to the task to be tested according to a task identifier of the task to be tested, and generating a test case corresponding to a page element test node in the task link;
taking the task identifier as a calling parameter, calling a data query interface of a back-end server to perform data query, and obtaining log data associated with the task to be tested;
and running the test case to test the page element test nodes according to the log data, triggering the back-end server based on the task identification to test the data test nodes in the task link according to the log data, and generating and displaying a corresponding test result.
Optionally, before determining the task link corresponding to the task to be tested according to the task identifier of the task to be tested, the method further includes:
responding to a project processing request submitted by a user, processing a project to be processed of the user, and generating corresponding log data;
determining the item identification of the item to be processed, and establishing the association relationship between the item identification and the log data;
and storing the incidence relation and the log data to a back-end server.
Optionally, determining a task link corresponding to the task to be tested according to the task identifier of the task to be tested includes:
determining a project identifier of a project corresponding to the task to be tested;
and taking the project identification as a task identification of the task to be tested, and determining a task link corresponding to the task to be tested according to the task identification, wherein the task link is generated based on the processing of the project to be processed.
Optionally, the testing method further includes:
receiving a parameter configuration instruction submitted by a user aiming at the test case, wherein the parameter configuration instruction comprises the running time interval of the test case;
polling and detecting whether the time difference between the current time and the historical running time of the test case is greater than or equal to the running time interval or not according to a preset detection period;
and if so, running the test case to test the page element test nodes according to the log data associated with the task to be tested, triggering a back-end server to test the data test nodes in the task link according to the log data, and generating and displaying a corresponding test result.
Optionally, generating a test case corresponding to the page element test node in the task link includes:
and configuring parameters of a test case template corresponding to the page element test node based on a page element test rule input by a user, and generating a test case corresponding to the page element test node.
Optionally, configuring parameters of a test case template corresponding to the page element test node based on a page element test rule input by a user, and generating a test case corresponding to the page element test node, including:
and respectively configuring a page element positioning parameter, a page element action parameter and an error identification parameter in the test case template according to a page element matching rule, a page element operation rule and an error identification rule contained in the page element test rule so as to generate a test case corresponding to the page element test node.
Optionally, running the test case to test the page element test node according to the log data includes:
running the test case to match page elements to be tested from the tasks to be tested according to the page element positioning parameters in the test case;
simulating the operation on the page element to be tested according to the page element action parameters in the test case, and generating a corresponding operation result; and the number of the first and second groups,
and identifying an error result from the operation result according to the error identification parameter in the test case, wherein the error result is used as a test result corresponding to the page element test node.
Optionally, triggering, by the back-end server, the test on the data test node in the task link according to the log data based on the task identifier includes:
and determining a test rule corresponding to the data test node in the task link, and triggering the back-end server to test the data test node according to the log data and the test rule based on the task identifier.
Optionally, triggering, by the back-end server, the test on the data test node in the task link according to the log data based on the task identifier includes:
and determining test rules respectively corresponding to the plurality of data test nodes in the task link, and triggering the back-end server based on the task identifier to sequentially test the plurality of data test nodes according to the log data, the test rules and the connection relation of the plurality of data test nodes in the task link.
According to a second aspect of embodiments herein, there is provided a test apparatus comprising:
the determining module is configured to respond to a test instruction of a task to be tested, determine a task link corresponding to the task to be tested according to a task identifier of the task to be tested, and generate a test case corresponding to a page element test node in the task link;
the calling module is configured to call a data query interface of a back-end server to perform data query by taking the task identifier as a calling parameter so as to obtain log data associated with the task to be tested;
and the testing module is configured to run the test case to test the page element testing nodes according to the log data, and based on the task identifier, the back-end server is triggered to test the data testing nodes in the task link according to the log data, so that a corresponding testing result is generated and displayed.
According to a third aspect of embodiments herein, there is provided a computing device comprising:
a memory and a processor;
the memory is to store computer-executable instructions, and the processor is to execute the computer-executable instructions to:
responding to a test instruction of a task to be tested, determining a task link corresponding to the task to be tested according to a task identifier of the task to be tested, and generating a test case corresponding to a page element test node in the task link;
taking the task identifier as a calling parameter, calling a data query interface of a back-end server to perform data query, and obtaining log data associated with the task to be tested;
and running the test case to test the page element test nodes according to the log data, triggering the back-end server based on the task identification to test the data test nodes in the task link according to the log data, and generating and displaying a corresponding test result.
According to a fourth aspect of embodiments herein, there is provided a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the test method.
In one embodiment of the present specification, a task link corresponding to a task to be tested is determined according to a task identifier of the task to be tested in response to a test instruction for the task to be tested, a test case corresponding to a page element test node in the task link is generated, the task identifier is used as a call parameter, a data query interface of a back-end server is called to perform data query, log data associated with the task to be tested is obtained, the test case is run, the page element test node is tested according to the log data, the back-end server is triggered based on the task identifier to test the data test node in the task link according to the log data, and a corresponding test result is generated and displayed.
In the embodiment of the present specification, after a test instruction of a task to be tested is received, a task identifier may be used as an interface call parameter according to an association relationship between the task identifier of the task to be tested and log data stored in a back-end server, the log data may be called from the back-end server, and when a test of a front-end page element is performed according to the log data, in addition, the back-end server may be synchronously triggered to test the content of a data layer of the task to be tested based on the task identifier, which is beneficial to simplifying a front-end and back-end test flow, and reducing time consumed by the test, thereby improving test efficiency.
Drawings
FIG. 1 is a schematic diagram of a testing process provided by one embodiment of the present description;
FIG. 2 is a process flow diagram of a testing method provided in one embodiment of the present description;
FIG. 3(a) is a schematic diagram of a testing process provided by one embodiment of the present description;
FIG. 3(b) is a diagram of a test result display page provided in an embodiment of the present specification;
FIG. 4 is a flowchart of a process for applying a test method to a transaction scenario according to an embodiment of the present disclosure;
FIG. 5 is a schematic diagram of a testing apparatus provided in one embodiment of the present disclosure;
fig. 6 is a block diagram of a computing device according to an embodiment of the present disclosure.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. This description may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein, as those skilled in the art will be able to make and use the present disclosure without departing from the spirit and scope of the present disclosure.
The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present specification refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It will be understood that, although the terms first, second, etc. may be used herein in one or more embodiments to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first can also be referred to as a second and, similarly, a second can also be referred to as a first without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
First, the noun terms to which one or more embodiments of the present specification relate are explained.
UI (user interface): the system and the user can interact and exchange information.
In the present specification, a test method is provided, and the present specification relates to a test apparatus, a computing device, and a computer-readable storage medium, which are described in detail in the following embodiments one by one.
At present, in most internet enterprises, the front end and the back end of the internet enterprises form a system from a development framework to quality technology and are not related to each other. Taking an automated test as an example, the front end only tests the contents of the display layer such as page elements, and the back end only tests the contents of the service layer, and a verification path is lacked between the front end and the back end. In the process of testing the full links of a certain item at the front end and the back end, the two full link tests are actually overlapped, and the difference lies in that the test emphasis of the two parts is different, namely the test emphasis of the front end is concentrated on the data of the display layer of the item, and the test emphasis of the back end is concentrated on the data of the service layer.
In addition, the current testing method adopted by the back end to test the data of the service layer is as follows: by respectively calling different testing capabilities and assembling the testing items of the rear-end test case, the testing process of each testing capability is relatively dispersed, and a mechanism for triggering multi-step testing capabilities to test at one time is lacked.
Based on this, the embodiment of the specification realizes that the complete test closed loop from the front end to the back end is completed by one-time automatic scheduling by digging the possibility of the automatic linkage of the front end and the back end; in addition, the embodiment of the specification realizes a testing process of triggering multi-step testing capability at one time by integrating multiple testing capabilities of the rear end, so that the testing process is simplified, and the testing efficiency is improved.
FIG. 1 is a schematic diagram illustrating a testing process provided in accordance with one embodiment of the present specification, a user configuring a task for front-end UI test case execution through a UI automation testing platform and scheduling the front-end UI test case execution UI automation testing task through the front-end UI automation testing platform; after the front-end test task is executed, the back-end server is started to carry out back-end data check, after the test items at the back end are tested one by one, the comprehensive test result of the back-end server is returned, and the test result of the front end and the back end is summarized and displayed through the UI automatic test platform.
Fig. 2 shows a process flow diagram of a testing method provided according to an embodiment of the present disclosure, which includes steps 202 to 206.
Specifically, the testing method provided in the embodiment of the present specification is applied to a client, and the client performs a front-end test, that is, a UI test, and specifically may perform a test on a certain test object in the client, for example, perform a UI test on an application program or a certain website.
The task to be tested is a test task which needs to test a test object (for example, data generated by project processing) of the client; the items in the embodiment of the present specification include, but are not limited to, a resource transaction item, an account opening item, and the like, and the task to be tested may be a test task that needs to test data generated in a processing process of the account opening item, or a test task that needs to test data generated in a processing process of the resource transaction item.
The test case is a set of test programs generated for a test object. Generally, a test case may contain preconditions of a test, execution conditions of the test, objects of the test, input in the test process, and screening rules of expected results, etc. to test whether the test object meets a specific requirement.
The task link is a link to be tested, the link is generated by processing a project corresponding to the task to be tested, the node in the link is a processing node related to the project processing, and taking the project as a transaction project as an example, the processing node includes but is not limited to a transaction amount, a transaction object, a transaction result and transaction information check peer.
Page elements, i.e., various controls in the front page, include, but are not limited to, text, pictures, input boxes, buttons, dialog boxes in the page.
In the embodiment of the present specification, because the client only performs the page element verification of the front end, in response to a test instruction for the task to be tested, the task link corresponding to the task to be tested may be determined according to the task identifier corresponding to the task to be tested, and a test case corresponding to the page element test node in the task link may be automatically generated.
In practical application, a test case corresponding to the page element test node in the task link can be configured and generated on an automatic test platform of the client, and the configured parameters include but are not limited to an operating device type parameter, an operating environment parameter, a task type parameter, an installation package link parameter and the like.
Because the task to be tested tests the data generated in the project processing process, before receiving the test instruction of the task to be tested, project processing needs to be performed, and the method can be specifically realized by the following steps:
responding to a project processing request submitted by a user, processing a project to be processed of the user, and generating corresponding log data;
determining the item identification of the item to be processed, and establishing the association relationship between the item identification and the log data;
and storing the incidence relation and the log data to a back-end server.
Further, determining a task link corresponding to the task to be tested according to the task identifier of the task to be tested, including:
determining a project identifier of a project corresponding to the task to be tested;
and taking the project identification as a task identification of the task to be tested, and determining a task link corresponding to the task to be tested according to the task identification, wherein the task link is generated based on the processing of the project to be processed.
Specifically, the items to be processed include, but are not limited to, account opening items, resource transaction items, and the like, before testing the tasks to be tested, the items need to be processed, that is, account opening operation is performed, resource transaction operation is performed, log data corresponding to an operation process is generated, so that the tasks to be tested are generated based on the log data, and the log data is tested.
In practical application, when an item to be processed is processed, an association relationship can be established among the item to be processed, an item identifier of the item to be processed, and log data generated by processing, and the association relationship and the log data are stored in a back-end server, so that when a test instruction of a task to be tested is received, related log data can be inquired from the back-end server based on the association relationship, and the back-end server is triggered to automatically perform data test based on the task identifier (item identifier) and the association relationship.
The task to be tested is generated based on the log data generated in the project processing process, so that the project identification of the project corresponding to the task to be tested can be used as the task identification of the task to be tested, and the task link corresponding to the task to be tested is determined according to the task identification, namely the link generated by processing the project corresponding to the task to be tested.
In addition, after the user configures and generates the test case on the automatic test platform, the user can also set an automatic running period of the test case so as to automatically run the test case at regular time according to a certain period, which can be specifically realized by the following modes:
receiving a parameter configuration instruction submitted by a user aiming at the test case, wherein the parameter configuration instruction comprises the running time interval of the test case;
polling and detecting whether the time difference between the current time and the historical running time of the test case is greater than or equal to the running time interval or not according to a preset detection period;
and if so, running the test case to test the page element test nodes according to the log data associated with the task to be tested, triggering a back-end server to test the data test nodes in the task link according to the log data, and generating and displaying a corresponding test result.
Specifically, after the automatic test platform is configured and generates the test case, the user can set an automatic running period of the test case, so that the automatic test platform can automatically run the test case at regular time according to a certain period.
Therefore, after receiving a parameter configuration instruction submitted by a user for the test case, the automated test platform may query the parameter configuration instruction for a running period, that is, a running time interval, of the test case, and automatically run the test case to test the front-end page element when detecting that a time difference between a current time and a last running time (historical running time) of the test case is greater than or equal to the running time interval.
After the front-end page element test is completed, the back-end server is triggered to test the data layer content of the task to be tested according to the task identification of the task to be tested, and after the test is completed, the test results of the front end and the back end are displayed by the automatic test platform.
In practical application, after the test case of the task to be tested is generated, the user can manually trigger the test case to run in real time, and the test case can be determined according to practical requirements without limitation.
In the embodiment of the description, by setting the running period of the test case, that is, the running time interval, the automated test platform can automatically run the test case to test the page element when detecting that the time interval between the current time and the last running time of the test case is greater than or equal to the running time interval, so as to reduce the time consumed in the page element testing process, and thus improve the testing efficiency.
In specific implementation, in the embodiment of the present specification, under the condition that the front end and the back end are tested, only the test case of the front end needs to be generated, and because the front end test is a UI test, that is, a page test, a test case corresponding to a page element test node in the task link is generated, that is, based on a page element test rule input by a user, parameters of a test case template corresponding to the page element test node are configured, and the test case corresponding to the page element test node is generated.
Further, configuring parameters of a test case template corresponding to the page element test node based on a page element test rule input by a user, and generating a test case corresponding to the page element test node, including:
and respectively configuring a page element positioning parameter, a page element action parameter and an error identification parameter in the test case template according to a page element matching rule, a page element operation rule and an error identification rule contained in the page element test rule so as to generate a test case corresponding to the page element test node.
In particular, page elements, i.e., various controls in the front page, include, but are not limited to, text, pictures, input boxes, buttons, and dialog boxes in the page.
The test rule is used for indicating a test object, a test method of the test object, a display mode of a test result, and/or the like. In practical applications, the test rule may be set by a user according to the characteristics and/or the test requirements of the test object, which is not limited herein.
The test case template, that is, the test case template including the format, the test content, the test parameters for testing the test object, and the like, can be set by the user according to the test requirements.
In the process of testing the page elements, the test case template can be configured by combining the test rule, and then the test case which accords with the test object is automatically generated.
In practical application, the page element displayed on the page of the client can realize the interaction function between the user and the client, so that the test on the page element can be equivalent to the test on the interaction process between the user and the page element and the corresponding interaction result, and is mainly used for testing whether display abnormality exists in the interaction process or whether the display result is consistent with an expected display result.
In the embodiment of the present specification, a test case is automatically generated in response to a test instruction for a task to be tested, and then the page element is tested based on the test rule, so as to reduce the time consumed in the process of testing the page element, thereby improving the test efficiency.
And 204, taking the task identifier as a calling parameter, calling a data query interface of a back-end server to perform data query, and obtaining log data associated with the task to be tested.
Specifically, after a test case corresponding to a page element test node in a task link is generated, the task identifier is used as an interface call parameter, log data associated with a task to be tested is inquired from a data inquiry interface of a back-end server, so that the page element test node at the front end is tested based on the log data, and the data test node at the back-end server is tested.
And step 206, running the test case to test the page element test nodes according to the log data, triggering the back-end server based on the task identifier to test the data test nodes in the task link according to the log data, and generating and displaying a corresponding test result.
Specifically, after a test case corresponding to the front-end page element test node is configured and generated by the automated test platform, the automated test platform may be manually triggered to run the test case, or the running time interval of the test case is set, and the automated test platform automatically executes the test case when detecting that the time interval between the current time and the last running time of the test case is greater than or equal to the running time interval, so as to test the front-end page element test node.
After the testing process of the front end is finished, the rear end server can be triggered to test the data testing nodes according to the task identification of the task to be tested, after all testing items of the rear end server are tested, a comprehensive rear end server testing result is returned to the client, and the testing results of the front end and the rear end are summarized and displayed through the automatic testing platform.
In specific implementation, the running of the test case to test the page element test node according to the log data includes:
running the test case to match page elements to be tested from the tasks to be tested according to the page element positioning parameters in the test case;
simulating the operation on the page element to be tested according to the page element action parameters in the test case, and generating a corresponding operation result; and the number of the first and second groups,
and identifying an error result from the operation result according to the error identification parameter in the test case, wherein the error result is used as a test result corresponding to the page element test node.
Specifically, the page element positioning parameter is used for determining a page element to be tested in a page in the process of running a test case; the page element action parameters are used for simulating the operation process of the page elements to be tested during project processing in the process of running the test cases; and the error identification parameters are used for screening out the operation results which do not accord with the expectation of the test object from the operation results generated by simulating the operation process of the page elements to be tested.
The test case corresponding to the page element test node is generated through the method, the test case can be operated after the associated log data is obtained, in the process of operating the test case, the automatic test platform can take the page elements matched with the page element positioning parameters in the test case as the page elements to be tested, the operation process of the page elements to be tested is simulated in the project processing process according to the page element action parameters in the test case, and the error results (the expected operation results which do not accord with the test object) are screened out from the simulation results according to the error identification parameters in the test case.
In the embodiment of the specification, the test case is operated to position the page elements to be tested in the page, and the operation on the page elements to be tested is simulated, so that the dependency of the page test process on manual compiling of the test case can be effectively reduced, the time cost spent on testing the page is reduced, and the page test efficiency is improved.
Further, the back-end server is triggered to test the data test nodes in the task link according to the log data based on the task identifier, that is, a test rule corresponding to the data test nodes in the task link is determined, and the back-end server is triggered to test the data test nodes according to the log data and the test rule based on the task identifier.
Or triggering the back-end server to test the data test nodes in the task link according to the log data based on the task identifier, namely determining test rules respectively corresponding to the plurality of data test nodes in the task link, and triggering the back-end server to sequentially test the plurality of data test nodes according to the log data, the test rules and the connection relations of the plurality of data test nodes in the task link based on the task identifier.
Specifically, as described above, the test rule is used to indicate the test object, the test method of the test object, and/or the display mode of the test result. In practical applications, the test rule may be set by a user according to the characteristics and/or the test requirements of the test object, which is not limited herein.
In the embodiment of the present specification, because a plurality of test items exist in the back-end server, and different test items correspond to different test rules, after the test of the page element test node at the front end is completed, the back-end server can be triggered to test different test items according to the task identifier of the task to be tested.
In practical application, the test process of different test items can be realized based on the connection relationship of a plurality of data test nodes in a task link, that is, the plurality of test items (data test nodes) are sequentially tested based on the connection relationship.
Through the process, the embodiment of the specification realizes the boundary breaking of the end, so that the data test of the display level of the front end supplements the data test of the data level of the rear end server, and the integration of the front end test and the rear end test is realized, namely the data test of the front end and the rear end can be realized through one-time triggering; in addition, the embodiment of the specification can break the boundary of the test platform, integrate the test capability of the back-end server, and realize that a plurality of test items of the back-end server are triggered once to be tested in sequence, thereby simplifying the test flow and being beneficial to improving the test efficiency.
In addition, the embodiment of the specification can break the environment boundary, and the complete on-line testing capability can be realized by utilizing the characteristic of the front-end automatic seamless cutting environment.
A schematic diagram of a testing process provided in an embodiment of the present specification is shown in fig. 3(a), where fig. 3(a) shows a schematic diagram of an online testing process, which includes the following steps.
Step 302, the client performs test case scheduling.
Step 304, the client initiates a test to the backend server.
Step 306, the test module 1 in the back-end server obtains the serial number from the client.
In step 308, the test module 1 tests the test item 1.
And step 310, the back-end server archives the result.
And particularly, archiving the test result.
In step 312, the testing module 2 in the back-end server tests the testing item 2.
And step 314, the back-end server archives the result.
Step 316, the test module 3 in the back-end server obtains the resource exchange order number.
Step 318, the testing module 3 in the back-end server tests the testing item 3.
And step 320, the back-end server archives the result.
And step 322, the back-end server returns the test result to the client.
Specifically, in the embodiment of the present specification, the test module 1, the test module 2, and the test module 3 are all deployed in a backend server, and different test modules are used to test different test items, where the test module 1 is used to test the test item 1, the test module 2 is used to test the test item 2, and the test module 3 is used to test the test item 3.
In addition, fig. 3(a) is a schematic diagram of an online test process, and compared with the online test process, the offline test process cannot acquire the serial number in step 306, and also cannot acquire the resource exchange single number in step 316, and other processing processes are similar to the online test process and are not described herein again.
In addition, after the page element test node at the front end and the data test node at the back end are tested and corresponding test results are generated, the test results can be displayed through an automatic test platform, and include but are not limited to basic configuration information of tasks to be tested, test result analysis, such as success rate, success number, case detail list and the like. A schematic diagram of a test result presentation page provided in the embodiment of the present specification is shown in fig. 3(b), where in the test result presentation page, for each use case, there is a more detailed and more complete use case detail, in which end-to-end data checks requested by each front-end page are presented one by one, and a user can view details of an end-to-end data test result through the page.
In one embodiment of the present specification, a task link corresponding to a task to be tested is determined according to a task identifier of the task to be tested in response to a test instruction for the task to be tested, a test case corresponding to a page element test node in the task link is generated, the task identifier is used as a call parameter, a data query interface of a back-end server is called to perform data query, log data associated with the task to be tested is obtained, the test case is run, the page element test node is tested according to the log data, the back-end server is triggered based on the task identifier to test the data test node in the task link according to the log data, and a corresponding test result is generated and displayed.
In the embodiment of the present specification, after a test instruction of a task to be tested is received, a task identifier may be used as an interface call parameter according to an association relationship between the task identifier of the task to be tested and log data stored in a back-end server, the log data may be called from the back-end server, and when a test of a front-end page element is performed according to the log data, in addition, the back-end server may be synchronously triggered to test the content of a data layer of the task to be tested based on the task identifier, which is beneficial to simplifying a front-end and back-end test flow, and reducing time consumed by the test, thereby improving test efficiency.
The following description will further describe the testing method provided in this specification with reference to fig. 4 by taking an application of the testing method in a transaction scenario as an example. Fig. 4 is a flowchart illustrating a processing procedure of applying a testing method to a transaction scenario according to an embodiment of the present disclosure, where specific steps include steps 402 to 420.
Step 402, responding to a transaction item processing request submitted by a user, processing a to-be-processed transaction item of the user, and generating corresponding log data.
Step 410, using the project identifier as a task identifier of the task to be tested, and determining a task link corresponding to the task to be tested according to the task identifier, wherein the task link is generated based on the processing of the transaction project to be processed.
Step 412, configuring parameters of the test case template corresponding to the page element test node based on the page element test rule input by the user, and generating the test case corresponding to the page element test node.
And 414, taking the task identifier as a calling parameter, calling a data query interface of a back-end server to perform data query, and obtaining log data associated with the task to be tested.
And 416, running the test case to test the page element test node according to the log data.
And step 420, generating and displaying a test result corresponding to the task to be tested.
In the embodiment of the present specification, after a test instruction of a task to be tested is received, a task identifier may be used as an interface call parameter according to an association relationship between the task identifier of the task to be tested and log data stored in a back-end server, the log data may be called from the back-end server, and when a test of a front-end page element is performed according to the log data, in addition, the back-end server may be synchronously triggered to test the content of a data layer of the task to be tested based on the task identifier, which is beneficial to simplifying a front-end and back-end test flow, and reducing time consumed by the test, thereby improving test efficiency.
Corresponding to the above method embodiment, the present specification further provides an embodiment of a testing apparatus, and fig. 5 shows a schematic diagram of a testing apparatus provided in an embodiment of the present specification. As shown in fig. 5, the apparatus includes:
a determining module 502, configured to respond to a test instruction for a task to be tested, determine a task link corresponding to the task to be tested according to a task identifier of the task to be tested, and generate a test case corresponding to a page element test node in the task link;
a calling module 504, configured to call a data query interface of a back-end server to perform data query by using the task identifier as a calling parameter, so as to obtain log data associated with the task to be tested;
the test module 506 is configured to run the test case, so as to test the page element test nodes according to the log data, and based on the task identifier, trigger the back-end server to test the data test nodes in the task link according to the log data, generate and display a corresponding test result.
Optionally, the testing apparatus further includes:
the project processing module is configured to respond to a project processing request submitted by a user, process a project to be processed of the user and generate corresponding log data;
the establishing module is configured to determine an item identifier of the to-be-processed item and establish an association relation between the item identifier and the log data;
and the storage module is configured to store the incidence relation and the log data to a back-end server.
Optionally, the determining module 502 is further configured to:
determining a project identifier of a project corresponding to the task to be tested;
and taking the project identification as a task identification of the task to be tested, and determining a task link corresponding to the task to be tested according to the task identification, wherein the task link is generated based on the processing of the project to be processed.
Optionally, the testing apparatus further includes:
the receiving module is configured to receive a parameter configuration instruction submitted by a user aiming at the test case, wherein the parameter configuration instruction comprises a running time interval of the test case;
the detection module is configured to poll and detect whether the time difference between the current time and the historical running time of the test case is greater than or equal to the running time interval or not according to a preset detection period;
if the operation result of the detection module is yes, the trigger module is operated;
the trigger module is configured to run the test case to test the page element test nodes according to log data associated with the task to be tested, and trigger the back-end server to test the data test nodes in the task link according to the log data to generate and display a corresponding test result.
Optionally, the determining module 502 is further configured to:
and configuring parameters of a test case template corresponding to the page element test node based on a page element test rule input by a user, and generating a test case corresponding to the page element test node.
Optionally, the determining module 502 is further configured to:
and respectively configuring a page element positioning parameter, a page element action parameter and an error identification parameter in the test case template according to a page element matching rule, a page element operation rule and an error identification rule contained in the page element test rule so as to generate a test case corresponding to the page element test node.
Optionally, the testing module 506 is further configured to:
running the test case to match page elements to be tested from the tasks to be tested according to the page element positioning parameters in the test case;
simulating the operation on the page element to be tested according to the page element action parameters in the test case, and generating a corresponding operation result; and the number of the first and second groups,
and identifying an error result from the operation result according to the error identification parameter in the test case, wherein the error result is used as a test result corresponding to the page element test node.
Optionally, the testing module 506 is further configured to:
and determining a test rule corresponding to the data test node in the task link, and triggering the back-end server to test the data test node according to the log data and the test rule based on the task identifier.
Optionally, the testing module 506 is further configured to:
and determining test rules respectively corresponding to the plurality of data test nodes in the task link, and triggering the back-end server based on the task identifier to sequentially test the plurality of data test nodes according to the log data, the test rules and the connection relation of the plurality of data test nodes in the task link.
The above is a schematic scheme of a testing apparatus of the present embodiment. It should be noted that the technical solution of the testing apparatus and the technical solution of the testing method belong to the same concept, and details that are not described in detail in the technical solution of the testing apparatus can be referred to the description of the technical solution of the testing method.
FIG. 6 illustrates a block diagram of a computing device 600 provided in accordance with one embodiment of the present description. The components of the computing device 600 include, but are not limited to, a memory 610 and a processor 620. The processor 620 is coupled to the memory 610 via a bus 630 and a database 650 is used to store data.
Computing device 600 also includes access device 640, access device 640 enabling computing device 600 to communicate via one or more networks 660. Examples of such networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. Access device 640 may include one or more of any type of network interface (e.g., a Network Interface Card (NIC)) whether wired or wireless, such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.
In one embodiment of the present description, the above-described components of computing device 600, as well as other components not shown in FIG. 6, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device architecture shown in FIG. 6 is for purposes of example only and is not limiting as to the scope of the present description. Those skilled in the art may add or replace other components as desired.
Computing device 600 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smartphone), wearable computing device (e.g., smartwatch, smartglasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 600 may also be a mobile or stationary server.
Wherein the memory 610 is configured to store computer-executable instructions and the processor 620 is configured to execute the following computer-executable instructions:
responding to a test instruction of a task to be tested, determining a task link corresponding to the task to be tested according to a task identifier of the task to be tested, and generating a test case corresponding to a page element test node in the task link;
taking the task identifier as a calling parameter, calling a data query interface of a back-end server to perform data query, and obtaining log data associated with the task to be tested;
and running the test case to test the page element test nodes according to the log data, triggering the back-end server based on the task identification to test the data test nodes in the task link according to the log data, and generating and displaying a corresponding test result.
The above is an illustrative scheme of a computing device of the present embodiment. It should be noted that the technical solution of the computing device and the technical solution of the testing method belong to the same concept, and details that are not described in detail in the technical solution of the computing device can be referred to the description of the technical solution of the testing method.
An embodiment of the present specification also provides a computer readable storage medium storing computer instructions which, when executed by a processor, are used to implement the steps of the test method.
The above is an illustrative scheme of a computer-readable storage medium of the present embodiment. It should be noted that the technical solution of the storage medium belongs to the same concept as the technical solution of the test method, and details that are not described in detail in the technical solution of the storage medium can be referred to the description of the technical solution of the test method.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The computer instructions comprise computer program code which may be in the form of source code, object code, an executable file or some intermediate form, or the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
It should be noted that, for the sake of simplicity, the foregoing method embodiments are described as a series of acts, but those skilled in the art should understand that the present embodiment is not limited by the described acts, because some steps may be performed in other sequences or simultaneously according to the present embodiment. Further, those skilled in the art should also appreciate that the embodiments described in this specification are preferred embodiments and that acts and modules referred to are not necessarily required for an embodiment of the specification.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
The preferred embodiments of the present specification disclosed above are intended only to aid in the description of the specification. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the embodiments and the practical application, to thereby enable others skilled in the art to best understand and utilize the embodiments. The specification is limited only by the claims and their full scope and equivalents.
Claims (12)
1. A method of testing, comprising:
responding to a test instruction of a task to be tested, determining a task link corresponding to the task to be tested according to a task identifier of the task to be tested, and generating a test case corresponding to a page element test node in the task link;
taking the task identifier as a calling parameter, calling a data query interface of a back-end server to perform data query, and obtaining log data associated with the task to be tested;
and running the test case to test the page element test nodes according to the log data, triggering the back-end server based on the task identification to test the data test nodes in the task link according to the log data, and generating and displaying a corresponding test result.
2. The testing method according to claim 1, wherein before determining the task link corresponding to the task to be tested according to the task identifier of the task to be tested, the method further comprises:
responding to a project processing request submitted by a user, processing a project to be processed of the user, and generating corresponding log data;
determining the item identification of the item to be processed, and establishing the association relationship between the item identification and the log data;
and storing the incidence relation and the log data to a back-end server.
3. The testing method of claim 2, wherein the determining the task link corresponding to the task to be tested according to the task identifier of the task to be tested comprises:
determining a project identifier of a project corresponding to the task to be tested;
and taking the project identification as a task identification of the task to be tested, and determining a task link corresponding to the task to be tested according to the task identification, wherein the task link is generated based on the processing of the project to be processed.
4. The testing method of claim 1, further comprising:
receiving a parameter configuration instruction submitted by a user aiming at the test case, wherein the parameter configuration instruction comprises the running time interval of the test case;
polling and detecting whether the time difference between the current time and the historical running time of the test case is greater than or equal to the running time interval or not according to a preset detection period;
and if so, running the test case to test the page element test nodes according to the log data associated with the task to be tested, triggering a back-end server to test the data test nodes in the task link according to the log data, and generating and displaying a corresponding test result.
5. The testing method according to claim 1 or 4, wherein the generating of the test case corresponding to the page element testing node in the task link includes:
and configuring parameters of a test case template corresponding to the page element test node based on a page element test rule input by a user, and generating a test case corresponding to the page element test node.
6. The testing method according to claim 5, wherein the configuring parameters of the test case template corresponding to the page element testing node based on the page element testing rule input by the user to generate the test case corresponding to the page element testing node comprises:
and respectively configuring a page element positioning parameter, a page element action parameter and an error identification parameter in the test case template according to a page element matching rule, a page element operation rule and an error identification rule contained in the page element test rule so as to generate a test case corresponding to the page element test node.
7. The testing method of claim 6, wherein the running the test case to test the page element test node according to the log data comprises:
running the test case to match page elements to be tested from the tasks to be tested according to the page element positioning parameters in the test case;
simulating the operation on the page element to be tested according to the page element action parameters in the test case, and generating a corresponding operation result; and the number of the first and second groups,
and identifying an error result from the operation result according to the error identification parameter in the test case, wherein the error result is used as a test result corresponding to the page element test node.
8. The testing method of claim 1, wherein the triggering the back-end server to test the data testing node in the task link according to the log data based on the task identifier comprises:
and determining a test rule corresponding to the data test node in the task link, and triggering the back-end server to test the data test node according to the log data and the test rule based on the task identifier.
9. The testing method of claim 1, wherein the triggering the back-end server to test the data testing node in the task link according to the log data based on the task identifier comprises:
and determining test rules respectively corresponding to the plurality of data test nodes in the task link, and triggering the back-end server based on the task identifier to sequentially test the plurality of data test nodes according to the log data, the test rules and the connection relation of the plurality of data test nodes in the task link.
10. A test apparatus, comprising:
the determining module is configured to respond to a test instruction of a task to be tested, determine a task link corresponding to the task to be tested according to a task identifier of the task to be tested, and generate a test case corresponding to a page element test node in the task link;
the calling module is configured to call a data query interface of a back-end server to perform data query by taking the task identifier as a calling parameter so as to obtain log data associated with the task to be tested;
and the testing module is configured to run the test case to test the page element testing nodes according to the log data, and based on the task identifier, the back-end server is triggered to test the data testing nodes in the task link according to the log data, so that a corresponding testing result is generated and displayed.
11. A computing device, comprising:
a memory and a processor;
the memory is configured to store computer-executable instructions, and the processor is configured to execute the computer-executable instructions to implement the steps of the testing method of any one of claims 1 to 9.
12. A computer readable storage medium storing computer instructions which, when executed by a processor, carry out the steps of the test method of any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110785962.2A CN113485880A (en) | 2021-07-12 | 2021-07-12 | Test method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110785962.2A CN113485880A (en) | 2021-07-12 | 2021-07-12 | Test method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113485880A true CN113485880A (en) | 2021-10-08 |
Family
ID=77938790
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110785962.2A Pending CN113485880A (en) | 2021-07-12 | 2021-07-12 | Test method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113485880A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114448852A (en) * | 2021-12-30 | 2022-05-06 | 中国电信股份有限公司 | Gateway terminal testing method, device and storage medium |
| CN114740829A (en) * | 2022-05-07 | 2022-07-12 | 镁佳(北京)科技有限公司 | Domain controller test system |
| CN116107913A (en) * | 2023-04-06 | 2023-05-12 | 阿里云计算有限公司 | Test control method, device and system of single-node server |
| WO2023093702A1 (en) * | 2021-11-25 | 2023-06-01 | 华为技术有限公司 | Network measurement method and related apparatus |
| CN116506340A (en) * | 2023-06-27 | 2023-07-28 | 云账户技术(天津)有限公司 | Flow link testing method and device, electronic equipment and storage medium |
| CN116795723A (en) * | 2023-08-21 | 2023-09-22 | 建信金融科技有限责任公司 | Chain unit test processing method and device and computer equipment |
| CN117472783A (en) * | 2023-12-14 | 2024-01-30 | 中电金信数字科技集团有限公司 | Test integrated platform |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107908549A (en) * | 2017-10-24 | 2018-04-13 | 北京小米移动软件有限公司 | Method for generating test case, device and computer-readable recording medium |
| CN108228443A (en) * | 2016-12-14 | 2018-06-29 | 北京国双科技有限公司 | A kind of test method and device of web applications |
| CN108241580A (en) * | 2016-12-30 | 2018-07-03 | 深圳壹账通智能科技有限公司 | The test method and terminal of client-side program |
| CN108427639A (en) * | 2018-01-24 | 2018-08-21 | 深圳壹账通智能科技有限公司 | Automated testing method, application server and computer readable storage medium |
| CN109062809A (en) * | 2018-09-20 | 2018-12-21 | 北京奇艺世纪科技有限公司 | Method for generating test case, device and electronic equipment on a kind of line |
| CN109144842A (en) * | 2017-06-16 | 2019-01-04 | 百度在线网络技术（北京）有限公司 | Method and apparatus for test application |
| CN111209184A (en) * | 2019-12-20 | 2020-05-29 | 北京你财富计算机科技有限公司 | Automatic testing method and device and electronic equipment |
| CN111427760A (en) * | 2019-01-09 | 2020-07-17 | 阿里巴巴集团控股有限公司 | Page testing method, device, equipment and storage medium |
-
2021
- 2021-07-12 CN CN202110785962.2A patent/CN113485880A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108228443A (en) * | 2016-12-14 | 2018-06-29 | 北京国双科技有限公司 | A kind of test method and device of web applications |
| CN108241580A (en) * | 2016-12-30 | 2018-07-03 | 深圳壹账通智能科技有限公司 | The test method and terminal of client-side program |
| CN109144842A (en) * | 2017-06-16 | 2019-01-04 | 百度在线网络技术（北京）有限公司 | Method and apparatus for test application |
| CN107908549A (en) * | 2017-10-24 | 2018-04-13 | 北京小米移动软件有限公司 | Method for generating test case, device and computer-readable recording medium |
| CN108427639A (en) * | 2018-01-24 | 2018-08-21 | 深圳壹账通智能科技有限公司 | Automated testing method, application server and computer readable storage medium |
| CN109062809A (en) * | 2018-09-20 | 2018-12-21 | 北京奇艺世纪科技有限公司 | Method for generating test case, device and electronic equipment on a kind of line |
| CN111427760A (en) * | 2019-01-09 | 2020-07-17 | 阿里巴巴集团控股有限公司 | Page testing method, device, equipment and storage medium |
| CN111209184A (en) * | 2019-12-20 | 2020-05-29 | 北京你财富计算机科技有限公司 | Automatic testing method and device and electronic equipment |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023093702A1 (en) * | 2021-11-25 | 2023-06-01 | 华为技术有限公司 | Network measurement method and related apparatus |
| CN114448852A (en) * | 2021-12-30 | 2022-05-06 | 中国电信股份有限公司 | Gateway terminal testing method, device and storage medium |
| CN114740829A (en) * | 2022-05-07 | 2022-07-12 | 镁佳(北京)科技有限公司 | Domain controller test system |
| CN116107913A (en) * | 2023-04-06 | 2023-05-12 | 阿里云计算有限公司 | Test control method, device and system of single-node server |
| CN116107913B (en) * | 2023-04-06 | 2023-11-14 | 阿里云计算有限公司 | Test control method, device and system of single-node server |
| CN116506340A (en) * | 2023-06-27 | 2023-07-28 | 云账户技术(天津)有限公司 | Flow link testing method and device, electronic equipment and storage medium |
| CN116795723A (en) * | 2023-08-21 | 2023-09-22 | 建信金融科技有限责任公司 | Chain unit test processing method and device and computer equipment |
| CN116795723B (en) * | 2023-08-21 | 2023-11-21 | 建信金融科技有限责任公司 | Chain unit test processing method and device and computer equipment |
| CN117472783A (en) * | 2023-12-14 | 2024-01-30 | 中电金信数字科技集团有限公司 | Test integrated platform |
| CN117472783B (en) * | 2023-12-14 | 2024-06-11 | 中电金信数字科技集团有限公司 | Test integrated platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113485880A (en) | Test method and device | |
| US10162740B1 (en) | Automated intelligent execution of computer software test cases | |
| CN109636309B (en) | Task processing method and device, electronic equipment and storage medium | |
| CN110321273B (en) | Service statistics method and device | |
| CN107436844B (en) | Method and device for generating interface use case aggregate | |
| CN110008109B (en) | Application testing method and device | |
| CN109977012B (en) | Joint debugging test method, device, equipment and computer readable storage medium of system | |
| CN108241582A (en) | A kind of software automated testing platform based on RabbitMQ message-oriented middlewares | |
| CN111212142A (en) | Service processing method, integrated open docking platform and computer storage medium | |
| CN108694120B (en) | Method and device for testing service component | |
| US12032477B2 (en) | Method and apparatus for generating and applying deep learning model based on deep learning framework | |
| CN115391219A (en) | Test case generation method and device, electronic equipment and storage medium | |
| CN113704112B (en) | Data processing method and system | |
| CN110888800A (en) | Service interaction function test method, device, storage medium and test system | |
| CN116107913B (en) | Test control method, device and system of single-node server | |
| CN112423024A (en) | Video transcoding method and device, computer equipment and storage medium | |
| CN112905457B (en) | Software testing method and device | |
| CN113806624B (en) | Data processing method and device | |
| CN113268360A (en) | Request processing method, device, server and storage medium | |
| CN114371866A (en) | Version reconfiguration test method, device and equipment of service system | |
| US11928052B2 (en) | Automated testing of mobile computing devices | |
| CN118170692B (en) | Code testing method | |
| CN110659214B (en) | Information processing system, method, computing device, and storage medium | |
| CN115878079B (en) | Demand management method, device, electronic equipment and storage medium | |
| CN118394641A (en) | Code coverage rate testing method, device and system |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20211008 |