CN113535352A - Testing method for generating blood relationship based on scheduling configuration to realize automatic batch running - Google Patents
Testing method for generating blood relationship based on scheduling configuration to realize automatic batch running Download PDFInfo
- Publication number
- CN113535352A CN113535352A CN202110716454.9A CN202110716454A CN113535352A CN 113535352 A CN113535352 A CN 113535352A CN 202110716454 A CN202110716454 A CN 202110716454A CN 113535352 A CN113535352 A CN 113535352A
- Authority
- CN
- China
- Prior art keywords
- batch
- relationship
- program
- scheduling configuration
- running
- 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
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
-
- 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
- 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
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention belongs to the field of software development and software testing, and particularly relates to a testing method for realizing automatic batch running based on a bloody border relationship generated by scheduling configuration, aiming at solving the problems of long batch running time, complex operation and low efficiency in the testing process in the prior art; the invention solves the problems by adopting the following technical scheme: acquiring actual scheduling configuration content of the current production environment; acquiring configuration change frequency according to the online frequency; determining a synchronous frequency according to the configuration change frequency; synchronizing the production scheduling configuration content to the test environment according to the configuration synchronization frequency; generating a blood relationship according to the synchronized scheduling configuration content; packaging the automatic batch program according to the relationship of the blood relationship; calling the automatic batch running program to execute by the calling terminal program; through the encapsulation and calling of the batch running program, the calling at any time can be supported, and the trigger time limit is removed. And the calling mode is simple and unique, the batch running execution complexity is reduced, flexible batch running is finally realized, and batch running is completed in the minimum time.
Description
Technical Field
The invention belongs to the field of software development and software testing, and particularly relates to a testing method for realizing automatic batch running based on a relationship of a blood relationship generated by scheduling configuration.
Background
Enterprises establish big data systems, and big data are used for analyzing decisions. A data warehouse is required to be built firstly for summarizing a plurality of data source data, and hierarchical ETL processing is carried out to finally obtain target data for each service scene.
The ETL processing often involves dependency relationships, the dependent input in the data processing process is the corresponding blood margin, and all blood margin relationships are formed through layer-by-layer dependence or layer-by-layer dependence.
Because of the complicated dependency, the program execution needs to be executed in a dependent order, and thus the task configuration needs to be uniformly performed by the scheduling system, and the task execution needs to be uniformly allocated by the scheduling system.
Most of the bottom-layer task execution modes of the existing scheduling system are time triggering, the time triggering is limited in the test process, the test cannot be supported at any time, and if the test is performed temporarily, all task triggering time needs to be modified manually. The test process has long batch running time, complex operation and low efficiency.
Disclosure of Invention
The invention provides a test method for realizing automatic batch running based on a scheduling configuration generation blooding relationship, which aims to solve the problems of long batch running execution time, complex operation and low efficiency in the test process in the prior art.
In order to achieve the purpose, the invention provides the following technical scheme:
a test method for realizing automatic batch running based on a relationship of a blood relationship generated by scheduling configuration comprises the following steps:
step 1: acquiring actual scheduling configuration content of the current production environment;
step 2: acquiring configuration change frequency according to the online frequency; determining a synchronous frequency according to the configuration change frequency;
and step 3: synchronizing the production scheduling configuration content to the test environment according to the configuration synchronization frequency;
and 4, step 4: generating a blood relationship according to the synchronized scheduling configuration content in the step 3;
and 5: packaging the automatic batch program according to the relationship of the blood relationship;
step 6: calling the automatic batch running program to execute by the calling terminal program;
and 7: performing test checking on the result after batch running;
and 8: and (4) summarizing the execution result and the problem repair result in the step (7) and compiling a quality report.
Compared with the prior art, the invention has the beneficial effects that: 1. by synchronizing the production scheduling configuration to the test environment, the scheduling configuration is guaranteed to be updated timely and the completeness and effectiveness of the scheduling configuration are guaranteed.
2. The blood relationship is generated through configuration, the minimum complete batch program set can be obtained according to the needs facing the target file, and the minimum complete batch program set can not be missed or repeated.
3. Through the encapsulation and calling of the batch running program, the calling at any time can be supported, and the trigger time limit is removed. And the calling mode is simple and unique, the batch running execution complexity is reduced, flexible batch running is finally realized, and batch running is completed in the minimum time.
4. Through the packaging and calling of the batch running program, the concurrency number can be flexibly adjusted, a CPU is fully utilized, and the batch running execution efficiency is improved.
5. The batch running execution process can be simplified and the batch running complexity is reduced by calling the end program at the same time.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The following describes in detail the preferred embodiments of the present invention.
A test method for realizing automatic batch running based on a relationship of a blood relationship generated by scheduling configuration comprises the following steps:
step 1: acquiring actual scheduling configuration content of the current production environment; selecting a data synchronization mode according to the storage form of the actual scheduling configuration content;
step 2: acquiring configuration change frequency according to the online frequency; determining a synchronous frequency according to the configuration change frequency; the synchronous change frequency is higher than the configuration change frequency so as to ensure that the configuration change can be synchronized to the detection environment in time; the synchronization time should be later than the change time to avoid that the change does not happen before the synchronization; for example: if the change configuration frequency is changed on monday and three weeks, the synchronous configuration frequency can be two or four weeks per week.
And step 3: synchronizing the production scheduling configuration content to the test environment according to the configuration synchronization frequency;
the step 3 comprises a step 3.1: determining a storage position of the scheduling configuration of the test environment;
step 3.2: configuring a timing synchronization task according to the synchronization frequency;
step 3.3: the timing synchronization task runs to a point to be executed, and the synchronization action is triggered to be executed when the point is reached;
step 3.4: detecting whether the configuration contents of the test environment and the generation environment are the same or not, and if not, continuing to execute the synchronous operation in the step 3; if yes, executing step 4.
And 4, step 4: generating a blood relationship according to the synchronized scheduling configuration content in the step 3;
the generation of the blood relationship in step 4 comprises the following steps:
step 4.1: reading the contents of all scheduling configurations; reading all configuration contents, namely reading all newly synchronized configurations in a scheduling system, including the contents of a new scheduling configuration and the contents of an old scheduling configuration;
step 4.2: determining a unique attribute of the task;
step 4.3: determining the unique attributes of all target tasks of the tested program;
step 4.4: extracting unique attributes of the preposed tasks according to the unique attributes of each target task;
step 4.5: continuously extracting the unique attribute of the preposed task in the step 4.4;
step 4.6: step 4.5 is executed circularly; until all task unique attributes of the bottommost layer are extracted;
step 4.7: arranging all the extracted unique attributes of the tasks in a reverse order according to the extraction sequence, and obtaining the blood relationship of each target task;
step 4.8: traversing all the unique attributes of the target tasks in the step 4.3, and sequentially executing the step 4.4 to the step 4.7; the blood relationship of all target tasks can be obtained;
step 4.9: aiming at the blood relationship of all target tasks, if the same dependency relationship exists, merging, and reserving after merging; if the relationship of the same layer dependency exists, the same layer dependency needs to be executed separately.
And 5: packaging the automatic batch program according to the relationship of the blood relationship;
the step 5 comprises the following steps: step 5.1: obtaining a batch running program to be executed according to a one-to-one mapping relation among different task attributes; the different task attributes comprise task numbers, task names and task execution programs; therefore, in step 5.1, according to the one-to-one mapping relationship between the task attributes, it can be understood as a one-to-one mapping relationship between the task number, the task name and the task execution program.
Step 5.2: determining a program language based on the program name suffix of the batch program to be executed, which is acquired in the step 5.1, so as to determine a batch program execution command;
step 5.3: and packaging each batch program execution command into different files in a hierarchical manner according to the blooding margin dependency relationship sequence.
Step 6: calling the automatic batch running program to execute by the calling terminal program;
the step 6 comprises the following steps: step 6.1: determining a calling end program code language;
step 6.2: determining functions to be realized by the calling terminal program based on the file contents packaged in the step 5.3; the file content packaged in the step 5.3 is a batch command; the calling terminal program supports a starting batch starting command; meanwhile, in order to realize the personalized batch running function, other configuration parameters can be designed in the batch running command, such as a concurrency parameter used for adjusting CPU utilization rate, and a date parameter used for determining batch running date.
According to the step 4.9, the dependency relationship of the same layer needs to be separately executed; according to the step 5.3, according to the sequence of the blood-margin dependency relationship, hierarchically packaging the execution command of each batch program into different files; preferably, step 6.2 involves processing of batch runs belonging to the same floor but having no dependencies; the invention aims at batch running programs which are on the same layer and have no dependency relationship with each other, and can reduce the execution time and improve the efficiency by concurrent execution.
Step 6.3: executing the batch running program according to the calling end program determined in the step 6.2 and the running mode of the calling end program;
step 6.4: if the batch running process is executed with errors, positioning and correcting the error reasons;
step 6.5: evaluating the concurrency number according to the resources and the consumed time and adjusting the concurrency number; the utilization rate of the CPU is maximized, and the maximum batch is run in the least time.
And 7: performing test checking on the result after batch running;
the step 7 comprises the following steps: step 7.1: compiling a test case;
step 7.2: after the batch running is completed in the step 6, performing test check on the batch running result according to the test case compiling content, and marking whether the test case passes or not;
step 7.3: and 7.2, if the test core fails, positioning the cause of the problem, and performing bug classification according to the influence range and importance of the problem.
And 8: and (4) summarizing the execution result and the problem repair result in the step (7) and compiling a quality report.
The explanation about the unique attributes in step 4 is as follows: the unique attribute represents an attribute that does not produce duplicates; for example, the task number is used as the unique attribute, and the generation of the blood relationship in the corresponding step 4 comprises the following steps:
step 4.1: reading the contents of all scheduling configurations;
step 4.2: determining the unique attribute of the task as a task number;
step 4.3: determining all target task numbers of the tested program;
step 4.4: extracting a preposed task number according to each target task number;
step 4.5: continuing to extract the preposed task number of the preposed task number in the step 4.4;
step 4.6: step 4.5 is executed circularly; until all task numbers of the bottommost layer are extracted;
step 4.7: numbering all the extracted tasks, and arranging the extracted tasks in a reverse order according to the extraction sequence to obtain the blood relationship of each target task;
step 4.8: traversing all target task numbers in the step 4.3, and sequentially executing the step 4.4 to the step 4.7; the blood relationship of all target tasks can be obtained;
step 4.9: aiming at the blood relationship of all target tasks, if the same dependency relationship exists, merging, and reserving after merging; if the relationship of the same layer dependency exists, the same layer dependency needs to be executed separately.
Of course, the task number is not limited to be used as the unique attribute, and other non-repetitive attributes may be used as the unique attribute.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.
Furthermore, it should be understood that although the present description refers to embodiments, not every embodiment may contain only a single embodiment, and such description is for clarity only, and those skilled in the art should integrate the description, and the embodiments may be combined as appropriate to form other embodiments understood by those skilled in the art.
Claims (9)
1. A test method for realizing automatic batch running based on the relationship of blood relationship generated by scheduling configuration is characterized in that: the method comprises the following steps:
step 1: acquiring actual scheduling configuration content of the current production environment;
step 2: acquiring configuration change frequency according to the online frequency; determining a synchronous frequency according to the configuration change frequency;
and step 3: synchronizing the production scheduling configuration content to the test environment according to the configuration synchronization frequency;
and 4, step 4: generating a blood relationship according to the synchronized scheduling configuration content in the step 3;
and 5: packaging the automatic batch program according to the relationship of the blood relationship;
step 6: calling the automatic batch running program to execute by the calling terminal program;
and 7: performing test checking on the result after batch running;
and 8: and (4) summarizing the execution result and the problem repair result in the step (7) and compiling a quality report.
2. The method of claim 1, wherein the generating of the relationship based on the scheduling configuration is a test method for automatic running batch, and wherein: the step 1 further needs to select a data synchronization mode according to the storage form of the scheduling configuration content.
3. The method of claim 1, wherein the generating of the relationship based on the scheduling configuration is a test method for automatic running batch, and wherein: the synchronization frequency should be higher than the configuration change frequency; the synchronization time should be later than the change time.
4. The method of claim 1, wherein the generating of the relationship based on the scheduling configuration is a test method for automatic running batch, and wherein: the step 3 comprises a step 3.1: determining a storage position of the scheduling configuration of the test environment;
step 3.2: configuring a timing synchronization task according to the synchronization frequency;
step 3.3: the timing synchronization task runs to a point to be executed, and the synchronization action is triggered to be executed when the point is reached;
step 3.4: detecting whether the configuration contents of the test environment and the generation environment are the same or not, and if not, continuing to execute the synchronous operation in the step 3; if yes, executing step 4.
5. The method of claim 4, wherein the generating of the relationship based on the scheduling configuration is a test method for automatic running batch, and wherein: the generation of the blood relationship in step 4 comprises the following steps:
step 4.1: reading the contents of all scheduling configurations;
step 4.2: determining a unique attribute of the task;
step 4.3: determining the unique attributes of all target tasks of the tested program;
step 4.4: extracting unique attributes of the preposed tasks according to the unique attributes of each target task;
step 4.5: continuously extracting the unique attribute of the preposed task in the step 4.4;
step 4.6: step 4.5 is executed circularly; until all task unique attributes of the bottommost layer are extracted;
step 4.7: arranging all the extracted unique attributes of the tasks in a reverse order according to the extraction sequence, and obtaining the blood relationship of each target task;
step 4.8: traversing all the unique attributes of the target tasks in the step 4.3, and sequentially executing the step 4.4 to the step 4.7; the blood relationship of all target tasks can be obtained;
step 4.9: aiming at the blood relationship of all target tasks, if the same dependency relationship exists, merging, and reserving after merging; if the relationship of the same layer dependency exists, the same layer dependency needs to be executed separately.
6. The method of claim 5, wherein the generating of the relationship based on the scheduling configuration is a test method for automatic running batch, and wherein: the step 5 comprises the following steps: step 5.1: obtaining a batch running program to be executed according to a one-to-one mapping relation among different task attributes;
step 5.2: determining a program language based on the program name suffix of the batch program to be executed, which is acquired in the step 5.1, so as to determine a batch program execution command;
step 5.3: and packaging each batch program execution command into different files in a hierarchical manner according to the blooding margin dependency relationship sequence.
7. The method of claim 6, wherein the generating of the relationship based on the scheduling configuration is a test method for automatic running batch, and wherein: the step 6 comprises the following steps: step 6.1: determining a calling end program code language;
step 6.2: determining the functions to be realized by the calling terminal program based on the files packaged in the step 5.3;
step 6.3: executing the batch running program according to the calling end program determined in the step 6.2 and the running mode of the calling end program;
step 6.4: if the batch running process is executed with errors, positioning and correcting the error reasons;
step 6.5: evaluating the concurrency number according to the resources and the consumed time and adjusting the concurrency number;
8. the method of claim 7, wherein the generating of the relationship based on the scheduling configuration is a test method for performing an automated run batch, the method comprising: the step 7 comprises the following steps: step 7.1: compiling a test case;
step 7.2: after the batch running is completed in the step 6, performing test check on the batch running result according to the test case compiling content, and marking whether the test case passes or not;
step 7.3: and 7.2, if the test core fails, positioning the cause of the problem, and performing bug classification according to the influence range and importance of the problem.
9. The method of claim 7, wherein the generating of the relationship based on the scheduling configuration is a test method for performing an automated run batch, the method comprising: step 6.2 also includes executing the batch runs concurrently for the same floor and without dependency relationship between each other.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110716454.9A CN113535352B (en) | 2021-06-28 | 2021-06-28 | Test method for realizing automatic batch running based on blood relationship generated by scheduling configuration |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110716454.9A CN113535352B (en) | 2021-06-28 | 2021-06-28 | Test method for realizing automatic batch running based on blood relationship generated by scheduling configuration |
Publications (2)
Publication Number | Publication Date |
---|---|
CN113535352A true CN113535352A (en) | 2021-10-22 |
CN113535352B CN113535352B (en) | 2023-06-06 |
Family
ID=78096841
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202110716454.9A Active CN113535352B (en) | 2021-06-28 | 2021-06-28 | Test method for realizing automatic batch running based on blood relationship generated by scheduling configuration |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN113535352B (en) |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106484520A (en) * | 2016-10-17 | 2017-03-08 | 北京集奥聚合科技有限公司 | A kind of intelligent dispatching method based on data blood relationship and system |
CN107545030A (en) * | 2017-07-17 | 2018-01-05 | 阿里巴巴集团控股有限公司 | Processing method, device and the equipment of data genetic connection |
US20180217883A1 (en) * | 2017-01-31 | 2018-08-02 | Hewlett Packard Enterprise Development Lp | Performing a computation using provenance data |
CN111158990A (en) * | 2019-12-31 | 2020-05-15 | 重庆富民银行股份有限公司 | Data warehouse intelligent scheduling task batch running system and method |
CN111858065A (en) * | 2020-07-28 | 2020-10-30 | 中国平安财产保险股份有限公司 | Data processing method, device, storage medium and device |
CN112015722A (en) * | 2020-11-02 | 2020-12-01 | 浙江大华技术股份有限公司 | Database management method, data blood relationship analysis method and related device |
-
2021
- 2021-06-28 CN CN202110716454.9A patent/CN113535352B/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106484520A (en) * | 2016-10-17 | 2017-03-08 | 北京集奥聚合科技有限公司 | A kind of intelligent dispatching method based on data blood relationship and system |
US20180217883A1 (en) * | 2017-01-31 | 2018-08-02 | Hewlett Packard Enterprise Development Lp | Performing a computation using provenance data |
CN107545030A (en) * | 2017-07-17 | 2018-01-05 | 阿里巴巴集团控股有限公司 | Processing method, device and the equipment of data genetic connection |
CN111158990A (en) * | 2019-12-31 | 2020-05-15 | 重庆富民银行股份有限公司 | Data warehouse intelligent scheduling task batch running system and method |
CN111858065A (en) * | 2020-07-28 | 2020-10-30 | 中国平安财产保险股份有限公司 | Data processing method, device, storage medium and device |
CN112015722A (en) * | 2020-11-02 | 2020-12-01 | 浙江大华技术股份有限公司 | Database management method, data blood relationship analysis method and related device |
Non-Patent Citations (4)
Title |
---|
ANILA SAHAR BUTT 等: ""A provenance model for control-flow driven scientific workflows"", 《DATA & KNOWLEDGE ENGINEERING》, pages 1 - 8 * |
DATAWORKS向翠: ""DataWorks调度依赖配置深度解析"", pages 1 - 9, Retrieved from the Internet <URL:《https://developer.aliyun.com/article/778463》> * |
SCALAD: ""Apache DolphinScheduler 大数据工作流调度***"", pages 1 - 10, Retrieved from the Internet <URL:《https://blog.csdn.net/qq_20545159/article/details/116973143》> * |
李春梅 等: ""基于数据血缘构建数据分析方法"", 《中国新通信》, pages 50 - 51 * |
Also Published As
Publication number | Publication date |
---|---|
CN113535352B (en) | 2023-06-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106777101B (en) | Data processing engine | |
CN107515874B (en) | Method and equipment for synchronizing incremental data in distributed non-relational database | |
CN107168879B (en) | Method and device for generating test report of centralized configuration management system | |
CN104484269A (en) | Method for automatically generating testing script | |
CN104407973A (en) | Method and device for realizing automatic unit test | |
CN111158741B (en) | Method and device for monitoring dependency relationship change of service module on third party class library | |
CN114741375A (en) | Rapid and automatic data migration system and method for multi-source heterogeneous database | |
CN109558318B (en) | Code management method and code warehouse distributed system | |
CN108446224B (en) | Performance analysis method of application program on mobile terminal and storage medium | |
CN107179982B (en) | Cross-process debugging method and device | |
CN111694750A (en) | Method and device for constructing software testing environment | |
CN112131315A (en) | Database synchronization method and device under multi-task parallel development | |
CN111400102A (en) | Application program change monitoring method, device, equipment and storage medium | |
CN110764747A (en) | Data calculation scheduling method based on Airflow | |
CN112559525B (en) | Data checking system, method, device and server | |
CN110688147A (en) | Method for packing and analyzing metadata | |
CN114416547A (en) | Test case based test method | |
CN108021495B (en) | Code debugging method based on playback | |
CN113535352A (en) | Testing method for generating blood relationship based on scheduling configuration to realize automatic batch running | |
CN112035444A (en) | Method and device for transferring image data between heterogeneous systems without stopping | |
CN116627609A (en) | Hive batch processing-based scheduling method and device | |
CN116400950A (en) | DevOps element pipeline system based on version control | |
CN116069334A (en) | Cloud-protogenesis-based online development and code hosting method and system | |
CN111984311B (en) | Software structure reproduction method based on running log | |
CN115705297A (en) | Code call detection method, device, computer equipment 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 |