CN107797918B - Test method and test device - Google Patents
Test method and test device Download PDFInfo
- Publication number
- CN107797918B CN107797918B CN201710147237.6A CN201710147237A CN107797918B CN 107797918 B CN107797918 B CN 107797918B CN 201710147237 A CN201710147237 A CN 201710147237A CN 107797918 B CN107797918 B CN 107797918B
- Authority
- CN
- China
- Prior art keywords
- test
- test case
- request
- result
- execution
- 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.)
- Active
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 477
- 238000010998 test method Methods 0.000 title claims abstract description 11
- 238000000034 method Methods 0.000 claims abstract description 23
- 230000006870 function Effects 0.000 description 27
- 238000012546 transfer Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 12
- 238000012545 processing Methods 0.000 description 7
- 238000011161 development Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000011990 functional testing Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
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 invention relates to a test method, comprising: the method comprises the steps of obtaining a test object selected by a test tool and an input test case identification, wherein the test object is generated according to the service type of a first system, the test tool and the first system run in the same end, sending a test case execution request to a second system according to the test object and the test case identification, receiving an execution result generated by the second system executing a test case corresponding to the test case identification according to the test case execution request, sending an execution result return request to the second system, and receiving a return result returned by the second system returning the execution result to the first system according to the execution result return request. By adopting the test method, the test efficiency of the joint test among the multiple systems can be improved. In addition, a test device is also provided.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a test method and a test apparatus.
Background
In order to improve the operation efficiency of the system, the system is generally kept functional, that is, the overall function of the system is unitary, and partial functions constituting the overall function need to be realized by other systems. If the insurance company business system has the overall function of providing various business information and generating business process lists, and the payment state generating function in the business process list generating function is the function that the intermediate system is responsible for processing relevant data and submitting the data to the payment system, so that the payment system searches the corresponding payment record according to the data submitted by the intermediate system and returns the payment record to the intermediate system, and the intermediate system returns the payment record to the insurance company business system. At this time, in order to test the overall function of the system, it is necessary to simultaneously test the functions of other systems associated therewith.
However, in the conventional joint test between multiple systems, testers of the multiple systems which are related to each other need to test the respective systems on a webpage respectively in the same time period, so that the labor cost is high, and the time is difficult to coordinate, so that the test efficiency is low.
Disclosure of Invention
In view of the above, it is necessary to provide a test method and a test apparatus for improving test efficiency.
A method of testing, the method comprising:
acquiring a test object selected by a test tool and an input test case identifier, wherein the test object is generated according to the service type of a first system, and the test tool and the first system run in the same end;
sending a test case execution request to a second system according to the test object and the test case identification;
receiving an execution result generated by the second system executing the test case corresponding to the test case identification according to the test case execution request;
sending an execution result return request to the second system;
and receiving a return result of the second system returning the execution result to the first system according to the execution result return request.
In one embodiment, before sending the test case execution request to the second system according to the test object and the test case identifier, the method further includes: sending a database name acquisition request to the second system according to the test object;
receiving a first database name which is acquired by the second system according to a database name acquisition request and is currently connected with the test object;
if the first database name is different from the database name required by the current test, receiving an input second database name, and sending a database updating request to the second system;
and receiving an updating result generated by the second system for updating the database currently connected with the test object into the second database according to the database updating request.
In one embodiment, before sending the test case execution request to the second system according to the test object and the test case identifier, the method further includes: sending a test data acquisition request to the second system according to the test object and the test case identifier; and receiving an acquisition result of the test data corresponding to the test case identification acquired by the second system according to the test data acquisition request.
In one embodiment, the method further comprises: if the acquisition result is that the test data acquisition fails, sending a test data secondary acquisition request to the second system; and receiving an acquisition result of the second system for acquiring the test data corresponding to the test case identifier from the first system according to the secondary acquisition request of the test data.
In one embodiment, if the execution result is successful and the return result is successful, sending a certificate making request to the second system; and receiving the execution time of the test case corresponding to the test case identification obtained by the second system according to the test case execution voucher making request, and making a proof making result by using the test data corresponding to the test case identification and the execution time of the test case corresponding to the test case identification according to a pre-stored receipt format.
A test apparatus, the apparatus comprising:
the test object receiving module is used for acquiring a test object selected by a test tool, the test object is generated according to the service type of a first system, and the test tool and the first system run in the same end;
the test case identification receiving module is used for receiving the test case identification input by the test tool;
the test case execution request sending module is used for sending a test case execution request to the second system according to the test object and the test case identification;
the test case execution result receiving module is used for receiving the execution result generated by the second system according to the test case execution request for executing the test case corresponding to the test case identifier;
the test case execution result return request sending module is used for sending an execution result return request to the second system;
and the test case execution result return result receiving module is used for receiving a return result of the second system returning the execution result to the first system according to the execution result return request.
In one embodiment, the apparatus further comprises: a database name acquisition request sending module, configured to send a database name acquisition request to the second system according to the test object; the first database name receiving module is used for receiving a first database name which is obtained by the second system according to the database name obtaining request and is currently connected with the test object; the second database name receiving module is used for receiving an input second database name if the first database name is different from the database name required by the current test; a database update request sending module, configured to send a database update request to the second system; and the database updating result acquisition module is used for receiving an updating result generated by the second system for updating the database currently connected with the test object into the second database according to the database updating request.
In one embodiment, the apparatus further comprises: a test data acquisition request sending module, configured to send a test data acquisition request to the second system according to the test object and the test case identifier; and the test data acquisition result receiving module is used for receiving the acquisition result of the test data corresponding to the test case identifier acquired by the second system according to the test data acquisition request.
In one embodiment, the apparatus further comprises: the test data secondary acquisition request sending module is used for sending a test data secondary acquisition request to the second system if the acquisition result is that the test data acquisition fails; the test data obtaining result receiving module is further configured to receive a result obtained by the second system according to the test data secondary obtaining request to obtain the test data corresponding to the test case identifier from the first system.
In one embodiment, the apparatus further comprises: the certificate making request sending module is used for sending a certificate making request to the second system if the execution result is that the execution is successful and the return result is that the return is successful; and the certification result receiving module is used for receiving the certification result which is obtained by the second system according to the test case execution voucher making request, acquiring the execution time of the test case corresponding to the test case identifier, and making the certification according to the test data corresponding to the test case identifier and the execution time of the test case corresponding to the test case identifier in a pre-stored receipt format.
According to the test method and the test device, the test object selected through the test tool and the input test case identification are obtained, the test object is generated according to the service type of the first system, the test tool and the first system run in the same end, the test case execution request is sent to the second system according to the test object and the test case identification, the execution result generated when the second system executes the test case corresponding to the test case identification according to the test case execution request is received, the execution result return request is sent to the second system, and the return result of the second system returning the execution result to the first system according to the execution result return request is received. Because the operation in the test tool completes the complete test of the function associated with the first system in the second system, and the test tool is at the same end as the first system, for the combined test of the first system and the second system, only the tester of the first system needs to test according to the test flow of the tester, when the function associated with the second system is tested, the test tool is used for completing the test of the function, the cost of the tester is reduced, the problem that the time of the tester for the combined test among multiple systems is difficult to coordinate is solved, and the test efficiency of the combined test among multiple systems is improved.
Drawings
FIG. 1 is a diagram of an application environment of an embodiment test method;
FIG. 2 is an internal block diagram of a terminal in one embodiment;
FIG. 3 is a flow diagram of a testing method in one embodiment;
FIG. 4 is a flow diagram of a method for testing whether a database connection of FIG. 3 is correct in one embodiment;
FIG. 5 is a flow diagram of a method for testing for the presence or absence of the test data of FIG. 3 in one embodiment;
FIG. 6 is a flow chart of a test method in another embodiment;
FIG. 7 is an interface diagram of a test tool in one embodiment;
FIG. 8 is a block diagram showing the structure of a test apparatus according to an embodiment;
FIG. 9 is a block diagram showing the structure of a test apparatus according to another embodiment;
FIG. 10 is a block diagram showing the structure of a test apparatus according to still another embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The testing method provided by the embodiment of the invention can be applied to the environment shown in FIG. 1. Referring to fig. 1, a terminal 102 where a first system and a testing tool are located may send a test case execution request to a server 104 where a second system is located, and may also receive a test case execution result returned by the server 104, where the first system is a service system, and the second system is an associated system associated with the first system, such as a transit system between the service system and a payment system; the test tool is used for testing the second system; the first system and the test tool are at the same terminal 102 so that a tester of the first system utilizes the test tool to perform a functional test associated with the second system. Specifically, the terminal 102 where the first system and the test tool are located communicates with the server 104 where the second system is located through a network, and the terminal 102 where the first system and the test tool are located obtains the test object and the test case identifier, sends a test case execution request to the server 104 where the second system is located, and receives a test execution result and the like returned by the server 104 where the second system is located. The terminal includes, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, portable wearable devices, and the like.
In one embodiment, as shown in fig. 2, there is further provided a terminal, where the terminal includes a processor, a non-volatile storage medium, an internal memory, a network connection port, a display screen, and an input device, which are connected through a system bus, and the non-volatile storage medium stores therein an operating system and computer-executable instructions for implementing a testing method provided in an embodiment of the present application and applied to the terminal. The processor is used for improving the calculation and control capacity and supporting the operation of the whole terminal. The internal memory is used to provide an environment for the operating system and the execution of computer-executable instructions in the non-volatile storage medium. The network interface is used for network communication with the server. The display screen of the terminal can be a liquid crystal display screen or an electronic ink display screen, and the input device can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on a shell of the mobile terminal, or an external keyboard, a touch pad or a mouse. It will be understood by those skilled in the art that the structure shown in fig. 2 is a block diagram of only a part of the structure relevant to the present application, and does not constitute a limitation of the terminal to which the present application is applied, and in particular, the terminal may include more or less components than those shown in the drawings, or combine some components, or have a different arrangement of components.
In one embodiment, as shown in fig. 3, there is provided a testing method, which is exemplified by being applied to the terminal shown in fig. 1, and comprises:
step 302, a test object selected by a test tool and an input test case identifier are obtained, the test object is generated according to the service type of the first system, and the test tool and the first system operate in the same end.
In this embodiment, the first system is a business system, such as an insurance business processing system of an insurance company; the test object is generated according to the service type of the first system, for example, the first system is a service system of an insurance company, and the service type of the service system has property insurance and personal insurance, then the test object is a program module of the property insurance and a program module of the personal insurance; the test case identifier is a unique identifier for distinguishing the test case, such as a service serial number.
And step 304, sending a test case execution request to the second system according to the test object and the test case identification.
In this embodiment, the second system is an associated system associated with the first system, for example, the first system is a service system, the second system is a transfer system between the service system and the payment system, and the sales information of the service product in the service system is submitted to the payment system through the transfer system, so that the payment system returns the payment completion condition of the service product; the test case is a set of test input, execution conditions and expected results corresponding to the test case identification and compiled to achieve correct execution or not of the function of the test object.
In order to complete testing of all functions of the first system, when testing the functions associated with the second system, the associated functions of the second system need to be tested, for example, in order to test whether the whole shopping process of the shopping website is executed correctly, when testing the completion condition of the shopping order, the payment system needs to be tested whether the payment of the shopping order is executed successfully, so a test case execution request is sent to the second system according to the test object and the test case identifier.
In other embodiments, there may be multiple second systems associated with the first system, for example, there may be different versions of the relay system due to the requirement of the project development, and at this time, the test tool interface may display multiple second systems, and determine the second system currently needing to be tested in conjunction with the first system according to the selection of the user. In this embodiment, when the plurality of different second systems are respectively connected with the first system, the user only needs to select a mode to quickly switch, and compared with a traditional switching mode through inputting a website, the testing efficiency is improved.
And step 306, receiving an execution result generated by the second system executing the test case corresponding to the test case identification according to the test case execution request.
And after the test case execution request is sent to the second system, receiving an execution result generated by the test case corresponding to the test case identification executed by the second system.
And after the test case is executed, the second system returns the execution result to the first system so that the first system completes the test of the associated function according to the execution result.
And 310, receiving a return result of the second system returning the execution result to the first system according to the execution result return request.
In this embodiment, after the second system successfully returns the execution result of the test case to the first system, a successful identifier is generated. If the success identification is received, the execution result is successfully returned; and if the success identification is not received, indicating that the execution result is failed to return.
In this embodiment, since the operation in the test tool completes the complete test of the function associated with the first system in the second system, and the test tool is at the same end as the first system, for the joint test of the first system and the second system, it is only necessary for the tester of the first system to perform the test according to the test flow of the tester, and when the function associated with the second system is tested, the test tool is used to complete the test of the function, so that the cost of the tester is reduced, the problem that the time of the tester for the joint test among multiple systems is difficult to coordinate is solved, and thus the test efficiency of the joint test among multiple systems is improved.
In one embodiment, as shown in fig. 4, before step 304, the method further includes:
In a more complex project development process, the same test object may correspond to multiple databases, and at this time, a tester needs to test the database to which the test object is currently connected according to the test requirement. Specifically, before testing whether the second system can successfully execute the test case, it is tested whether the database currently connected to the test object in the second system is the database where the test data corresponding to the test case identifier is located.
Step 404, receiving a first database name to which the second system currently connects and acquiring the test object according to the database name acquisition request.
In this embodiment, the first database is a database to which the test object in the second system is currently connected.
In step 406, if the first database name is different from the database name required by the current test, the input second database name is received.
In this embodiment, the second database is a database connected to the test data corresponding to the input test case identifier.
And after receiving a second database name input by the tester, sending a database updating request to the second system according to the second database name so that the second system changes the database currently connected with the test object into the database connected with the test data corresponding to the input test case identifier.
And the second system changes the database currently connected with the test object into a second database according to the database updating request, namely the database where the test data corresponding to the subsequently input test case identifier is located, and returns an updating result.
In this embodiment, before testing whether the second system can successfully execute the test case, it is tested whether the database currently connected to the test object in the second system is the database where the test data corresponding to the test case identifier is located, so that it is convenient to quickly find the reason when the subsequently received test case execution result is failure.
In one embodiment, as shown in fig. 5, before step 304, the method further includes:
step 502, according to the test object and the test case identifier, sending a test data acquisition request to the second system.
Before testing whether the second system can successfully execute the test case, whether test data corresponding to the test case identifier exists in the second system can be tested.
Step 504, receiving an obtaining result of the test data corresponding to the test case identifier obtained by the second system according to the test data obtaining request.
And the second system searches the test data corresponding to the test case identifier in the currently connected database according to the test case identifier, if the search result is empty, the second system does not have the test data corresponding to the test case identifier, otherwise, the second system has the test data corresponding to the test case identifier.
In this embodiment, before testing whether the second system can successfully execute the test case, whether the second system has test data corresponding to the test case identifier is tested, so that the reason can be conveniently and quickly found when the subsequently received test case execution result is failure.
In one embodiment, after step 504, the method further includes: if the acquisition result is that the test data acquisition fails, sending a test data secondary acquisition request to the second system; and receiving an acquisition result of the second system for acquiring the test data corresponding to the test case identifier from the first system according to the secondary acquisition request of the test data.
Because the second system is a transit system associated with the first system, and data in the second system originates from the first system, when the second system does not obtain test data corresponding to the test case identifier, the second system is required to obtain the test data from the first system.
In this embodiment, whether the second system has the test data corresponding to the test case identifier is further tested by sending the test data secondary acquisition request to the second system, so that the reason can be conveniently and quickly found when the subsequently received test case execution result is failure.
In one embodiment, after step 310, further comprising: if the execution result is successful and the return result is successful, sending a certificate making request to the second system;
and receiving the execution time of the test case corresponding to the test case identification obtained by the second system according to the test case execution voucher making request, and making the proof making result of the proof according to the test data corresponding to the test case identification and the execution time of the test case corresponding to the test case identification in a pre-stored receipt format. In this embodiment, after the second system successfully executes the test case and successfully returns the execution result to the first system, the second system displays the test data corresponding to the test case identifier, the test case execution time, and the like according to the pre-stored document format, that is, the certification making function is implemented, so that a tester needs to test the certification making function.
In one embodiment, as shown in fig. 6, another testing method is provided, comprising:
step 602, a second system and a test object which are selected by a test tool and are subjected to joint test with a first system are obtained, the test object is generated according to the service type of the first system, and the test tool and the first system operate in the same end.
In this embodiment, because the project requirements are constantly changed, there are multiple versions of the second system, and during testing, a tester needs to select the second system that needs to be tested in parallel with the first system currently from multiple test systems. The first is a multiple version of the second system, as shown in the interface diagram of the test tool in fig. 7.
In this embodiment, the same test object corresponds to multiple databases, and a tester first tests whether the database connected to the test object in the second system is correct.
In this embodiment, the second database is a database connected to the test data corresponding to the test case identifier input subsequently.
In this embodiment, the second system may update the database to which the test object is currently connected, and the tester needs to test the update function of the database.
In this embodiment, the test case identifier is a unique identifier for distinguishing the test case, such as a service serial number.
In this embodiment, after testing whether the database connected to the test object in the second system is correct or not, it is tested whether test data corresponding to the test case identifier exists in the second system or not.
And 614, acquiring an execution result generated by the test case corresponding to the test case identifier executed by the second system according to the test object and the test case identifier.
In this embodiment, after testing whether the database connected to the test object in the second system is correct and whether the test data corresponding to the test case identifier exists in the second system, the execution test of the test case corresponding to the test case identifier may be performed.
In this embodiment, after the second system executes the test case, the second system returns the execution result to the first system, so that the tester needs to test the execution result return function.
And step 618, if the execution result is successful and the return result is successful, obtaining a certification making result that the test data corresponding to the execution case identifier and the execution time of the test case corresponding to the execution case identifier in the second system are certified according to a pre-stored receipt format.
In this embodiment, after the second system successfully executes the test case and successfully returns the execution result to the first system, the second system displays the test data corresponding to the test case identifier, the test case execution time, and the like according to the pre-stored document format, that is, the certification making function is implemented, so that a tester needs to test the certification making function.
In this embodiment, whether the test object in the second system is connected to the database is tested in sequence, whether the test data exists, whether the test case is executed successfully or not, and whether the proof is manufactured successfully or not are tested in sequence, so that the reason for the failure can be conveniently and quickly found when the test fails.
In one embodiment, a joint test applied to an insurance company between a business system and a transit system associated with the business system is described as an example. After a customer purchases certain insurance in an insurance company, the business system generates a purchase order according to the purchase information of the customer, and the purchase order is provided with a business serial number, an insurance name, an insurance price and a payment state, wherein the business serial number, the insurance name and the insurance price can be directly obtained from the business system, and the payment state needs to be obtained from an intermediate system. Therefore, the business system tester tests the business system, and when the payment condition in the customer insurance purchase order is tested, the function of the associated transfer system needs to be tested. In conjunction with the interface diagram of the testing tool shown in fig. 7, due to the requirement of software development, multiple versions of the transit system associated with the business system may be possible, and the transit system associated with the business system insurance order in the transit system may be tested by selecting the transit system (e.g., STG2) for testing in conjunction with the business system through the testing tool. Firstly, selecting insurance types (such as endowment insurance) on a test tool according to insurance names on purchase orders provided by a service system, and sending a query request of database names currently connected with the endowment insurance to a transfer system by clicking a query button so as to test whether the database connection is correct or not; if the received database name is inconsistent with the database name required by the current test, receiving the input database name, and sending a database updating request to the transfer system by clicking an updating button so as to test whether the database is updated successfully or not; receiving an input service serial number, and sending a query request of purchasing order data to a transit system by clicking a query button so as to test whether the purchasing order data exists or not; if the purchase order data cannot be inquired, clicking a 'gear-drawing' button, and sending a purchase order secondary inquiry request to the transit system so that the transit system acquires the purchase order data from the service system, thereby testing whether the acquisition of the purchase order data is successful or not; according to the input service serial number, clicking 'forming batch', sending a batch processing request to a transfer system so that the transfer system stores purchase order data corresponding to the service serial number into the same file according to an online banking data storage mode, and then sending the file to the online banking system so that the online banking system inquires a payment result of the purchase order by analyzing the file and returns the payment result to the transfer system, thereby testing whether the batch processing is successfully executed (if the transfer system successfully executes the batch processing, generating a batch number and displaying the batch number in a text box of a testing tool); sending an execution result write-back request to the transfer system by clicking a capital confirmation button so that the transfer system writes back the execution result of batch processing to the service system, thereby testing whether the execution result is written back correctly or not; and sending a certificate making request to the transfer system by clicking a 'certificate making' button so that the transfer system makes a certificate for executing batch processing, including certificate making identification, payment time, payment amount and payment result.
In one embodiment, as shown in fig. 8, there is provided a test apparatus including:
a test object receiving module 802, configured to obtain a test object selected by a test tool, where the test object is generated according to a service type of a first system, and the test tool and the first system operate in the same end;
a test case identifier receiving module 804, configured to receive a test case identifier input by a test tool;
the test case execution request sending module is used for sending a test case execution request to the second system according to the test object and the test case identification;
a test case execution result receiving module 806, configured to receive an execution result generated by the second system according to the test case corresponding to the test case identifier executed by the test case execution request;
a test case execution result return request sending module 808, configured to send an execution result return request to the second system;
the test case execution result return result receiving module 810 is configured to receive a return result that the second system returns the execution result to the first system according to the execution result return request.
In one embodiment, as shown in fig. 9, the test apparatus further comprises:
a database name obtaining request sending module 902, configured to send a database name obtaining request to the second system according to the test object;
the first database name receiving module 904 receives a first database name which is currently connected with the test object and is obtained by the second system according to the database name obtaining request;
a second database name receiving module 906, configured to receive an input second database name if the first database name is different from the database name required for the current test;
a database update request sending module 908, configured to send a database update request to the second system;
the database update result obtaining module 910 is configured to receive an update result generated by the second system updating the database currently connected to the test object to the second database according to the database update request.
In one embodiment, as shown in fig. 10, the test apparatus further comprises:
a test data obtaining request sending module 1002, configured to send a test data obtaining request to the second system according to the test object and the test case identifier;
the test data obtaining result receiving module 1004 is configured to receive an obtaining result of the second system obtaining the test data corresponding to the test case identifier according to the test data obtaining request.
In one embodiment, the testing apparatus further comprises: the test data secondary acquisition request sending module is used for sending a test data secondary acquisition request to the second system if the acquisition result is that the test data acquisition fails; the test data obtaining result receiving module 1004 is further configured to receive an obtaining result of the second system obtaining the test data corresponding to the test case identifier from the first system according to the test data secondary obtaining request.
In one embodiment, the test apparatus further comprises: the system certificate request sending module is used for sending a system certificate request to the second system if the execution result is the execution success and the return result is the return success; and the certification making result receiving module is used for receiving the certification making result of the second system for obtaining the execution time of the test case corresponding to the test case identifier according to the test case execution voucher making request, and making the test data corresponding to the test case identifier and the execution time of the test case corresponding to the test case identifier according to the pre-stored receipt format.
It should be noted that "first" and "second" in the embodiments of the present invention are used only for distinguishing and are not used as limitations on the size, the subordination, the order of precedence, and the like.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. The storage medium may be a magnetic disk, an optical disk, a Read-only memory (ROM), or the like.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (8)
1. A method of testing, the method comprising:
acquiring a test object selected by a test tool and an input test case identifier, wherein the test object is generated according to the service type of a first system, and the test tool and the first system run in the same end;
sending a test case execution request to a second system according to the test object and the test case identification;
receiving an execution result generated by the second system executing the test case corresponding to the test case identification according to the test case execution request;
sending an execution result return request to the second system;
receiving a return result of the second system returning the execution result to the first system according to the execution result return request;
before sending a test case execution request to the second system according to the test object and the test case identifier, the method further includes:
sending a database name acquisition request to the second system according to the test object;
receiving a first database name which is acquired by the second system according to a database name acquisition request and is currently connected with the test object;
if the first database name is different from the database name required by the current test, receiving an input second database name, and sending a database updating request to the second system;
and receiving an updating result generated by the second system for updating the database currently connected with the test object into the second database according to the database updating request.
2. The method according to claim 1, before said sending a test case execution request to the second system according to the test object and the test case identifier, further comprising:
sending a test data acquisition request to the second system according to the test object and the test case identifier;
and receiving an acquisition result of the test data corresponding to the test case identification acquired by the second system according to the test data acquisition request.
3. The method of claim 2, further comprising:
if the acquisition result is that the test data acquisition fails, sending a test data secondary acquisition request to the second system;
and receiving an acquisition result of the second system for acquiring the test data corresponding to the test case identifier from the first system according to the secondary acquisition request of the test data.
4. The method of claim 1, further comprising:
if the execution result is successful and the return result is successful, sending a certificate making request to the second system;
and receiving the execution time of the test case corresponding to the test case identification obtained by the second system according to the test case execution voucher making request, and making a proof making result by using the test data corresponding to the test case identification and the execution time of the test case corresponding to the test case identification according to a pre-stored receipt format.
5. A test apparatus, the apparatus comprising:
the test object receiving module is used for acquiring a test object selected by a test tool, the test object is generated according to the service type of a first system, and the test tool and the first system run in the same end;
the test case identification receiving module is used for receiving the test case identification input by the test tool;
the test case execution request sending module is used for sending a test case execution request to the second system according to the test object and the test case identification;
the test case execution result receiving module is used for receiving the execution result generated by the second system according to the test case execution request for executing the test case corresponding to the test case identifier;
the test case execution result return request sending module is used for sending an execution result return request to the second system;
the test case execution result return result receiving module is used for receiving a return result of the second system returning the execution result to the first system according to the execution result return request;
the device further comprises:
a database name acquisition request sending module, configured to send a database name acquisition request to the second system according to the test object;
the first database name receiving module is used for receiving a first database name which is obtained by the second system according to the database name obtaining request and is currently connected with the test object;
the second database name receiving module is used for receiving an input second database name if the first database name is different from the database name required by the current test;
a database update request sending module, configured to send a database update request to the second system;
and the database updating result acquisition module is used for receiving an updating result generated by the second system for updating the database currently connected with the test object into the second database according to the database updating request.
6. The apparatus of claim 5, further comprising:
a test data acquisition request sending module, configured to send a test data acquisition request to the second system according to the test object and the test case identifier;
and the test data acquisition result receiving module is used for receiving the acquisition result of the test data corresponding to the test case identifier acquired by the second system according to the test data acquisition request.
7. The apparatus of claim 6, further comprising:
the test data secondary acquisition request sending module is used for sending a test data secondary acquisition request to the second system if the acquisition result is that the test data acquisition fails;
the test data obtaining result receiving module is further configured to receive a result obtained by the second system according to the test data secondary obtaining request to obtain the test data corresponding to the test case identifier from the first system.
8. The apparatus of claim 5, further comprising:
the certificate making request sending module is used for sending a certificate making request to the second system if the execution result is that the execution is successful and the return result is that the return is successful;
and the certification result receiving module is used for receiving the certification result which is obtained by the second system according to the test case execution voucher making request, acquiring the execution time of the test case corresponding to the test case identifier, and making the certification according to the test data corresponding to the test case identifier and the execution time of the test case corresponding to the test case identifier in a pre-stored receipt format.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710147237.6A CN107797918B (en) | 2017-03-13 | 2017-03-13 | Test method and test device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710147237.6A CN107797918B (en) | 2017-03-13 | 2017-03-13 | Test method and test device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107797918A CN107797918A (en) | 2018-03-13 |
| CN107797918B true CN107797918B (en) | 2020-05-05 |
Family
ID=61530182
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710147237.6A Active CN107797918B (en) | 2017-03-13 | 2017-03-13 | Test method and test device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107797918B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108694124A (en) * | 2018-06-19 | 2018-10-23 | 链家网（北京）科技有限公司 | A kind of house prosperity transaction system test data building method and system based on Mock |
| CN109617755B (en) * | 2018-11-22 | 2022-08-19 | 银清科技有限公司 | Acceptance method and device of access system |
| CN110489325A (en) * | 2019-07-09 | 2019-11-22 | 微民保险代理有限公司 | Vehicle insurance data test method, apparatus, test platform and vehicle insurance test macro |
| CN110597736B (en) * | 2019-10-31 | 2023-01-17 | 口碑(上海)信息技术有限公司 | Test data generation method and device |
| CN111338953A (en) * | 2020-02-26 | 2020-06-26 | 深圳壹账通智能科技有限公司 | Service component testing method, apparatus, computer equipment and storage medium |
| CN111787089B (en) * | 2020-06-28 | 2022-05-13 | 中国建设银行股份有限公司 | Method, device and system for network integration service of process robot |
| CN112612703B (en) * | 2020-12-25 | 2024-11-26 | 航天信息股份有限公司 | An automated testing method and device involving multi-system interactive interfaces |
| CN112783788B (en) * | 2021-02-05 | 2023-12-05 | 北京同邦卓益科技有限公司 | Test system, method, electronic device and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102148729A (en) * | 2011-05-20 | 2011-08-10 | 烽火通信科技股份有限公司 | Automatic test method for private SNMP (simple network management protocol) management instruction of passive optical network equipment |
| CN102855182A (en) * | 2011-06-28 | 2013-01-02 | 乐活在线（北京）网络技术有限公司 | Web system test method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9424171B1 (en) * | 2015-04-23 | 2016-08-23 | International Business Machines Corporation | Resource-constrained test automation |
-
2017
- 2017-03-13 CN CN201710147237.6A patent/CN107797918B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102148729A (en) * | 2011-05-20 | 2011-08-10 | 烽火通信科技股份有限公司 | Automatic test method for private SNMP (simple network management protocol) management instruction of passive optical network equipment |
| CN102855182A (en) * | 2011-06-28 | 2013-01-02 | 乐活在线（北京）网络技术有限公司 | Web system test method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107797918A (en) | 2018-03-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107797918B (en) | Test method and test device | |
| US12079841B2 (en) | Configurable relevance service platform incorporating a relevance test driver | |
| CN111858296B (en) | Interface testing method, device, equipment and storage medium | |
| US20140052578A1 (en) | Promoter system and method for processing product and service data | |
| CN107783861B (en) | Transaction rollback method, device, storage medium and computer equipment | |
| CN112613932B (en) | Invoicing method, device, storage medium and electronic device | |
| CN110244934B (en) | Method and device for generating product demand document and test information | |
| JP2017068580A (en) | Information providing system and mobile terminal | |
| US10607204B2 (en) | Support messages based on merchant account context | |
| CN111753203A (en) | Card number recommendation method, device, equipment and medium | |
| US20110307313A1 (en) | Search system and method using search library | |
| CN108228611B (en) | Document information copying method and device | |
| CN116266482A (en) | Equipment software upgrading method and device | |
| CN110955449A (en) | Method and device for releasing gray scale of client | |
| WO2024255141A1 (en) | Resource object display method and apparatus, and device, storage medium and product | |
| WO2014077150A1 (en) | Store visit authentication system | |
| WO2022044812A1 (en) | Recommendation device | |
| CN117350256A (en) | Form data processing method, device, equipment and storage medium | |
| CN111506340B (en) | Business rule information processing method, device and system | |
| KR102658546B1 (en) | A computer-readable recording medium storing an information processing system, an information processing method, and an information processing program. | |
| CN111078550A (en) | Software testing method and device, computer device and storage medium | |
| JP7370292B2 (en) | Proposed device | |
| US20120041807A1 (en) | Incentive-based server cooperation system, incentive-based server cooperation method and incentive-based server cooperation program | |
| JP5686865B2 (en) | Server, service information transmission method, and program | |
| JP7555728B2 (en) | Virtual POS server and virtual POS 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |