[go: up one dir, main page]

WO2018036167A1 - Procédé, dispositif, serveur et support de stockage d'affectation d'exécuteurs de tâches de test - Google Patents

Procédé, dispositif, serveur et support de stockage d'affectation d'exécuteurs de tâches de test Download PDF

Info

Publication number
WO2018036167A1
WO2018036167A1 PCT/CN2017/079641 CN2017079641W WO2018036167A1 WO 2018036167 A1 WO2018036167 A1 WO 2018036167A1 CN 2017079641 W CN2017079641 W CN 2017079641W WO 2018036167 A1 WO2018036167 A1 WO 2018036167A1
Authority
WO
WIPO (PCT)
Prior art keywords
execution machine
idle
execution
identifier
test task
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.)
Ceased
Application number
PCT/CN2017/079641
Other languages
English (en)
Chinese (zh)
Inventor
林铭森
王瑞然
余剑波
卢伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2018036167A1 publication Critical patent/WO2018036167A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Prevention of errors by analysis, debugging or testing of software
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Prevention of errors by analysis, debugging or testing of software
    • G06F11/3668—Testing of software
    • G06F11/3672—Test management
    • G06F11/3688—Test management for test execution, e.g. scheduling of test suites

Definitions

  • the present application relates to the field of computer application technologies, and in particular, to a test task execution machine allocation method, apparatus, server, and storage medium.
  • test task it is necessary to send a test task to an execution machine, and use the execution machine to perform a test task to obtain a test result.
  • the tester is required to apply to the executive manager for the execution machine.
  • the executive manager manually assigns the corresponding number of actuators to the tester, and then the tester can execute the test task with the execution machine.
  • the execution manager needs to manually allocate a corresponding number of execution machines for each tester, so that the test task execution machine allocation process is cumbersome and the execution manager manually assigns The speed and accuracy of the actuator are low, so that the tester cannot quickly and accurately obtain the corresponding number of actuators to perform the test task, resulting in inefficient distribution of the test task actuator.
  • test task execution machine allocation method apparatus, server, and storage medium are provided.
  • a test task execution machine allocation method includes:
  • An execution machine is assigned to the test task based on the found idle execution machine identification.
  • a test task actuator distribution device comprising:
  • the test task obtaining module is configured to obtain a test task created by each terminal in the test page;
  • test task adding module configured to add the test task to the task queue according to the obtaining order
  • a task queue reading module configured to read a test task in the task queue
  • An execution quantity extraction module for extracting the number of execution machines from the read test tasks
  • An execution identifier identification module configured to search for an idle execution machine identifier in the idle execution machine identifier set according to the number of execution machines;
  • the test task sending module is configured to allocate an execution machine to the test task according to the found idle executable machine identifier.
  • a server comprising a memory and a processor, the memory storing computer executable instructions that, when executed by the processor, cause the processor to perform the following steps:
  • An execution machine is assigned to the test task based on the found idle execution machine identification.
  • One or more non-volatile storage media storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform the following steps:
  • An execution machine is assigned to the test task based on the found idle execution machine identification.
  • 1 is an application environment diagram of a test task execution machine distribution system in an embodiment
  • FIG. 2 is a functional block diagram of a test server in a test task execution machine distribution system in an embodiment
  • FIG. 3 is a schematic flow chart of a test task execution machine allocation method in an embodiment
  • FIG. 4 is a schematic flowchart of a step of searching for an idle execution machine identifier in an embodiment
  • FIG. 5 is a schematic flowchart of a step of updating an execution machine identifier in a test task in an embodiment
  • FIG. 6 is a flow chart showing the steps of periodically detecting an actuator in an embodiment
  • Figure 7 is a functional block diagram of a test task actuator distribution device in one embodiment
  • Figure 8 is a functional block diagram of a test task actuator distribution device in another embodiment
  • FIG. 9 is a functional block diagram of an execution machine identification finding module in an embodiment
  • test task sending module 10 is a functional block diagram of a test task sending module in an embodiment
  • Figure 11 is a functional block diagram of a test task actuator distribution device in still another embodiment.
  • the test task execution machine distribution system includes a plurality of terminals 110, a test server 120 and a plurality of execution machines 130, and the plurality of terminals 110 pass through the network and the test server 120. Connected, a plurality of execution machines 130 are connected to the test server 120 via a network.
  • the test server 120 may also be multiple, and the execution machine 130 may specifically be a virtual machine.
  • the terminal 110 may be a desktop computer or a mobile terminal, and the mobile terminal may specifically be at least one of a tablet computer, a smart phone, and a personal data assistant.
  • test server 120 includes a processor coupled through a system bus, a non-volatile storage medium, an internal memory, and a network interface.
  • the processor is used to provide computing and control capabilities to support the operation of the entire test server 120.
  • the non-volatile storage medium of test server 120 stores operating system and computer executable instructions.
  • Computer executable instructions are executable by the processor to implement a test task actuator allocation method provided in the following embodiments.
  • the internal memory in test server 120 provides a cached operating environment for operating systems and computer executable instructions in a non-volatile storage medium.
  • the network interface is used for network communication with the terminal 110 and the execution machine 130. It can be understood that the test server 120 can be implemented by a stand-alone server or a server cluster composed of a plurality of servers.
  • FIG. 2 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the test server to which the solution of the present application is applied.
  • the specific test server may It includes more or less components than those shown in Figure 2, or some components are combined, or have different component arrangements.
  • a test task execution machine allocation method is provided.
  • the method is illustrated by being applied to the test server 120 in the test task execution machine distribution system of FIG.
  • the test task execution machine allocation program, the test task execution machine allocation program is used to implement the test task execution machine allocation method, and the test task execution machine allocation method specifically includes the following contents:
  • the test page is displayed in the terminal 110, and the terminal 110 creates a test task in the test page.
  • the test task specifically includes the test case and the number of the execution machine, and specifically includes the execution machine identifier.
  • the terminal 110 sends the test task to the test server 120.
  • the test server 120 receives the test tasks transmitted by the respective terminals 110.
  • the terminal 110 sends an access request to the test server 120.
  • the test server 120 returns test page data to the terminal 110 according to the access request, and the terminal 110 renders the test page according to the received test page data.
  • the test server 120 After obtaining the test task created by each terminal 110, the test server 120 records the acquisition time of each test task, and adds the test task to the end of the task queue according to the order of the acquisition time.
  • the test server 120 acquires one test task, stops acquiring the next test task, adds the obtained test task to the task queue, and acquires the next test task.
  • the test task includes a priority
  • the test server 120 reads the priority in each test task, and sorts the test tasks according to the priority from high to low, according to the priority. The high to low order adds test tasks to the task queue in turn.
  • the test server 120 reads the test task in the task queue, and the test task may include the number of execution machines, the number of execution machines is the number of execution machines required for the test task, and the test server 120 extracts execution from the read test tasks. Number of machines.
  • the test server 120 stores an idle execution machine identifier, the idle execution machine identifier constitutes an idle execution machine identifier set, and the idle execution machine identifier corresponding execution machine is in an idle state. After the test server 120 extracts the number of execution machines from the read test tasks, it searches for the idle execution machine identifier in the idle execution machine identification set, and the number of found idle execution machine identifiers is equal to the number of extracted execution machines.
  • the step S210 further includes the step of updating the idle execution machine identifier set, where the step specifically includes: counting the number of identifiers in the idle execution machine identifier set; comparing the number of execution machines with the number of identifiers; If the number of the identifiers is greater than the number of the identifiers, the identifiers of the executables corresponding to the executables in the idle state are re-acquired, and the obtained executable identifiers are stored in the idle executable identifier set.
  • the test server 120 counts the number of identifiers in the idle execution machine identifier set, compares the number of statistics obtained by the statistics with the number of executed execution machines, and performs an identifier according to the idle execution machine. The number of identifiers in the set determines whether there is enough execution machine assigned to the test task.
  • the number of identifiers obtained by the statistics is greater than or equal to the number of executed machines, it means that there are enough actuators assigned to the test task; if the number of identifiers obtained by statistics is less than The number of executed execution machines indicates that there is not enough execution machine assigned to the test task, and the test server 120 re-detects the execution machine in the idle state and acquires the execution machine identifier corresponding to the execution machine in the idle state, which will be obtained.
  • the execution machine identification is stored in the idle execution machine identification set.
  • the test server 120 allocates the found execution machine 130 corresponding to the idle execution machine identifier to the test task read from the task queue, and reads the information from the task queue.
  • the test task is sent to the executed execution machine 130 corresponding to the found idle executable identifier.
  • the test task is executed to generate a test result.
  • the test task is added to the task queue according to the acquisition order, and the test task in the task queue is read to ensure that the test task is read in a certain order. This avoids the situation where the test task is congested and the test task is not processed for a long time.
  • the idle execution machine identifier is searched from the idle execution machine identification set according to the number of execution machines in the read test task, and the idle task identifier is allocated according to the found idle execution machine identifier. Executing the corresponding machine of the machine identification, thereby simplifying the test task execution machine allocation operation process, quickly and accurately assigning the execution machine to the test task, and improving the test task execution machine allocation efficiency.
  • S310 specifically includes the step of searching for an idle execution machine identifier, and the step specifically includes the following content:
  • S402. Generate an execution machine scheduling request according to the number of execution machines.
  • the number of execution machines is encapsulated in the execution machine scheduling request, and the test server 120 can also encrypt the number of execution machines and encrypt the number of execution machines.
  • the number of execution machines is encapsulated in the execution machine scheduling request.
  • the scheduling server monitors the state of the execution machine, acquires the execution machine identifier corresponding to the execution machine in the idle state, and stores the obtained execution machine identifier in the idle execution machine identifier set.
  • the timing starts.
  • the test server 120 extracts the execution machine scheduling request, and sends the execution machine scheduling request to the scheduling server again.
  • the test server 120 sends an execution machine scheduling request to the scheduling server, where the scheduling server stores the idle execution machine identifier, and the idle execution machine identifier constitutes the idle execution machine identifier set.
  • the scheduling server extracts the number of execution machines in the execution machine scheduling request, searches for the idle execution machine identifier in the idle execution machine identification set according to the number of execution machines, and the scheduling server sends the found idle execution machine identifier.
  • the number of found idle performer IDs is equal to the number of extracted performers.
  • the scheduling server searches for the idle execution machine identifier from the idle execution machine identifier set according to the number of execution machines in the execution machine scheduling request, and receives the found idle execution returned by the scheduling server.
  • the machine identifier is used to search for the idle execution machine identifier by using the dispatching server, and the executed execution machine corresponding to the idle idle machine identifier is allocated to the test task, thereby improving the use efficiency of the execution machine.
  • S312 specifically includes the step of updating the execution machine identifier in the test task, and the step specifically includes the following content:
  • test server 120 detects that there is an execution machine identifier in the test task, the execution server identifier in the test task is deleted, and the found idle execution machine identifier is added to the test task to obtain the updated test task;
  • server 120 does not detect that there is an execution machine identifier in the test task, the server finds the idle execution machine identifier to be added to the test task, and obtains the updated test task.
  • S504 Send the updated test task to the scheduling server, so that the scheduling server extracts the idle execution machine identifier in the updated test task, and allocates the extracted execution machine corresponding to the idle execution machine identifier to the updated test task.
  • the test server 120 sends the updated test task to the scheduling server.
  • the scheduling server parses the test task, extracts the idle execution machine identifier in the test task, and schedules idle execution.
  • the execution machine 130 corresponding to the machine identifier assigns the execution machine to the test task, and synchronously sends the received test task to the execution machine corresponding to the idle execution machine identifier, so that the execution machine performs the test task and generates the test result.
  • the updated test task may further include verification information, and after receiving the updated test task, the scheduling server extracts the verification information in the updated test task, and verifies the verification information, after the verification is passed.
  • the scheduling server extracts the idle execution machine identifier in the updated test task, and allocates an execution machine to the updated test task according to the extracted idle execution identifier.
  • the executable identifier in the read test task is updated according to the found idle execution machine identifier, and after the updated test task is sent to the scheduling server, the scheduling server is caused to perform the idle execution machine according to the test task.
  • the identification assigns an actuator to the test task, which increases the speed and accuracy of the assigned actuator.
  • a test task execution machine allocation method is provided.
  • the method further includes the step of periodically detecting an execution machine, and the step specifically includes the following content:
  • the test server 120 periodically acquires the resource occupancy rate of each execution machine according to the preset duration, and compares the resource occupancy rate of each execution machine with a preset threshold. When the resource occupancy rate is less than the preset threshold, the execution server is in the The idle state; when the resource occupancy rate is greater than or equal to the preset threshold, it indicates that the execution machine is in a state of performing a test task, and is not in an idle state.
  • the resource occupancy rate may specifically be a thread occupancy rate.
  • test server 120 adds an idle flag to the executable identifier corresponding to the execution machine whose resource occupancy is less than the preset threshold, and extracts the identifier of the executable carrying the idle token.
  • test server 120 stores the extracted execution machine identification into the idle execution machine identification set as the idle execution machine identification.
  • the extraction will be performed.
  • the obtained execution machine identifier is stored in the idle execution machine identification set as the idle execution machine identification, so that the idle execution machine can be allocated again, improving the utilization efficiency of the idle execution machine.
  • a test task execution device distribution device 700 is provided.
  • the device specifically includes: a test task acquisition module 702, a test task addition module 704, a task queue reading module 706, and an execution machine number.
  • the test task obtaining module 702 is configured to obtain a test task created by each terminal in the test page.
  • the test task adding module 704 is configured to add the test task to the task queue in the order of acquisition.
  • the task queue reading module 706 is configured to read the test task in the task queue.
  • the execution machine quantity extraction module 708 is configured to extract the number of execution machines from the read test tasks.
  • the execution machine identifier finding module 710 is configured to search for an idle execution machine identifier in the idle execution machine identifier set according to the number of execution machines.
  • the test task sending module 712 is configured to allocate an execution machine to the test task according to the found idle executable machine identifier.
  • the test task is added to the task queue according to the acquisition order, and the test task in the task queue is read to ensure that the test task is read in a certain order. This avoids the situation where the test task is congested and the test task is not processed for a long time.
  • the idle execution machine identifier is searched from the idle execution machine identification set according to the number of execution machines in the read test task, and the idle task identifier is allocated according to the found idle execution machine identifier. Executing the corresponding machine of the machine identification, thereby simplifying the test task execution machine allocation operation process, quickly and accurately assigning the execution machine to the test task, and improving the test task execution machine allocation efficiency.
  • the test task execution device allocation device 700 further includes an identifier quantity statistics module 714 , an identifier quantity comparison module 716 , and an identifier reacquisition module 718 .
  • the identifier quantity statistics module 714 is configured to count the number of identifiers in the idle executable machine identifier set.
  • the identification quantity comparison module 716 is configured to compare the number of execution machines with the number of identifications.
  • the identifier re-acquisition module 718 is configured to re-acquire the execution machine identifier corresponding to the execution machine in the idle state when the number of execution machines is greater than the number of identifiers, and store the acquired execution machine identifier into the idle execution machine identifier set.
  • the number of execution machines required for the test task is compared with the number of statistical identifiers, and when the number of execution machines is greater than the number of identifiers, re-acquiring the idle state. Executing the machine identifier corresponding to the execution machine, storing the obtained execution machine identifier into the idle execution machine identifier set, so that there are enough idle execution machine identifiers in the idle execution machine identifier set, and ensuring that there are enough executions in the idle state.
  • Machines can be assigned to test tasks, increasing the utilization of the actuators and increasing the success rate of assigning actuators to test tasks.
  • the execution machine identification lookup module 710 specifically includes a scheduling request generation module 710a, a scheduling request sending module 710b, and an execution machine identification receiving module 710c.
  • the scheduling request generating module 710a is configured to generate an execution machine scheduling request according to the number of executing machines.
  • the scheduling request sending module 710b is configured to send an execution machine scheduling request to the scheduling server.
  • the execution machine identifier receiving module 710c is configured to receive the idle execution machine identifier returned by the scheduling server, where the idle execution machine identifier is obtained by the scheduling server in the idle execution machine identifier set according to the execution machine scheduling request.
  • the scheduling server searches for the idle execution machine identifier from the idle execution machine identifier set according to the number of execution machines in the execution machine scheduling request, and receives the found idle execution returned by the scheduling server.
  • the machine identifier is used to search for the idle execution machine identifier by using the dispatching server, and the executed execution machine corresponding to the idle idle machine identifier is allocated to the test task, thereby improving the use efficiency of the execution machine.
  • the test task sending module 712 specifically includes a test task update module 712a and a test task synchronization module 712b.
  • the test task update module 712a is configured to update the execution machine identifier in the test task according to the found idle executable machine identifier.
  • the test task synchronization module 712b is configured to send the updated test task to the scheduling server, so that the scheduling server extracts the idle execution machine identifier in the updated test task, and allocates the extracted idle execution machine to the updated test task. Identify the corresponding actuator.
  • the executable identifier in the read test task is updated according to the found idle execution machine identifier, and after the updated test task is sent to the scheduling server, the scheduling server is caused to perform the idle execution machine according to the test task.
  • the identification assigns an actuator to the test task, which increases the speed and accuracy of the assigned actuator.
  • the test task execution device allocation device 700 further includes an execution machine detection module 720 , an execution machine identification extraction module 722 , and an execution machine identification storage module 724 .
  • the execution machine detection module 720 is configured to periodically detect whether the resource occupancy rate of each execution machine is less than a preset threshold.
  • the execution machine identifier extraction module 722 is configured to: when detecting that the resource occupancy rate of the execution machine is less than a preset threshold, extract the detected execution machine identifier corresponding to the execution machine;
  • the executable identifier storage module 724 is configured to store the extracted executable identifier into the idle executable identifier set.
  • the extraction will be performed.
  • the obtained execution machine identifier is stored in the idle execution machine identification set as the idle execution machine identification, so that the idle execution machine is allocated again, and the utilization efficiency of the idle execution machine is improved.
  • Each of the above-described test task actuator distribution devices may be implemented in whole or in part by software, hardware, and combinations thereof.
  • the network interface may be an Ethernet or a wireless network card.
  • Each of the above modules may be embedded in a hardware form or independent of a processor in the server, or may be stored in a memory of the server in a software form, so that the processor calls to perform operations corresponding to the above modules.
  • the processor can be a central processing unit (CPU), a microprocessor, a microcontroller, or the like.
  • the storage medium may be a magnetic disk, an optical disk, or a read-only storage memory (Read-Only) Memory, ROM) or Random Access Memory (RAM).

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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Debugging And Monitoring (AREA)

