WO2019153472A1 - Procédé de test automatisé d'interfaces, dispositif, équipement, et support de stockage - Google Patents

Procédé de test automatisé d'interfaces, dispositif, équipement, et support de stockage Download PDF

Info

Publication number
WO2019153472A1
WO2019153472A1 PCT/CN2018/081545 CN2018081545W WO2019153472A1 WO 2019153472 A1 WO2019153472 A1 WO 2019153472A1 CN 2018081545 W CN2018081545 W CN 2018081545W WO 2019153472 A1 WO2019153472 A1 WO 2019153472A1
Authority
WO
WIPO (PCT)
Prior art keywords
test
json
test case
interface
automatically
Prior art date
Application number
PCT/CN2018/081545
Other languages
English (en)
Chinese (zh)
Inventor
贾江丽
Original Assignee
平安科技（深圳）有限公司
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 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019153472A1 publication Critical patent/WO2019153472A1/fr

Links

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/3684—Test management for test design, e.g. generating new test cases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3688—Test management for test execution, e.g. scheduling of test suites

Definitions

  • This application belongs to the field of software testing, and more specifically to an interface automatic test method, apparatus, device and storage medium.
  • Interface testing is a test of the interface between test system components. It is mainly used to detect the interaction between external systems and systems and internal subsystems, focusing on data exchange, transfer and control management processes, and inter-system Mutual logical dependencies, etc.
  • the present application provides an interface automatic test method, apparatus, device, and storage medium, which can improve the degree of automation and the efficiency of testing.
  • a first aspect of the present application provides an interface automation testing method, the method comprising the following steps:
  • the second party of the present application provides an interface automatic testing device, the device comprising:
  • a sample generation module an interface document for acquiring different interfaces, and automatically generating a Json test sample of different interfaces according to the interface document;
  • a script generation module configured to automatically generate a test case template according to the Json test sample, automatically generate a Json test case according to the test case template, and automatically generate a Jmeter test script according to the Json test case;
  • the interface test module is configured to generate an integrated test case according to the Jmeter test script, invoke the integrated test case by using a test tool, and trigger the Jmeter test script to test by the integrated test case, and automatically output the test result.
  • a third aspect of the present application provides a terminal device including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, wherein the processor executes the computer The following steps are implemented when the instructions are readable:
  • a fourth aspect of the present application provides one or more non-transitory readable storage mediums storing computer readable instructions, the computer readable instructions being executed by one or more processors such that the one or more processes Perform the following steps:
  • the interface automatic test method, device, device and storage medium provided by the application automatically generate test samples, test sample sets, test case templates, Json test cases, Jmeter test scripts and integrated test cases through interface documents, and then pass the test.
  • the tool calls the Jmeter test script to test, automatically outputs the test result, and the degree of automation is high, which improves the efficiency of the test.
  • a new test script can be quickly generated for testing, and the interface test process is easy to maintain.
  • FIG. 1 is a flowchart of an interface automatic testing method according to an embodiment of the present application
  • FIG. 2 is a diagram showing an example of a request message and a response message in the embodiment shown in FIG. 1;
  • FIG. 3 is a diagram showing an example of a test sample set of the embodiment shown in FIG. 1;
  • FIG. 4 is a diagram showing an example of a test case template of the embodiment shown in FIG. 1;
  • Figure 5 is a flow chart showing the sub-steps of the step S103 of the embodiment shown in Figure 1;
  • FIG. 6 is a schematic structural diagram of an interface automatic testing apparatus according to another embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a terminal device according to another embodiment of the present disclosure.
  • FIG. 1 is a flowchart of an interface automatic testing method provided by an embodiment of the present application.
  • Interface testing refers to testing the application program interface (API), including two types: one is the external interface, that is, the call between the system and the system, such as the interface call between the Taobao order system and the payment system; the other is the internal interface. It refers to the call of the upper layer service to the lower layer service or the call between the service and the service.
  • API application program interface
  • the business layer calls the data layer, the business layer is the upper layer service, the data layer is the lower layer service, and for example, the goods are selected and the order is created.
  • the role of interface testing is to check whether the data exchange, delivery, and management processes between interfaces are normal.
  • the interface automatic testing method provided by the embodiment of the present application includes the following steps:
  • Step S101 Obtain an interface document of different interfaces, and automatically generate a Json test sample of different interfaces according to the interface document.
  • the interface document refers to the interface parameters provided by the developer of the application for different interface tests.
  • the interface document mainly includes four parts of the request method, the URI, the request parameter and the return parameter.
  • the request method usually includes: GET/PUT/POST/DELETE; the URI is a Uniform Resource Identifier (URI), which is a string for identifying the name of an Internet resource, starting with /a, if you need to log in.
  • the interface to be called (such as adding, modifying; user information of the foreground, fund information, etc.) needs to add /u, ie: /a/u; generally put the table name or the word that can express this interface; request parameters and return Parameters usually include: field, description, type, comment, required or not.
  • the data of the interface document can be called according to the outer field name in the interface description table of an interface document, and a test sample in the Json format is automatically generated.
  • the interface description table refers to a table that generalizes the interface, including the name, field name, type, format, and the like of the interface document information; the outer field name refers to the field of the outermost interface in the interface document.
  • the information of the inspector is used as an outer field name, and the name, gender, ID number, etc. of the inspected person can be called from the interface document according to the information of the inspected person.
  • Information data is used as an outer field name, and the name, gender, ID number, etc.
  • the names of the outer field names of the interface description document mainly include: system code, salesperson code, effective date, hierarchical information, information of the inspected person, the total number of inspected persons, and the like.
  • the Json test sample generation tool can be used to call various information data in the interface document through these outer field names.
  • the JSON format is generated by the test sample, mainly because the data between the interfaces is transmitted in the Json format; optionally, the Json test sample automatic generation tool is generated by the VBA script.
  • the test sample of the Json format mainly includes a request message and a response message.
  • FIG. 2 shows an example diagram of the request message and the response message, as shown in FIG. 2(a)
  • the request message The request method in the text is a method for sending a request to the interface, requesting the field name as the outer field name, and calling the data of the interface document according to the outer field name to make a specific request for the interface, “non-empty”, “length”, “ The type is to limit the format of the request message; as shown in Figure 2(b), the returned result in the response message is the result returned by the interface, and the return field name is the outer field name, according to the outer field name.
  • the data of the calling interface document returns the specific result.
  • Non-empty "length”, and “type” are used to define the format of the response message.
  • the interface receives the request packet, searches for the resource to be requested in the system or the platform according to the request packet, and converts the resource into a response packet after the resource is found.
  • Step S102 automatically generate a test case template according to the Json test sample, and automatically generate a Json test case according to the test case template, and then automatically generate a Jmeter test script according to the Json test case.
  • Interface testing includes testing many different interfaces. For example, in the interface test for purchasing insurance, you need to test the interfaces such as "customer authentication”, “insurance information verification”, “mobile phone number change”, “insured” and so on. Therefore, the Json test samples of all interfaces can be gathered together to generate a Json test sample set, which facilitates centralized management of interface tests and subsequent integration tests, making the interface test process more intuitive.
  • FIG. 3 shows an example diagram of a test sample set. As shown in FIG.
  • the interface test includes testing of N interfaces
  • the interface name refers to a process of the system under test
  • the interface description means that the interface name is The corresponding process direction in the system
  • the data following the interface description is the request message and the response message corresponding to the Json sample generated by each interface document.
  • Json test sample is automatically generated according to each interface document, and then all Json test samples are grouped in a table to form a Json test sample set.
  • the test case template mainly includes the request message and the result verification corresponding to the request message, please refer to FIG. It shows an example diagram of a test case template.
  • Figure 4 is an example of a Json test sample with the request field name "Customer Authentication", where the call field name is a request with the request field name "Customer Authentication”.
  • the field name called by the method parameter, including "customer name”, “gender”, "date of birth”, “document type”, “document number”, and then set the result verification according to the data of each call field name.
  • the result is a security test on the interface, so that the interface can run normally in various scenarios.
  • the result verification can be set according to the pre-defined interface test strategy and actual situation.
  • Jmeter test case generation tool After inputting the value verified by the result, click the Json test case generation tool, you can generate a JSON format test case based on the test case module of an interface, and then click the Jmeter test case generation tool to generate the Jmeter format according to the Json format test case.
  • the test script, jmx. is the suffix file; the Jmeter test script named after the interface name is generated in the preset storage path while generating the test script, for example, according to the "customer authentication" interface in the predetermined storage path (eg D hard drive) Generate a Jmeter test script for "Customer Authentication.jmx".
  • Jmeter is a Java-based stress testing tool developed by the Apache organization, which can be applied to interface testing.
  • the Json test case generation tool and the Jmeter test case generation tool are also generated by VBA scripts.
  • Step S103 generating an integrated test case according to the Jmeter test script, calling the integration test case through the test tool, and triggering the Jmeter test script to test through the integrated test case, and automatically outputting the test result.
  • the integration test case refers to the integration of all modules according to the design requirements (such as according to the structure diagram) into subsystems or systems for integration testing; the role of integration testing is that each unit and module can work normally. Under the premise, verify that the connection works for global operation.
  • test cases are written into the integration test case of the integration test tool so that integration tests can be performed.
  • the integration test tool uses the Ant integration test tool.
  • Ant is a tool that automates the steps of compiling, testing, and deploying software. Most of them are used for software development in the Java environment.
  • step S103 the following sub-steps are further included:
  • Step S1031 Generate an integrated test case in an xml format according to the storage path and the result output path of the Jmeter test script.
  • Step S1032 running the Ant integration test tool to call the integration test case, so that the integration test case triggers the Jmeter test script to test through the storage path of the Jmeter test script.
  • step S1033 the test response message is automatically compared with the response message, and the test result is output according to the result output path.
  • BUILD.xml create an integration test case named BUILD.xml, generate a test case according to the format of the Ant integration tool, and input the storage path of the Jmeter test script and the test result path to be output into the BUILD.xml integration test case.
  • test result is that the response message obtained after running the test is automatically compared with the response message in the Json sample. If the test result is consistent with the expected result, the interface meets the usage requirements and can be used normally, if the test result and expectation If the results are inconsistent, the interface is faulty and needs to be further improved.
  • the Jmeter test tool can be used to directly call the Jmeter test case to perform interface test.
  • Jmeter can only perform interface test on one interface. That is, integration testing cannot be performed, but testing with Jmeter can simulate stress testing by means of concurrent threads, and has better effect on performance testing of interface testing. Therefore, Jmeter can be used to perform interface testing of a single interface before integration. Testing to make interface testing more complete.
  • the performance test mainly includes: response speed, interface fault tolerance, interface load and other performance tests.
  • the specific maintenance process is: obtaining a modified interface document from a developer, and then sequentially generating a Json test sample, a Json test case, and a Jmeter test case according to the modified interface file, and then writing the Jmeter test case.
  • the test tool is called to test the test case and output the test result.
  • the interface automatic test method provided by the embodiment of the present application can make the whole maintenance process relatively simple and high in efficiency.
  • the template automatically generates Json test cases, and then clicks the Jmeter test case generation tool to automatically generate Jmeter test cases.
  • the interface automatic test method provided by the embodiment of the present application automatically generates a test case from the interface document through an automated generation tool, and then uses the integrated test tool to call the test case for interface test, automatically outputs the test result, and verifies the performance and security of the test result.
  • the test case can be automatically generated only by modifying the interface part, and the test cases of other interfaces need not be regenerated, the maintenance process is relatively simple and the efficiency is high;
  • the corresponding automatic data generation tool automatically generates the corresponding transition data, which reduces the requirements of the interface tester, improves the degree of automation, and improves the interface test efficiency.
  • FIG. 6 is a schematic structural diagram of an interface automatic testing apparatus provided by an embodiment of the present application.
  • the interface automation test apparatus 20 includes a sample generation module 201, a script generation module 202, and an interface test module 203.
  • the sample generation module 201 is configured to obtain an interface document of different interfaces, and automatically generate a Json test sample of different interfaces according to the interface document.
  • the sample generation module 201 can automatically generate a test sample of the Json format according to the outer field name in the interface description table of an interface document by running the Json test sample automatic generation tool, Json.
  • the test samples of the format mainly include request messages and response messages.
  • the Json test sample auto-generation tool is generated by a VBA script.
  • the script generation module 202 is configured to automatically generate a test case template according to the Json test sample, automatically generate a Json test case according to the test case module, and automatically generate a Jmeter test script according to the Json test case.
  • the sample generation module 201 automatically generates a Json test sample according to each interface document, and then the script generation module 202 sets all the Json test samples in a table to form a Json test sample set.
  • the script generation module 202 can automatically generate a test case template of all interfaces according to the test sample set by running the test case template generation tool.
  • the test case template mainly includes the request message and the result verification corresponding to the request message.
  • the script generation module 202 obtains the specific value of the result verification.
  • the Json test case generation tool By running the Json test case generation tool, the JSON format test case can be generated according to the test case module of an interface, and then the Jmeter test case generation tool can be executed according to the Jmeter test case generation tool. Test cases in Json format generate test scripts in Jmeter format.
  • the Json test case generation tool and the Jmeter test case generation tool are also generated by VBA scripts.
  • the interface test module 203 is configured to generate an integrated test case according to the Jmeter test script, invoke the integration test case through the test tool, and trigger the Jmeter test script to test through the integrated test case, and automatically output the test result.
  • the interface test module 203 writes the Jmeter test script into an integrated test case of the integrated test tool.
  • the integration test tool adopts an Ant integration test tool
  • the interface test module 203 creates an integration test case named BUILD.xml, generates a test case according to the format of the Ant integration tool, and simultaneously stores the storage path of the Jmeter test script and outputs The test result path is entered into the BUILD.xml integration test case.
  • the interface test module 203 calls the integration test case of BUILD.xml by running Ant's integrated test tool, so that the integration test case triggers the Jmeter test case to perform the integration test through the storage path of the Jmeter test script, and outputs the path according to the input test result after the test is completed. Test Results.
  • the interface test module 203 can directly call the Jmeter test case to test the interface by using the Jmeter test tool. It should be understood that the Jmeter can only be used for one interface. Interface testing, that is, integration testing is not possible, but testing with Jmeter can simulate stress testing by means of concurrent threads, and has better effect on performance testing of interface testing. Therefore, interface testing module 203 can use Jmeter for single testing. After the interface test of the interface, the integration test is performed to make the interface test more complete.
  • the specific maintenance process is: the interface automation testing device 20 obtains the modified interface document through the sample generation module 201, generates a modified Json test sample, and then the script generation module 202 sequentially according to the Json test sample. The test case template, the Json test case, and the Jmeter test case are generated. Finally, the modified Jmeter test case is written into the integrated test case by the interface test module 203, and the test tool is called to test the test case and output the test result.
  • the interface automatic testing device provided by the embodiment of the present application automatically generates test cases step by step from the interface document through the automatic generation tool, and then uses the integrated test tool to call the test case for interface test, automatically outputs the test result, and verifies the performance and security of the test result.
  • the test case can be automatically generated only by modifying the interface part, and the test cases of other interfaces need not be regenerated, the maintenance process is relatively simple and the efficiency is high;
  • the corresponding automatic data generation tool automatically generates the corresponding transition data, which reduces the requirements of the interface tester, improves the degree of automation, and improves the interface test efficiency.
  • Another embodiment of the present application provides one or more non-volatile readable storage media storing computer readable instructions that, when executed by one or more processors, cause one or more processors
  • the interface automatic test method in the foregoing embodiment is executed. To avoid repetition, details are not described herein again.
  • the computer readable instructions are executed by one or more processors, the one or more processors are configured to perform the functions of the modules/units in the interface automation test apparatus in the above embodiments. To avoid repetition, details are not described herein again.
  • FIG. 7 shows a schematic diagram of a terminal device of the present embodiment.
  • the terminal device 60 includes a processor 61, a memory 62, and computer readable instructions 63 stored in the memory 62 and executable on the processor 61.
  • the processor 61 executes the computer readable instructions 63 to implement the various steps of the interface automation test method of the above-described embodiments, such as steps S101, S102, and S103 shown in FIG.
  • the processor 61 executes the computer readable instructions 63
  • the functions of the modules/units of the interface automation test apparatus in the above embodiments are implemented, for example, the functions of the sample generation module 201, the script generation module 202, and the interface test module 203 shown in FIG. .

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

