CN110554958A - Graph database testing method, system, device and storage medium - Google Patents
Graph database testing method, system, device and storage medium Download PDFInfo
- Publication number
- CN110554958A CN110554958A CN201910709047.8A CN201910709047A CN110554958A CN 110554958 A CN110554958 A CN 110554958A CN 201910709047 A CN201910709047 A CN 201910709047A CN 110554958 A CN110554958 A CN 110554958A
- Authority
- CN
- China
- Prior art keywords
- data
- testing
- graph
- graph database
- test
- 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.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/901—Indexing; Data structures therefor; Storage structures
- G06F16/9024—Graphs; Linked lists
Abstract
the application discloses a graph database testing method, a graph database testing system, graph database testing equipment and a storage medium, wherein the method comprises the following steps: generating graph data meeting the target service scene according to the requirements of the target service scene; determining a test type for a graph database to be tested; generating test data suitable for the test type according to the test type and the graph data meeting the target service scene; and testing the graph database to be tested according to the test data suitable for the test type. The graph data meeting different service scenes are dynamically generated according to different service scene requirements, and the graph database to be tested is tested based on the graph data meeting different service scenes, so that the problem of graph data testing in the prior art is solved, the function of testing the graph database is realized, the complex relationships of multiple scenes can be covered, the performance difference of a graph database system in different scenes is realized, the application scenes of the testing scheme of the embodiment of the application are greatly expanded, and the reusability of the testing system is improved.
Description
Technical Field
The present application relates to the field of database testing technologies, and in particular, to a method, a system, a device, and a computer-readable storage medium for testing a graph database.
Background
Currently, graph databases are the fastest growing category among all data management systems. Through the graph format storage of nodes, attributes and edges, the graph database overcomes the problem of large and complex data which cannot be solved by other databases, and has obvious advantages in the processing of complex problems, and the advantages are mainly reflected in that: better, faster query and analysis; simpler and more natural data modeling; meanwhile, real-time updating and query are supported; more flexible data structures. Thus, more and more graph database based products, analysis systems, are emerging in the market.
There are some relatively sophisticated functional, performance automated test schemes and systems available for traditional databases. Compared with the traditional database, the database is different in data modeling, storage and application expression scenes, so that the test scheme of the traditional database cannot be suitable for testing the database. In addition, since graph databases are an emerging database modality that has prevailed in recent years, no systematic testing method has emerged for this type of data.
therefore, how to implement the test of the graph database becomes a problem to be solved.
Disclosure of Invention
The present application aims to solve at least one of the technical problems in the related art to some extent.
Therefore, a first objective of the present application is to provide a graph database testing method, which can solve the problem of graph data testing, so as to implement the function of testing graph databases.
A second object of the present application is to provide a graph database testing system.
A third object of the present application is to provide an apparatus based on a graph database testing method.
A fourth object of the present application is to propose a computer readable storage medium.
in order to achieve the above object, an embodiment of a first aspect of the present application provides a method for testing a graph database, including: generating graph data meeting the target service scene according to the requirements of the target service scene; determining a test type for a graph database to be tested; generating test data suitable for the test type according to the test type and the graph data meeting the target service scene; and testing the graph database to be tested according to the test data suitable for the test type.
according to the graph database testing method, graph data meeting the target business scene are generated according to the requirements of the target business scene, the testing type of the graph database to be tested is determined, testing data suitable for the testing type are generated according to the testing type and the graph data meeting the target business scene, and the graph database to be tested is tested according to the testing data suitable for the testing type. The graph data meeting different service scenes are dynamically generated according to different service scene requirements, and the graph database to be tested is tested based on the graph data meeting different service scenes, so that the problem of graph data testing in the prior art is solved, the function of testing the graph database is realized, the complex relationships of various scenes can be covered, the performance difference of a graph database system in different scenes can be realized, the application scenes of the testing scheme of the embodiment of the application are greatly expanded, and the reusability of the testing system is improved.
To achieve the above object, a second aspect of the present application provides a graph database testing system, including: the graph data generation module is used for generating graph data meeting the target service scene according to the requirements of the target service scene; the graph database testing module is used for determining the testing type of the graph database to be tested, generating testing data suitable for the testing type according to the testing type and the graph data meeting the target service scene, and testing the graph database to be tested according to the testing data suitable for the testing type.
according to the graph database testing system, graph data meeting the target business scene are generated according to the requirements of the target business scene; determining a test type for a graph database to be tested; generating test data suitable for the test type according to the test type and the graph data meeting the target service scene; and testing the graph database to be tested according to the test data suitable for the test type. The graph data meeting different service scenes are dynamically generated according to different service scene requirements, and the graph database to be tested is tested based on the graph data meeting different service scenes, so that the problem of graph data testing in the prior art is solved, the function of testing the graph database is realized, the complex relationships of various scenes can be covered, the performance difference of a graph database system in different scenes can be realized, the application scenes of the testing scheme of the embodiment of the application are greatly expanded, and the reusability of the testing system is improved.
In order to achieve the above object, a third aspect of the present application provides an apparatus based on a graph database testing method, including: the system comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the computer program to realize the graph database testing method in the embodiment of the first aspect of the application.
To achieve the above object, a fourth aspect of the present application provides a computer-readable storage medium, on which a computer program is stored, wherein the computer program, when executed by a processor, implements the graph database testing method according to the first aspect of the present application.
Additional aspects and advantages of the present application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
FIG. 1 is a schematic flow chart diagram of a graph database testing method according to a first embodiment of the present application;
FIG. 2 is a schematic flow chart diagram of a graph database testing method according to a second embodiment of the present application;
FIG. 3 is a schematic flow chart diagram illustrating a method for testing a graph database according to a third embodiment of the present application;
FIG. 4 is a schematic flow chart diagram illustrating a graph database testing method according to a fourth embodiment of the present application;
FIG. 5 is a schematic diagram of a graph database testing system according to a first embodiment of the present application;
FIG. 6 is a schematic diagram of a graph database testing system according to a second embodiment of the present application;
FIG. 7 is a schematic diagram of a graph database testing system according to a third embodiment of the present application;
FIG. 8 is a schematic diagram of a fourth embodiment of a graph database testing system according to the present application;
FIG. 9 is a schematic diagram of a graph database testing system according to a fifth embodiment of the present application;
FIG. 10 is a schematic diagram of a graph database testing system according to a sixth embodiment of the present application;
FIG. 11 shows a block diagram of an apparatus suitable for use in implementing the graph database-based testing method of embodiments of the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary and intended to be used for explaining the present application and should not be construed as limiting the present application.
A graph database testing method, system, device and computer readable storage medium according to embodiments of the present application are described below with reference to the accompanying drawings. The graph database testing method of the embodiment of the application can be applied to the graph database testing system of the embodiment of the application, so that the graph database testing system can execute the graph database testing method. The graph database testing system can be applied to any business scenes depending on the graph database, such as financial transaction scenes, e-commerce transaction scenes, network management scenes and the like.
FIG. 1 is a schematic flow chart diagram of a graph database testing method according to one embodiment of the present application.
As shown in fig. 1, the graph database testing method includes the steps of:
Step 101, generating graph data meeting the target service scene according to the requirements of the target service scene.
It can be understood that the graph database testing system according to the embodiment of the present application can be applied to any business scenarios depending on the graph database, such as financial transaction scenarios, e-commerce transaction scenarios, network management scenarios, and the like. Therefore, the target business scene is a business scene which is applied by the graph database test system and depends on the graph database.
in the embodiment of the application, in order to generate test data of a graph database, graph data meeting a target service scene can be generated according to the requirements of the target service scene. The graph data format satisfying the target service scenario may include, but is not limited to, a CSV (Comma-Separated Values) file format, a JSON (JavaScript Object Notation) file format, and the like.
Optionally, as shown in fig. 2, the specific steps of generating the graph data meeting the target service scenario according to the requirement of the target service scenario are as follows:
step 201, acquiring configuration information required for generating graph data according to the requirements of a target service scene; the configuration information comprises entity data mode definition information in graph data, scale definition information of each type of entity, definition information of a story scene template and relation density setting information.
In the embodiment of the application, in order to generate the graph data meeting the target service scene, firstly, the configuration information required for generating the graph data can be acquired according to the requirement of the target service scene; the configuration information may include entity data pattern definition information in the graph data, scale definition information of each type of entity, definition information of the story scenario template, and relationship density setting information. It is to be understood that the configuration information may be previously configured by a person skilled in the relevant art.
for example, the entity data mode definition information in the graph data in the configuration information may be customer information, account information, device information, and the like; the scale definition information of each type of corresponding entity can be that the scale of the customer information is 50 ten thousand, the scale of the account information is 100 ten thousand, and the scale of the equipment information is 10 ten thousand; the obtaining of the definition information of the story scenario template may be based on the story scenario template, where the story scenario template may include a simple story scenario template and a complex story scenario template, and for example, the simple story scenario template is: the customer A has an account C, and the definition information of the corresponding story scene template is as follows: customer A (owning) - -Account C; the complex story scene template is: account C transfers account M by using equipment D, and the definition information of the corresponding story scene template is as follows: account C (use) -device D (transfer)) account M.
In addition, in order to facilitate the generation of the relationship between each type of entity in the graph data, the relationship density setting information may be set according to the proportion of the entities with different degrees in the configuration information, for example: the out degree can be set to be 50% of the range of 0-10, 30% of the range of 10-100 and 20% of the range of 100-10000. Wherein out-degree represents the number of edges connecting other entities from the entity.
Step 202, generating entity data information according to the entity data mode definition information and the scale definition information of each type of entity in the configuration information.
further, after configuration information required for generating graph data is acquired, entity data information may be generated according to entity data pattern definition information and scale definition information of each type of entity in the configuration information.
For example, taking a transfer scenario as an example: the entity data mode definition information in the configuration information is client information, account information and equipment information, the scale definition information of each type of entity is that the scale of the client information is 50 thousands, the scale of the account information is 100 thousands and the scale of the equipment information is 10 thousands, so that the entity data mode definition information and the scale definition information of each type of entity in the configuration information can be used for generating the entity data information of 50 thousands of client information, 100 thousands of account information and 10 thousands of ATM equipment information.
And step 203, instantiating the story scene template into a plurality of story scene data correspondingly according to the definition information, the relation density setting information and the entity data information of the story scene template.
Specifically, the story scenario templates may be instantiated into a plurality of pieces of story scenario data according to definition information, relationship density setting information, and generated entity data information of the story scenario templates in the configuration information.
For example, assuming that the generated entity data information is "50 ten thousand customer information and 100 ten thousand account information", and assuming that the definition information of the story scenario template in the configuration information is "customer a (owning) -" account C ", and the relationship density setting information is" 50% of the set out degree in the interval of 0 to 10, 30% of the set out degree in the interval of 10 to 100, and 20% of the set out degree in the interval of 100 + 10000 ", the configured story scenario template may be instantiated into a plurality of pieces of completed story scenario data according to these information. Wherein the plurality of pieces of story scene data satisfy the following conditions: the plurality of story scenario data comprise 50 ten thousand customer entities and 100 ten thousand account entities, and the customer entities and the account entities meet the following story scenarios: some customer entity (owning) -some account entity; in the 50 ten thousand customer entities and the 100 ten thousand account entities, the proportion of the entity number with the out degree of 0-10 to the total entity number is 50%, the proportion of the entity number with the out degree of 10-100 to the total entity number is 30%, and the proportion of the entity number with the out degree of 100-10000 to the total entity number is 20%.
And step 204, determining the relation contained in the story scene template, and analyzing the plurality of story scene data into corresponding relation data according to the relation contained in the story scene template to obtain the graph data meeting the target service scene.
It can be understood that the story scene template includes the corresponding relationship between the entities in the configuration information, and therefore after the plurality of pieces of story scene data are acquired, the plurality of pieces of story scene data can be analyzed into corresponding relationship data according to the relationship included in the story scene template, and the corresponding relationship data obtained through analysis is used as the graph data meeting the target service scene, so that the graph data meeting the target service scene is obtained.
For example, a story scene template is used as follows: for example, account C (use) -device D (transfer)) -account M, the 2 types of relationships included in the story scenario template may be resolved according to the story scenario template, that is: the account uses the device, and the account transfers to the account. Then, according to the relation contained in the story scene template, the plurality of story scene data obtained after instantiation can be analyzed into specific relation data, so that graph data meeting the target service scene can be obtained.
In addition, it should be further noted that, in the embodiment of the present application, the data format generated in step 201 and 204 is a CSV, and if the user needs the generated data to be in a JSON format, the data in the CSV format is converted into a corresponding JSON format. In addition, since the data in the CSV format has no header attribute value, if the user needs the generated data to be the CSV, the corresponding entity attribute information needs to be initialized so as to correspondingly supplement the generated relational data with the attribute values of the respective entities.
Step 102, determining a test type for a graph database to be tested.
in the embodiment of the application, in order to further construct a complete test system of a graph data product, after graph data meeting a target business scene is generated, the test type of a graph database to be tested needs to be judged, and the test type of the graph database to be tested is determined. For example, the test type of the graph database to be tested can be determined according to the test requirement of the graph database to be tested. For example: when the test requirement of the graph database to be tested is as follows: when the graph database to be tested meets the specified storage target, determining the test type of the graph database to be tested as a storage test type according to the requirement; when the test requirement of the graph database to be tested is as follows: and when the graph database to be tested has the query analysis function, determining that the test type aiming at the graph database to be tested is the query analysis test type. It should be noted that the test type may include, but is not limited to, a storage test type and a query analysis test type. The storage test type can include but is not limited to batch offline data loading test, streaming data writing test and the like; query analysis test types may include, but are not limited to, basic query function tests, path analysis tests, centrality analysis tests, population analysis tests, and the like. And 103, generating test data suitable for the test type according to the test type and the graph data meeting the target service scene.
further, after generating the graph data meeting the target service scenario and determining the test type for the graph database to be tested, the test data suitable for the test type can be generated according to the test type and the graph data meeting the target service scenario.
It will be appreciated that the types of tests differ, as will the manner in which test data suitable for the test type is generated. For example, when the test type is a storage test type, the data preprocessing can be performed on the graph data meeting the target service scene according to the data input format supported by the graph database to be tested, so as to generate corresponding test data; when the test type is a query analysis test type, a corresponding graph retrieval grammar can be generated according to a preset test requirement, and specific request content corresponding to the graph retrieval grammar is generated to generate corresponding test data. Specific implementation can be seen in the description of the following embodiments.
And 104, testing the graph database to be tested according to the test data suitable for the test type.
Further, after the test data suitable for the test type is generated, the graph database to be tested is tested according to the test data suitable for the test type.
In order to be compatible with and support testing of multiple databases and to mask internal differences between different database systems, and to improve reusability of a database testing system, optionally, in an embodiment of the present application, the specific process of testing a database to be tested according to test data applicable to a test type may include the following steps: determining an adaptive application program interface for a graph database to be tested; and testing the graph database to be tested through the adaptive application program interface according to the test data suitable for the test type.
That is, adaptation development is performed according to the application program interface type of the graph database to be tested, and then the graph database to be tested is tested through the adaptation application program interface according to the test data suitable for the test type. For example, application program interfaces for graph databases can be divided into three categories, such as: the service acquisition application program interface, the data loading application program interface and the query application program interface. After the three types of application program interfaces are correspondingly supported, different database systems can be accessed by unifying the application program interfaces, so that the test of various database systems can be supported, and the internal difference among different database systems can be shielded.
To better improve the efficiency and quality of the test, the index data generated by each test may be analyzed. Therefore, when the test of the graph database to be tested is completed, the index data generated by the test can be collected. It should be noted that, the test types are different, and the index data generated by the test is also different, and when the test type is the storage test type, the index data generated by the test may include, but is not limited to: the success rate and throughput of data loading, and the occupation of disk and memory space after loading, etc. when the test type is the query analysis test type, the index data generated by the test may include but is not limited to: success rate of query analysis, time-consuming situation, concurrency performance, etc.
in addition, it should be noted that, in order to further improve the testing efficiency, the environment data information of the server in the process of testing the graph database to be tested needs to be known at any time, so that the environment data information of the server where the graph database to be tested is located needs to be collected in the process of testing the graph database to be tested. Such as: and monitoring the health state of the service, the existence of a core file, the use condition of a memory, the use condition of a disk and the use condition of a central processing unit in the test process, and respectively giving the consumption conditions of system resources and the like in different test scenes.
In the embodiment of the application, in order to enhance readability of the test result, after the index data and the environment data generated by the current test are collected, optionally, the test result for the graph database to be tested is generated according to the collected index data and environment data information generated by the current test, and the test result is output.
that is, after the index data and the environmental data generated by the current test are collected, the test result can be integrated according to the collected index data and the collected environmental data information generated by the current test, and the integrated test result is used as the test result of the graph database to be tested, so that the readability of the test result is high.
According to the graph database testing method, graph data meeting the target business scene are generated according to the requirements of the target business scene; determining a test type for a graph database to be tested; generating test data suitable for the test type according to the test type and the graph data meeting the target service scene; and testing the graph database to be tested according to the test data suitable for the test type. The graph data meeting different service scenes are dynamically generated according to different service scene requirements, and the graph database to be tested is tested based on the graph data meeting different service scenes, so that the problem of graph data testing in the prior art is solved, the function of testing the graph database is realized, the complex relationships of various scenes can be covered, the performance difference of a graph database system in different scenes can be realized, the application scenes of the testing scheme of the embodiment of the application are greatly expanded, and the reusability of the testing system is improved. In addition, the embodiment of the application provides the chart data generated based on the story contextual model, and the problem of generating complex relation data of the chart database in various service scenes is solved. Finally, the application effectively integrates the test of various graph database products through the adaptation of the application program interface of the graph database, greatly expands the application scene of the test scheme and improves the system reusability.
It should be noted that, the test types are different, and the manner used for generating the test data suitable for the test types is also different, and two different implementations will be given below in conjunction with fig. 3 and 4.
FIG. 3 is a flow diagram of a graph database testing method according to one embodiment of the present application. It should be noted that, the graph database testing method according to the embodiment of the present application is described with the test type as the storage test type, and as shown in fig. 3, the graph database testing method may include:
Step 301, generating graph data meeting the target service scene according to the requirements of the target service scene.
step 302, determining the test type of the graph database to be tested as a storage test type.
step 303, determining a data input format supported by the graph database to be tested.
Step 304, according to the data input format supported by the graph database to be tested, data preprocessing is carried out on the graph data meeting the target business scene, and test data suitable for the storage test type are generated.
It is to be understood that the data of the graph data satisfying the target service scenario may be, but is not limited to, offline graph data, and the offline graph data format may include, but is not limited to, CSV, JSON format, and the like. Therefore, when the graph database to be tested of the storage test type is tested, the data input format supported by the graph database to be tested needs to be determined, and then the graph data meeting the target service scene is subjected to data preprocessing according to the data input format supported by the graph database to be tested so as to generate the test data suitable for the storage test type.
Step 305, testing the graph database to be tested according to the test data suitable for the test type.
Specifically, according to the test data suitable for the test type, corresponding test data can be executed, and the graph database to be tested is tested. Executing the corresponding test data may include, but is not limited to, bulk data loading, streaming data writing, and the like.
according to the graph database testing method, graph data meeting the target business scene are generated according to the requirements of the target business scene; determining the test type of a graph database to be tested as a storage test type; determining a data input format supported by a graph database to be tested; according to a data input format supported by a graph database to be tested, carrying out data preprocessing on graph data meeting a target service scene to generate test data suitable for a storage test type; and testing the graph database to be tested according to the test data suitable for the test type. The graph data meeting different service scenes are dynamically generated according to different service scene requirements, and the graph database to be tested is tested based on the graph data meeting different service scenes, so that the problem of graph data testing in the prior art is solved, the function of testing the graph database is realized, the complex relationships of various scenes can be covered, the performance difference of a graph database system in different scenes can be realized, the application scenes of the testing scheme of the embodiment of the application are greatly expanded, and the reusability of the testing system is improved.
FIG. 4 is a flow diagram of a method for graph database testing according to another embodiment of the present application. It should be noted that, the graph database testing method according to the embodiment of the present application is described in a case where the test type is a query analysis test type, as shown in fig. 4, the graph database testing method may include:
Step 401, generating graph data meeting the target service scene according to the requirements of the target service scene.
Step 402, determining the test type of the graph database to be tested as a query analysis test type.
Step 403, generating a corresponding graph retrieval grammar according to the preset test requirement.
Step 404, generating specific request content of the corresponding graph retrieval grammar according to the graph data meeting the target service scene, and taking the specific request content of the corresponding graph retrieval grammar as test data suitable for the query analysis test type.
In the embodiment of the present application, when testing a graph database to be tested of a query analysis test type, a corresponding graph retrieval grammar may be generated according to a preset test requirement, for example: out syntax of neighbor query. And then, generating specific request content corresponding to the retrieval grammar, such as an entity id list which specifically needs to be subjected to neighbor query, according to the graph data and the graph retrieval grammar which meet the target service scene. Then, the specific request content of the corresponding graph retrieval grammar is used as test data suitable for the query analysis test type. The preset test requirement may be, but is not limited to, a test requirement of a user.
Step 405, testing the graph database to be tested according to the test data suitable for the test type.
Specifically, according to the test data suitable for the test type, corresponding test data can be executed, and the graph database to be tested is tested. Then, in order to further confirm the correctness of the test result, after the graph database test is completed, an interface difference (Diff for short) test may be performed on the test result and the baseline result, that is, whether the returned content of the same interface under different versions or different environments meets expectations may be compared, so that the correctness of the result may be verified.
according to the graph database testing method, graph data meeting the target business scene are generated according to the requirements of the target business scene; determining the test type of a graph database to be tested as a query analysis test type; generating a corresponding graph retrieval grammar according to a preset test requirement; generating specific request content of the corresponding graph retrieval grammar according to graph data meeting the target service scene, and taking the specific request content of the corresponding graph retrieval grammar as test data suitable for the query analysis test type; and testing the graph database to be tested according to the test data suitable for the test type. The graph data meeting different service scenes are dynamically generated according to different service scene requirements, and the graph database to be tested is tested based on the graph data meeting different service scenes, so that the problem of graph data testing in the prior art is solved, the function of testing the graph database is realized, the complex relationships of various scenes can be covered, the performance difference of a graph database system in different scenes can be realized, the application scenes of the testing scheme of the embodiment of the application are greatly expanded, and the reusability of the testing system is improved.
corresponding to the graph database testing methods provided in the above embodiments, an embodiment of the present application further provides a graph database testing system, and since the graph database testing system provided in the embodiment of the present application corresponds to the graph database testing methods provided in the above embodiments, the implementation of the graph database testing method is also applicable to the graph database testing system provided in the embodiment, and will not be described in detail in the embodiment. FIG. 5 is a block diagram of a graph database testing system according to one embodiment of the present application. As shown in fig. 5, the graph database testing system includes: a graph data generation module 510 and a graph database testing module 520.
The graph data generating module 510 is configured to generate graph data meeting a target service scenario according to a target service scenario requirement;
The graph database testing module 520 is configured to determine a testing type for the graph database to be tested, generate testing data suitable for the testing type according to the testing type and the graph data meeting the target service scenario, and test the graph database to be tested according to the testing data suitable for the testing type.
As a possible implementation manner of the embodiment of the present application, the graph data generating module 510 is specifically configured to: acquiring configuration information required for generating graph data according to the requirements of a target service scene; the configuration information comprises entity data mode definition information, scale definition information of each type of entity, definition information of a story scene template and relation density setting information in graph data; generating entity data information according to entity data mode definition information and scale definition information of each type of entity in the configuration information; according to definition information, relation density setting information and the entity data information of the story scene template, instantiating the story scene template into a plurality of story scene data; and determining the relation contained in the story scene template, and analyzing the plurality of story scene data into corresponding relation data according to the relation contained in the story scene template to obtain the graph data meeting the target service scene.
As a possible implementation manner of the embodiment of the present application, the test type includes a storage test type and a query analysis test type.
As a possible implementation manner of the embodiment of the present application, as shown in fig. 6, on the basis of fig. 5, the graph database testing module 520 includes: a graph storage test unit 521 and a graph query analysis test unit 522.
The graph storage testing unit 521 is configured to determine a data input format supported by a graph database to be tested, perform data preprocessing on graph data meeting a target service scenario according to the data input format supported by the graph database to be tested, generate testing data suitable for a storage testing type, and test the graph database to be tested according to the testing data suitable for the storage testing type. The graph query analysis testing unit 522 is configured to generate a corresponding graph retrieval syntax according to a preset testing requirement, generate specific request content corresponding to the graph retrieval syntax according to graph data meeting a target service scenario, use the specific request content corresponding to the graph retrieval syntax as testing data applicable to a query analysis testing type, and test a graph database to be tested according to the testing data applicable to the query analysis testing type.
As a possible implementation manner of the embodiment of the present application, as shown in fig. 7, on the basis of fig. 6, the graph database testing system further includes: an index data collection module 530.
Specifically, the index data collection module 530 is configured to collect index data generated by the current test when the test on the graph database to be tested is completed.
as a possible implementation manner of the embodiment of the present application, as shown in fig. 8, on the basis of fig. 7, the graph database testing system further includes: the environmental data information monitoring module 540.
specifically, the environmental data information monitoring module 540 is configured to collect environmental data information of a server where a graph database to be tested is located in a process of testing the graph database to be tested.
As a possible implementation manner of the embodiment of the present application, as shown in fig. 9, on the basis of fig. 8, the graph database testing system further includes: a test result generation module 550.
Specifically, the test result generating module 550 is configured to generate a test result for the graph database to be tested according to the collected index data and the collected environmental data information generated by the current test, and output the test result.
As a possible implementation manner of the embodiment of the present application, as shown in fig. 10, on the basis of fig. 5, the graph database testing system further includes: a graph database system access module 560.
Specifically, the graph database system access module 560 has an adaptive application program interface for multiple graph databases; the graph database testing module 520 is specifically configured to: and determining an adaptive application program interface aiming at the graph database to be tested, and testing the graph database to be tested through the adaptive application program interface according to the test data suitable for the test type.
According to the graph database testing system, graph data meeting the target business scene are generated according to the requirements of the target business scene; determining the test type of a graph database to be tested as a query analysis test type; generating a corresponding graph retrieval grammar according to a preset test requirement; generating specific request content of the corresponding graph retrieval grammar according to graph data meeting the target service scene, and taking the specific request content of the corresponding graph retrieval grammar as test data suitable for the query analysis test type; and testing the graph database to be tested according to the test data suitable for the test type. The graph data meeting different service scenes are dynamically generated according to different service scene requirements, and the graph database to be tested is tested based on the graph data meeting different service scenes, so that the problem of graph data testing in the prior art is solved, the function of testing the graph database is realized, the complex relationships of various scenes can be covered, the performance difference of a graph database system in different scenes can be realized, the application scenes of the testing scheme of the embodiment of the application are greatly expanded, and the reusability of the testing system is improved.
in order to implement the foregoing embodiments, an apparatus based on a graph database testing method is further provided in the embodiments of the present application, and fig. 11 is a schematic structural diagram of the apparatus based on the graph database testing method provided in the embodiments of the present application. The device based on the graph database test method comprises the following steps: memory 1001, processor 1002, and computer programs stored on memory 1001 and executable on processor 1002.
The processor 1002, when executing the program, implements the graph database testing method provided in the above-described embodiments.
Further, the device based on the graph database test method further comprises:
A communication interface 1003 for communicating between the memory 1001 and the processor 1002.
A memory 1001 for storing computer programs that may be run on the processor 1002.
Memory 1001 may include high-speed RAM memory and may also include non-volatile memory (e.g., at least one disk memory).
the processor 1002 is configured to implement the graph database testing method according to the above embodiments when executing the program.
If the memory 1001, the processor 1002, and the communication interface 1003 are implemented independently, the communication interface 1003, the memory 1001, and the processor 1002 may be connected to each other through a bus and perform communication with each other. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (Extended Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 11, but this is not intended to represent only one bus or type of bus.
Optionally, in a specific implementation, if the memory 1001, the processor 1002, and the communication interface 1003 are integrated on one chip, the memory 1001, the processor 1002, and the communication interface 1003 may complete communication with each other through an internal interface.
The processor 1002 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement embodiments of the present Application.
In order to implement the above embodiments, the present application further proposes a computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the graph database testing method according to the embodiments of the present application.
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 are not necessarily intended to 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. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
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 steps of a custom logic function or process, and alternate implementations are included within the scope of the preferred embodiment of the present application 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.
The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
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. 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. 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 (19)
1. A method for testing a graph database, comprising:
Generating graph data meeting the target service scene according to the requirements of the target service scene;
Determining a test type for a graph database to be tested;
Generating test data suitable for the test type according to the test type and the graph data meeting the target service scene;
And testing the graph database to be tested according to the test data suitable for the test type.
2. the graph database testing method according to claim 1, wherein said generating graph data satisfying a target business scenario according to a target business scenario requirement comprises:
Acquiring configuration information required for generating the graph data according to the target service scene requirement; wherein the configuration information includes entity data mode definition information, scale definition information of each type of entity, definition information of a story scene template, and relation density setting information in the graph data;
Generating entity data information according to the entity data mode definition information and the scale definition information of each type of entity in the configuration information;
Instantiating the story scene template into a plurality of story scene data according to the definition information of the story scene template, the relation density setting information and the entity data information;
And determining the relation contained in the story scene template, and analyzing the plurality of story scene data into corresponding relation data according to the relation contained in the story scene template to obtain the graph data meeting the target service scene.
3. A method for testing a graph database according to claim 1, wherein said test types include a storage test type and a query analysis test type.
4. A graph database testing method according to claim 3, wherein when said test type is a storage test type, said generating test data suitable for said test type based on said test type and said graph data satisfying said target business scenario comprises:
Determining a data input format supported by the graph database to be tested;
and according to a data input format supported by the graph database to be tested, carrying out data preprocessing on the graph data meeting the target service scene to generate test data suitable for the storage test type.
5. A graph database testing method according to claim 3, wherein when said test type is a query analysis test type, said generating test data suitable for said test type based on said test type and said graph data satisfying said target business scenario comprises:
generating a corresponding graph retrieval grammar according to a preset test requirement;
and generating specific request content of the corresponding graph retrieval grammar according to the graph data meeting the target service scene, and taking the specific request content of the corresponding graph retrieval grammar as test data suitable for the query analysis test type.
6. A graph database testing method according to any one of claims 1-5, further comprising:
And when the test of the graph database to be tested is finished, collecting index data generated by the test.
7. A method for testing a graph database according to claim 6, further comprising:
and in the process of testing the graph database to be tested, collecting the environment data information of a server where the graph database to be tested is located.
8. A method for testing a graph database according to claim 7, further comprising:
And generating a test result aiming at the graph database to be tested according to the collected index data generated by the test and the collected environment data information, and outputting the test result.
9. a method for testing a graph database according to claim 1, wherein said testing said graph database to be tested according to said test data applicable to said test type comprises:
Determining an adaptive application program interface for the graph database to be tested;
And testing the graph database to be tested through the adaptive application program interface according to the test data suitable for the test type.
10. A graph database testing system, comprising:
The graph data generation module is used for generating graph data meeting the target service scene according to the requirements of the target service scene;
the graph database testing module is used for determining the testing type of the graph database to be tested, generating testing data suitable for the testing type according to the testing type and the graph data meeting the target service scene, and testing the graph database to be tested according to the testing data suitable for the testing type.
11. the graph database testing system according to claim 10, wherein said graph data generating module is specifically configured to:
Acquiring configuration information required for generating the graph data according to the target service scene requirement; wherein the configuration information includes entity data mode definition information, scale definition information of each type of entity, definition information of a story scene template, and relation density setting information in the graph data;
Generating entity data information according to the entity data mode definition information and the scale definition information of each type of entity in the configuration information;
Instantiating the story scene template into a plurality of story scene data according to the definition information of the story scene template, the relation density setting information and the entity data information;
and determining the relation contained in the story scene template, and analyzing the plurality of story scene data into corresponding relation data according to the relation contained in the story scene template to obtain the graph data meeting the target service scene.
12. A graph database testing system as claimed in claim 10, wherein said test types include a storage test type and a query analysis test type.
13. A graph database testing system according to claim 12, wherein said graph database testing module comprises:
The graph storage testing unit is used for determining a data input format supported by the graph database to be tested, performing data preprocessing on the graph data meeting the target service scene according to the data input format supported by the graph database to be tested, generating testing data suitable for the storage testing type, and testing the graph database to be tested according to the testing data suitable for the storage testing type;
And the graph query analysis testing unit is used for generating a corresponding graph retrieval grammar according to a preset testing requirement, generating specific request content of the corresponding graph retrieval grammar according to the graph data meeting the target service scene, taking the specific request content of the corresponding graph retrieval grammar as the testing data suitable for the query analysis testing type, and testing the graph database to be tested according to the testing data suitable for the query analysis testing type.
14. A graph database testing system according to any of claims 10-13, further comprising:
And the index data collection module is used for collecting the index data generated by the current test when the test of the graph database to be tested is completed.
15. a graph database testing system as claimed in claim 14, further comprising:
and the environment data information monitoring module is used for collecting the environment data information of the server where the graph database to be tested is located in the process of testing the graph database to be tested.
16. A graph database testing system as claimed in claim 15, further comprising:
and the test result generating module is used for generating a test result aiming at the graph database to be tested according to the collected index data generated by the current test and the collected environment data information, and outputting the test result.
17. a graph database testing system as claimed in claim 10, further comprising: a graph database system access module; the map database system access module is provided with adaptive application program interfaces of various map databases;
Wherein the graph database testing module is specifically configured to: and determining an adaptive application program interface aiming at the graph database to be tested, and testing the graph database to be tested through the adaptive application program interface according to the test data suitable for the test type.
18. An apparatus based on a graph database testing method, comprising: memory, processor and computer program stored on the memory and executable on the processor, when executing the computer program, implementing a graph database testing method according to any of claims 1 to 9.
19. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out a method for graph database testing according to any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910709047.8A CN110554958B (en) | 2019-08-01 | 2019-08-01 | Graph database testing method, system, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910709047.8A CN110554958B (en) | 2019-08-01 | 2019-08-01 | Graph database testing method, system, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110554958A true CN110554958A (en) | 2019-12-10 |
| CN110554958B CN110554958B (en) | 2023-04-04 |
Family
ID=68736839
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910709047.8A Active CN110554958B (en) | 2019-08-01 | 2019-08-01 | Graph database testing method, system, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110554958B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111259205A (en) * | 2020-01-15 | 2020-06-09 | 北京百度网讯科技有限公司 | Graph database traversal method, device, equipment and storage medium |
| CN111679990A (en) * | 2020-06-17 | 2020-09-18 | 北京字节跳动网络技术有限公司 | Test data generation method and device, readable medium and electronic equipment |
| CN111858506A (en) * | 2020-06-30 | 2020-10-30 | 北京百度网讯科技有限公司 | Test data processing method and device, electronic equipment and storage medium |
| CN112015645A (en) * | 2020-08-27 | 2020-12-01 | 云账户技术(天津)有限公司 | Function test method and device of web system and electronic equipment |
| CN112073709A (en) * | 2020-07-27 | 2020-12-11 | 武汉旷视金智科技有限公司 | Test data generation method and device and electronic equipment |
| CN112181816A (en) * | 2020-09-22 | 2021-01-05 | 建信金融科技有限责任公司 | Interface testing method and device based on scene, computer equipment and medium |
| CN112380167A (en) * | 2020-11-17 | 2021-02-19 | 深圳市和讯华谷信息技术有限公司 | Batch data verification method and device, computer equipment and storage medium |
| CN112882956A (en) * | 2021-03-30 | 2021-06-01 | 中信银行股份有限公司 | Method and device for automatically generating full-scene automatic test case through data combination calculation, storage medium and electronic equipment |
| CN113656315A (en) * | 2021-08-19 | 2021-11-16 | 北京百度网讯科技有限公司 | Data testing method and device, electronic equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103425578A (en) * | 2012-05-18 | 2013-12-04 | 日立汽车系统株式会社 | Test support system, test support method, method and program for testing support |
| CN103729361A (en) * | 2012-10-12 | 2014-04-16 | 百度在线网络技术（北京）有限公司 | Method and device for testing performance of database |
| CN105224458A (en) * | 2015-10-09 | 2016-01-06 | 上海瀚银信息技术有限公司 | A kind of database method of testing and system |
| US20180089252A1 (en) * | 2016-09-28 | 2018-03-29 | Linkedin Corporation | Verifying correctness in graph databases |
| CN107894953A (en) * | 2017-11-21 | 2018-04-10 | 中国银行股份有限公司 | A kind of generation method and device of Bank application test data |
| CN109254909A (en) * | 2018-08-06 | 2019-01-22 | 四川蜀天梦图数据科技有限公司 | A kind of test big drawing generating method and system |
| CN109800147A (en) * | 2018-12-14 | 2019-05-24 | 平安普惠企业管理有限公司 | A kind of test cases generation method and terminal device |
-
2019
- 2019-08-01 CN CN201910709047.8A patent/CN110554958B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103425578A (en) * | 2012-05-18 | 2013-12-04 | 日立汽车系统株式会社 | Test support system, test support method, method and program for testing support |
| CN103729361A (en) * | 2012-10-12 | 2014-04-16 | 百度在线网络技术（北京）有限公司 | Method and device for testing performance of database |
| CN105224458A (en) * | 2015-10-09 | 2016-01-06 | 上海瀚银信息技术有限公司 | A kind of database method of testing and system |
| US20180089252A1 (en) * | 2016-09-28 | 2018-03-29 | Linkedin Corporation | Verifying correctness in graph databases |
| CN107894953A (en) * | 2017-11-21 | 2018-04-10 | 中国银行股份有限公司 | A kind of generation method and device of Bank application test data |
| CN109254909A (en) * | 2018-08-06 | 2019-01-22 | 四川蜀天梦图数据科技有限公司 | A kind of test big drawing generating method and system |
| CN109800147A (en) * | 2018-12-14 | 2019-05-24 | 平安普惠企业管理有限公司 | A kind of test cases generation method and terminal device |
Non-Patent Citations (3)
| Title |
|---|
| RAQUEL BLANCO 等: ""Modelling Test Views for Graph Database Applications"", 《IEEE LATIN AMERICA TRANSACTIONS》 * |
| 吕冰清: ""大规模图数据库中的模式查询算法研究"", 《中国博士学位论文全文数据库信息科技辑》 * |
| 德哥: ""使用facebook linkbench 测试PostgreSQL社交关系图谱场景性能"", 《HTTPS://DEVELOPER.ALIYUN.COM/ARTICLE/60731》 * |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111259205A (en) * | 2020-01-15 | 2020-06-09 | 北京百度网讯科技有限公司 | Graph database traversal method, device, equipment and storage medium |
| CN111259205B (en) * | 2020-01-15 | 2023-10-20 | 北京百度网讯科技有限公司 | Graph database traversal method, device, equipment and storage medium |
| CN111679990A (en) * | 2020-06-17 | 2020-09-18 | 北京字节跳动网络技术有限公司 | Test data generation method and device, readable medium and electronic equipment |
| CN111679990B (en) * | 2020-06-17 | 2023-08-08 | 北京字节跳动网络技术有限公司 | Test data generation method and device, readable medium and electronic equipment |
| CN111858506A (en) * | 2020-06-30 | 2020-10-30 | 北京百度网讯科技有限公司 | Test data processing method and device, electronic equipment and storage medium |
| CN111858506B (en) * | 2020-06-30 | 2024-03-22 | 北京百度网讯科技有限公司 | Test data processing method and device, electronic equipment and storage medium |
| CN112073709B (en) * | 2020-07-27 | 2023-04-14 | 武汉旷视金智科技有限公司 | Test data generation method and device and electronic equipment |
| CN112073709A (en) * | 2020-07-27 | 2020-12-11 | 武汉旷视金智科技有限公司 | Test data generation method and device and electronic equipment |
| CN112015645A (en) * | 2020-08-27 | 2020-12-01 | 云账户技术(天津)有限公司 | Function test method and device of web system and electronic equipment |
| CN112181816B (en) * | 2020-09-22 | 2023-06-02 | 建信金融科技有限责任公司 | Scene-based interface testing method and device, computer equipment and medium |
| CN112181816A (en) * | 2020-09-22 | 2021-01-05 | 建信金融科技有限责任公司 | Interface testing method and device based on scene, computer equipment and medium |
| CN112380167A (en) * | 2020-11-17 | 2021-02-19 | 深圳市和讯华谷信息技术有限公司 | Batch data verification method and device, computer equipment and storage medium |
| CN112882956A (en) * | 2021-03-30 | 2021-06-01 | 中信银行股份有限公司 | Method and device for automatically generating full-scene automatic test case through data combination calculation, storage medium and electronic equipment |
| CN112882956B (en) * | 2021-03-30 | 2024-04-16 | 中信银行股份有限公司 | Method and device for automatically generating full-scene automatic test cases through data combination calculation, storage medium and electronic equipment |
| CN113656315A (en) * | 2021-08-19 | 2021-11-16 | 北京百度网讯科技有限公司 | Data testing method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110554958B (en) | 2023-04-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110554958B (en) | Graph database testing method, system, device and storage medium | |
| CN111221726A (en) | Test data generation method and device, storage medium and intelligent equipment | |
| CN111552509B (en) | Method and device for determining dependency relationship between interfaces | |
| US8676627B2 (en) | Vertical process merging by reconstruction of equivalent models and hierarchical process merging | |
| CN110956269A (en) | Data model generation method, device, equipment and computer storage medium | |
| CN110727580A (en) | Response data generation method, full-flow interface data processing method and related equipment | |
| CN113268403B (en) | Time series analysis and prediction method, device, equipment and storage medium | |
| CN111353754A (en) | Method and device for generating flow template, electronic equipment and readable storage medium | |
| CN112416369B (en) | Intelligent deployment method oriented to heterogeneous mixed environment | |
| CN113238740A (en) | Code generation method, code generation device, storage medium, and electronic apparatus | |
| CN112559525A (en) | Data checking system, method, device and server | |
| CN110188033B (en) | Data detection device, method, computer device, and computer-readable storage medium | |
| CN115345600B (en) | RPA flow generation method and device | |
| CN116225690A (en) | Memory multidimensional database calculation load balancing method and system based on docker | |
| CN115423040A (en) | User portrait identification method and AI system of interactive marketing platform | |
| CN115469915A (en) | Method, device, equipment and medium for managing API (application program interface) based on tree structure classification | |
| CN111966597B (en) | Test data generation method and device | |
| CN110177006B (en) | Node testing method and device based on interface prediction model | |
| CN113703739A (en) | Cross-language fusion computing method, system and terminal based on omiga engine | |
| CN113238940A (en) | Interface test result comparison method, device, equipment and storage medium | |
| CN113806205A (en) | Software performance testing method and device, electronic equipment and readable storage medium | |
| CN110851254A (en) | Equipment production method, device, server and storage medium based on microservice | |
| CN111400219A (en) | Interface adapter and electronic equipment thereof | |
| CN113570333B (en) | Process design method suitable for integration | |
| CN115237817B (en) | Dynamic model detection method and device for data exchange sharing low-code process |
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 |