Abstract

L'invention concerne un procédé d'affectation d'exécuteurs de tâches de test, comportant les étapes consistant à: acquérir des tâches de test établies par chaque terminal dans une page de test; ajouter les tâches de test acquises dans une file d'attente de tâches selon l'ordre d'acquisition; lire les tâches de test dans la file d'attente de tâches; extraire des tâches de test lues un nombre d'exécuteurs; trouver des identifications d'exécuteurs au repos dans un ensemble d'identifications d'exécuteurs au repos selon le nombre d'exécuteurs; et affecter des exécuteurs aux tâches de test lues d'après les identifications d'exécuteurs au repos trouvées.
PCT/CN2017/079641 2016-08-22 2017-04-07 Procédé, dispositif, serveur et support de stockage d'affectation d'exécuteurs de tâches de test Ceased WO2018036167A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610704227.3A CN106452830A (zh) 2016-08-22 2016-08-22 测试任务执行机分配方法和装置
CN201610704227.3 2016-08-22

Publications (1)

Publication Number Publication Date
WO2018036167A1 true WO2018036167A1 (fr) 2018-03-01

Family

ID=58182533

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/079641 Ceased WO2018036167A1 (fr) 2016-08-22 2017-04-07 Procédé, dispositif, serveur et support de stockage d'affectation d'exécuteurs de tâches de test