La présente invention se rapporte au domaine des tests de logiciels. L'invention concerne un procédé de test automatisé d'interfaces, un dispositif, un équipement, et un support de stockage. Le procédé comporte les étapes consistant à: acquérir des fichiers d'Interface de différentes interfaces, générer automatiquement des échantillons de test JSON des différentes interfaces d'après les fichiers d'Interface; générer automatiquement un modèle de cas-test d'après les échantillons de test JSON, générer automatiquement un cas-test JSON d'après le modèle de cas-test, puis générer automatiquement un script de test JMeter d'après le cas-test JSON; générer un cas-test intégré d'après le script de test JMeter, appeler le cas-test intégré par l'intermédiaire d'un outil de test, déclencher le script de test JMeter par l'intermédiaire du cas-test intégré en vue de tests, et délivrer automatiquement le résultat de test. Le procédé de test automatisé d'interfaces, le dispositif, l'équipement, et le support de stockage selon la présente invention accroissent le degré d'automatisation des tests d'interfaces et facilitent la maintenance d'un cas-test lors de la modification d'une interface.
PCT/CN2018/081545 2018-02-07 2018-04-02 Procédé de test automatisé d'interfaces, dispositif, équipement, et support de stockage WO2019153472A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810121971.XA CN108415832B (zh) 2018-02-07 2018-02-07 接口自动化测试方法、装置、设备及存储介质
CN201810121971.X 2018-02-07

