[go: up one dir, main page]

WO2020233089A1 - Procédé et appareil de création de jeu de test, terminal et support de stockage lisible par ordinateur - Google Patents

Procédé et appareil de création de jeu de test, terminal et support de stockage lisible par ordinateur Download PDF

Info

Publication number
WO2020233089A1
WO2020233089A1 PCT/CN2019/122781 CN2019122781W WO2020233089A1 WO 2020233089 A1 WO2020233089 A1 WO 2020233089A1 CN 2019122781 W CN2019122781 W CN 2019122781W WO 2020233089 A1 WO2020233089 A1 WO 2020233089A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
preset
scene
nodes
backbone
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/CN2019/122781
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.)
OneConnect Smart Technology Co Ltd
Original Assignee
OneConnect Smart Technology 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 OneConnect Smart Technology Co Ltd filed Critical OneConnect Smart Technology Co Ltd
Publication of WO2020233089A1 publication Critical patent/WO2020233089A1/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
    • G06F11/3668—Testing of software
    • G06F11/3672—Test management
    • G06F11/3684—Test management for test design, e.g. generating new test cases

Definitions

  • This application relates to the technical field of program testing, and in particular to a method, device, terminal, and computer-readable storage medium for generating test cases.
  • Test case Case is a set of test inputs, execution conditions, and expected results prepared for a particular goal in order to test a program path or verify whether a particular requirement is met.
  • designers write test requirements documents, and testers manually write test cases according to the requirements documents. If there are many process steps or branch processes in the requirements document, there will be many test scenarios. Manually writing test scenarios for all processes will be time-consuming and work-intensive.
  • the main purpose of this application is to provide a test case generation method, device, terminal, and computer-readable storage medium, aiming to solve the technical problems of long time-consuming and heavy workload caused by manually writing test cases, which has become a technical problem that needs to be solved urgently.
  • test case generation method includes:
  • the preset test scenarios corresponding to each of the nodes are associated according to the connection relationship between the nodes, and the test codes corresponding to each of the associated preset test scenarios are combined to form a test case.
  • test case generation device includes:
  • An analysis module which is used to receive a demand document, analyze the demand document, and generate a number of nodes corresponding to the demand document, a scene description corresponding to the node, and the connection relationship between each node ;
  • a query module where the query module is used for the scene description of each node to query the preset test scene corresponding to each node from the preset address;
  • An export module which is configured to associate preset test scenarios corresponding to each of the nodes according to the connection relationship between each node, and combine the test codes corresponding to each of the associated preset test scenarios to form a test case .
  • This application provides a terminal, including a processor, a memory, a communicator, and computer-readable instructions stored on the memory that can be executed by the processor, wherein the computer-readable instructions are executed by the processor When executed, the steps of the aforementioned test case generation method are implemented.
  • This application provides a computer-readable storage medium having computer-readable instructions stored on the computer-readable storage medium, wherein, when the computer-readable instructions are executed by a processor, the test case generation method described above is implemented step.
  • the connection relationship between each node is determined according to the scene description of each node.
  • the preset test scenarios corresponding to the nodes are combined according to the connection relationship, thereby realizing automatic generation of test cases, eliminating the need for staff to manually edit test cases based on demand documents, improving work efficiency and reducing workload.
  • the test cases are automatically generated according to the connection relationship, which effectively avoids the situation that the logic relationship between adjacent nodes is prone to errors in the process of writing test cases due to the complex logic relationship, which leads to inconsistency with the requirements document.
  • FIG. 1 is a schematic diagram of the hardware structure of a terminal involved in a solution of an embodiment of the application
  • FIG. 2 is a schematic flowchart of the first embodiment of the test case generation method of this application.
  • FIG. 3 is a schematic flowchart of a second embodiment of the test case generation method of this application.
  • FIG. 4 is a schematic flowchart of a third embodiment of a test case generation method according to this application.
  • FIG. 5 is a schematic flowchart of a fourth embodiment of a test case generation method according to this application.
  • FIG. 6 is a schematic flowchart of a seventh embodiment of a test case generation method of this application.
  • FIG. 7 is a schematic diagram of modules of the test case generation device of this application.
  • the test case generation method involved in the embodiment of the present application is mainly applied to a terminal.
  • the terminal is a device with processing functions, and may be a portable computer or a server.
  • FIG. 1 is a schematic diagram of a terminal structure involved in a solution of an embodiment of this application.
  • the terminal may include a processor 1001 (for example, a CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005.
  • the communication bus 1002 is used to realize the connection and communication between these components;
  • the user interface 1003 may include a display (Display), an input unit such as a keyboard (Keyboard);
  • the network interface 1004 may optionally include a standard wired interface, a wireless interface (Such as WI-FI interface);
  • the memory 1005 can be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk memory.
  • the memory 1005 may optionally be a storage device independent of the aforementioned processor 1001.
  • the hardware structure shown in FIG. 1 does not constitute a limitation on the device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange different components.
  • the memory 1005 as a computer-readable storage medium in FIG. 1 may include an operating system, a network communication module, and computer-readable instructions.
  • the network communication module is mainly used to connect to the user terminal and perform data communication with the user terminal; and the processor 1001 can call the computer readable instructions stored in the memory 1005 and execute the steps of the test case generation method.
  • test case generation method includes the following steps:
  • Step S100 receiving a demand document, analyzing the demand document, and generating a number of nodes corresponding to the demand document, a scene description corresponding to the node, and the connection relationship between each of the nodes;
  • the requirement document is a pre-set outline set by the designer according to the functions to be tested by the program to be tested.
  • the staff sets up test cases according to the requirement document to test each function of the program to be tested.
  • the requirement document is a flowchart.
  • the requirement document can also be embodied in tabular form or plain text.
  • different analysis programs can be established to integrate the requirement documents. Dataization and standardization of the content in, obtain the nodes listed in the requirements document, the scene description of the corresponding nodes, and the connection relationship between each node.
  • the scene description is a detailed description of the functions and application scenarios of each node.
  • the connection relationship is the logical relationship and judgment rule between each node.
  • the demand document When the demand document is expressed in plain text, it is recognized through word segmentation, semantic recognition, keyword comparison, etc.
  • the demand document composed of plain text there are several nodes, the scene description of each node, and the connection between each node relationship. For example, if the requirement document records "the first test account is incorrectly entered in the login page, the test password is incorrectly entered, and the final test verification code is incorrectly entered", it can be known through word segmentation, semantic recognition, keyword comparison, etc., that there is a "verification account entry There are three nodes, "Error”, “Incorrect verification password”, and “Incorrect verification code”, among which the connection relationship is carried out in sequence.
  • Step S200 query the preset test scene corresponding to each node from the preset address according to the scene description of each node;
  • the preset address points to a storage space that stores preset test scenarios and test codes of preset test scenarios preset by those skilled in the art, and may specifically be a uniform resource locator (niform Resoure Locator, url).
  • the test code is test data prepared by those skilled in the art for each scenario in advance. For example: for the scenario where the login password is wrong and the wrong password prompt pops up, write the test data for logging in with the wrong password in advance. When it is necessary to verify the scenario where the login password is wrong, write the test data for logging in with the wrong password in advance.
  • Step S300 Associate preset test scenarios corresponding to each of the nodes according to the connection relationship between each of the nodes, and combine the test codes corresponding to each of the associated preset test scenarios to form a test case.
  • the test agent corresponding to the preset test scenario of each node is formed into a whole according to the connection relationship, and the whole is a test case that matches the requirement document .
  • This application analyzes the requirements document to obtain the required number of nodes in the requirement document, the scene description of the node, and the connection relationship between each node.
  • the preset corresponding to each node is determined according to the scene description of each node.
  • the test cases are automatically generated according to the connection relationship, which effectively avoids the situation that the logic relationship between adjacent nodes is prone to errors in the process of writing test cases due to the complex logic relationship, which leads to inconsistency with the requirements document.
  • step S100 includes:
  • Step S110 receiving the flowchart, comparing the flowchart with a preset graphic element template library, and identifying the positions of arrows and connecting lines in the flowchart;
  • arrows and connecting lines of various shapes and different manifestations are preset in the preset graphic element template library, so that the arrows and connecting lines in the process can be identified.
  • Step S120 Perform grayscale processing on the flowchart to generate a grayscale value matrix
  • the color parameters in the flowchart are discarded by gray-scale processing of the flowchart, which is helpful for identifying the node boxes in the flowchart.
  • Each element in the matrix represents the gray value of the corresponding pixel (the value is 0-255).
  • the background color in the flowchart is white (gray value 255)
  • the node frame is black (gray value less than 255).
  • Step S130 Identify the node frame in the grayscale matrix according to the gray value matrix in combination with the arrow and connecting line positions, and set one of the node frames as one of the nodes;
  • each node frame has a color difference with the background, through color difference analysis, the position coordinates of each node frame and each node frame are obtained.
  • Step S140 generating a connection relationship between each of the nodes according to the position of the arrow and the connecting line;
  • step S 110 Identify the arrows and connecting lines in the flowchart, and combine the gray value matrix to mark the start and end positions of each arrow and connecting line, and compare the marked results with the position coordinates of the node box, namely The connection relationship of the nodes corresponding to each node frame can be obtained.
  • Step S150 Recognize the text in each node frame through OCR text recognition technology, and generate a scene description corresponding to the node.
  • OCR optical character recognition
  • the nodes, scene descriptions, and connection relationships embodied in the flow chart in the form of pictures can be transformed into a computer-understandable data form.
  • the designer expresses the requirement document with a flowchart, which is convenient for the designer to design.
  • test scenario includes a preset backbone scenario and a preset branch scenario;
  • step S200 includes:
  • Step S210 Query the preset backbone scene corresponding to the current node from the preset address according to the scene description of the current node;
  • the scene description is not clear, it is possible that the corresponding preset backbone scene cannot be queried from the preset address according to the scene description of the node.
  • the node is marked and prompt information is generated. The user is prompted to manually edit the test code added to the node.
  • the preset main test scenario cannot be queried. At this time, you can set to skip the node or start from the preset branch test scenario corresponding to the previous node of the current node Inquire.
  • the node in the first order must be the default backbone scene
  • the node in the second-Nth order may be the default backbone scene or the preset branch scene.
  • the preset test scenario corresponding to the first node is queried from the preset address from the first node, that is, the current node in step S210 must be available from the preset address.
  • the preset backbone scene corresponding to the current node is queried in the address.
  • Step S220 if the preset backbone scene corresponding to the current node is queried from the preset address, determine the connection relationship between the current node and the previous node as the backbone process;
  • the previous node is the node performed before the current node.
  • the connection relationship not only indicates the direct connection or indirect connection between the nodes, but also indicates whether the relationship between the nodes is the main process or the branch process.
  • Step S230 If the preset backbone scene corresponding to the current node cannot be found from the preset address, determine that the connection relationship between the current node and the previous node is a branch process;
  • the preset address stores a preset backbone scene, and when the corresponding preset backbone scene cannot be queried for the scene description of the node, the node may be a preset branch scene.
  • Step S240 sequentially determining subsequent nodes connected to the current node according to the arrow and the position of the connecting line, and querying the preset backbone corresponding to the subsequent node from the preset address according to the scene description of the subsequent node Scenes;
  • multiple subsequent nodes N+1, N+2, N+n... can also be directly or indirectly connected, and it is determined in turn whether the preset address can be queried with each subsequent node.
  • Step S250 Confirm the connection relationship between each node according to the query result.
  • step S220 There may be two query results. One is similar to step S220, and the corresponding preset backbone scene is queried, then the connection relationship between nodes is confirmed as the backbone process; the other is similar to step S230, and the corresponding preset backbone scene cannot be queried. , Then confirm that the connection relationship between nodes is a branch process. Determine the connection relationship between each node until the last node is determined.
  • the connection relationship between the nodes corresponding to the preset trunk scene is listed as the trunk process, so that each node in the trunk process can be further corresponding to the preset trunk
  • the test code combination of the scenario forms a test case.
  • FIG. 5 is a schematic flowchart of the fourth embodiment of the test case generation method of this application. Based on the third embodiment, after step S230, it includes:
  • Step S260 Query at least one of the preset branch scenarios corresponding to the previous node from the preset address;
  • One or more preset branch scenes are preset in the preset address to correspond to one preset trunk scene.
  • one preset branch scene may also correspond to multiple preset trunk scenes.
  • the default backbone scene corresponding to node N-1 is the login page scene, you can set the verification verification code input error scene, the verification account input error scene, and the verification password input error scene.
  • the preset branch scene corresponds to the login page scene, the current node N corresponds to one of the scenario where the verification code is entered incorrectly, the verification account is entered incorrectly, and the verification password is entered incorrectly.
  • Step S270 According to the scene description of the current node, a preset branch scene corresponding to the current node is obtained by comparing from the preset branch scene corresponding to the previous node.
  • preset branch scenes are preset for the preset trunk scenes, so that the nodes after the nodes corresponding to the preset trunk scenes can be selected from the preset branch scenes , To reduce the amount of calculation in the comparison process.
  • step S270 the method includes:
  • the required scene is a preset branch scene that must be performed after a preset main scene.
  • the number of necessary scenes corresponding to the preset main scene is less than or equal to the preset branch scenes corresponding to the preset main scene.
  • step S300 includes:
  • connection relationship with each node in the backbone node chain is the node of the branch process, and the test code of the preset branch scene corresponding to the node of the branch process is filled in the test code according to the connection relationship.
  • a test case is formed.
  • each backbone node chain can be parallel, that is, the nodes in each backbone node chain are evenly distributed; it can also be crossed, that is, the same points are both It belongs to the backbone node chain A, and belongs to the backbone node chain B.
  • the user makes node chain selection operations by clicking, sliding, etc., one backbone node chain can be selected at a time, or multiple backbone node chains can be selected.
  • test cases are dynamically generated, which is convenient for users to change dynamic use cases according to actual conditions.
  • step S210 includes:
  • Step S211 Obtain a first keyword corresponding to the preset backbone scene, and determine whether the first keyword exists in the scene description of the node;
  • the first keyword may specifically be composed of one vocabulary or multiple vocabulary, or may be composed of multiple vocabulary and logical words. Each node can be distinguished by the first keyword. For example, if the scenario description is "Test the account login function on the login page", the first keyword can be set to "Login page and account account”.
  • Step S212 If the first keyword exists in the scene description, set the node to correspond to the preset backbone scene corresponding to the first keyword.
  • the previous node connected to the node is determined according to the position of the arrow and the connecting line, in the preset branch scene corresponding to the previous node Select a preset branch scene to correspond to the node. If it fails to match a preset backbone scene corresponding to the node in the preset branch scene corresponding to the previous node, a prompt message is generated to prompt the user to edit manually.
  • the preset backbone scene corresponding to each node is determined by setting the first keyword, and then the preset branch scene is determined by the scene description, so that the amount of setting of the first keyword is small and the comparison error is reduced.
  • test case generation device which includes:
  • the analysis module 10 is used to receive a demand document, analyze the demand document, and generate a number of nodes corresponding to the demand document, a scene description corresponding to the node, and the relationship between each node Connection relationship
  • Query module 20 which is used for the scene description of each node to query the preset test scene corresponding to each node from the preset address;
  • An export module 30 which is configured to associate preset test scenarios corresponding to each of the nodes according to the connection relationship between each node, and combine the test codes corresponding to each of the associated preset test scenarios to form Test case.
  • the requirement document is a flowchart;
  • the analysis module 10 includes: a first recognition unit, the first recognition unit is configured to receive the flowchart, and compare the flowchart with a preset graphic element template library Yes, identify the positions of the arrows and connecting lines in the flowchart; the gray-scale processing unit, perform gray-scale processing on the flowchart to generate a gray-scale value matrix; the second identification unit, the second identification unit is used According to the gray value matrix and the position of the arrow and the connecting line, the node frame in the gray value matrix is identified, and one of the node frames is set as one of the nodes; the first identification unit is also used for The connection relationship between the nodes is generated according to the position of the arrow and the connecting line; the third recognition unit, the third recognition unit is used to recognize the text in each of the node frames through OCR text recognition technology, and generate the corresponding The scene description of the node.
  • the query module 20 includes: a query unit configured to query the preset backbone scene corresponding to the current node from the preset address according to the scene description of the current node; a determination unit, the The determining unit is configured to determine that the connection relationship between the current node and the previous node is the backbone process if the preset backbone scene corresponding to the current node is queried from the preset address; If the preset backbone scene corresponding to the current node cannot be queried in the preset address, it is determined that the connection relationship between the current node and the previous node is a branch process; the query unit is further configured to The subsequent nodes connected to the current node are sequentially determined according to the position of the arrow and the connecting line, and the preset backbone scene corresponding to the subsequent node is queried from the preset address according to the scene description of the subsequent node; The determining unit is also used for confirming the connection relationship between the various nodes according to the query result.
  • the query unit is further configured to query at least one of the preset branch scenes corresponding to the previous node from the preset address; according to the scene description of the current node, from the previous node The comparison among the corresponding preset branch scenes obtains a preset branch scene corresponding to the current node.
  • the query module 20 further includes: an acquiring unit configured to acquire the necessary scene corresponding to the previous node, and determine whether the preset branch scene of each node connected to the previous node is Contains all the necessary scenes; a prompt unit configured to generate prompt information if the preset branch scenes of each node connected to the previous node do not contain all the necessary scenes.
  • the export module 30 includes: an associating unit, the associating unit is used to associate the connection relationship between the nodes of the backbone process to form at least one backbone node chain; a receiving unit, the receiving unit is used to receive users The node chain selection operation made according to the backbone node chain; the association unit is further configured to associate preset backbone scenarios corresponding to each node in at least one of the backbone node chains according to the node chain selection operation, and The associated test codes corresponding to each of the preset backbone scenarios are combined to form a backbone use case; it is determined that the connection relationship with each node in the backbone node chain is the node of the branch process, which will correspond to the node of the branch process The test code of the preset branch scenario is filled into the main use case according to the connection relationship to form a test case.
  • the query unit is also used to obtain the first keyword corresponding to the preset backbone scene, and determine whether the first keyword exists in the scene description of the node; if all the first keywords exist in the scene description If the first keyword is mentioned, the node is set to correspond to the preset backbone scene corresponding to the first keyword.
  • the present application also provides a computer-readable storage medium on which computer-readable instructions are stored.
  • the steps of the above-mentioned interface update method are implemented.
  • the storage medium is specifically a non-volatile computer-readable storage medium.

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)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Debugging And Monitoring (AREA)

