CN111831530A - Test method and device - Google Patents
Test method and device Download PDFInfo
- Publication number
- CN111831530A CN111831530A CN201910298264.2A CN201910298264A CN111831530A CN 111831530 A CN111831530 A CN 111831530A CN 201910298264 A CN201910298264 A CN 201910298264A CN 111831530 A CN111831530 A CN 111831530A
- Authority
- CN
- China
- Prior art keywords
- tested
- test request
- test
- terminal
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the disclosure discloses a test method and a test device. The specific implementation mode of the method comprises the following steps: receiving a first test request sent by a terminal according to a domain name; selecting a system to be tested from at least one system to be tested associated with the domain name; sending the selected system identification of the system to be tested to the terminal, wherein the terminal generates a second test request based on the first test request, and the second test request comprises the system identification received by the terminal; and testing the selected system to be tested based on the first test request and the second test request. This embodiment provides a new way of testing.
Description
Technical Field
The embodiment of the disclosure relates to the technical field of computers, in particular to a testing method and a testing device.
Background
With the development of computer technology, various functions implemented by computer technology are in endless. Individual functions may be packaged as functional components and one or more functional components may be packaged as a test system. After an engineer develops a test system, the performance of the test system needs to be tested.
Disclosure of Invention
The embodiment of the disclosure provides a test method and a test device.
In a first aspect, an embodiment of the present disclosure provides a testing method, including: receiving a first test request sent by a terminal according to a domain name; selecting a system to be tested from at least one system to be tested associated with the domain name; sending the selected system identification of the system to be tested to the terminal, wherein the terminal generates a second test request based on the first test request, and the second test request comprises the system identification received by the terminal; and testing the selected system to be tested based on the first test request and the second test request.
In some embodiments, the testing the selected system to be tested based on the first test request and the second test request includes: receiving at least one second test request including a system identification; analyzing the received second test request to obtain a system identifier in the second test request; and for a second test request in the at least one second test request, sending the second test request to a system to be tested indicated by the system identifier obtained from the second test request.
In some embodiments, the selecting a system to be tested from at least one system to be tested associated with the domain name includes: acquiring test indication information, wherein the test indication information is used for indicating a system to be tested; and selecting the system to be tested indicated by the test indication information from the at least one system to be tested.
In some embodiments, the sending the selected system identifier of the system to be tested to the terminal includes: taking the selected system identification of the system to be tested as a label, and establishing an association relation with the first test request; and sending the first test request of the associated label to the terminal.
In some embodiments, the first test request is sent through a browser of the terminal, and the terminal stores a received system identifier in a browser cache of the browser in response to receiving the system identifier.
In a second aspect, embodiments of the present disclosure provide a test apparatus, the apparatus comprising: the receiving unit is configured to receive a first test request sent by a terminal according to a domain name; the selecting unit is configured to select a system to be tested from at least one system to be tested associated with the domain name; a sending unit configured to send the selected system identifier of the system to be tested to the terminal, where the terminal generates a second test request based on the first test request, and the second test request includes the system identifier received by the terminal; and the test unit is configured to test the selected system to be tested based on the first test request and the second test request.
In some embodiments, the test unit is further configured to: receiving at least one second test request including a system identification; analyzing the received second test request to obtain a system identifier in the second test request; and for a second test request in the at least one second test request, sending the second test request to a system to be tested indicated by the system identifier obtained from the second test request.
In some embodiments, the selecting unit is further configured to: acquiring test indication information, wherein the test indication information is used for indicating a system to be tested; and selecting the system to be tested indicated by the test indication information from the at least one system to be tested.
In some embodiments, the sending unit is further configured to: taking the selected system identification of the system to be tested as a label, and establishing an association relation with the first test request; and sending the first test request of the associated label to the terminal.
In some embodiments, the first test request is sent through a browser of the terminal, and the terminal stores a received system identifier in a browser cache of the browser in response to receiving the system identifier.
In a third aspect, an embodiment of the present disclosure provides an electronic device, including: one or more processors; a storage device, on which one or more programs are stored, which, when executed by the one or more processors, cause the one or more processors to implement the method as described in any implementation manner of the first aspect.
In a fourth aspect, an embodiment of the present disclosure provides a computer-readable medium on which a computer program is stored, wherein the computer program, when executed by a processor, implements the method as described in any implementation manner of the first aspect.
According to the testing method and the testing device provided by the embodiment of the disclosure, a first testing request sent by a receiving terminal according to a domain name is received; then, selecting a system to be tested from at least one system to be tested associated with the domain name; then, sending the selected system identifier of the system to be tested to the terminal, wherein the terminal generates a second test request based on the first test request, and the second test request comprises the system identifier received by the terminal; finally, based on the first test request and the second test request, testing the selected system to be tested, wherein the technical effects at least include: a new test mode is provided.
Drawings
Other features, objects and advantages of the disclosure will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is an exemplary system architecture diagram in which some embodiments of the present disclosure may be applied;
FIG. 2 is a flow diagram of one embodiment of a testing method according to the present disclosure;
FIG. 3 is a schematic diagram of one application scenario of a testing method according to the present disclosure;
FIG. 4 is a flow diagram of yet another embodiment of a testing method according to the present disclosure;
FIG. 5 is a schematic structural diagram of one embodiment of a testing device according to the present disclosure;
FIG. 6 is a schematic block diagram of a computer system suitable for use with an electronic device implementing embodiments of the present disclosure.
Detailed Description
The present disclosure is described in further detail below with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that, in the present disclosure, the embodiments and features of the embodiments may be combined with each other without conflict. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of the testing method or testing apparatus of the present disclosure may be applied.
As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 may be a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. Various communication client applications, such as a test application, a call application, a live application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like, may be installed on the terminal devices 101, 102, and 103.
The terminal apparatuses 101, 102, and 103 may be hardware or software. When the terminal devices 101, 102, and 103 are hardware, they may be various electronic devices with communication functions, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, mpeg Audio Layer 3), MP4 players (Moving Picture Experts Group Audio Layer IV, mpeg Audio Layer 4), laptop portable computers, desktop computers, and the like. When the terminal apparatuses 101, 102, 103 are software, they can be installed in the electronic apparatuses listed above. It may be implemented as multiple pieces of software or software modules (e.g., to provide distributed services) or as a single piece of software or software module. And is not particularly limited herein.
The server 105 may be a server providing various services, such as a background server supporting test-class applications on the terminal devices 101, 102, 103. The terminal devices 101, 102, 103 may send some parameters of the test (e.g. a request for a test, etc.) to the server 105. The server 105 may test the system to be tested based on the received parameters, and optionally, may return the test result to the terminal devices 101, 102, and 103.
It should be noted that the testing method provided by the embodiment of the present disclosure is generally executed by the server 105, and accordingly, the testing apparatus is generally disposed in the server 105.
The server may be hardware or software. When the server is hardware, it may be implemented as a distributed server cluster formed by multiple servers, or may be implemented as a single server. When the server is software, it may be implemented as multiple pieces of software or software modules (e.g., to provide distributed services), or as a single piece of software or software module. And is not particularly limited herein.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring to FIG. 2, a flow 200 of one embodiment of a testing method is shown. The embodiment is mainly exemplified by applying the method to an electronic device with certain computing capability, and the electronic device may be the server shown in fig. 1. The test method comprises the following steps:
In this embodiment, an execution subject of the testing method (for example, the server shown in fig. 1) may receive a first testing request sent by the terminal according to the domain name.
Generally, the terminal may send, according to the first test request sent by the domain name, the first test request to a server on which the website indicated by the domain name operates from the domain name resolution server.
In this embodiment, the first test request may be a request of a system to be tested for testing. Alternatively, the type of test request may be varied. By way of example, a test request may be used to request a page, may be used to request a video to be played, and so on.
In this embodiment, the execution subject may select a system to be tested from at least one system to be tested associated with the domain name.
Here, simulating one or more functions of a website may establish a system under test. As an example, a functional component for realizing a given function may be taken as a component to be tested; combining one or more components to be tested may generate a system to be tested. The system to be tested also needs to hang the test request which can be received under the domain name. The system to be tested can be evaluated through the processing process and/or the processing result of the system to be tested on the test request.
In this embodiment, the execution subject may pre-establish an association relationship between the domain name and a system to be tested.
It should be noted that, in the prior art, there is usually only one test system associated with a domain name, that is, only one system to be tested can be hung under the domain name at a time. If a plurality of systems to be tested need to be tested, a new system to be tested can be hung for testing only after the last system to be tested is tested and removed.
In this embodiment, the system to be tested may be selected from the at least one system to be tested associated with the domain name in various manners.
In the present disclosure, there may be a plurality of systems to be tested with which the domain name is associated. Optionally, the system to be tested may be selected from the at least one system to be tested in a random or polling manner.
And 203, sending the selected system identifier of the system to be tested to the terminal.
In this embodiment, the execution subject may send the selected system identifier of the system to be tested to the terminal.
Here, the terminal may generate a second test request based on the first test request. The second test request may include a system identifier received by the terminal. It will be appreciated that the second test request has more system identification than the first test request.
It is to be appreciated that the second test request may be based on the first test request. As an example, the end user may request to enter a home page of a certain website, based on which a first test request may be generated, i.e. based on the first test request, a website home page may be returned. The end user may click on a title of the home page of the website, request entry into the detail page indicated by the title, and may generate a second test request based thereon, i.e., the detail page may be returned based on the second test request.
In practice, the test request sent by the terminal may have an association or a series, for example, all controls in a certain page are clicked to test whether each control is valid. A series of test requests need to be sent to the same system under test for processing.
As an example, the at least one system to be tested having an association relationship with the domain name may be a plurality of systems to be tested, and each system to be tested may implement the same function in a different manner. If the plurality of systems to be tested are required to be tested simultaneously, the systems to be tested can be appointed for the received first testing request in a random mode. When the number of the first testing requests is multiple, each first testing request can be randomly sent to each system to be tested. Therefore, the system to be tested can be tested simultaneously.
And step 204, testing the selected system to be tested based on the first test request and the second test request.
In this embodiment, the execution body may test the selected system to be tested based on the first test request and the second test request.
It should be noted that the types of functions implemented by the system to be tested may be varied according to different application scenarios. Thus, the test mode for the system to be tested may be various.
It should be noted that, the present disclosure sends the system identifier of the system to be tested back to the terminal, so that a plurality of systems to be tested can be distinguished, and the first test request and the second test request based on the first test request, i.e. the series of test requests, can be both sent to the system to be tested that is expected to be tested. The system to be tested can be evaluated through the processing process and/or the processing result of the system to be tested on the test request. Therefore, the multiple systems to be tested can be hung under one domain name, and the multiple systems to be tested can be tested at the same time.
Continuing to refer to fig. 3, fig. 3 is a schematic diagram of an application scenario of the testing method according to the embodiment shown in fig. 2. In the application scenario of fig. 3:
first, the terminal device 301 may send a first test request to the server 302 indicated by the domain name according to the domain name. It is to be appreciated that a domain name can be indicated to a server by associating the domain name with an internet protocol address of the server 302. Here, the server 302 may store the association relationship between the domain name and the system to be tested in advance. For example, the system to be tested having an association relationship with the domain name may include: a system to be tested A, a system to be tested B and a system to be tested C.
Then, the server 302 may select a system to be tested from at least one system to be tested associated with the domain name. For example, system B to be tested is picked.
The server 302 may then send the selected system identification of the system to be tested, e.g. "system B", to the terminal 301.
Then, the terminal 301 may package the selected system identifier of the system to be tested, for example, "system B", into the second test request when the second test request is generated based on the first test request. The terminal 301 may send a second test request to the server 302.
Finally, the server 302 may test the selected system to be tested (e.g., system B to be tested) based on the first test request and the second test request.
In the method provided by the above embodiment of the present disclosure, a first test request sent by a receiving terminal according to a domain name is received; then, selecting a system to be tested from at least one system to be tested associated with the domain name; then, sending the selected system identifier of the system to be tested to the terminal, wherein the terminal generates a second test request based on the first test request, and the second test request comprises the system identifier received by the terminal; finally, based on the first test request and the second test request, testing the selected system to be tested, wherein the technical effects at least include: a new test mode is provided.
In some embodiments, step 202 may be implemented as follows: acquiring test indication information, wherein the test indication information can be used for indicating a system to be tested; and then selecting the system to be tested indicated by the test indication information from at least one system to be tested associated with the domain name.
Here, the test instruction information may be transmitted to the execution main body by an operator through an electronic device. Through the test indication information, the system to be tested can be selected in a targeted manner, and then the system to be tested is tested in a targeted manner.
In some embodiments, step 203 may be implemented as follows: taking the selected system identification of the system to be tested as a label, and establishing an association relation with the first test request; the first test request associated with the tag is transmitted to the terminal (terminal that transmitted the first test request).
Here, the first test request is labeled and returned to the terminal, so that: firstly, sending a system identifier to a terminal for storage; secondly, the terminal may send the first test request to the execution main body again, and the execution main body may send the first test request to the corresponding system to be tested when receiving the first test request with the tag for the second time (which may also be considered as a second test request with unchanged request content).
In some embodiments, the first test request may be sent via a browser of the terminal, and the terminal, in response to receiving the system identifier, stores the received system identifier in a browser cache (cookie) of the browser. It should be noted that the cookie may be generated by the server, bound to the domain name, and read by the browser. A cookie may be understood as a container into which the server may write data. When the browser sends the request, the browser sends the data band bound by the domain name corresponding to the request to the server indicated by the domain name together.
It should be noted that, when the terminal sends a request based on the browser, the storage system identifier can be implemented by using the characteristic that the browser has a cookie; the system identifier can also be packaged into the second test request by using the characteristic that the browser packages the data of the domain name binding. Therefore, the additional arrangement of a storage space for storing the system identifier can be avoided, and the additional arrangement of a program for packaging the system identifier to the second test request by the terminal can also be avoided; therefore, the storage space can be saved and links required by implementation can be reduced.
With further reference to fig. 4, a flow 400 of yet another embodiment of a testing method is shown. The process 400 of the test method includes the following steps:
In this embodiment, an execution subject of the testing method (for example, the server shown in fig. 1) may receive a first testing request sent by the terminal according to the domain name.
In this embodiment, the execution subject may select a system to be tested from at least one system to be tested associated with the domain name.
And step 403, sending the selected system identifier of the system to be tested to the terminal.
In this embodiment, the execution subject may send the selected system identifier of the system to be tested to the terminal.
Here, the terminal may generate a second test request based on the first test request. The second test request may include a system identifier received by the terminal.
It should be noted that, for details and technical effects of the implementation of step 401, step 402, and step 403, reference may be made to the records in step 201, step 202, and step 203, which are not described herein again.
At step 404, at least one second test request including a system identification is received.
In this embodiment, the execution body may receive at least one second test request including the system identifier from at least one terminal.
It will be appreciated that when a plurality of systems to be tested are tested simultaneously, the number of terminals to which the executing body is directed is plural. For the second testing requests sent by different terminals based on different first testing requests, it is necessary to distinguish to which system to be tested each second testing request should be sent.
In this embodiment, the execution body may analyze each received second testing request to obtain a system identifier in each second testing request.
In this embodiment, the execution main body may send, for a second test request of the at least one second test request, the second test request to a system to be tested indicated by a system identifier obtained from the second test request.
In some embodiments, the execution body may generate the test result of the device to be tested according to a processing result and/or a processing procedure of the system to be tested on the first test request and/or the second test request.
As an example, the execution body may generate a test result of the system to be tested according to a processing procedure of the system to be tested on the first test request and/or the second test request. As an example, if the system under test processes the derived request for too long, the test result indicates that the system under test is poor in performance.
As can be seen from fig. 4, compared to the corresponding embodiment of fig. 2, the flow 400 of the testing method in this embodiment highlights the steps of obtaining at least one second testing request and sending each second testing request to the corresponding system to be tested. Therefore, the technical effects of the solution described in this embodiment at least include:
first, a new test mode is provided.
Second, a more comprehensive testing method is provided.
Thirdly, the test system can be simultaneously oriented to a plurality of terminals and a plurality of systems to be tested for processing. The processing efficiency of the test system is improved.
With further reference to fig. 5, as an implementation of the method shown in the above figures, the present disclosure provides an embodiment of a testing apparatus, which corresponds to the embodiment of the method shown in fig. 2, and which can be applied in various electronic devices.
As shown in fig. 5, the test apparatus 500 of the present embodiment includes: a receiving unit 501, a selecting unit 502, a sending unit 503 and a testing unit 504. The receiving unit is configured to receive a first test request sent by a terminal according to a domain name; the selecting unit is configured to select a system to be tested from at least one system to be tested associated with the domain name; a sending unit configured to send the selected system identifier of the system to be tested to the terminal, where the terminal generates a second test request based on the first test request, and the second test request includes the system identifier received by the terminal; and the test unit is configured to test the selected system to be tested based on the first test request and the second test request.
In this embodiment, specific processes of the obtaining unit 501, the inserting unit 502, the establishing unit 503, and the testing unit 504 of the testing apparatus 500 and technical effects thereof may refer to related descriptions of step 201, step 202, step 203, and step 204 in the corresponding embodiment of fig. 2, which are not described herein again.
In some embodiments, the test unit is further configured to: receiving at least one second test request including a system identification; analyzing the received second test request to obtain a system identifier in the second test request; and for a second test request in the at least one second test request, sending the second test request to a system to be tested indicated by the system identifier obtained from the second test request.
In some embodiments, the selecting unit is further configured to: acquiring test indication information, wherein the test indication information is used for indicating a system to be tested; and selecting the system to be tested indicated by the test indication information from the at least one system to be tested.
In some embodiments, the sending unit is further configured to: taking the selected system identification of the system to be tested as a label, and establishing an association relation with the first test request; and sending the first test request of the associated label to the terminal.
In some embodiments, the first test request is sent through a browser of the terminal, and the terminal stores a received system identifier in a browser cache of the browser in response to receiving the system identifier.
It should be noted that, for details of implementation and technical effects of each unit in the testing apparatus provided in the embodiments of the present disclosure, reference may be made to descriptions of other embodiments in the present disclosure, and details are not described herein again.
Referring now to fig. 6, shown is a schematic diagram of an electronic device (e.g., a terminal or server of fig. 1) 600 suitable for use in implementing embodiments of the present disclosure. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 6, electronic device 600 may include a processing means (e.g., central processing unit, graphics processor, etc.) 601 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM603, various programs and data necessary for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 illustrates an electronic device 600 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 609, or may be installed from the storage means 608, or may be installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the methods of embodiments of the present disclosure.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: transmitting, to a processor of the at least two processors, a subset of training samples in the set of training samples, wherein the processor is configured to: receiving a first test request sent by a terminal according to a domain name; selecting a system to be tested from at least one system to be tested associated with the domain name; sending the selected system identification of the system to be tested to the terminal, wherein the terminal generates a second test request based on the first test request, and the second test request comprises the system identification received by the terminal; and testing the selected system to be tested based on the first test request and the second test request.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Here, the name of the unit does not in some cases constitute a limitation to the unit itself, and for example, the receiving unit may also be described as "a unit that receives the first test request sent by the terminal according to the domain name".
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Claims (12)
1. A method of testing, comprising:
receiving a first test request sent by a terminal according to a domain name;
selecting a system to be tested from at least one system to be tested associated with the domain name;
sending the selected system identification of the system to be tested to the terminal, wherein the terminal generates a second test request based on the first test request, and the second test request comprises the system identification received by the terminal;
and testing the selected system to be tested based on the first test request and the second test request.
2. The method of claim 1, wherein said testing the selected system under test based on the first test request and the second test request comprises:
receiving at least one second test request including a system identification;
analyzing the received second test request to obtain a system identifier in the second test request;
and for a second test request in the at least one second test request, sending the second test request to the system to be tested indicated by the system identifier obtained from the second test request.
3. The method of claim 1, wherein said selecting a system to be tested from at least one system to be tested associated with said domain name comprises:
acquiring test indication information, wherein the test indication information is used for indicating a system to be tested;
and selecting the system to be tested indicated by the test indication information from the at least one system to be tested.
4. The method of claim 1, wherein the sending the selected system identifier of the system to be tested to the terminal comprises:
taking the selected system identification of the system to be tested as a label, and establishing an association relation with the first test request;
and sending the first test request of the associated label to the terminal.
5. The method of claim 1, wherein the first test request is sent by a browser of the terminal, and the terminal, in response to receiving a system identification, stores the received system identification in a browser cache of the browser.
6. A test apparatus, comprising:
the receiving unit is configured to receive a first test request sent by a terminal according to a domain name;
the selecting unit is configured to select a system to be tested from at least one system to be tested associated with the domain name;
a sending unit configured to send the selected system identifier of the system to be tested to the terminal, wherein the terminal generates a second testing request based on the first testing request, and the second testing request includes the system identifier received by the terminal;
a test unit configured to test the selected system to be tested based on the first test request and the second test request.
7. The apparatus of claim 6, wherein the test unit is further configured to:
receiving at least one second test request including a system identification;
analyzing the received second test request to obtain a system identifier in the second test request;
and for a second test request in the at least one second test request, sending the second test request to the system to be tested indicated by the system identifier obtained from the second test request.
8. The apparatus of claim 6, wherein the selecting unit is further configured to:
acquiring test indication information, wherein the test indication information is used for indicating a system to be tested;
and selecting the system to be tested indicated by the test indication information from the at least one system to be tested.
9. The apparatus of claim 6, wherein the transmitting unit is further configured to:
taking the selected system identification of the system to be tested as a label, and establishing an association relation with the first test request;
and sending the first test request of the associated label to the terminal.
10. The apparatus of claim 6, wherein the first test request is sent by a browser of the terminal, and the terminal, in response to receiving a system identification, stores the received system identification in a browser cache of the browser.
11. An electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-5.
12. A computer-readable medium, on which a computer program is stored, wherein the program, when executed by a processor, implements the method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910298264.2A CN111831530A (en) | 2019-04-15 | 2019-04-15 | Test method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910298264.2A CN111831530A (en) | 2019-04-15 | 2019-04-15 | Test method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111831530A true CN111831530A (en) | 2020-10-27 |
Family
ID=72915389
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910298264.2A Pending CN111831530A (en) | 2019-04-15 | 2019-04-15 | Test method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111831530A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112395204A (en) * | 2020-12-04 | 2021-02-23 | 京东数科海益信息科技有限公司 | Method, apparatus, system, electronic device, and medium for obtaining test coverage |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100030862A1 (en) * | 2008-07-31 | 2010-02-04 | International Business Machines Corporation | Testing a network system |
| CN103095783A (en) * | 2011-11-08 | 2013-05-08 | 阿里巴巴集团控股有限公司 | Method and device for web application debugging |
| CN104580540A (en) * | 2013-10-09 | 2015-04-29 | 腾讯科技（深圳）有限公司 | Method and device for achieving website access |
| CN105763662A (en) * | 2014-12-17 | 2016-07-13 | 中国移动通信集团黑龙江有限公司 | Method for creating similar network test environments, device and DNS server |
| US20170180238A1 (en) * | 2015-12-16 | 2017-06-22 | Software Ag | Systems and/or methods for automated testing and monitoring of backend services |
| CN107154976A (en) * | 2017-05-10 | 2017-09-12 | 北京微影时代科技有限公司 | Website testing method, device and system |
| CN107360269A (en) * | 2017-07-21 | 2017-11-17 | 中国移动通信集团江苏有限公司 | Domain name analysis system optimization method, device, equipment and storage medium |
| CN107508720A (en) * | 2017-07-25 | 2017-12-22 | 中国银联股份有限公司 | A kind of automated testing method and device |
| CN107959579A (en) * | 2016-10-14 | 2018-04-24 | 北京京东尚科信息技术有限公司 | The dispositions method and deployment system of multisystem |
| CN109344052A (en) * | 2018-08-30 | 2019-02-15 | 北京金山安全软件有限公司 | Automatic interface testing method and device and electronic equipment |
-
2019
- 2019-04-15 CN CN201910298264.2A patent/CN111831530A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100030862A1 (en) * | 2008-07-31 | 2010-02-04 | International Business Machines Corporation | Testing a network system |
| CN103095783A (en) * | 2011-11-08 | 2013-05-08 | 阿里巴巴集团控股有限公司 | Method and device for web application debugging |
| CN104580540A (en) * | 2013-10-09 | 2015-04-29 | 腾讯科技（深圳）有限公司 | Method and device for achieving website access |
| CN105763662A (en) * | 2014-12-17 | 2016-07-13 | 中国移动通信集团黑龙江有限公司 | Method for creating similar network test environments, device and DNS server |
| US20170180238A1 (en) * | 2015-12-16 | 2017-06-22 | Software Ag | Systems and/or methods for automated testing and monitoring of backend services |
| CN107959579A (en) * | 2016-10-14 | 2018-04-24 | 北京京东尚科信息技术有限公司 | The dispositions method and deployment system of multisystem |
| CN107154976A (en) * | 2017-05-10 | 2017-09-12 | 北京微影时代科技有限公司 | Website testing method, device and system |
| CN107360269A (en) * | 2017-07-21 | 2017-11-17 | 中国移动通信集团江苏有限公司 | Domain name analysis system optimization method, device, equipment and storage medium |
| CN107508720A (en) * | 2017-07-25 | 2017-12-22 | 中国银联股份有限公司 | A kind of automated testing method and device |
| CN109344052A (en) * | 2018-08-30 | 2019-02-15 | 北京金山安全软件有限公司 | Automatic interface testing method and device and electronic equipment |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112395204A (en) * | 2020-12-04 | 2021-02-23 | 京东数科海益信息科技有限公司 | Method, apparatus, system, electronic device, and medium for obtaining test coverage |
| CN112395204B (en) * | 2020-12-04 | 2024-04-16 | 京东科技信息技术有限公司 | Method, system, related device and medium for obtaining test coverage rate |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110708346B (en) | Information processing system and method | |
| CN107390994B (en) | Interface presentation method and device | |
| CN110377440B (en) | Information processing method and device | |
| CN109862100B (en) | Method and device for pushing information | |
| US20220043898A1 (en) | Methods and apparatuses for acquiring information | |
| CN110007936B (en) | Data processing method and device | |
| CN110232091B (en) | Method, system and apparatus for synchronizing data | |
| CN108933695B (en) | Method and apparatus for processing information | |
| CN110619100B (en) | Method and apparatus for acquiring data | |
| CN111694757B (en) | Application program testing method and device, electronic equipment and computer readable storage medium | |
| CN111913738A (en) | Access request processing method, device, computing equipment and medium | |
| CN110619096B (en) | Method and apparatus for synchronizing data | |
| CN108549586B (en) | Information processing method and device | |
| CN111782988A (en) | Method, device, computer system and storage medium for determining source of application program | |
| CN114840379A (en) | Log generation method, device, server and storage medium | |
| CN111813685B (en) | Automatic test method and device | |
| CN109218041B (en) | Request processing method and device for server system | |
| CN111831530A (en) | Test method and device | |
| CN109144864B (en) | Method and device for testing window | |
| CN111324470A (en) | Method and device for generating information | |
| CN109614137B (en) | Software version control method, device, equipment and medium | |
| CN111831531B (en) | Test method and device | |
| CN109766246B (en) | Method and apparatus for monitoring applications | |
| CN112306858A (en) | Test method and device and electronic equipment | |
| CN110716699A (en) | Method and apparatus for writing data |
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 |