Publications (1)

Publication Number Publication Date
WO2019153472A1 true WO2019153472A1 (fr) 2019-08-15

Family

ID=63128025

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/081545 WO2019153472A1 (fr) 2018-02-07 2018-04-02 Procédé de test automatisé d'interfaces, dispositif, équipement, et support de stockage

Country Status (2)

Country Link
CN (1) CN108415832B (fr)
WO (1) WO2019153472A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112069078A (zh) * 2020-09-15 2020-12-11 平安银行股份有限公司 Esa接口压力测试方法、装置、测试设备及存储介质
CN112084108A (zh) * 2020-08-28 2020-12-15 山东英信计算机技术有限公司 一种测试脚本生成方法、装置及相关组件
CN114090454A (zh) * 2021-11-29 2022-02-25 苏州万店掌网络科技有限公司 一种接口自动化测试方法、装置、设备及存储介质

Families Citing this family (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109408370A (zh) * 2018-09-18 2019-03-01 深圳壹账通智能科技有限公司 接口测试文件生成方法、装置、计算机设备和存储介质
CN109408375B (zh) * 2018-09-27 2023-06-09 深圳壹账通智能科技有限公司 接口文档的生成方法和装置
CN109324974A (zh) * 2018-10-09 2019-02-12 郑州云海信息技术有限公司 一种控制批量执行脚本的方法及装置
CN109522220A (zh) * 2018-10-23 2019-03-26 中国银行股份有限公司 一种文本测试方法及装置
CN109542767B (zh) * 2018-10-25 2023-04-11 平安科技（深圳）有限公司 基于区块链的自动化测试方法、装置、计算机设备和存储介质
CN109684195A (zh) * 2018-10-26 2019-04-26 平安科技（深圳）有限公司 电子装置、脚本转换方法及存储介质
CN109634841B (zh) * 2018-10-26 2024-03-12 平安科技（深圳）有限公司 电子装置、接口自动化测试方法及存储介质
CN111124876A (zh) * 2018-10-31 2020-05-08 北京国双科技有限公司 接口测试用例的实现方法和装置、存储介质及处理器
CN111198810A (zh) * 2018-11-16 2020-05-26 鸿合科技股份有限公司 一种软件测试方法及装置、电子设备
CN111221718A (zh) * 2018-11-23 2020-06-02 鸿合科技股份有限公司 一种接口测试方法和装置
CN111274120B (zh) * 2018-12-05 2024-02-02 三六零科技集团有限公司 一种接口文档的验证方法和装置
CN111290933A (zh) * 2018-12-06 2020-06-16 中兴通讯股份有限公司 一种软件自动化软件测试方法及装置
CN111324526B (zh) * 2018-12-14 2024-04-26 北京金山云网络技术有限公司 接口测试系统、方法和服务器
CN109697150A (zh) * 2018-12-14 2019-04-30 平安普惠企业管理有限公司 展示测试报告的方法、装置、计算机设备及存储介质
CN109685626A (zh) * 2018-12-27 2019-04-26 北京顺丰同城科技有限公司 一种下单测试方法及装置
CN109710531B (zh) * 2018-12-29 2022-07-05 奇安信科技集团股份有限公司 应用程序的审计方法、装置、系统、电子设备及存储介质
CN109902002B (zh) * 2019-02-14 2020-06-02 浙江口碑网络技术有限公司 组合测试用例的生成方法及装置、存储介质、计算机设备
CN109885498A (zh) * 2019-02-26 2019-06-14 北京首汽智行科技有限公司 一种测试脚本生成方法及系统
CN110046093A (zh) * 2019-03-14 2019-07-23 平安信托有限责任公司 接口测试方法、装置、计算机设备和存储介质
CN111752823A (zh) * 2019-03-29 2020-10-09 北京新能源汽车股份有限公司 一种车载电源应用软件的测试方法、装置及设备
CN110134584A (zh) * 2019-04-12 2019-08-16 深圳壹账通智能科技有限公司 一种接口测试用例的生成方法、装置、存储介质和服务器
CN110221948B (zh) * 2019-04-18 2023-03-28 深圳壹账通智能科技有限公司 测试脚本生成方法、装置、计算机装置及存储介质
CN110059011A (zh) * 2019-04-22 2019-07-26 泰康保险集团股份有限公司 接口测试方法、装置、介质及电子设备
CN110109837B (zh) * 2019-05-06 2023-10-13 上海蔚来汽车有限公司 集成测试方法、装置以及控制器和介质
CN110232018A (zh) * 2019-05-17 2019-09-13 浙江数链科技有限公司 接口测试方法、装置、计算机设备
CN112131091B (zh) * 2019-06-24 2024-04-16 百度在线网络技术（北京）有限公司 一种测试方法、装置及电子设备
CN110532169A (zh) * 2019-07-08 2019-12-03 平安科技（深圳）有限公司 接口测试用例生成方法、装置、计算机设备及存储介质
CN110377514A (zh) * 2019-07-12 2019-10-25 中汇信息技术（上海）有限公司 软件构件的管理方法、装置、电子设备和存储介质
CN110471842A (zh) * 2019-07-12 2019-11-19 平安普惠企业管理有限公司 一种测试方法、装置及计算机可读存储介质
CN112395184A (zh) * 2019-08-19 2021-02-23 中移(苏州)软件技术有限公司 一种信息获取方法、设备和计算机存储介质
CN110716870B (zh) * 2019-09-23 2023-01-31 中国建设银行股份有限公司 服务的自动化测试方法及装置
CN111427765B (zh) * 2020-02-17 2022-09-20 叮当快药科技集团有限公司 自动开启基于jmeter实现的接口性能测试方法和系统
CN111290968A (zh) * 2020-03-19 2020-06-16 上海异势信息科技有限公司 一种自动测试的实现方法、装置、设备和存储介质
CN111209218A (zh) * 2020-04-01 2020-05-29 中电万维信息技术有限责任公司 一种基于Jmeter的性能自动化测试方法
CN111522741B (zh) * 2020-04-14 2023-11-14 北京奇艺世纪科技有限公司 接口测试代码生成方法、装置、电子设备及可读存储介质
CN111858376A (zh) * 2020-07-29 2020-10-30 平安养老保险股份有限公司 请求报文生成方法和接口测试方法
CN112328503A (zh) * 2020-11-30 2021-02-05 武汉空心科技有限公司 一种软件开发工作平台任务验收方法
CN112486846A (zh) * 2020-12-18 2021-03-12 上海中通吉网络技术有限公司 测试用例自动生成并执行的方法、装置、设备和存储介质
CN113190445A (zh) * 2021-04-29 2021-07-30 中国邮政储蓄银行股份有限公司 接口测试方法、接口测试装置和接口测试系统
CN113778395A (zh) * 2021-08-30 2021-12-10 东风汽车集团股份有限公司 基于一种软件开发平台的软件自动集成控制方法
CN116188107A (zh) * 2023-02-16 2023-05-30 上海聚水潭网络科技有限公司 一种测试订单的生成方法、装置、设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160283364A1 (en) * 2015-03-24 2016-09-29 Hcl Technologies Limited System and method for automatically testing an application programming interface (api)
CN106021111A (zh) * 2016-05-30 2016-10-12 上海携程商务有限公司 接口测试方法及系统
CN106294177A (zh) * 2016-08-22 2017-01-04 腾讯科技（深圳）有限公司 一种接口的压力测试方法及测试设备
CN106708676A (zh) * 2016-12-01 2017-05-24 广州酷狗计算机科技有限公司 接口测试方法及装置
CN107239398A (zh) * 2017-05-24 2017-10-10 四川长虹电器股份有限公司 一种基于Postman的接口测试用例自动生成系统及方法
CN107608889A (zh) * 2017-09-15 2018-01-19 杭州销冠网络科技有限公司 一种测试脚本自动生成方法及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101996132A (zh) * 2009-08-14 2011-03-30 中兴通讯股份有限公司 公用对象请求代理程序体系结构接口自动测试方法和装置
KR101132560B1 (ko) * 2010-06-09 2012-04-03 강원대학교산학협력단 로봇 소프트웨어 컴포넌트를 위한 시뮬레이션 기반 인터페이스 테스팅 자동화 시스템 및 그 방법
CN107402884A (zh) * 2017-07-31 2017-11-28 深圳乐信软件技术有限公司 生成接口测试代码的方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160283364A1 (en) * 2015-03-24 2016-09-29 Hcl Technologies Limited System and method for automatically testing an application programming interface (api)
CN106021111A (zh) * 2016-05-30 2016-10-12 上海携程商务有限公司 接口测试方法及系统
CN106294177A (zh) * 2016-08-22 2017-01-04 腾讯科技（深圳）有限公司 一种接口的压力测试方法及测试设备
CN106708676A (zh) * 2016-12-01 2017-05-24 广州酷狗计算机科技有限公司 接口测试方法及装置
CN107239398A (zh) * 2017-05-24 2017-10-10 四川长虹电器股份有限公司 一种基于Postman的接口测试用例自动生成系统及方法
CN107608889A (zh) * 2017-09-15 2018-01-19 杭州销冠网络科技有限公司 一种测试脚本自动生成方法及系统

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112084108A (zh) * 2020-08-28 2020-12-15 山东英信计算机技术有限公司 一种测试脚本生成方法、装置及相关组件
CN112069078A (zh) * 2020-09-15 2020-12-11 平安银行股份有限公司 Esa接口压力测试方法、装置、测试设备及存储介质
CN112069078B (zh) * 2020-09-15 2024-03-19 平安银行股份有限公司 Esa接口压力测试方法、装置、测试设备及存储介质
CN114090454A (zh) * 2021-11-29 2022-02-25 苏州万店掌网络科技有限公司 一种接口自动化测试方法、装置、设备及存储介质
CN114090454B (zh) * 2021-11-29 2023-01-24 苏州万店掌网络科技有限公司 一种接口自动化测试方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN108415832A (zh) 2018-08-17
CN108415832B (zh) 2021-03-02

Similar Documents

Publication Publication Date Title
WO2019153472A1 (fr) Procédé de test automatisé d'interfaces, dispositif, équipement, et support de stockage
WO2019072110A1 (fr) Procédé de génération de programme d'application, appareil, système, dispositif, et support
US9740594B2 (en) Automated debug trace specification
US11010283B2 (en) Mock-based unit test(s) for an end-to-end test of a code snippet
US10261890B2 (en) Methods and systems for executing tests using grouped/filtered test classes during testing of an application
US10114737B2 (en) Methods and systems for computing code coverage using grouped/filtered source classes during testing of an application
WO2021184725A1 (fr) Procédé et appareil de test d'interface utilisateur, support d'enregistrement et dispositif informatique
US20200201689A1 (en) System and method for determining a process flow of a software application and for automatically generating application testing code
US10452522B1 (en) Synthetic data generation from a service description language model
US8661356B2 (en) Time application having an intergrated check engine
US20130067439A1 (en) Injecting faults into program for testing
WO2020186680A1 (fr) Procédé de test d'interface fondé sur une plateforme de modélisation
CN110879781B (zh) 程序调试方法、装置、电子设备及计算机可读存储介质
WO2021047240A1 (fr) Procédé et appareil d'analyse de données reposant sur un moteur flink
US20210117313A1 (en) Language agnostic automation scripting tool
US10873628B2 (en) System and method for non-intrusive context correlation across cloud services
US10169198B2 (en) Aggregating data for debugging software
US7805711B2 (en) Redirection interface system and method for CIM object manager provider
CN111782207A (zh) 任务流代码生成方法、装置、设备及存储介质
US20140215441A1 (en) Providing directional debugging breakpoints
CN108595656B (zh) 一种数据的处理方法及系统
US20100250228A1 (en) Modeling a composite application
CN116841543A (zh) 基于Flutter动态生成跨平台多端应用的开发方法
CN110362294A (zh) 开发任务执行方法、装置、电子设备及存储介质
CN111881025A (zh) 一种自动化测试任务调度方法、装置及系统

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

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 02.11.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18905091

Country of ref document: EP

Kind code of ref document: A1