Abstract

L'invention concerne un procédé et un appareil de création de jeu de test, un terminal et un support de stockage lisible par ordinateur, le procédé consistant à : recevoir un document de conditions et analyser le document de conditions pour générer un certain nombre de nœuds correspondant au document de conditions, une description de scénario des nœuds, et la relation de connexion entre chaque nœud (S100) ; sur la base de la description de scénario des nœuds, interroger à partir d'une adresse prédéfinie un scénario de test prédéfini correspondant à chaque nœud (S200) ; sur la base de la relation de connexion entre chaque nœud, associer le scénario de test prédéfini correspondant à chaque nœud, et combiner les codes de test correspondant à chaque scénario de test prédéfini associé pour former un jeu de test (S300).
PCT/CN2019/122781 2019-05-21 2019-12-03 Procédé et appareil de création de jeu de test, terminal et support de stockage lisible par ordinateur Ceased WO2020233089A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910433511.5A CN110287104A (zh) 2019-05-21 2019-05-21 测试用例生成方法、装置、终端及计算机可读存储介质
CN201910433511.5 2019-05-21

Publications (1)

Publication Number Publication Date
WO2020233089A1 true WO2020233089A1 (fr) 2020-11-26

Family

ID=68002437

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/122781 Ceased WO2020233089A1 (fr) 2019-05-21 2019-12-03 Procédé et appareil de création de jeu de test, terminal et support de stockage lisible par ordinateur