Country Status (2)

Country Link
CN (1) CN106452830A (fr)
WO (1) WO2018036167A1 (fr)

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110083528A (zh) * 2019-03-19 2019-08-02 深圳壹账通智能科技有限公司 测试任务的分配方法、装置、计算机设备及存储介质
CN110162481A (zh) * 2019-05-31 2019-08-23 北京星网锐捷网络技术有限公司 一种软件测试方法、装置、设备以及存储介质
CN110489222A (zh) * 2019-08-22 2019-11-22 深圳前海微众银行股份有限公司 任务调度方法、系统、集群服务器及可读存储介质
CN110716876A (zh) * 2019-09-30 2020-01-21 国核自仪系统工程有限公司 自动化验证可编程逻辑代码的测试平台及测试方法
CN111159046A (zh) * 2019-12-31 2020-05-15 斑马网络技术有限公司 测试方法、装置、电子设备、系统和存储介质
CN112579269A (zh) * 2020-12-04 2021-03-30 深圳前海微众银行股份有限公司 一种定时任务处理方法及装置
CN113722237A (zh) * 2021-11-01 2021-11-30 荣耀终端有限公司 设备测试方法和电子设备
CN114024735A (zh) * 2021-11-02 2022-02-08 北京天融信网络安全技术有限公司 一种多任务并行的特征库测试方法及装置
CN114064225A (zh) * 2020-07-31 2022-02-18 中移(苏州)软件技术有限公司 一种自适应调度方法、装置、计算机存储介质及系统
CN114880235A (zh) * 2022-05-20 2022-08-09 统信软件技术有限公司 一种测试用例执行方法、计算设备及存储介质
CN114900574A (zh) * 2022-05-17 2022-08-12 浪潮软件集团有限公司 一种基于多设备与多个app的日常巡检方法及系统
CN115297024A (zh) * 2022-08-19 2022-11-04 山石网科通信技术股份有限公司 网络安全设备的性能测试方法、装置及电子设备
CN115757152A (zh) * 2022-11-23 2023-03-07 五八同城信息技术有限公司 数据处理方法、装置、电子设备及存储介质
CN118331841A (zh) * 2023-12-21 2024-07-12 深圳市智慧城市科技发展集团有限公司 测试引擎管理方法、设备及可读存储介质

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106452830A (zh) * 2016-08-22 2017-02-22 平安科技（深圳）有限公司 测试任务执行机分配方法和装置
CN107291621A (zh) * 2017-07-07 2017-10-24 恒生电子股份有限公司 测试用例的处理方法、处理装置、介质和电子设备
CN107943686A (zh) * 2017-10-30 2018-04-20 北京奇虎科技有限公司 一种测试调度方法、装置、服务器及存储介质
CN108763085A (zh) * 2018-05-31 2018-11-06 平安科技（深圳）有限公司 测试案例的在线调试装置、方法及计算机可读存储介质
CN109194538B (zh) * 2018-08-03 2022-03-25 平安科技（深圳）有限公司 基于分布式协调的测试方法、装置、服务器及存储介质
CN109165158B (zh) * 2018-08-03 2022-11-04 北京奇虎科技有限公司 测试用例的调度方法、装置、计算设备及计算机存储介质
CN109032784A (zh) * 2018-08-07 2018-12-18 郑州云海信息技术有限公司 一种多任务并行构建方法及装置
CN110096416B (zh) * 2019-03-13 2022-07-08 中国平安人寿保险股份有限公司 异常报警方法、装置、计算机装置及可读存储介质
CN110046081A (zh) * 2019-03-18 2019-07-23 平安普惠企业管理有限公司 性能测试方法、性能测试装置、电子设备及存储介质
CN112597030B (zh) * 2020-12-26 2024-09-17 中国农业银行股份有限公司 一种任务发布方法及装置、执行方法及装置、系统
CN112799953A (zh) * 2021-02-08 2021-05-14 北京字节跳动网络技术有限公司 一种接口测试方法及装置、计算机设备及存储介质
CN115796476A (zh) * 2022-10-28 2023-03-14 中车工业研究院有限公司 设计任务审查方法及装置
CN118585308B (zh) * 2024-07-30 2024-11-26 苏州元脑智能科技有限公司 测试方法、装置、系统、电子设备及存储介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101246439A (zh) * 2008-03-18 2008-08-20 中兴通讯股份有限公司 一种基于任务调度的自动化测试方法及系统
CN101719097A (zh) * 2009-12-24 2010-06-02 深圳市金蝶移动互联技术有限公司 自动化测试脚本的调试方法、系统和自动化应用服务器
CN103425536A (zh) * 2013-08-26 2013-12-04 中国科学院软件研究所 一种面向分布式系统性能测试的测试资源管理方法
CN103530231A (zh) * 2013-10-12 2014-01-22 北京京东尚科信息技术有限公司 一种基于业务流程控制的应用程序测试方法及系统
US20150180950A1 (en) * 2013-12-19 2015-06-25 International Business Machines Corporation Test management using distributed computing
CN105183564A (zh) * 2015-09-30 2015-12-23 北京奇虎科技有限公司 基于云测试平台的设备调度方法、装置及系统
CN106452830A (zh) * 2016-08-22 2017-02-22 平安科技（深圳）有限公司 测试任务执行机分配方法和装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9218261B2 (en) * 2013-09-18 2015-12-22 Bank Of America Corporation Test case execution

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101246439A (zh) * 2008-03-18 2008-08-20 中兴通讯股份有限公司 一种基于任务调度的自动化测试方法及系统
CN101719097A (zh) * 2009-12-24 2010-06-02 深圳市金蝶移动互联技术有限公司 自动化测试脚本的调试方法、系统和自动化应用服务器
CN103425536A (zh) * 2013-08-26 2013-12-04 中国科学院软件研究所 一种面向分布式系统性能测试的测试资源管理方法
CN103530231A (zh) * 2013-10-12 2014-01-22 北京京东尚科信息技术有限公司 一种基于业务流程控制的应用程序测试方法及系统
US20150180950A1 (en) * 2013-12-19 2015-06-25 International Business Machines Corporation Test management using distributed computing
CN105183564A (zh) * 2015-09-30 2015-12-23 北京奇虎科技有限公司 基于云测试平台的设备调度方法、装置及系统
CN106452830A (zh) * 2016-08-22 2017-02-22 平安科技（深圳）有限公司 测试任务执行机分配方法和装置

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110083528A (zh) * 2019-03-19 2019-08-02 深圳壹账通智能科技有限公司 测试任务的分配方法、装置、计算机设备及存储介质
CN110162481A (zh) * 2019-05-31 2019-08-23 北京星网锐捷网络技术有限公司 一种软件测试方法、装置、设备以及存储介质
CN110489222A (zh) * 2019-08-22 2019-11-22 深圳前海微众银行股份有限公司 任务调度方法、系统、集群服务器及可读存储介质
CN110716876A (zh) * 2019-09-30 2020-01-21 国核自仪系统工程有限公司 自动化验证可编程逻辑代码的测试平台及测试方法
CN111159046B (zh) * 2019-12-31 2024-04-09 斑马网络技术有限公司 测试方法、装置、电子设备、系统和存储介质
CN111159046A (zh) * 2019-12-31 2020-05-15 斑马网络技术有限公司 测试方法、装置、电子设备、系统和存储介质
CN114064225A (zh) * 2020-07-31 2022-02-18 中移(苏州)软件技术有限公司 一种自适应调度方法、装置、计算机存储介质及系统
CN112579269A (zh) * 2020-12-04 2021-03-30 深圳前海微众银行股份有限公司 一种定时任务处理方法及装置
CN112579269B (zh) * 2020-12-04 2024-07-02 深圳前海微众银行股份有限公司 一种定时任务处理方法及装置
CN113722237A (zh) * 2021-11-01 2021-11-30 荣耀终端有限公司 设备测试方法和电子设备
CN113722237B (zh) * 2021-11-01 2022-02-08 荣耀终端有限公司 设备测试方法和电子设备
CN114024735A (zh) * 2021-11-02 2022-02-08 北京天融信网络安全技术有限公司 一种多任务并行的特征库测试方法及装置
CN114024735B (zh) * 2021-11-02 2024-02-02 北京天融信网络安全技术有限公司 一种多任务并行的特征库测试方法及装置
CN114900574A (zh) * 2022-05-17 2022-08-12 浪潮软件集团有限公司 一种基于多设备与多个app的日常巡检方法及系统
CN114880235A (zh) * 2022-05-20 2022-08-09 统信软件技术有限公司 一种测试用例执行方法、计算设备及存储介质
CN115297024A (zh) * 2022-08-19 2022-11-04 山石网科通信技术股份有限公司 网络安全设备的性能测试方法、装置及电子设备
CN115297024B (zh) * 2022-08-19 2024-02-06 山石网科通信技术股份有限公司 网络安全设备的性能测试方法、装置及电子设备
CN115757152A (zh) * 2022-11-23 2023-03-07 五八同城信息技术有限公司 数据处理方法、装置、电子设备及存储介质
CN118331841A (zh) * 2023-12-21 2024-07-12 深圳市智慧城市科技发展集团有限公司 测试引擎管理方法、设备及可读存储介质

