CN117251358A - Method, device, equipment and storage medium for testing application interface - Google Patents
Method, device, equipment and storage medium for testing application interface Download PDFInfo
- Publication number
- CN117251358A CN117251358A CN202310888263.XA CN202310888263A CN117251358A CN 117251358 A CN117251358 A CN 117251358A CN 202310888263 A CN202310888263 A CN 202310888263A CN 117251358 A CN117251358 A CN 117251358A
- Authority
- CN
- China
- Prior art keywords
- interface
- response data
- key value
- value
- network request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000012360 testing method Methods 0.000 title claims description 84
- 230000004044 response Effects 0.000 claims abstract description 68
- 238000004590 computer program Methods 0.000 claims description 4
- 238000010998 test method Methods 0.000 abstract description 13
- 230000008569 process Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 208000024780 Urticaria Diseases 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Human Computer Interaction (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a test method, a device, equipment and a storage medium of an application interface, after a network request of an application to be tested is acquired, interface response data needing hijacking is judged through a use case in the network request, key values needing redefining are obtained after the interface response data needing hijacking is hijacked and analyzed, specific values corresponding to the key values needing redefining are generated according to a preset generation method, and finally the specific values are fed back to the application interface.
Description
Technical Field
The application belongs to the technical field of automatic testing, and particularly relates to a testing method, device, equipment and storage medium of an application interface.
Background
For application interfaces, also called User Interfaces (UI), there are two main types of testing methods for application interfaces in the prior art.
The first method is to test the application interface by configuring test data in the background, which requires writing a large amount of code, and for different test scenarios: different codes are required to be written in the background every time; each time the data in the same place in the same scene is replaced, the configuration is needed to be carried out in the background again, namely, each time the corresponding code is needed to be modified. The method for configuring the test data through the background is complex in process, long time is needed for completing the test of the application interface each time, and the test efficiency is low.
The second method is to hijack the interface through the packet grabbing tool, modify the response data of the interface, and test the application interface through whether the display of the application interface is normal or not. Compared with the first method in the prior art, the application testing method has the advantages that the background configuration data is not needed for each test, a certain time is saved, but the manual modification of response data at the interface is needed for each test, a certain time is consumed in the process, and the testing efficiency of the application interface testing method is still low.
Disclosure of Invention
In view of the above, the present application provides a method, apparatus, device and storage medium for testing an application interface, so as to solve the problem of low testing efficiency of the existing method for testing an application interface.
In order to solve the above problems, the present application provides the following solutions:
a method for testing an application interface, comprising:
acquiring a network request of a tested application;
judging whether the interface response data corresponding to the network request needs to be hijacked according to the use case in the network request, if so, then:
hijacking the interface response data;
analyzing the interface response data and determining key values needing redefinition;
generating a specific value corresponding to the key value to be redefined according to a preset generation method;
and feeding back the specific value to the application interface.
Optionally, the determining whether to hijack the response data corresponding to the network request according to the use case in the network request includes:
judging whether an interface corresponding to a use case in the network request is in a white list of a host filter or not;
and taking an interface corresponding to the use case in the white list of the host filter as a hijacking interface, wherein interface response data corresponding to the hijacking interface is data needing hijacking.
Optionally, the hijacking the interface response data includes:
and hijacking interface response data returned by the data server, wherein the interface response data is real interface response data corresponding to the network request.
Optionally, the parsing the interface response data and determining the key value to be redefined includes:
and determining the key value needing redefinition and the type of the key value needing redefinition from the interface response data through a key value filter.
Optionally, generating the specific value corresponding to the key value to be redefined according to a preset generating method includes:
and generating a specific value corresponding to the key value to be redefined through the regular expression.
Optionally, the specific value corresponding to the key value to be redefined according to the preset generating method includes:
and sending a key value generation request corresponding to the key value to be redefined to a key value generator so that the key value generator generates the specific value corresponding to the key value to be redefined, wherein the specific value is one of a random value, a special value and a file value.
Optionally, the generating, according to a preset generating method, the specific value corresponding to the key value to be redefined includes:
inquiring the corresponding relation between the preset key value type and the database, determining the database corresponding to the key value type needing redefinition, and taking any data in the database as a specific value.
An application interface testing apparatus, comprising:
the device comprises an acquisition unit, a judgment unit, a hijacking unit, an analysis unit, a generation unit and a feedback unit;
the acquisition unit is used for acquiring a network request of the tested application;
the judging unit is used for judging whether the interface response data corresponding to the network request needs to be hijacked according to the use case in the network request;
the hijacking unit is used for hijacking the interface response data when judging that the interface response data corresponding to the network request needs to be hijacked;
the analyzing unit is used for analyzing the interface response data and determining key values needing redefinition;
the generating unit is used for generating a specific value corresponding to the key value to be redefined according to a preset generating method;
and the feedback unit is used for feeding back the specific value to the application interface.
An application interface test device includes a memory and a processor;
the memory is used for storing instructions;
the processor is configured to execute the instructions stored in the memory to implement the method for testing an application interface described in any one of the above.
A storage medium having stored thereon a computer program which, when executed by a processor, enables a method of testing an application interface as claimed in any one of the preceding claims.
According to the scheme, after the network request of the application to be tested is acquired, the interface response data needing hijacking is judged through the use case in the network request, the key value needing redefining is obtained after the interface response data needing hijacking is hijacked and analyzed, the specific value corresponding to the key value needing redefining is generated according to the preset generation method, and finally the specific value is fed back to the application interface.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings may be obtained according to the provided drawings without inventive effort to a person skilled in the art.
FIG. 1 is a flowchart illustrating an exemplary prior art application interface testing method provided herein;
FIG. 2 is a flow chart of a testing method of an application interface provided in the present application;
FIG. 3 is a flowchart illustrating an exemplary method for testing an application interface provided herein;
FIG. 4 is an exemplary diagram of an application interface prior to testing provided herein;
FIG. 5 is an exemplary diagram of a tested application interface provided herein;
FIG. 6 is a block diagram of a testing device of the application interface provided by the present application;
fig. 7 is a block diagram of a hardware structure of a test method of an application interface provided in the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The term "including" and variations thereof as used herein are intended to be open-ended, i.e., including, but not limited to. The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. Related definitions of other terms will be given in the description below.
It should be noted that the terms "first," "second," and the like herein are merely used for distinguishing between different devices, modules, or units and not for limiting the order or interdependence of the functions performed by such devices, modules, or units.
It should be noted that references to "one" or "a plurality" in this application are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be interpreted as "one or more" unless the context clearly indicates otherwise.
In the prior art, two methods for testing an application interface are mainly used, one method is to test the application interface by configuring test data in the background, the test data needs to be configured in the background every time when one scene is replaced, and the test data in the same scene needs to be manually set in the background every time. For example, for places with numbers and characters on an application interface, test data is configured by writing codes in the background, and the test data is required to be configured in the background again after each scene is replaced; each time test data in the same scene is replaced, the number or the text which is specifically replaced needs to be manually set: two digits are converted into five digits, three words are converted into ten words, and so on. On the one hand, the procedure of modifying the code is cumbersome, and on the other hand, the configuration and modification of the code requires a certain degree of expertise, which results in limited use of the test method by the user. Because the background is configured with the test data each time for a certain time, the background can limit the value of the test data, for example, the number can only reach ten digits at most, the text can only reach one hundred words at most, and the like, so that the possibility that the application interface test is covered by the background limit is incomplete. The test method of the application interface needs a long time each time to finish the test of the application interface, and has low test efficiency.
The other test method of the application interface mainly includes that after the response data of the interface are hijacked by the packet grabbing tool, the response data are modified. The response data is manually modified once every time the interface test is applied, the test method for modifying the response by tool hijacking is very complicated, and the test efficiency is also very low. Referring to fig. 1, an exemplary flowchart of a prior art application interface testing method is provided in the present application. As shown in the figure, the TestDevices are test equipment, the charles/fiddler and Map local are packet capturing tools, after a tested application in the test equipment initiates a network request, the packet capturing tools carry out interface hijacking, redirect to local acquisition of analog data as response data, then the packet capturing tools hijack the response data, then carry out data modification on the equipment where the test equipment is located, then return the test data, and the test interface can be normally displayed through the application interface.
The problem of the test method of the application interface in the prior art is mainly low test efficiency, and the problem is that the applicable scene is very limited, namely the universality of the test method of the application interface is low.
In order to solve the above problems, the present application provides a testing method of an application interface, referring to fig. 2, a flow chart of the testing method of an application interface provided in the present application includes the following specific steps:
step 101, obtaining a network request of the tested application.
Alternatively, the Application to be tested may be an APP (Application program) or a device to be tested, and mainly tests whether each display area on the Application interface can normally display different contents of the same data type. The network request may be transmitted wirelessly or by wire.
The DNS (Domain Name Server ) server obtains network requests sent by the application under test or device under test.
Specifically, at the tested end, an APP is connected to a DNS server through a wireless network, clicks a button for performing an application interface test, and sends a network request for performing the application interface test. Or dragging the APP to be tested into a test port corresponding to the application interface test on the equipment connected with the DNS server. For example, the test of the application interface can be automatically performed once when the button is clicked once, and it can be understood that the refresh display of the data of the corresponding area on the application interface is performed once when the button is clicked once, so that the test of the application interface is completed once.
Step 102, judging whether to hijack interface response data corresponding to the network request according to the use case in the network request.
The DNS server is provided with a host filter, an interface in a white list of the host filter is used as a hijacking interface, and data transmitted through the hijacking interface is interface response data needing hijacking.
After the interface needing hijacking is obtained through the host filter, the hijacking of the interface data can be automatically carried out when the interface carries out data transmission.
Step 103, hijacking the interface response data.
And when the interface which is required to be hijacked is judged to have data transmission, acquiring interface response data, wherein the interface response data is real interface response data which is not tampered or replaced and is acquired from the data server by the network request.
Step 104, analyzing the interface response data and determining the key value to be redefined.
The response analyzer analyzes the obtained interface response data to determine the attribute of the value and what data type the corresponding value should correspond to, for example: the name field needs to automatically generate a name, and the age field needs to automatically generate a number. And then determining the key value needing redefinition and the type of the key value needing redefinition from the interface response data through a key value filter.
And 105, generating a specific value corresponding to the key value to be redefined according to a preset generation method.
Alternatively, a specific value corresponding to a key value that needs to be redefined may be generated by a regular expression.
Specifically, a key value generation request corresponding to a key value to be redefined is sent to a key value generator, the key value generator generates a corresponding specific value for the key value to be redefined, the characteristic value can be a value corresponding to the key value, and the specific value taking methods mainly comprise three kinds of random value taking methods, special value taking methods and file value taking methods. In either method, the corresponding relation between the preset key value type and the database can be queried, the database corresponding to the key value type needing redefinition is determined, and any data in the database is taken as a specific value.
Illustratively, the random value may be in random form, randomly generating a particular value; the file value can be a preset file in the reading system, and the file value is returned to the tested device through an interface; the special value can be selected from the corresponding database randomly, for example: special fields such as "& … …%" # ".
And 106, feeding back the specific value to the application interface.
Optionally, before returning to the specific value, the DNS server needs to assemble the acquired specific value and the key value and then return to the application interface, where the assembling process may be a json reconstruction process, analyzing the real interface response data acquired from the data server, that is, analyzing the real json string, and performing total replacement or targeted replacement on the fields in the real json string with the specific value, and then sending the assembled value to the tested device.
The application also provides an automatic screenshot function, and comparison of application interfaces before and after the test can be performed after the test is finished, and example implementation codes can be as follows:
the application interface test method also provides high data simulation, and ensures that the generated data accords with the actual scene, for example, names such as Zhang Sanand Liqu are automatically generated for a name field, and different numbers such as 21 are automatically generated for an age field. The test method of the application interface supports automatic test and manual test simultaneously, namely, the use case can be executed through automatic test, the screenshot verifies whether the display of the application interface is normal or not, and the manual test can also check whether the display of the application interface is normal or not in real time.
Optionally, referring to fig. 3, an exemplary flowchart of a testing method for an application interface is provided.
As shown in fig. 3, the TestDevices are connected with the dns server, the tested devices initiate a network request, redirect the network request to the dns server, and the dns server screens the website of the interface to be hijacked according to the use case in the network request, and determines whether the network request needs to be tampered. The dns server hives a real response returned from the real server according to the screened interface needing hijacking, then the dns server starts the response analysis service to analyze the real response, inputs the real response into a key filter, determines a key needing to be redefined according to use cases, then sends a key value generating request to a key value generator, generates a value corresponding to the key needing to be redefined by the key value generator, wherein the value can be obtained through methods of random value, special value, file value and the like, and finally returns the generated value to tested equipment to see that the corresponding application interface can be normally displayed, and the test of the application interface is completed.
Referring to fig. 4 and 5, fig. 4 is an exemplary diagram of an application interface before testing provided in the present application, and fig. 5 is an exemplary diagram of an application interface after testing provided in the present application.
As shown in fig. 4 and 5, the nickname of the user is replaced after the test, the original "2004 recall" is changed to a longer character form, and the changed result can be displayed normally. The text play record is automatically modified, and the play record is changed into the play record which is lengthened by a little and lengthened by a little, and the tested application interface can still be normally displayed. The content of the test is also the attention number, the fan number and the friend number of the user, and the tested places in the figure 5 are normally displayed, so that abnormal phenomena such as inoperable and application breakdown do not occur.
In summary, after the network request of the application to be tested is obtained, the interface response data to be hijacked is judged through the use case in the network request, the key value to be redefined is obtained after the interface response data to be hijacked is hijacked and analyzed, the specific value corresponding to the key value to be redefined is generated according to the preset generation method, and finally the specific value is fed back to the application interface.
For the method for testing the application interface, the application interface testing device is further provided, and the composition of the device is shown in fig. 6.
An acquisition unit 10, a judgment unit 20, a hijacking unit 30, an analysis unit 40, a generation unit 50 and a feedback unit 60;
the acquiring unit 10 is configured to acquire a network request of an application under test;
the judging unit 20 is configured to judge whether to hijack interface response data corresponding to the network request according to a use case in the network request;
the hijacking unit 30 is configured to hijack the interface response data when it is determined that the interface response data corresponding to the network request needs to be hijacked;
the parsing unit 40 is configured to parse the interface response data and determine a key value that needs to be redefined;
the generating unit 50 is configured to generate a specific value corresponding to the key value to be redefined according to a preset generating method;
the feedback unit 60 is configured to feedback the specific value to the application interface.
In one embodiment, the determining unit 20 is specifically configured to:
judging whether an interface corresponding to a use case in the network request is in a white list of a host filter or not;
and taking an interface corresponding to the use case in the white list of the host filter as a hijacking interface, wherein interface response data corresponding to the hijacking interface is data needing hijacking.
In one embodiment, the hijacking unit 30 is specifically configured to:
and hijacking interface response data returned by the data server, wherein the interface response data is real interface response data corresponding to the network request.
In one embodiment, the parsing unit 40 is specifically configured to:
and determining the key value needing redefinition and the type of the key value needing redefinition from the interface response data through a key value filter.
In one embodiment, the generating unit 50 is specifically configured to:
and generating a specific value corresponding to the key value to be redefined through the regular expression.
In one embodiment, the generating unit 50 is specifically configured to:
and sending a key value generation request corresponding to the key value to be redefined to a key value generator so that the key value generator generates the specific value corresponding to the key value to be redefined, wherein the specific value is one of a random value, a special value and a file value.
In one embodiment, the generating unit 50 is specifically configured to:
inquiring the corresponding relation between the preset key value type and the database, determining the database corresponding to the key value type needing redefinition, and taking any data in the database as a specific value.
Optionally, the present application further provides a testing device for an application interface, as shown in fig. 7, and the hardware structure block diagram of the application interface testing device provided by the present application mainly includes a processor 1 and a memory 3, and at least one processor 1, at least one communication interface 2, at least one memory 3 and at least one communication bus 4.
The memory 3 is used for storing instructions;
the processor 1 is configured to execute the instructions stored in the memory, so as to implement each process flow of the application interface test method.
In addition, the embodiment of the application also provides a storage medium, on which a computer program is stored, and when the computer program is executed by a processor, each processing flow of the application interface test method can be realized.
It should be noted that, in the present specification, each embodiment is described in a progressive manner, and each embodiment is mainly described as different from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.
For convenience of description, the above system or apparatus is described as being functionally divided into various modules or units, respectively. Of course, the functions of each element may be implemented in one or more software and/or hardware elements when implemented in the present application.
From the above description of embodiments, it will be apparent to those skilled in the art that the present application may be implemented in software plus a necessary general purpose hardware platform. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the methods described in the embodiments or some parts of the embodiments of the present application.
Finally, it is further noted that relational terms such as first, second, third, fourth, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing is merely a preferred embodiment of the present application and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present application and are intended to be comprehended within the scope of the present application.
Claims (10)
1. A method for testing an application interface, comprising:
acquiring a network request of a tested application;
judging whether the interface response data corresponding to the network request needs to be hijacked according to the use case in the network request, if so, then:
hijacking the interface response data;
analyzing the interface response data and determining key values needing redefinition;
generating a specific value corresponding to the key value to be redefined according to a preset generation method;
and feeding back the specific value to the application interface.
2. The method of claim 1, wherein the determining whether the response data corresponding to the network request needs to be hijacked according to the use case in the network request comprises:
judging whether an interface corresponding to a use case in the network request is in a white list of a host filter or not;
and taking an interface corresponding to the use case in the white list of the host filter as a hijacking interface, wherein interface response data corresponding to the hijacking interface is data needing hijacking.
3. The method of claim 1, wherein hijacking the interface response data comprises:
and hijacking interface response data returned by the data server, wherein the interface response data is real interface response data corresponding to the network request.
4. The method of claim 1, wherein parsing the interface response data and determining key values that require redefinition comprises:
and determining the key value needing redefinition and the type of the key value needing redefinition from the interface response data through a key value filter.
5. The method according to claim 1, wherein generating the specific value corresponding to the key value to be redefined according to a preset generation method includes:
and generating a specific value corresponding to the key value to be redefined through the regular expression.
6. The method according to claim 1, wherein the specific value corresponding to the key value to be redefined according to the preset generating method includes:
and sending a key value generation request corresponding to the key value to be redefined to a key value generator so that the key value generator generates the specific value corresponding to the key value to be redefined, wherein the specific value is one of a random value, a special value and a file value.
7. The method according to claim 4, wherein the generating the specific value corresponding to the key value to be redefined according to the preset generating method includes:
inquiring the corresponding relation between the preset key value type and the database, determining the database corresponding to the key value type needing redefinition, and taking any data in the database as a specific value.
8. An application interface testing apparatus, comprising:
the device comprises an acquisition unit, a judgment unit, a hijacking unit, an analysis unit, a generation unit and a feedback unit;
the acquisition unit is used for acquiring a network request of the tested application;
the judging unit is used for judging whether the interface response data corresponding to the network request needs to be hijacked according to the use case in the network request;
the hijacking unit is used for hijacking the interface response data when judging that the interface response data corresponding to the network request needs to be hijacked;
the analyzing unit is used for analyzing the interface response data and determining key values needing redefinition;
the generating unit is used for generating a specific value corresponding to the key value to be redefined according to a preset generating method;
and the feedback unit is used for feeding back the specific value to the application interface.
9. An application interface test device, comprising a memory and a processor;
the memory is used for storing instructions;
the processor is configured to execute instructions stored in the memory to implement the method for testing an application interface according to any one of claims 1-7.
10. A storage medium having stored thereon a computer program which, when executed by a processor, is capable of implementing the application interface testing method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310888263.XA CN117251358A (en) | 2023-07-19 | 2023-07-19 | Method, device, equipment and storage medium for testing application interface |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310888263.XA CN117251358A (en) | 2023-07-19 | 2023-07-19 | Method, device, equipment and storage medium for testing application interface |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117251358A true CN117251358A (en) | 2023-12-19 |
Family
ID=89127092
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310888263.XA Pending CN117251358A (en) | 2023-07-19 | 2023-07-19 | Method, device, equipment and storage medium for testing application interface |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117251358A (en) |
-
2023
- 2023-07-19 CN CN202310888263.XA patent/CN117251358A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110221982B (en) | Performance test method, device and equipment of business system and readable storage medium | |
| US20050120112A1 (en) | Intelligent knowledge management and content delivery system | |
| CN108628748B (en) | Automatic test management method and automatic test management system | |
| CN109669795B (en) | Crash information processing method and device | |
| CN107918575B (en) | Page state monitoring method and device | |
| CN110569159A (en) | Baffle generation method, device, equipment and computer storage medium | |
| CN111522728A (en) | Method for generating automatic test case, electronic device and readable storage medium | |
| CN111045879B (en) | Method, device and storage medium for generating pressure test report | |
| WO2021129335A1 (en) | Operation monitoring method and apparatus, operation analysis method and apparatus | |
| CN114595201A (en) | Method, equipment and storage medium for inquiring acquisition record of interface access log | |
| CN112882927A (en) | Interface automatic testing method, device, equipment and medium | |
| US7797590B2 (en) | Consensus testing of electronic system | |
| CN108650123B (en) | Fault information recording method, device, equipment and storage medium | |
| CN112965912B (en) | Interface test case generation method and device and electronic equipment | |
| CN110334019B (en) | Test method, test device and readable storage medium | |
| CN113672497B (en) | Method, device and equipment for generating non-buried point event and storage medium | |
| CN117251358A (en) | Method, device, equipment and storage medium for testing application interface | |
| CN105893462A (en) | User network behavior analysis method and device | |
| CN111026669A (en) | Test log management method, test log management device, and storage medium | |
| CN114268569B (en) | Configurable network operation and maintenance acceptance test method and device | |
| CN112506765A (en) | Software testing method, device, equipment and storage medium | |
| CN112256648A (en) | Method and device for collecting and tracking log behaviors based on Nginx | |
| CN111752847A (en) | Interface comparison method, micro server, computer readable storage medium and electronic device | |
| CN111275563A (en) | WeChat action-based generation method and system of interpersonal relationship and storage medium | |
| CN114301904A (en) | Monitoring method and device for big data cluster, monitoring system and readable storage medium |
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 |