Country Status (2)

Country Link
CN (1) CN110287104A (fr)
WO (1) WO2020233089A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112597034A (zh) * 2020-12-25 2021-04-02 深圳证券交易所 测试用例的生成方法、装置及计算机可读存储介质
CN113590453A (zh) * 2021-01-28 2021-11-02 腾讯科技（深圳）有限公司 测试用例的生成方法、装置与存储介质
CN114338472A (zh) * 2021-12-31 2022-04-12 北京百度网讯科技有限公司 地图服务器的容量测试方法、装置、设备、介质及产品
CN114911709A (zh) * 2022-06-09 2022-08-16 湖南快乐阳光互动娱乐传媒有限公司 一种数据处理方法、装置、电子设备、计算机存储介质
CN114968795A (zh) * 2022-06-07 2022-08-30 中国银行股份有限公司 一种测试方法、装置、电子设备、及计算机存储介质
CN115391216A (zh) * 2022-09-01 2022-11-25 中国银行股份有限公司 一种测试案例生成方法及相关装置

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110287104A (zh) * 2019-05-21 2019-09-27 深圳壹账通智能科技有限公司 测试用例生成方法、装置、终端及计算机可读存储介质
CN114077534B (zh) * 2020-08-11 2024-05-31 腾讯科技（深圳）有限公司 测试用例生成方法、装置和计算机可读存储介质
CN113377653B (zh) * 2021-06-10 2023-09-26 北京京东振世信息技术有限公司 生成测试用例的方法和装置
CN113760754A (zh) * 2021-08-23 2021-12-07 苏宁易购集团股份有限公司 基于图搜索的测试案例生成的方法、系统及存储介质
CN119883937A (zh) * 2025-03-25 2025-04-25 杭州新中大科技股份有限公司 测试用例生成方法、装置、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150026664A1 (en) * 2013-07-17 2015-01-22 International Business Machines Corporation Method and system for automated test case selection
CN107832231A (zh) * 2017-12-05 2018-03-23 郑州云海信息技术有限公司 一种系统测试方法、装置及介质
CN108595338A (zh) * 2018-05-08 2018-09-28 平安普惠企业管理有限公司 测试用例编写方法、装置、计算机设备及存储介质
CN109710508A (zh) * 2018-08-20 2019-05-03 平安普惠企业管理有限公司 测试方法、测试装置、测试设备及计算机可读存储介质
CN110287104A (zh) * 2019-05-21 2019-09-27 深圳壹账通智能科技有限公司 测试用例生成方法、装置、终端及计算机可读存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150026664A1 (en) * 2013-07-17 2015-01-22 International Business Machines Corporation Method and system for automated test case selection
CN107832231A (zh) * 2017-12-05 2018-03-23 郑州云海信息技术有限公司 一种系统测试方法、装置及介质
CN108595338A (zh) * 2018-05-08 2018-09-28 平安普惠企业管理有限公司 测试用例编写方法、装置、计算机设备及存储介质
CN109710508A (zh) * 2018-08-20 2019-05-03 平安普惠企业管理有限公司 测试方法、测试装置、测试设备及计算机可读存储介质
CN110287104A (zh) * 2019-05-21 2019-09-27 深圳壹账通智能科技有限公司 测试用例生成方法、装置、终端及计算机可读存储介质

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112597034A (zh) * 2020-12-25 2021-04-02 深圳证券交易所 测试用例的生成方法、装置及计算机可读存储介质
CN113590453A (zh) * 2021-01-28 2021-11-02 腾讯科技（深圳）有限公司 测试用例的生成方法、装置与存储介质
CN114338472A (zh) * 2021-12-31 2022-04-12 北京百度网讯科技有限公司 地图服务器的容量测试方法、装置、设备、介质及产品
CN114338472B (zh) * 2021-12-31 2024-05-07 北京百度网讯科技有限公司 地图服务器的容量测试方法、装置、设备、介质及产品
CN114968795A (zh) * 2022-06-07 2022-08-30 中国银行股份有限公司 一种测试方法、装置、电子设备、及计算机存储介质
CN114911709A (zh) * 2022-06-09 2022-08-16 湖南快乐阳光互动娱乐传媒有限公司 一种数据处理方法、装置、电子设备、计算机存储介质
CN115391216A (zh) * 2022-09-01 2022-11-25 中国银行股份有限公司 一种测试案例生成方法及相关装置