Also Published As

Publication number Publication date
CN106452830A (zh) 2017-02-22

Similar Documents

Publication Publication Date Title
WO2018036167A1 (fr) Procédé, dispositif, serveur et support de stockage d'affectation d'exécuteurs de tâches de test
WO2018014580A1 (fr) Procédé et appareil de test d'interface de données, serveur et support de stockage
WO2018036168A1 (fr) Procédé et dispositif d'exécution de tâche de traitement de données, serveur d'exécution et support de stockage
WO2020253116A1 (fr) Procédé d'exécution de données par lots, dispositif, support d'enregistrement et hôte membre en groupe
WO2020224246A1 (fr) Procédé et appareil de gestion de données fondée sur une chaîne de blocs, dispositif et support d'informations
WO2018103315A1 (fr) Procédé de traitement de données de surveillance, appareil, serveur et équipement de stockage
WO2020224249A1 (fr) Procédé, dispositif et appareil de traitement de transaction basé sur chaîne de blocs, et support de stockage associé
WO2021034024A1 (fr) Appareil électronique et son procédé de commande
WO2020186787A1 (fr) Procédé, dispositif et appareil de planification de tâche intelligente et support de stockage
WO2011105860A2 (fr) Procédé et appareil permettant de générer une image de démarrage minimale
WO2016190476A1 (fr) Procédé destiné à la gestion de clé de chiffrement pour service en nuage et appareil correspondant
WO2015062220A1 (fr) Procédé et système de transmission parallèle sur liaisons sans fil de différents types
WO2020147264A1 (fr) Procédé, appareil et dispositif de surveillance de données de journal multisystème, support d'informations lisible
WO2014044136A1 (fr) Procédé et système de traitement concurrent à base de données distribuées, et support de stockage informatique
WO2021072881A1 (fr) Procédé, appareil et dispositif de traitement de demande fondée sur un stockage d'objet, et support de stockage
WO2020237859A1 (fr) Procédé de migration de données employant un dispositif nbd, appareil, dispositif et support de stockage
WO2020119115A1 (fr) Procédé, dispositif, appareil de vérification de données, et support de stockage
WO2015156596A1 (fr) Dispositif de gestion de mémoire de type matériel et procédé de gestion de mémoire associé
WO2018227772A1 (fr) Procédé et appareil de mise à jour de commande de guichet automatique bancaire, dispositif informatique et support d'informations
WO2018035929A1 (fr) Procédé et appareil de traitement de code de vérification
WO2020224251A1 (fr) Procédé de traitement de transactions de chaîne de blocs, dispositif, appareil et support de stockage
WO2014029354A1 (fr) Procédé, système et client de téléchargement d'images vers l'amont
WO2021051492A1 (fr) Procédé, appareil et dispositif de communication de nœud de service de base de données, et support d'informations informatique
WO2016123898A1 (fr) Procédé de gestion de message court et terminal mobile associé
WO2023018002A1 (fr) Serveur de service de messagerie capable de transmettre un message optimal de notification de distribution sélective en reflétant une rétroaction d'un récepteur de message en temps réel, et son procédé d'exploitation

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17842592

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 25.6.19).

122 Ep: pct application non-entry in european phase

Ref document number: 17842592

Country of ref document: EP

Kind code of ref document: A1