CN110879779B - Joint debugging test method and system - Google Patents
Joint debugging test method and system Download PDFInfo
- Publication number
- CN110879779B CN110879779B CN201910993753.XA CN201910993753A CN110879779B CN 110879779 B CN110879779 B CN 110879779B CN 201910993753 A CN201910993753 A CN 201910993753A CN 110879779 B CN110879779 B CN 110879779B
- Authority
- CN
- China
- Prior art keywords
- test
- information
- data
- account information
- commodity
- 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
- 238000010998 test method Methods 0.000 title claims abstract description 5
- 238000012360 testing method Methods 0.000 claims abstract description 124
- 238000000034 method Methods 0.000 claims abstract description 39
- 238000002955 isolation Methods 0.000 claims abstract description 16
- 238000004519 manufacturing process Methods 0.000 claims abstract description 15
- 230000000977 initiatory effect Effects 0.000 claims description 10
- 230000004044 response Effects 0.000 claims description 9
- 238000003860 storage Methods 0.000 claims description 9
- 238000012795 verification Methods 0.000 claims description 8
- 230000008569 process Effects 0.000 abstract description 21
- 230000002159 abnormal effect Effects 0.000 description 4
- 238000006243 chemical reaction Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000013507 mapping Methods 0.000 description 2
- 238000003032 molecular docking Methods 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 238000002360 preparation method Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000011990 functional testing Methods 0.000 description 1
- 230000008570 general process Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000007726 management method Methods 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
- 230000008520 organization Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000006467 substitution reaction Methods 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—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
-
- 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
Abstract
The application relates to a joint debugging test method and a system, wherein the method comprises the following steps: when a test request is received, verifying account information of a request terminal; inquiring information in test data corresponding to the account information, wherein the test data is logically isolated and stored through the account information; and returning a query result. According to the scheme, the test data are distinguished through the account information, the logic isolation among the data of different test projects is realized, the simultaneous test of multiple users can be realized, and the data security is ensured; all testing processes are carried out in independent testing data, and isolation from the production environment is achieved.
Description
Technical Field
The application relates to the technical field of interface debugging, in particular to a joint debugging testing method and system.
Background
Joint debugging test is a logical extension of unit testing, and its simplest form is: two already tested units are combined into one component and the interface between them is tested. In an actual test scenario, many units are combined into components, which in turn are aggregated into a larger part of the program.
Currently, many open platforms can provide various interface services for users, and users need to perform joint debugging testing on interfaces before using the interface services. In the interface joint debugging test process, the general butt joint mode between the open platform and the client is that the open platform provides different servers for different clients respectively, deploys environments required by the clients, and test data is provided by the clients respectively.
In the related art, a plurality of pain points exist in a joint debugging test link in the standard API user access process:
one is the data isolation requirement. Different customers need to use different test data, and thus the test data of different customers need to be isolated.
And incomplete data of the tested goods. In the API joint debugging process, due to the fact that various service scenes are involved, peripheral system data preparation is greatly depended on. Such as: 1. a commodity type demand; the commodity types comprise self-service, factory delivery, package, virtual products, gift cards and the like. 2. Commodity attribute requirements; the user needs to be supported to modify commodity details, commodity parameters, commodity prices, commodity specifications and the like at any time in the joint debugging process. When the commodity data is simulated comprehensively, the required time is long, the flow is complex, the user requirements cannot be met in time, and the API user access efficiency is seriously influenced.
And thirdly, a process deletion. The test environment cannot be translated to the production environment after being verified, so that the production environment still has known problems of various test environments.
Disclosure of Invention
To overcome, at least to some extent, the problems in the related art, the present application provides a joint debugging testing method and system.
According to a first aspect of embodiments of the present application, there is provided a joint debugging test method, including:
when a test request is received, verifying account information of a request terminal;
inquiring information in test data corresponding to the account information, wherein the test data is logically isolated and stored through the account information;
and returning a query result.
Further, the test data comprises commodity basic information; accordingly, the method further comprises:
acquiring configuration information;
initializing commodity basic information according to the configuration information;
and performing data isolation on corresponding commodity basic information according to the account information.
Further, the initializing the commodity basic information according to the configuration information includes:
collecting relevant data from a production environment according to the configuration information;
and copying and isolating the collected data in batches for storage.
Further, the account information of the verification request terminal includes:
verifying the validity of the parameters;
after the verification parameter is legal, initiating a query request;
checking whether account information exists;
if not, returning an error response; and if so, inquiring corresponding information according to the test request.
Further, querying information in the test data corresponding to the account information includes:
determining corresponding test data according to the account information;
calling an interface to be tested according to the test request;
and inquiring information in corresponding test data through the interface to be tested.
According to a second aspect of embodiments of the present application, there is provided a joint debugging test system, including:
the test foreground is used for verifying the account information of the request end when receiving the test request;
the test center is used for inquiring information in the test data corresponding to the account information and returning an inquiry result to the test foreground;
and the database is used for storing the test data logically isolated through the account information.
Further, the test data comprises commodity basic information;
the test foreground is also used for: acquiring configuration information;
accordingly, the system further comprises:
the test background is used for initializing commodity basic information according to the configuration information; and performing data isolation on corresponding commodity basic information according to the account information.
Further, the initializing of the commodity basic information by the test background according to the configuration information specifically includes:
collecting relevant data from a production environment according to the configuration information;
and copying and isolating the collected data in batches for storage.
Further, the verifying, by the foreground, the account information of the request end specifically includes:
verifying the validity of the parameters;
after the verification parameter is legal, initiating a query request;
checking whether account information exists;
if not, returning an error response; and if so, inquiring corresponding information according to the test request.
Further, the querying, by the test center, information in the test data corresponding to the account information specifically includes:
determining corresponding test data according to the account information;
calling an interface to be tested according to the test request;
and inquiring information in the corresponding test data through the interface to be tested.
The technical scheme provided by the embodiment of the application has the following beneficial effects:
according to the scheme, the test data are distinguished through the account information, the logic isolation among the data of different test projects is realized, the simultaneous test of multiple users can be realized, and the data security is ensured; all testing processes are carried out in independent testing data, and isolation from the production environment is achieved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and, together with the description, serve to explain the principles of the application.
FIG. 1 is a flow chart illustrating a method of joint debugging testing in accordance with an exemplary embodiment.
FIG. 2 is a flow chart illustrating a method of joint debugging testing in accordance with an exemplary embodiment.
FIG. 3 is a flowchart illustration of a timed task to receive in accordance with an exemplary embodiment.
FIG. 4 is an illustration of a test flow for obtaining details of an article of merchandise, according to an example embodiment.
Fig. 5 is a schematic diagram of a technical architecture of a joint debugging test system, according to an exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
FIG. 1 is a flow chart illustrating a method of joint debugging testing in accordance with an exemplary embodiment. The method comprises the following steps:
step S1: when a test request is received, verifying account information of a request terminal;
step S2: inquiring information in test data corresponding to the account information, wherein the test data is logically isolated and stored through the account information;
and step S3: and returning a query result.
According to the scheme, the test data are distinguished through the account information, the logic isolation among the data of different test projects is realized, the simultaneous test of multiple users can be realized, and the data security is ensured; all testing processes are carried out in independent testing data, and isolation from the production environment is achieved.
Referring to fig. 2, the specific flow of the joint debugging test scheme of the present application includes three parts as described below.
First, commodity basic information is initialized. The basic information of the commodity needs to collect relevant data from the main station; and according to the flow sequence, initializing the basic related information of the commodity, distinguishing by the client number, and realizing the multi-tenant data isolation.
In some embodiments, the test data includes commodity basis information; correspondingly, the method further comprises:
acquiring configuration information;
initializing commodity basic information according to the configuration information;
and performing data isolation on corresponding commodity basic information according to the account information.
Specifically, data isolation may be performed in the following manner: sharing the same base table, binding a client number custNo field in each record stored in the database, and acquiring the data according to the bound client number field to acquire the data of the data. Wherein, the customer number is the account information.
According to the scheme, the business data can be distinguished through the member name numbers, the logic isolation of all the business data is realized, multi-tenancy is realized, and the safety of the data is ensured. And the data is quickly simulated by modifying the commodity details, the commodity parameters, the commodity price and the commodity specification at any time through configuration.
In some embodiments, the initializing the basic information of the commodity according to the configuration information includes:
collecting relevant data from a production environment according to the configuration information;
and copying and isolating the collected data in batches for storage.
Related service data are simulated and initialized in batches by configuring related parameters, commodity data consistent with a production environment are generated rapidly, and the problems of data dependence on a peripheral system and data preparation timeliness are solved. Because real service data are copied from the production environment, more comprehensive test data can be conveniently provided, various abnormal conditions can be easily verified, and the test environment can be translated to the production environment after being verified.
In some specific embodiments, the commodity basic information initialization process may include the following steps:
initializing commodity detail table information zs _ product _ info;
importing contract data from xls documents in batch, and initializing a contract table zs _ user _ contract;
initializing address information in batches, wherein the address information comprises provinces, regions and towns as basic data;
the user inputs the customer number through the interface;
through the sql, a client number is firstly numbered to initialize user data, the client number is used for interface parameter transmission, and other data are fixed through the sql;
firstly, a contract table is removed, and the legality of a client number is verified;
initializing a zs _ user _ vatticket customer ticket information adding authentication table, only initializing topClusNo, transmitting a value interface, and leaving other fields empty;
initializing a zs _ user _ product _ category client commodity catalog configuration information maintenance table, wherein the client number is transmitted through an interface, other data are fixed through sql, and a message is inserted at the same time;
initializing a zs _ user _ product _ pool commodity pool, taking interface parameters from a client number, taking other values from an information table, and inserting a message;
initialize zs _ user _ product _ inventoryy: taking intersection of the city, the commodity number, the commodity detail table zs _ product _ info and the region table zs _ discard;
initializing a user account number table zs _ user _ account, acquiring a client number from an interface, and fixing other data;
initializing a table zs _ user _ account _ log;
initializing a table zs _ user _ product _ mapping;
the table zs _ user _ address _ mapping is initialized.
And the second part, customer information initialization. The customer initialization process simplifies the initialization configuration work of the system user, and the initialization work of the relevant configuration information is automatically completed by the system through setting a default value.
Registering a batch (such as 1000) of test accounts in a member center in advance; synchronously registering the 1000 account numbers in an open platform synchronously and acquiring corresponding appkeys; if a new user needs to be jointly called, the user needs to be registered into the contract configuration in the test system firstly, then the initialization button is clicked to complete automatic initialization, and one user can only initialize once.
In some embodiments, the customer information initialization process may include the steps of:
the member center: registering a test enterprise account (CustNo account);
an open platform: registering the appkey;
and (3) client contract configuration: automatically writing into a zs _ user _ extract table;
customer organization architecture configuration: initializing an account as a current parent account into a zs _ user table by default;
and (3) customer account configuration: defaulting a current account to create two accounts of an account period and a pre-deposit;
customer inventory configuration: taking default primary, secondary and tertiary directories to directly initialize to a zs _ user _ product _ category table;
customer commodity pool configuration: acquiring a default commodity from the commodity basic table and directly initializing the default commodity into a zs _ user _ product _ pool table of the user commodity pool;
customer commodity pool inventory configuration: and acquiring initialized inventory information of the commodities from the commodity pool according to the default region into a zs _ user _ product _ inventory table.
And in the third part, after the initialization of the commodity basic information and the customer information is completed, subsequent test work can be carried out.
Referring to fig. 2, before the testing process is performed, a process of modifying order information (i.e., a task to be received) by a timing task may be further included. The to-be-received goods mainly simulate the delivery flow of oms and logistics for the orders with the reduced stock; the timing task is executed once every 5 minutes, the order before the state is 01 (namely B2C is sent) and the time is less than 30 minutes is retrieved in the order row table, and the order task needs to complete the processes of generating logistics details, generating messages, changing order rows, head states and the like.
Referring to fig. 3, the task to be received may specifically include the following steps:
and (3) starting a task: opening a jobdelivery;
and (3) retrieving the order: -30 minutes in zs _ order _ item according to status =01and update _time < = current time;
initiating a logistics detail request;
writing details: zs _ order _ logist and zs _ order _ logist _ detail are written in rows;
if the writing is successful, initiating a message pushing request;
writing order logistics messages: writing zs _ user _ push _ message order logistics messages according to rows;
updating the zs _ order _ item state after the writing is successful;
and executing the job.
Referring to fig. 4, in some embodiments, in the process of performing an actual test, the verifying account information of the requesting end includes:
verifying the validity of the parameters;
after the verification parameter is legal, initiating a query request;
checking whether account information exists;
if not, returning an error response; and if so, inquiring corresponding information according to the test request.
The account information may be a customer number.
In some embodiments, querying information in the test data corresponding to the account information includes:
determining corresponding test data according to the account information;
calling an interface to be tested according to the test request;
and inquiring information in the corresponding test data through the interface to be tested.
Referring to fig. 4, the testing process of the present application is described in an expanded manner in combination with a specific application scenario for obtaining detailed data of a commodity. The test process for obtaining the detailed data of the commodity specifically comprises the following steps:
1. initiating a request: and the user initiates a request for acquiring the information of the commodity pool to the foreground through the open platform.
2. Message conversion: converting the json request message into a DTO by a foreground; if the conversion is erroneous, the corresponding error code is returned (biz. Govbus. Proddetail. Invalid-biz: 100).
And (3) validity checking: after the conversion is successful, the foreground carries out DTO parameter validity check; if the check-in fails, the corresponding error code is returned (biz. Govbus. Proddetail. Invalid-biz: 101).
3. Initiating a query request: and after the foreground verifies that the parameters are legal, the foreground initiates a query request to the middle station through the RSF.
4. Checking whether the client number exists: the GCTEST center checks whether the client number exists in a zs _ user _ contract table; if not (custo does not exist), then an error response is returned to the foreground and the client number does not exist (biz. Govbus. Prodddetail. Invalid-biz: 102).
And then foreground feedback is given to the open platform.
5. Querying whether information exists: the middle station checks whether the information to be inquired exists in the data table zs _ user _ product _ pool or not according to the commodity code and the client number.
If the information does not exist, the information returned to the foreground by the middle station is null; the foreground returns an error response to the open platform, and informs that the commodity does not belong to the client (biz.
6. And querying detailed commodity data: the middle station inquires basic information in a data table zs _ product _ info according to the commodity code, inquires picture information in a data table zs _ product _ image according to the commodity code, and inquires description information in a data table zs _ product _ description according to the commodity code.
If no commodity data is searched, the middle station feeds back to the foreground that zs _ product _ info has no commodity data; the foreground returns an error response to the open platform to inform that the inquired commodity information is abnormal (biz. Govbus. Incremental. Invalid-biz: 105). If the commodity data can be found, the detail data is returned normally.
The scheme of the application simulates all abnormal conditions and covers abnormal scenes by realizing a complete business process. And through a timing task, the order state is modified at regular time, and order logistics circulation information is completely simulated. The investment of the test joint debugging personnel in carrying out repeated work such as various coordination, investigation and the like is reduced, and the functional test is concentrated on. After verification of the test environment, the code may be translated to the production environment. All the general processes are adopted, and no special person is required to be arranged for docking, so that the problems that the docking time is long, the processes are complex, the user requirements cannot be met in time, and the API user access efficiency is seriously influenced are solved.
The present application also provides the following embodiments:
a joint debugging test system, comprising:
the test foreground is used for verifying the account information of the request end when receiving the test request;
the test center is used for inquiring information in the test data corresponding to the account information and returning an inquiry result to the test foreground;
and the database is used for storing the test data logically isolated through the account information.
Referring to fig. 5, the present solution may adopt the following technical architecture:
(1) The method comprises the following steps of (1) independently deploying GCTEST-ADMIN (background) and MYSQL (database), wherein the background is used as a system management platform and is mainly used for maintaining and configuring test data;
(2) Independently applying for capacity expansion of two servers, manually releasing a GCTEST-SERVICE middlebox, and independently configuring a data source of a test system;
(3) And the routing of the client number to different application servers is realized through the unitized script of the remote service framework RSF.
Wherein, the different application server is foreground server (GCTEST-WEB). And the foreground adopts cluster deployment to realize route distribution.
In some embodiments, the test data includes commodity basis information;
the test foreground is also used for: acquiring configuration information;
accordingly, the system further comprises:
the test background is used for initializing commodity basic information according to the configuration information; and performing data isolation on corresponding commodity basic information according to the account information.
In some embodiments, the initializing, by the test background, the commodity basic information according to the configuration information specifically includes:
collecting relevant data from a production environment according to the configuration information;
and copying and isolating the collected data in batches for storage.
In some embodiments, the verifying, by the foreground, the account information of the request end specifically includes:
verifying the validity of the parameters;
after the verification parameter is legal, initiating a query request;
checking whether account information exists;
if not, returning an error response; and if so, inquiring corresponding information according to the test request.
In some embodiments, the querying, by the test center, information in the test data corresponding to the account information specifically includes:
determining corresponding test data according to the account information;
calling an interface to be tested according to the test request;
and inquiring information in corresponding test data through the interface to be tested.
With respect to the system in the above embodiment, the specific steps of the operations performed by the various parts have been described in detail in the embodiment of the method, and are not described in detail here.
It is understood that the same or similar parts in the above embodiments may be mutually referred to, and the same or similar parts in other embodiments may be referred to for the content which is not described in detail in some embodiments.
It should be noted that, in the description of the present application, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, in the description of the present application, the meaning of "a plurality" means at least two unless otherwise specified.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.
Claims (6)
1. A joint debugging test method, comprising:
when a test request is received, verifying account information of a request terminal;
inquiring information in test data corresponding to the account information, wherein the test data is logically isolated and stored through the account information;
returning a query result;
the test data includes commodity base information, the method further includes:
acquiring configuration information;
initializing commodity basic information according to the configuration information;
performing data isolation on corresponding commodity basic information according to the account information;
the initializing of the basic information of the commodity according to the configuration information includes:
collecting relevant data from a production environment according to the configuration information;
and copying and isolating the collected data in batches for storage.
2. The method according to claim 1, wherein the verifying the account information of the requesting end comprises:
verifying the validity of the parameters;
after the verification parameter is legal, initiating a query request;
checking whether account information exists;
if not, returning an error response; and if so, inquiring corresponding information according to the test request.
3. The method according to any one of claims 1-2, wherein querying information in the test data corresponding to the account information comprises:
determining corresponding test data according to the account information;
calling an interface to be tested according to the test request;
and inquiring information in corresponding test data through the interface to be tested.
4. A joint debugging test system, comprising:
the test foreground is used for verifying the account information of the request end when receiving the test request;
the test center is used for inquiring information in the test data corresponding to the account information and returning an inquiry result to the test foreground;
the database is used for storing test data logically isolated through the account information;
the test data comprises commodity basic information;
the test foreground is also used for: acquiring configuration information;
correspondingly, the system further comprises:
the test background is used for initializing basic information of the commodity according to the configuration information; performing data isolation on corresponding commodity basic information according to the account information;
the initializing of the commodity basic information by the test background according to the configuration information specifically comprises:
collecting relevant data from a production environment according to the configuration information;
and copying and isolating the collected data in batches for storage.
5. The system according to claim 4, wherein the verifying the account information of the request end by the test foreground specifically includes:
verifying the validity of the parameters;
after the verification parameter is legal, initiating a query request;
checking whether account information exists;
if not, returning an error response; and if so, inquiring corresponding information according to the test request.
6. The system according to claim 4, wherein the information query by the test center in the test data corresponding to the account information specifically includes:
determining corresponding test data according to the account information;
calling an interface to be tested according to the test request;
and inquiring information in the corresponding test data through the interface to be tested.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910993753.XA CN110879779B (en) | 2019-10-18 | 2019-10-18 | Joint debugging test method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910993753.XA CN110879779B (en) | 2019-10-18 | 2019-10-18 | Joint debugging test method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110879779A CN110879779A (en) | 2020-03-13 |
| CN110879779B true CN110879779B (en) | 2022-11-18 |
Family
ID=69728091
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910993753.XA Active CN110879779B (en) | 2019-10-18 | 2019-10-18 | Joint debugging test method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110879779B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112835782B (en) * | 2020-12-22 | 2022-06-03 | 北京健康之家科技有限公司 | Interface access test method and system |
| CN113448873B (en) * | 2021-07-22 | 2022-12-20 | 亿咖通(湖北)技术有限公司 | Software testing method, device, storage medium and program product |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105515887A (en) * | 2014-10-16 | 2016-04-20 | 腾讯科技（深圳）有限公司 | Application test method, server and system |
| CN109783357A (en) * | 2018-12-14 | 2019-05-21 | 深圳壹账通智能科技有限公司 | The method and device of test application program, computer equipment, storage medium |
-
2019
- 2019-10-18 CN CN201910993753.XA patent/CN110879779B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105515887A (en) * | 2014-10-16 | 2016-04-20 | 腾讯科技（深圳）有限公司 | Application test method, server and system |
| CN109783357A (en) * | 2018-12-14 | 2019-05-21 | 深圳壹账通智能科技有限公司 | The method and device of test application program, computer equipment, storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110879779A (en) | 2020-03-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107370786B (en) | General information management system based on micro-service architecture | |
| CN108334387B (en) | Dynamic interface rendering method and device | |
| CN106844372B (en) | Logistics information query method and device | |
| US7751417B2 (en) | Accelerated system and methods for synchronizing, managing and publishing business information | |
| CN110879779B (en) | Joint debugging test method and system | |
| US20090234749A1 (en) | Order Processing Analysis Tool | |
| CN108874567A (en) | A kind of service processing method and system | |
| CN106547646B (en) | Data backup and recovery method and data backup and recovery device | |
| CN109308251A (en) | The method of calibration and device of test data | |
| CN111309624B (en) | Test method, test device, test equipment and storage medium | |
| CN110543469B (en) | Database version management method and server | |
| US9513997B2 (en) | Test data management | |
| CN113362085A (en) | Primary and secondary account management method and system | |
| CN111353841A (en) | Document data processing method, device and system | |
| CN111338825A (en) | E-commerce interface docking platform | |
| CN112581201A (en) | Mobile open platform for industrial interconnection manufacturing and implementation method | |
| CN111179073A (en) | System and method for generating a digital identity of a device on an online marketplace platform for the device | |
| US20070226085A1 (en) | System and method for automated mapping of data in a multi-valued data structure | |
| CN110781191A (en) | Processing method of layout data and server | |
| KR102432066B1 (en) | Method and Server for Providing Web Service with Customer Compatibility using Matching Table related to Standardized Bill of Material | |
| US11195127B2 (en) | Transport method | |
| US20040158498A1 (en) | Method for creating mass sales orders | |
| CN107851165B (en) | Key system, key client and key management method | |
| CN103164217A (en) | Standalone data entry for backend system | |
| CN110457541B (en) | Data processing method, service platform, terminal device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: No.1-1 Suning Avenue, Xuzhuang Software Park, Xuanwu District, Nanjing, Jiangsu Province, 210000 Patentee after: Jiangsu Suning cloud computing Co.,Ltd. Country or region after: China Address before: No.1-1 Suning Avenue, Xuzhuang Software Park, Xuanwu District, Nanjing, Jiangsu Province, 210000 Patentee before: Suning Cloud Computing Co.,Ltd. Country or region before: China |
|
| CP03 | Change of name, title or address | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240410 Address after: 210000, 1-5 story, Jinshan building, 8 Shanxi Road, Nanjing, Jiangsu. Patentee after: SUNING.COM Co.,Ltd. Country or region after: China Address before: No.1-1 Suning Avenue, Xuzhuang Software Park, Xuanwu District, Nanjing, Jiangsu Province, 210000 Patentee before: Jiangsu Suning cloud computing Co.,Ltd. Country or region before: China |
|
| TR01 | Transfer of patent right |