Also Published As

Publication number Publication date
CN110287104A (zh) 2019-09-27

Similar Documents

Publication Publication Date Title
WO2020233089A1 (fr) Procédé et appareil de création de jeu de test, terminal et support de stockage lisible par ordinateur
WO2020015067A1 (fr) Procédé d'acquisition de données, dispositif, équipement et support de stockage
WO2020233090A1 (fr) Procédé, appareil et dispositif de configuration d'application basés sur une page h5, et support de stockage
WO2020147385A1 (fr) Procédé et appareil d'entrée de données, terminal et support d'informations lisible par ordinateur
WO2016112558A1 (fr) Procédé et système de mise en correspondance de questions dans un système d'interaction intelligent
WO2020119115A1 (fr) Procédé, dispositif, appareil de vérification de données, et support de stockage
WO2021051558A1 (fr) Procédé et appareil de questions et réponses basées sur un graphe de connaissances et support de stockage
WO2020143322A1 (fr) Procédé et appareil de détection de demande d'utilisateur, dispositif informatique et support de stockage
WO2020107761A1 (fr) Procédé, appareil et dispositif de traitement de copie de publicité et support d'informations lisible par ordinateur
WO2020119369A1 (fr) Procédé, appareil et dispositif de positionnement de défaut de fonctionnement et de maintenance informatique intelligent, et support de stockage lisible
WO2020015064A1 (fr) Procédé de traitement de défaillance de système, appareil, dispositif et support d'informations
WO2020119069A1 (fr) Procédé et dispositif de génération de texte basés sur un réseau neuronal auto-codé, et terminal et support
WO2020087978A1 (fr) Procédé, appareil et dispositif de génération de modèle de vérification des contrôles des risques, et support d'informations
WO2021215620A1 (fr) Dispositif et procédé pour générer automatiquement un sous-titre d'image spécifique au domaine à l'aide d'une ontologie sémantique
WO2021003956A1 (fr) Procédé, appareil et dispositif de gestion d'informations de produit et support d'enregistrement
WO2020087981A1 (fr) Procédé et appareil de génération de modèle d'audit de contrôle de risque, dispositif, et support de stockage lisible
WO2020062640A1 (fr) Procédé, serveur et support de stockage pour changer une langue de rédaction dynamique d'application de terminal
WO2019024485A1 (fr) Procédé et dispositif de partage de données, et support de stockage lisible par ordinateur
WO2020062658A1 (fr) Procédé et appareil de génération de contrat, dispositif et support de stockage
WO2020098078A1 (fr) Procédé et appareil destinés à générer un échantillon d'entraînement d'ocr, dispositif et support de stockage lisible
WO2020107591A1 (fr) Procédé, appareil, dispositif de limitation de double assurance et support d'informations lisible
WO2020073494A1 (fr) Procédé de détection de porte arrière de page web, dispositif, support d'informations et appareil
WO2020062661A1 (fr) Procédé, dispositif et appareil de vérification de cohérence de données de contrat et support d'enregistrement
WO2020224251A1 (fr) Procédé de traitement de transactions de chaîne de blocs, dispositif, appareil et support de stockage
WO2024248451A1 (fr) Appareil basé sur un grand modèle de langage pour préparer un document électronique par conversation en langage naturel et procédé de préparation d'un document électronique au moyen de cet appareil

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: 19929439

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 1205 DATED 04/03/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 19929439

Country of ref document: EP

Kind code of ref document: A1