CN111309627A - Method and system for preventing test conflict in software test - Google Patents
Method and system for preventing test conflict in software test Download PDFInfo
- Publication number
- CN111309627A CN111309627A CN202010154793.8A CN202010154793A CN111309627A CN 111309627 A CN111309627 A CN 111309627A CN 202010154793 A CN202010154793 A CN 202010154793A CN 111309627 A CN111309627 A CN 111309627A
- Authority
- CN
- China
- Prior art keywords
- test case
- target test
- service
- processing
- time required
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 188
- 238000000034 method Methods 0.000 title claims abstract description 90
- 230000008569 process Effects 0.000 claims abstract description 65
- 238000012544 monitoring process Methods 0.000 claims abstract description 30
- 238000012545 processing Methods 0.000 claims description 48
- 238000004590 computer program Methods 0.000 claims description 12
- 238000013522 software testing Methods 0.000 claims description 10
- 230000008901 benefit Effects 0.000 abstract description 4
- 239000002699 waste material Substances 0.000 abstract description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000006872 improvement Effects 0.000 description 3
- 206010063385 Intellectualisation Diseases 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a method and a system for preventing test conflict in software test, aiming at the problems of low test efficiency, unintelligent test, waste of hardware equipment, insufficient test pressure, incomplete coverage of associated services and high cost existing in related operations such as changing bottom configuration or restarting service and the like in the existing software test process, monitoring whether the equivalent operation that the system executes the target test case exists, whether the service or the process in the configuration is running, whether the associated service is executing, the urgency and the importance of the target test case, and sending the execution operation request to the associated user, and judging whether the target test case is executed immediately according to the requirements of the associated users, so that the software test intelligence is improved, the product quality is improved, and the company benefit is increased.
Description
Technical Field
The invention relates to the technical field of software testing, in particular to a method and a system for preventing testing conflict in software testing.
Background
Nowadays, with the rapid development of information technology, software plays an increasingly important role in the aspects of social life, software testing is generated along with the generation of software, the problems of usability, safety and the like of the software are main concerns of users and developers, and many problems exist after the development of computer software, so that the software needs to be tested, namely as small as one app, and as large as an operating system or a cloud computing service platform, a plurality of testers are required to test the software. Since there are many people operating a test environment together, the operation of one tester may affect another, especially when the underlying configuration is involved or the restart service verifies certain services.
The existing software test is performed on a large environment such as a cloud management platform and the like by requiring a plurality of testers to perform module division and hierarchical testing, some tests involving the bottom layer in the testing process need to change configuration or restart operation services frequently, and the tests of other testers can be influenced when one person operates. The main ways to deal with this problem are currently the following: the communication software informs other testers of the operation required to be performed, inquires whether the testing of everybody is influenced or not, and starts the testing after the influence is not influenced; testing when other testers do not test; and redeploying a new test environment for testing. However, if the communication needs to be inquired whether to influence the test of others or the test is finished after the test of others is finished, the efficiency is low, and the test is not intelligent. If each person deploys one set of test environment, the deployment time is wasted, more hardware equipment is needed for support, resources are wasted, the cost is increased, and the testing pressure of the environment can be reduced when each person tests one module in one set of environment, the correlation influence among the modules cannot be fully covered, and the testing service cannot be systematically carried out.
Disclosure of Invention
The invention aims to provide a method and a system for preventing test conflict in software test, aims to solve the problems of low test efficiency, unintelligent test, waste of hardware equipment, insufficient test pressure, incomplete coverage of associated services, high cost and the like in the prior art, realizes the improvement of software test intellectualization, and is beneficial to the improvement of product quality.
In order to achieve the above technical object, the present invention provides a method for preventing test collision in software test, including the following operations:
setting a characteristic database, and recording and storing various services and time required by processing;
when a test case execution request exists, acquiring a target test case and issuing a monitoring command;
traversing whether the operation of all users has the same operation related to executing the target test case, if so, queuing and waiting, and performing interval polling according to the time required by processing stored in the characteristic database;
judging whether a running process or a related process related to the execution of the target test case exists, if so, queuing and waiting, and performing interval polling according to the time required for processing stored in the characteristic database;
judging whether the associated service related to the execution of the target test case exists, if not, directly executing the target test case, otherwise, executing the next step;
and judging whether the emergency degree of the target test case is the highest, if so, directly executing the target test case, otherwise, sending an execution request to a related test user, if the test personnel approve to interrupt the test, executing the target test case, and if not, queuing for waiting.
Preferably, the feature database records and stores time required for changing the configuration and restarting the service associated service and processing, time required for process and process processing of each service, and time required for associated service and processing of each service.
Preferably, when there is an equivalent operation related to executing the target test case, interval polling is performed according to the time required for changing the configuration and restarting the processing of the service associated with the service stored in the feature database; when the running process or the associated process related to the execution of the target test case exists, interval polling is carried out according to the process processing time of the process of each service stored in the characteristic database.
The invention also provides a system for preventing test conflict in software test, which comprises:
the characteristic database is used for setting the characteristic database and recording and storing various services and time required by processing;
the target test case acquisition module is used for acquiring a target test case and issuing a monitoring command when a test case execution request exists;
the monitoring module is used for traversing all the user operations according to the monitoring command to judge whether the same operation related to the execution of the target test case exists, judging whether the running process or the associated process related to the execution of the target test case exists, judging whether the associated service related to the execution of the target test case exists and sending the monitoring result to the judgment decision module;
the judgment decision module is used for processing the monitoring result returned by the monitoring module according to the priority, queuing for waiting when the same operation related to the execution of the target test case exists, and polling at intervals according to the processing time stored in the characteristic database; when a running process or a related process related to the execution of the target test case exists, queuing and waiting are carried out, and interval polling is carried out according to the time required for processing stored in the characteristic database; and when the associated service related to the execution of the target test case exists, determining whether to execute the target test case according to the emergency degree, and directly executing the target test case when the associated service does not exist.
Preferably, the feature database records and stores time required for changing the configuration and restarting the service associated service and processing, time required for process and process processing of each service, and time required for associated service and processing of each service.
Preferably, when there is an equivalent operation related to executing the target test case, interval polling is performed according to the time required for changing the configuration and restarting the processing of the service associated with the service stored in the feature database; when the running process or the associated process related to the execution of the target test case exists, interval polling is carried out according to the process processing time of the process of each service stored in the characteristic database.
The invention also provides a device for preventing test conflict in software test, which comprises:
a memory for storing a computer program;
and the processor is used for executing the computer program to realize the method for preventing the test conflict in the software test.
The invention also provides a readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the method for preventing test collision in software test.
The effect provided in the summary of the invention is only the effect of the embodiment, not all the effects of the invention, and one of the above technical solutions has the following advantages or beneficial effects:
compared with the prior art, the invention provides a method for preventing test conflict in software test aiming at the problems of low test efficiency, unintelligent test, waste of hardware equipment, insufficient test pressure, incomplete coverage of associated services and high cost in the related operations of changing bottom layer configuration or restarting service and the like in the existing software test process, monitoring whether the equivalent operation that the system executes the target test case exists, whether the service or the process in the configuration is running, whether the associated service is executing, the urgency and the importance of the target test case, and sending the execution operation request to the associated user, and judging whether the target test case is executed immediately according to the requirements of the associated users, so that the software test intelligence is improved, the product quality is improved, and the company benefit is increased.
Drawings
FIG. 1 is a flowchart of a method for preventing test conflicts in software testing according to an embodiment of the present invention;
FIG. 2 is a flowchart of a decision making process according to monitoring results and priorities in an embodiment of the present invention;
fig. 3 is a block diagram of a system for preventing test conflicts in software testing according to an embodiment of the present invention.
Detailed Description
In order to clearly explain the technical features of the present invention, the following detailed description of the present invention is provided with reference to the accompanying drawings. The following disclosure provides many different embodiments, or examples, for implementing different features of the invention. To simplify the disclosure of the present invention, the components and arrangements of specific examples are described below. Furthermore, the present invention may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed. It should be noted that the components illustrated in the figures are not necessarily drawn to scale. Descriptions of well-known components and processing techniques and procedures are omitted so as to not unnecessarily limit the invention.
The following describes a method and a system for preventing test conflicts in software testing according to embodiments of the present invention in detail with reference to the accompanying drawings.
As shown in FIG. 1, the invention discloses a method for preventing test conflict in software test, which comprises the following operations:
setting a characteristic database, and recording and storing various services and time required by processing;
when a test case execution request exists, acquiring a target test case and issuing a monitoring command;
traversing whether the operation of all users has the same operation related to executing the target test case, if so, queuing and waiting, and performing interval polling according to the time required by processing stored in the characteristic database;
judging whether a running process or a related process related to the execution of the target test case exists, if so, queuing and waiting, and performing interval polling according to the time required for processing stored in the characteristic database;
judging whether the associated service related to the execution of the target test case exists, if not, directly executing the target test case, otherwise, executing the next step;
and judging whether the emergency degree of the target test case is the highest, if so, directly executing the target test case, otherwise, sending an execution request to a related test user, if the test personnel approve to interrupt the test, executing the target test case, and if not, queuing for waiting.
The embodiment of the invention judges whether the decision target test case is allowed to be executed or not by monitoring the operation, service or configured process, associated service of the equivalent user of the executing target test case and the emergency degree of the target test case.
The method comprises the steps of collecting test cases, obtaining target test cases and storing the test cases when new test cases need to be executed, and issuing a monitoring command when the target test cases are triggered to be executed. The newly added test cases are supplemented into the test case library.
Setting a characteristic database, recording and storing the time required for changing the configuration and restarting the operation or the service and the process associated with the service, recording and storing the process and the process processing time of each service, and recording the time required for the associated service and the operation and the process of the service.
And monitoring the execution of the target test case, and making a judgment decision according to the monitoring result and the priority.
As shown in fig. 2, when a request for executing a test case is received, traversing whether the operations of all users in the system relate to the same operation of executing a target test case, and if the returned result is that the same operation exists, queuing and waiting are performed, and interval polling is performed according to the processing time stored in the feature database; when no equivalent operation is monitored, judging whether a process in the service or configuration is running, if so, queuing and waiting, and performing interval polling according to the processing time stored in the characteristic database; when no service or process in the configuration is monitored to be running, whether the associated service is operated or not is judged, if not, the test case can be directly executed, if yes, whether the emergency degree and the importance degree of the test case are the highest or not is judged, if not, the test case is directly executed, if not, an execution request is sent to an associated test user, when a tester agrees to interrupt the test, the test case is executed, and if not, queuing and waiting are carried out.
And aiming at the judgment decision, storing the result of executing the test case, returning the result to all testing personnel whether the test case is executed at present, recording the execution operation and simultaneously warning the user to avoid other related operations and carry out other tests, and if the user receives the request of executing the test case, deciding whether to allow the execution according to the requirement. In addition, whether the operation of the user is influenced by the execution of other use cases can be checked.
The embodiment of the invention aims at the problems of low test efficiency, unintelligent test, waste of hardware equipment, insufficient test pressure, incomplete coverage of associated services and high cost existing in related operations such as changing bottom layer configuration or restarting service in the existing software test process, and provides a method for changing bottom layer configuration or restarting service in software test, when a target test case requests to execute, whether the same operation of a system executing the target test case exists, whether the service or a process in the configuration is running, whether the associated service is executing, the emergency degree and the importance degree of the target test case are monitored, and the execution operation request is sent to an associated user, whether the target test case is executed immediately is judged according to the requirements of the associated user, thereby improving the intellectualization of software test and being beneficial to improving the product quality, the company benefit is increased.
As shown in fig. 3, an embodiment of the present invention further discloses a system for preventing test conflicts in software testing, where the system includes:
the characteristic database is used for setting the characteristic database and recording and storing various services and time required by processing;
the target test case acquisition module is used for acquiring a target test case and issuing a monitoring command when a test case execution request exists;
the monitoring module is used for traversing all the user operations according to the monitoring command to judge whether the same operation related to the execution of the target test case exists, judging whether the running process or the associated process related to the execution of the target test case exists, judging whether the associated service related to the execution of the target test case exists and sending the monitoring result to the judgment decision module;
the judgment decision module is used for processing the monitoring result returned by the monitoring module according to the priority, queuing for waiting when the same operation related to the execution of the target test case exists, and polling at intervals according to the processing time stored in the characteristic database; when a running process or a related process related to the execution of the target test case exists, queuing and waiting are carried out, and interval polling is carried out according to the time required for processing stored in the characteristic database; and when the associated service related to the execution of the target test case exists, determining whether to execute the target test case according to the emergency degree, and directly executing the target test case when the associated service does not exist.
The method comprises the steps of collecting test cases, obtaining target test cases and storing the test cases when new test cases need to be executed, and issuing decision-making judgment commands when the target test cases are triggered to be executed. The newly added test cases are supplemented into the test case library.
Setting a characteristic database, recording and storing the time required for changing the configuration and restarting the operation or the service and the process associated with the service, recording and storing the process and the process processing time of each service, and recording the time required for the associated service and the operation and the process of the service.
And monitoring the execution of the target test case, and making a judgment decision according to the monitoring result and the priority.
When a request for executing the test case is received, traversing whether the operation of all users in the system relates to the equivalent operation of executing the target test case, if the returned result is that the equivalent operation exists, queuing for waiting, and performing interval polling according to the processing time stored in the characteristic database; when no equivalent operation is monitored, judging whether a process in the service or configuration is running, if so, queuing and waiting, and performing interval polling according to the processing time stored in the characteristic database; when no service or process in the configuration is monitored to be running, whether the associated service is operated or not is judged, if not, the test case can be directly executed, if yes, whether the emergency degree and the importance degree of the test case are the highest or not is judged, if not, the test case is directly executed, if not, an execution request is sent to an associated test user, when a tester agrees to interrupt the test, the test case is executed, and if not, queuing and waiting are carried out.
And aiming at the judgment decision, storing the result of executing the test case, returning the result to all testing personnel whether the test case is executed at present, recording the execution operation and simultaneously warning the user to avoid other related operations and carry out other tests, and if the user receives the request of executing the test case, deciding whether to allow the execution according to the requirement. In addition, whether the operation of the user is influenced by the execution of other use cases can be checked.
The embodiment of the invention also discloses a device for preventing test conflict in software test, which comprises:
a memory for storing a computer program;
and the processor is used for executing the computer program to realize the method for preventing the test conflict in the software test.
The embodiment of the invention also discloses a readable storage medium for storing the computer program, wherein the computer program realizes the method for preventing the test conflict in the software test when being executed by the processor.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents and improvements made within the spirit and principle of the present invention are intended to be included within the scope of the present invention.
Claims (8)
1. A method for preventing test collision in software testing, the method comprising the operations of:
setting a characteristic database, and recording and storing various services and time required by processing;
when a test case execution request exists, acquiring a target test case and issuing a monitoring command;
traversing whether the operation of all users has the same operation related to executing the target test case, if so, queuing and waiting, and performing interval polling according to the time required by processing stored in the characteristic database;
judging whether a running process or a related process related to the execution of the target test case exists, if so, queuing and waiting, and performing interval polling according to the time required for processing stored in the characteristic database;
judging whether the associated service related to the execution of the target test case exists, if not, directly executing the target test case, otherwise, executing the next step;
and judging whether the emergency degree of the target test case is the highest, if so, directly executing the target test case, otherwise, sending an execution request to a related test user, if the test personnel approve to interrupt the test, executing the target test case, and if not, queuing for waiting.
2. The method of claim 1, wherein the time required for the services and processes comprises: time required for changing configuration and restarting services and processing associated with the services, time required for process and process processing of each service, and time required for associated services and processing of each service.
3. The method of claim 2, wherein when there is an equivalent operation related to executing a target test case, polling is performed at intervals according to the time required for changing the configuration and restarting the processing of the service associated with the service stored in the feature database; when the running process or the associated process related to the execution of the target test case exists, interval polling is carried out according to the process processing time of the process of each service stored in the characteristic database.
4. A system for preventing test conflicts in software testing, the system comprising:
the characteristic database is used for setting the characteristic database and recording and storing various services and time required by processing;
the target test case acquisition module is used for acquiring a target test case and issuing a monitoring command when a test case execution request exists;
the monitoring module is used for traversing all the user operations according to the monitoring command to judge whether the same operation related to the execution of the target test case exists, judging whether the running process or the associated process related to the execution of the target test case exists, judging whether the associated service related to the execution of the target test case exists and sending the monitoring result to the judgment decision module;
the judgment decision module is used for processing the monitoring result returned by the monitoring module according to the priority, queuing for waiting when the same operation related to the execution of the target test case exists, and polling at intervals according to the processing time stored in the characteristic database; when a running process or a related process related to the execution of the target test case exists, queuing and waiting are carried out, and interval polling is carried out according to the time required for processing stored in the characteristic database; and when the associated service related to the execution of the target test case exists, determining whether to execute the target test case according to the emergency degree, and directly executing the target test case when the associated service does not exist.
5. The system of claim 4, wherein the time required for the services and processes comprises: time required for changing configuration and restarting services and processing associated with the services, time required for process and process processing of each service, and time required for associated services and processing of each service.
6. The system of claim 5, wherein when there are equivalent operations related to executing target test cases, polling is performed at intervals according to the time required for changing the configuration and restarting the processing of the service associated with the service stored in the feature database; when the running process or the associated process related to the execution of the target test case exists, interval polling is carried out according to the process processing time of the process of each service stored in the characteristic database.
7. An apparatus for preventing test collision in software test, comprising:
a memory for storing a computer program;
a processor for executing the computer program to implement the method for preventing test collision in software testing according to any one of claims 1 to 3.
8. A readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements a method for preventing test collision in a software test according to any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010154793.8A CN111309627B (en) | 2020-03-08 | 2020-03-08 | Method and system for preventing test conflict in software test |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010154793.8A CN111309627B (en) | 2020-03-08 | 2020-03-08 | Method and system for preventing test conflict in software test |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111309627A true CN111309627A (en) | 2020-06-19 |
| CN111309627B CN111309627B (en) | 2022-11-29 |
Family
ID=71149532
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010154793.8A Active CN111309627B (en) | 2020-03-08 | 2020-03-08 | Method and system for preventing test conflict in software test |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111309627B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113687929A (en) * | 2021-08-24 | 2021-11-23 | 济南浪潮数据技术有限公司 | Exception handling method and related device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080320334A1 (en) * | 2007-06-19 | 2008-12-25 | Microsoft Corporation | Transactional debugger for a transactional memory system |
| WO2017219851A1 (en) * | 2016-06-24 | 2017-12-28 | 深圳市中兴微电子技术有限公司 | Method and apparatus for executing test case, and computer readable medium |
| CN110196804A (en) * | 2018-04-24 | 2019-09-03 | 腾讯科技（深圳）有限公司 | The test method and device of business, storage medium, electronic device |
-
2020
- 2020-03-08 CN CN202010154793.8A patent/CN111309627B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080320334A1 (en) * | 2007-06-19 | 2008-12-25 | Microsoft Corporation | Transactional debugger for a transactional memory system |
| WO2017219851A1 (en) * | 2016-06-24 | 2017-12-28 | 深圳市中兴微电子技术有限公司 | Method and apparatus for executing test case, and computer readable medium |
| CN107544899A (en) * | 2016-06-24 | 2018-01-05 | 深圳市中兴微电子技术有限公司 | A kind of method and device of implementation of test cases |
| CN110196804A (en) * | 2018-04-24 | 2019-09-03 | 腾讯科技（深圳）有限公司 | The test method and device of business, storage medium, electronic device |
Non-Patent Citations (1)
| Title |
|---|
| 李捷荧等: "Woodpecker:支持细粒度冲突模拟的数据库测试框架", 《华东师范大学学报(自然科学版)》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113687929A (en) * | 2021-08-24 | 2021-11-23 | 济南浪潮数据技术有限公司 | Exception handling method and related device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111309627B (en) | 2022-11-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10282279B2 (en) | System and method for diagnosing information technology systems in multiple virtual parallel universes | |
| US20180052711A1 (en) | Method and system for scheduling video analysis tasks | |
| US9479416B2 (en) | System and method for diagnosing information technology systems in multiple virtual parallel universes | |
| CN113157411B (en) | Celery-based reliable configurable task system and device | |
| CN111966603B (en) | Memory leakage detection method and device, readable storage medium and electronic equipment | |
| CN113986534A (en) | Task scheduling method and device, computer equipment and computer readable storage medium | |
| CN111309627B (en) | Method and system for preventing test conflict in software test | |
| CN112445686A (en) | Memory leak detection method, device and computer-readable storage medium | |
| CN114691407A (en) | Method and device for acquiring vehicle log, electronic equipment and storage medium | |
| CN112363828B (en) | Memory fragment management method and device, vehicle-mounted system and vehicle | |
| CN112580816A (en) | Machine learning training resource management | |
| US20090083747A1 (en) | Method for managing application programs by utilizing redundancy and load balance | |
| CN115190052A (en) | Long connection management method, system and control unit | |
| CN115525392A (en) | Container monitoring method and device, electronic equipment and storage medium | |
| CN111506422B (en) | Event analysis method and system | |
| CN110188008B (en) | Job scheduling master-slave switching method and device, computer equipment and storage medium | |
| US20220091887A1 (en) | System and method for finding and identifying computer nodes in a network | |
| CN113296945A (en) | Continuous integration method, system, equipment and computer readable storage medium | |
| CN112395119A (en) | Abnormal data processing method, abnormal data processing device, server and storage medium | |
| CN112825044B (en) | Task execution method, device and computer storage medium | |
| CN111404769B (en) | Performance test method, device, server and storage medium | |
| CN110825560A (en) | Execution error processing method, device, equipment and computer readable storage medium | |
| CN117370052B (en) | Microservice fault analysis method, device, equipment and storage medium | |
| CN117349127B (en) | GPU card-falling detection method and device | |
| JP2022080615A (en) | Information processing device, arrangement method, and program |
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 |