技术领域technical field
本发明涉及计算机技术领域，尤其涉及一种接口测试方法、装置及电子设备。The invention relates to the technical field of computers, in particular to an interface testing method, device and electronic equipment.
背景技术Background technique
对于电子设备而言，例如，智能手机、台式电脑、服务器等，与其他电子设备或者该电子设备内部各子系统之间的交互，主要基于接口调用实现。为此，针对众多接口，电子设备在推向市场之前，需要进行接口测试。For an electronic device, for example, a smart phone, a desktop computer, a server, etc., the interaction with other electronic devices or various subsystems inside the electronic device is mainly implemented based on interface calls. For this reason, for many interfaces, electronic equipment needs to be tested before being put on the market.
目前的接口测试，如果增加、删除或者修改某个接口，针对多种不同的测试场景，需要测试人员逐一手动导入不同的测试场景中进行接口测试，自动化程度不高，效率较低，而且浪费大量人力，测试成本居高不下。In the current interface test, if an interface is added, deleted, or modified, for a variety of different test scenarios, testers need to manually import different test scenarios one by one for interface testing. The degree of automation is not high, the efficiency is low, and a lot of waste Manpower and testing costs remain high.
发明内容Contents of the invention
为了解决相关技术中存在的基于多种不同测试场景中的接口测试依赖于人工实现的问题，本发明各实施例提供一种接口测试方法、装置及电子设备。In order to solve the problem in the related art that interface testing based on various testing scenarios relies on manual implementation, various embodiments of the present invention provide an interface testing method, device and electronic equipment.
其中，本发明所采用的技术方案为：Wherein, the technical scheme adopted in the present invention is:
在本发明实施例公开的一方面，一种接口测试方法，包括：在显示的测试任务中，接收测试人员针对显示的测试任务而发起的测试请求，所述测试请求用于指示所述测试人员请求测试的测试任务；根据所述测试人员请求测试的测试任务确定待测试接口；通过所确定的待测试接口获取对应的测试场景标识，所述测试场景标识用于表示所述待测试接口的测试场景；从配置文件中读取所述待测试接口在所述测试场景中的测试参数，生成场景测试用例；基于所述场景测试用例进行所述待测试接口的场景测试。In an aspect disclosed by the embodiments of the present invention, an interface testing method includes: in the displayed test task, receiving a test request initiated by the tester for the displayed test task, the test request is used to instruct the tester Request a test task for testing; determine the interface to be tested according to the test task requested by the tester; obtain a corresponding test scenario identifier through the determined interface to be tested, and the test scenario identifier is used to represent the test of the interface to be tested Scenario: reading the test parameters of the interface to be tested in the test scenario from the configuration file to generate a scenario test case; performing a scenario test of the interface to be tested based on the scenario test case.
在本发明实施例公开的另一方面，一种接口测试装置，包括：测试请求接收模块，用于在显示的测试任务中，接收测试人员针对显示的测试任务而发起的测试请求，所述测试请求用于指示所述测试人员请求测试的测试任务；待测试接口确定模块，用于根据所述测试人员请求测试的测试任务确定待测试接口；场景标识获取模块，用于通过所确定的待测试接口获取对应的测试场景标识，所述测试场景标识用于表示所述待测试接口的测试场景；场景用例生成模块，用于从配置文件中读取所述待测试接口在所述测试场景中的测试参数，生成场景测试用例；场景测试模块，用于基于所述场景测试用例进行所述待测试接口的场景测试。In another aspect disclosed by the embodiments of the present invention, an interface testing device includes: a test request receiving module, configured to receive a test request initiated by a tester for a displayed test task in the displayed test task, the test The request is used to indicate that the tester requests the test task of the test; the interface to be tested determination module is used to determine the interface to be tested according to the test task requested by the tester; the scene identification acquisition module is used to pass the determined to be tested The interface obtains the corresponding test scene identification, and the test scene identification is used to represent the test scene of the interface to be tested; the scene use case generation module is used to read the information of the interface to be tested in the test scene from the configuration file The test parameters are used to generate a scenario test case; the scenario test module is configured to perform a scenario test of the interface to be tested based on the scenario test case.
在一示例性实施例中，所述待测试接口确定模块包括：任务标识提取单元，用于从所述测试请求中提取所述测试任务对应的测试任务标识；候选接口查找单元，用于在接口集合中查找与所述测试任务标识具有关联关系的候选接口；候选接口筛选单元，用于基于所述测试任务的测试环境，由所述候选接口筛选得到所述待测试接口。In an exemplary embodiment, the module to determine the interface to be tested includes: a task identifier extraction unit, configured to extract the test task identifier corresponding to the test task from the test request; a candidate interface search unit, configured to Searching for a candidate interface associated with the test task identifier in the set; a candidate interface screening unit configured to filter the candidate interface to obtain the interface to be tested based on the test environment of the test task.
在一示例性实施例中，所述候选接口筛选单元包括：环境信息获取子单元，用于通过系统文件确定测试环境信息的存储路径，按照所述存储路径指向的存储位置获取所述测试环境信息，所述测试环境信息用于指示所述测试任务的测试环境；接口关系获取子单元，用于对所述测试环境信息进行解析，得到所述测试环境中的接口逻辑关系；候选接口筛选子单元，用于根据所述测试环境中的接口逻辑关系对所述候选接口进行筛选，得到所述待测试接口。In an exemplary embodiment, the candidate interface screening unit includes: an environment information acquisition subunit, configured to determine a storage path of the test environment information through a system file, and acquire the test environment information according to the storage location pointed to by the storage path , the test environment information is used to indicate the test environment of the test task; the interface relationship acquisition subunit is used to analyze the test environment information to obtain the interface logic relationship in the test environment; the candidate interface screening subunit is used to screen the candidate interfaces according to the logical relationship of the interfaces in the test environment to obtain the interface to be tested.
在一示例性实施例中，所述场景标识获取模块包括：场景信息显示单元，用于为所确定的待测试接口显示测试场景信息；选择操作检测单元，用于当检测到所述测试人员在显示的测试场景信息中触发的测试场景选择操作，根据所述测试场景选择操作的指示确定所述测试场景标识。In an exemplary embodiment, the scene identification acquisition module includes: a scene information display unit, configured to display test scene information for the determined interface to be tested; a selection operation detection unit, configured to detect that the tester is in the The test scene selection operation triggered in the displayed test scene information determines the test scene identifier according to the indication of the test scene selection operation.
在一示例性实施例中，所述场景测试模块包括：测试参数提取单元，用于从所述场景测试用例中，提取得到所述待测试接口在所述测试场景中的测试参数；响应数据获取单元，用于在所述测试场景中，根据所述测试参数调用所述待测试接口，获得所述待测试接口在场景测试过程中返回的响应数据；测试结果生成单元，用于根据所述响应数据生成所述待测试接口的测试结果。In an exemplary embodiment, the scenario test module includes: a test parameter extraction unit, configured to extract the test parameters of the interface to be tested in the test scenario from the scenario test case; response data acquisition A unit for calling the interface to be tested according to the test parameters in the test scenario to obtain response data returned by the interface to be tested during the scenario test; a test result generation unit for according to the response The data generates a test result of the interface to be tested.
在一示例性实施例中，所述响应数据获取单元包括：实参获取子单元，用于获取所述测试参数中的多个实参；响应值获取子单元，用于对多个实参进行遍历，在所述测试场景中将遍历到的实参传入所述待测试接口，得到遍历到实参对应的响应值；响应值打包子单元，用于将完成遍历的实参所对应响应值打包生成所述待测试接口在场景测试过程中返回的响应数据。In an exemplary embodiment, the response data acquisition unit includes: an actual parameter acquisition subunit, configured to acquire a plurality of actual parameters in the test parameters; a response value acquisition subunit, configured to perform multiple actual parameters Traversing, in the test scenario, passing the traversed actual parameters into the interface to be tested to obtain the response value corresponding to the traversed actual parameters; the response value packaging subunit is used to transfer the corresponding response value of the traversed actual parameters Packing and generating the response data returned by the interface to be tested during the scenario testing process.
在一示例性实施例中，所述响应数据获取单元还包括：停止条件获取子单元，用于获取所述测试参数中的测试停止条件；停止条件判断子单元，用于如果所述测试停止条件不满足，则进行多个实参的遍历，直至完成所述遍历，或者，所述测试停止条件满足。In an exemplary embodiment, the response data acquisition unit further includes: a stop condition acquisition subunit, configured to acquire a test stop condition in the test parameters; a stop condition judgment subunit, configured to determine if the test stop condition If it is not satisfied, the traversal of multiple actual parameters is performed until the traversal is completed, or the test stop condition is satisfied.
在一示例性实施例中，所述测试结果生成单元包括：目标数据获取子单元，用于获取所述测试参数中的目标数据和匹配条件；匹配性校验子单元，用于根据所述匹配条件进行所述响应数据与所述目标数据之间的匹配性校验；第一结果生成子单元，用于如果所述响应数据通过匹配性校验，则生成指示所述待测试接口通过测试的测试结果；第二结果生成子单元，用于如果所述响应数据未通过匹配性校验，则生成指示所述待测试接口未通过测试的测试结果。In an exemplary embodiment, the test result generation unit includes: a target data acquisition subunit, configured to acquire the target data and matching conditions in the test parameters; a matching checking subunit, configured to The condition is to perform a matching check between the response data and the target data; the first result generation subunit is used to generate a message indicating that the interface to be tested has passed the test if the response data passes the matching check. Test result; the second result generating subunit is configured to generate a test result indicating that the interface to be tested has failed the test if the response data fails the matching check.
在本发明实施例公开的另一方面，一种电子设备，包括处理器及存储器，所述存储器上存储有计算机可读指令，所述计算机可读指令被所述处理器执行时实现如上所述的接口测试方法。In another aspect disclosed by the embodiments of the present invention, an electronic device includes a processor and a memory, the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the above-mentioned The interface test method.
在本发明实施例公开的另一方面，一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如上所述的接口测试方法。In another aspect disclosed by the embodiments of the present invention, a computer-readable storage medium stores a computer program thereon, and when the computer program is executed by a processor, the above-mentioned interface testing method is implemented.
在上述技术方案中，通过测试请求所指示的测试人员请求测试的测试任务确定待测试接口，进而通过所确定的待测试接口获取对应的测试场景标识，以基于测试场景标识所标识的待测试接口的测试场景，从配置文件中读取待测试接口在该测试场景中的测试参数，生成场景测试用例进行待测试接口的场景测试，由此，随着测试任务的变化，待测试接口、测试场景及场景测试用例都将随之发生变化，实现了基于多种不同的测试场景中接口测试的自动化，避免依赖于测试人员手动导入，不仅有效地提高了测试效率，而且节省了大量人力，降低了测试成本。In the above technical solution, the test task requested by the tester indicated by the test request determines the interface to be tested, and then obtains the corresponding test scene identification through the determined interface to be tested, so as to identify the interface to be tested based on the test scene identification test scenario, read the test parameters of the interface to be tested in the test scenario from the configuration file, generate a scenario test case for the scenario test of the interface to be tested, thus, as the test task changes, the interface to be tested, the test scenario and scenario test cases will change accordingly, realizing the automation of interface testing based on a variety of different test scenarios, avoiding relying on manual import by testers, not only effectively improving test efficiency, but also saving a lot of manpower and reducing cost of testing.
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本发明。It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention.
附图说明Description of drawings
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明的实施例，并于说明书一起用于解释本发明的原理。The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description serve to explain the principles of the invention.
图1是根据一示例性实施例示出的一种电子设备的硬件结构框图。Fig. 1 is a block diagram showing a hardware structure of an electronic device according to an exemplary embodiment.
图2是根据一示例性实施例示出的一种接口测试方法的流程图。Fig. 2 is a flowchart of an interface testing method according to an exemplary embodiment.
图3是图2对应实施例中步骤330在一个实施例的流程图。FIG. 3 is a flowchart of step 330 in the embodiment corresponding to FIG. 2 in an embodiment.
图4是图3对应实施例中步骤335在一个实施例的流程图。FIG. 4 is a flow chart of step 335 in the embodiment corresponding to FIG. 3 in an embodiment.
图5是图2对应实施例中步骤350在一个实施例的流程图。FIG. 5 is a flow chart of step 350 in the embodiment corresponding to FIG. 2 in an embodiment.
图6是图2对应实施例中步骤370在一个实施例的流程图。FIG. 6 is a flowchart of step 370 in the embodiment corresponding to FIG. 2 in an embodiment.
图7是图6对应实施例中步骤373在一个实施例的流程图。FIG. 7 is a flowchart of an embodiment of step 373 in the embodiment corresponding to FIG. 6 .
图8是图6对应实施例中步骤375在一个实施例的流程图。FIG. 8 is a flow chart of an embodiment of step 375 in the embodiment corresponding to FIG. 6 .
图9是根据一示例性实施例示出的一种接口测试装置的框图。Fig. 9 is a block diagram of an interface testing device according to an exemplary embodiment.
图10是根据一示例性实施例示出的一种电子设备的框图。Fig. 10 is a block diagram of an electronic device according to an exemplary embodiment.
通过上述附图，已示出本发明明确的实施例，后文中将有更详细的描述，这些附图和文字描述并不是为了通过任何方式限制本发明构思的范围，而是通过参考特定实施例为本领域技术人员说明本发明的概念。Through the above drawings, specific embodiments of the present invention have been shown and will be described in more detail below. These drawings and text description are not intended to limit the scope of the inventive concept in any way, but by reference to specific embodiments. The concepts of the present invention are explained to those skilled in the art.
具体实施方式Detailed ways
这里将详细地对示例性实施例执行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本发明的一些方面相一致的装置和方法的例子。Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with aspects of the invention as recited in the appended claims.
图1是根据一示例性实施例示出的一种电子设备的硬件结构框图。该电子设备可以是服务器、台式电脑、笔记本电脑、智能手机等，在此并不构成具体限定。Fig. 1 is a block diagram showing a hardware structure of an electronic device according to an exemplary embodiment. The electronic device may be a server, a desktop computer, a notebook computer, a smart phone, etc., which is not specifically limited here.
需要说明的是，该种电子设备只是一个适配于本发明的示例，不能认为是提供了对本发明的使用范围的任何限制。该种电子设备也不能解释为需要依赖于或者必须具有图1中示出的示例性的电子设备200中的一个或者多个组件。It should be noted that this kind of electronic device is only an example adapted to the present invention, and should not be regarded as providing any limitation on the application scope of the present invention. This kind of electronic device cannot be interpreted as needing to rely on or having to have one or more components in the exemplary electronic device 200 shown in FIG. 1 .
电子设备200的硬件结构可因配置或者性能的不同而产生较大的差异，如图1所示，电子设备200包括：电源210、接口230、至少一存储器250、至少一中央处理器(CPU,Central Processing Units)270、显示屏幕280以及输入组件290。The hardware structure of the electronic device 200 may vary greatly due to different configurations or performances. As shown in FIG. Central Processing Units) 270, a display screen 280, and an input component 290.
具体地，电源210用于为电子设备200上的各硬件设备提供工作电压。Specifically, the power supply 210 is used to provide working voltage for each hardware device on the electronic device 200 .
接口230包括至少一有线或无线网络接口231、至少一串并转换接口233、至少一输入输出接口235以及至少一USB接口237等，用于与外部设备通信。The interface 230 includes at least one wired or wireless network interface 231 , at least one serial-to-parallel conversion interface 233 , at least one input-output interface 235 , and at least one USB interface 237 , etc., for communicating with external devices.
存储器250作为资源存储的载体，可以是只读存储器、随机存储器、磁盘或者光盘等，其上所存储的资源包括操作系统251、应用程序253及数据255等，存储方式可以是短暂存储或者永久存储。The memory 250 is used as a resource storage carrier, which can be read-only memory, random access memory, magnetic disk or optical disk, etc., and the resources stored thereon include operating system 251, application program 253 and data 255, etc., and the storage method can be temporary storage or permanent storage .
其中，操作系统251用于管理与控制电子设备200上的各硬件设备以及应用程序253，以实现中央处理器270对海量数据255的计算与处理，其可以是Windows ServerTM、MacOS XTM、UnixTM、LinuxTM、FreeBSDTM等。Wherein, the operating system 251 is used to manage and control each hardware device and application program 253 on the electronic device 200, so as to realize the calculation and processing of the massive data 255 by the central processing unit 270, which can be Windows ServerTM, MacOS XTM, UnixTM, LinuxTM , FreeBSDTM, etc.
应用程序253是基于操作系统251之上完成至少一项特定工作的计算机程序，其可以包括至少一模块(图1中未示出)，每个模块都可以分别包含有对电子设备200的一系列计算机可读指令。例如，接口测试装置可视为部署于电子设备的应用程序253，以实现接口测试方法。The application program 253 is a computer program based on the operating system 251 to complete at least one specific task, which may include at least one module (not shown in FIG. 1 ), and each module may include a series of functions for the electronic device 200 computer readable instructions. For example, the interface testing device can be regarded as the application program 253 deployed on the electronic device to implement the interface testing method.
数据255可以是存储于磁盘中的照片、图片，还可以是配置文件等，存储于存储器250中。The data 255 may be photos, pictures, or configuration files stored in the disk, and stored in the memory 250 .
中央处理器270可以包括一个或多个以上的处理器，并设置为通过通信总线与存储器250通信，以读取存储器250中存储的计算机可读指令，进而实现对存储器250中海量数据255的运算与处理。例如，通过中央处理器270读取存储器250中存储的一系列计算机可读指令的形式来完成接口测试方法。The central processing unit 270 may include one or more processors, and is configured to communicate with the memory 250 through the communication bus, so as to read the computer-readable instructions stored in the memory 250, and then realize the calculation of the massive data 255 in the memory 250 with processing. For example, the interface testing method is implemented by the CPU 270 reading a series of computer-readable instructions stored in the memory 250 .
显示屏幕280可以是液晶显示屏或者电子墨水显示屏等，此显示屏幕280在电子设备200与用户之间提供一个输出界面，以通过该输出界面将文字、图片或者视频任意一种形式或者组合所形成的输出内容向用户显示输出。例如，进行测试任务的显示，或者，进行测试场景信息的显示。The display screen 280 can be a liquid crystal display screen or an electronic ink display screen, etc., and the display screen 280 provides an output interface between the electronic device 200 and the user, so that any form or combination of text, pictures, or videos can be displayed through the output interface. The resulting output content displays the output to the user. For example, displaying test tasks, or displaying test scene information.
输入组件290，可以是显示屏幕280上覆盖的触摸层，也可以是电子设备200外壳上设置的按键、轨迹球或者触控板，还可以是外接的键盘、鼠标、触控板等，用于接收测试人员触发的各种操作。例如，在显示的测试场景信息中触发的测试场景选择操作。The input component 290 may be a touch layer covered on the display screen 280, or a button, a trackball or a touchpad provided on the housing of the electronic device 200, or an external keyboard, mouse, touchpad, etc., for Receive various actions triggered by testers. For example, a test scenario selection operation triggered in the displayed test scenario information.
此外，通过硬件电路或者硬件电路结合软件也能同样实现本发明，因此，实现本发明并不限于任何特定硬件电路、软件以及两者的组合。In addition, the present invention can also be realized by hardware circuits or a combination of hardware circuits and software. Therefore, the realization of the present invention is not limited to any specific hardware circuits, software or the combination of the two.
请参阅图2，在一示例性实施例中，一种接口测试方法适用于电子设备，该电子设备的结构可以如图1所示。Please refer to FIG. 2 . In an exemplary embodiment, an interface testing method is applicable to an electronic device, and the structure of the electronic device may be as shown in FIG. 1 .
该种接口测试方法可以由电子设备执行，也可以理解为由电子设备中部署的接口测试装置执行。在下述方法实施例中，为了便于描述，以各步骤的执行主体为接口测试装置加以说明，但是并不对此构成限定。This interface testing method can be executed by the electronic equipment, and can also be understood as being executed by an interface testing device deployed in the electronic equipment. In the following method embodiments, for ease of description, the execution subject of each step is an interface testing device for illustration, but this is not limited thereto.
该种接口测试方法可以包括以下步骤：This interface testing method may include the following steps:
步骤310，在显示的测试任务中，接收测试人员针对显示的测试任务而发起的测试请求，所述测试请求用于指示所述测试人员请求测试的测试任务。Step 310 , in the displayed test task, receiving a test request initiated by the tester for the displayed test task, where the test request is used to instruct the tester to request the test task to be tested.
如前所述，对于电子设备而言，与其他电子设备或者该电子设备内部各子系统之间的交互，主要基于接口调用实现。As mentioned above, for an electronic device, the interaction with other electronic devices or internal subsystems of the electronic device is mainly implemented based on interface calls.
为此，针对电子设备由众多接口组成的接口集合，只要该接口集合内的某个接口增加、删除或者修改，便可形成相应的测试任务。Therefore, for an interface set composed of many interfaces on an electronic device, as long as a certain interface in the interface set is added, deleted or modified, a corresponding test task can be formed.
举例来说，电子设备的接口集合包括接口A和接口B，那么，随着接口A、接口B增加、删除或者修改，可相应形成的测试任务包括但不限于：增加接口A的测试任务、删除接口A的测试任务、修改接口A的测试任务、增加接口B的测试任务、删除接口B的测试任务、修改接口B的测试任务。For example, the interface set of an electronic device includes interface A and interface B. Then, as interface A and interface B are added, deleted or modified, the test tasks that can be formed include but are not limited to: adding test tasks for interface A, deleting Test tasks for interface A, modify test tasks for interface A, add test tasks for interface B, delete test tasks for interface B, and modify test tasks for interface B.
也就是说，对于电子设备而言，测试任务，与接口集合中任一个接口的增加、删除或者修改有关，在接口集合确定之后，便可相应地确定，进而显示在电子设备所配置的显示屏幕中。That is to say, for electronic equipment, the test task is related to the addition, deletion or modification of any interface in the interface set. After the interface set is determined, it can be determined accordingly, and then displayed on the display screen configured by the electronic equipment. middle.
由此，在显示的测试任务中，测试人员便可以针对显示的测试任务而发起测试请求，以使电子设备获知测试人员请求测试的测试任务。Thus, in the displayed test task, the tester can initiate a test request for the displayed test task, so that the electronic device can know the test task requested by the tester.
具体地，电子设备将为测试人员提供一个请求发起入口，如果测试人员希望进行某项测试任务的测试，便可通过该请求发起入口触发相关的操作而发起测试请求。Specifically, the electronic device will provide a request initiation portal for the tester, and if the tester wants to test a certain test task, he can initiate a test request by triggering related operations through the request initiation portal.
举例来说，在电子设备所配置的显示屏幕中显示测试任务列表，测试任务列表罗列了一系列可供测试人员选择的测试任务，那么，测试人员便可借由电子设备所配置的输入组件点击测试任务列表中罗列的任一项测试任务。其中，测试任务列表即为电子设备提供的请求发起入口，而点击操作即为测试人员在请求发起入口触发的操作。For example, a test task list is displayed on the display screen configured by the electronic device, and the test task list lists a series of test tasks that can be selected by the tester. Then, the tester can click on the input component configured by the electronic device. Any test task listed in the test task list. Wherein, the test task list is the request initiation entry provided by the electronic device, and the click operation is an operation triggered by the tester at the request initiation entry.
需要说明的是，根据计算机设备所配置的输入组件(例如，显示屏幕上覆盖的触摸层、鼠标、键盘等)的不同，测试人员触发的操作也可以有所不同。例如，借由触摸层输入的智能手机而言，操作可以是点击、滑动等手势操作，而对于配置鼠标的台式电脑而言，操作则可以是拖拽、单击、双击等机械操作，在此不进行限定。It should be noted that, depending on the input components configured on the computer equipment (for example, the touch layer covered on the display screen, mouse, keyboard, etc.), the operations triggered by the tester may also be different. For example, for a smart phone with touch layer input, the operation can be gesture operations such as clicking and sliding, while for a desktop computer equipped with a mouse, the operation can be mechanical operations such as dragging, clicking, and double-clicking. Not limited.
当测试人员在请求发起入口触发了相关操作，电子设备便可检测到该操作，进而通过检测到的该操作为测试人员发起测试请求。其中，测试请求所指示的测试人员请求测试的测试任务，即为测试人员在请求发起入口触发的相关操作所选择的测试任务。When the tester triggers a relevant operation at the request initiation entry, the electronic device can detect the operation, and then initiate a test request for the tester through the detected operation. Wherein, the test task requested by the tester indicated by the test request is the test task selected by the tester for the relevant operation triggered at the request initiation entry.
步骤330，根据所述测试人员请求测试的测试任务确定待测试接口。Step 330: Determine the interface to be tested according to the test task requested by the tester.
如前述例子，如果测试人员请求测试的测试任务与接口A相关，那么，待测试接口至少包括接口A。As in the foregoing example, if the test task requested by the tester is related to interface A, then the interface to be tested includes at least interface A.
应当理解，对于同一电子设备而言，内部各子系统之间的交互也是基于接口的互相调用，也就是说，如果接口A进行了增加、删除或者修改，势必会影响与接口A互相调用的其余接口，那么，待测试接口还应该包括与接口A存在互相调用关系的其余接口。It should be understood that for the same electronic device, the interaction between internal subsystems is also based on the mutual calling of interfaces. That is to say, if interface A is added, deleted, or modified, it will inevitably affect other subsystems that call each other with interface A. interface, then the interface to be tested should also include other interfaces that have a mutual calling relationship with interface A.
由上可知，当测试任务确定，便可确定待测试接口。It can be seen from the above that when the test task is determined, the interface to be tested can be determined.
步骤350，通过所确定的待测试接口获取对应的测试场景标识。Step 350, obtain the corresponding test scene identifier through the determined interface to be tested.
首先，待测试接口的测试场景，是指基于不同测试停止条件对待测试接口进行多轮测试的应用场景。First, the test scenario of the interface to be tested refers to an application scenario in which multiple rounds of tests are performed on the interface to be tested based on different test stop conditions.
此测试停止条件包括按照次数轮询、按照时间轮询、按照不同的实参轮询、按照不同的匹配条件轮询等，相应地，待测试接口的测试场景包括但不限于：次数轮询场景、时间轮询场景、实参轮询场景、以及匹配条件轮询场景等。The test stop conditions include polling by the number of times, polling by time, polling by different actual parameters, polling by different matching conditions, etc. Correspondingly, the test scenarios of the interface to be tested include but are not limited to: polling by the number of times , time polling scenarios, actual parameter polling scenarios, and matching condition polling scenarios, etc.
当然，根据应用场景的实际需要，上述测试停止条件可以相互组合，例如，按照次数和时间轮询，那么，待测试接口的测试场景相应地包括次数时间轮询场景，本实施例并未对此构成具体限定。Of course, according to the actual needs of the application scenario, the above-mentioned test stop conditions can be combined with each other, for example, polling according to the number of times and time, then, the test scenario of the interface to be tested includes the number of time polling scenarios correspondingly, this embodiment does not address this form a specific limit.
其中，所述测试场景标识用于表示所述待测试接口的测试场景。Wherein, the test scenario identifier is used to represent the test scenario of the interface to be tested.
当待测试接口确定，测试人员便可根据实际需要为待测试接口选取适合的测试场景，进而使得电子设备获得对应的测试场景标识，并由此获知待测试接口的测试场景。When the interface to be tested is determined, the tester can select a suitable test scenario for the interface to be tested according to actual needs, so that the electronic device can obtain a corresponding test scenario identifier, and thereby know the test scenario of the interface to be tested.
步骤370，从配置文件中读取所述待测试接口在所述测试场景中的测试参数，生成场景测试用例。Step 370, read the test parameters of the interface to be tested in the test scenario from the configuration file, and generate a scenario test case.
配置文件，是测试人员为进行接口测试而预先部署于电子设备的，用于控制电子设备对待测试接口进行自动化测试。Configuration files are pre-deployed on electronic devices by testers for interface testing, and are used to control electronic devices to perform automated tests on interfaces to be tested.
每一个待测试接口在配置文件中存储有相应的测试参数。Each interface to be tested has corresponding test parameters stored in the configuration file.
可以理解，测试场景不同，待测试接口在测试场景中的测试参数可以有所区别。例如，次数轮询场景中的测试参数至少包括轮询次数，时间轮询场景中的测试参数至少包括轮询时间，实参轮询场景中的测试参数至少包括实参个数，匹配条件轮询场景中的测试参数至少包括匹配条件种类。It can be understood that different test scenarios may have different test parameters of the interface to be tested in the test scenario. For example, the test parameters in the times polling scenario include at least the number of polls, the test parameters in the time polling scenario include at least the polling time, the test parameters in the actual parameter polling scenario include at least the number of actual parameters, and the matching condition polling The test parameters in the scenario at least include the matching condition category.
也就是说，不同测试场景下，待测试接口存在各不相同的测试参数，包括但不限于：测试停止条件。That is to say, in different test scenarios, there are different test parameters for the interfaces to be tested, including but not limited to: test stop conditions.
其中，测试停止条件用于指示待测试接口停止测试的条件，可以是轮询次数、轮询时间、实参个数、匹配条件种类等。Wherein, the test stop condition is used to indicate the condition for stopping the test of the interface to be tested, and may be the number of polling times, polling time, number of actual parameters, type of matching conditions, and the like.
当然，不同测试场景下，待测试接口也存在部分相同的测试参数，包括但不限于：实参、目标数据、匹配条件等等。Of course, in different test scenarios, the interfaces to be tested also have some of the same test parameters, including but not limited to: actual parameters, target data, matching conditions, and so on.
其中，实参作为调用待测试接口的输入参数。Wherein, the actual parameter is used as an input parameter for invoking the interface to be tested.
目标数据用于指示测试人员期望待测试接口在测试过程中返回的响应数据。The target data is used to indicate the response data that the tester expects the interface to be tested to return during the test.
匹配条件用于指示目标数据与响应数据之间存在何种关系时待测试接口通过测试，可以是全部字段匹配、部分字段匹配、指定字段匹配、数据类型匹配、响应数据不包含目标数据等关系。The matching condition is used to indicate the relationship between the target data and the response data when the interface to be tested passes the test. It can be all field matching, partial field matching, specified field matching, data type matching, and response data does not contain target data.
在通过测试场景标识确定待测试接口的测试场景之后，即可在配置文件中查找待测试接口在测试场景中的测试参数，从而生成场景测试用例。After the test scenario of the interface to be tested is determined through the test scenario identifier, the test parameters of the interface to be tested in the test scenario can be searched in the configuration file, thereby generating a scenario test case.
步骤390，基于所述场景测试用例进行所述待测试接口的场景测试。Step 390, perform scenario testing of the interface to be tested based on the scenario test case.
场景测试用例，是对待测试接口在测试场景中进行场景测试的测试任务的描述，包括但不限于：测试场景、测试环境、测试步骤、测试预期结果、测试参数等等。应当理解，测试场景不同，场景测试用例也各不相同。Scenario test case is a description of the test task for the test interface to be tested in the test scenario, including but not limited to: test scenario, test environment, test steps, test expected results, test parameters, etc. It should be understood that the test scenarios are different, and the scenario test cases are also different.
为此，当获得待测试接口在测试场景中的场景测试用例，方能够实现电子设备对待测试接口的场景测试。Therefore, when the scenario test case of the interface to be tested in the test scenario is obtained, the scenario test of the interface to be tested by the electronic device can be realized.
通过如上所述的过程，测试人员仅需要确定测试任务和测试场景，便可控制电子设备基于场景测试用例自动地进行待测试接口的场景测试，避免依赖于测试人员手动导入不同测试场景，有效地提高了测试效率，而且节省了大量人力，降低了测试成本。Through the process described above, testers only need to determine the test tasks and test scenarios, and then control the electronic equipment to automatically perform scenario tests on the interfaces to be tested based on scenario test cases, avoiding relying on testers to manually import different test scenarios, effectively The test efficiency is improved, a lot of manpower is saved, and the test cost is reduced.
请参阅图3，在一示例性实施例中，步骤330可以包括以下步骤：Referring to FIG. 3, in an exemplary embodiment, step 330 may include the following steps:
步骤331，从所述测试请求中提取所述测试任务对应的测试任务标识。Step 331, extract the test task identifier corresponding to the test task from the test request.
其中，测试任务标识，以字符形式唯一地表示测试任务。例如，测试任务标识A唯一地表示测试任务A。Wherein, the test task identifier uniquely represents the test task in the form of characters. For example, test task identifier A uniquely represents test task A.
如前所述，测试请求用于指示测试人员请求测试的测试任务。也就是说，测试请求中至少携带有测试人员请求测试的测试任务所对应的测试任务标识。As mentioned earlier, a test request is used to instruct a tester to request a test task for a test. That is to say, the test request carries at least the test task identifier corresponding to the test task requested by the tester.
由此，测试人员请求测试的测试任务所对应的测试任务标识可以从测试请求中提取得到。Thus, the test task identifier corresponding to the test task requested by the tester can be extracted from the test request.
步骤333，在接口集合中查找与所述测试任务标识具有关联关系的候选接口。Step 333, searching for a candidate interface associated with the test task identifier in the interface set.
如前述例子，对于修改接口A的测试任务而言，待测试接口不仅可以包括接口A，还可以包括与接口A存在互相调用关系的其余接口。As in the foregoing example, for the test task of modifying interface A, the interface to be tested may not only include interface A, but also include other interfaces that have a mutual calling relationship with interface A.
那么，与测试任务标识具有关联关系的候选接口，可以认为，至少可以包括接口A、与接口A存在互相调用关系的其余接口。也就是说，与测试任务标识具有关联关系，是指接口本身以及与接口存在互相调用关系。Then, the candidate interfaces associated with the test task identifier can be considered to at least include interface A and other interfaces that have a mutual calling relationship with interface A. That is to say, being associated with the test task ID refers to the interface itself and the mutual calling relationship with the interface.
因此，基于测试任务标识，便可从接口集合中查找得到候选接口。Therefore, based on the test task identifier, the candidate interface can be found from the interface set.
步骤335，基于所述测试任务的测试环境，由所述候选接口筛选得到所述待测试接口。Step 335: Based on the test environment of the test task, the interface to be tested is obtained by screening the candidate interfaces.
对于电子设备而言，在部署了接口测试装置之后，即在电子设备中构建了用于测试电子设备各种接口的测试环境。For electronic equipment, after the interface testing device is deployed, a test environment for testing various interfaces of the electronic equipment is constructed in the electronic equipment.
应当理解，即使是同一个电子设备，不同的测试环境，各个接口之间的互相调用也会有所差别，为此，在得到候选接口之后，还需要基于测试任务的测试环境进一步筛选候选接口，从而得到最终需要进行场景测试的待测试接口。It should be understood that even for the same electronic device and different test environments, the mutual calls between interfaces will be different. Therefore, after obtaining the candidate interfaces, it is necessary to further screen the candidate interfaces based on the test environment of the test task. In this way, the interface to be tested that finally needs to be tested in the scenario is obtained.
例如，对于候选接口A、B、C来说，测试环境M中，接口A可以和接口B、接口C互相调用，那么，待测试接口包括接口A、B、C。For example, for candidate interfaces A, B, and C, in the test environment M, interface A can call interface B and interface C, then the interfaces to be tested include interfaces A, B, and C.
而测试环境N中，接口A仅可以和接口B互相调用，那么，待测试接口包括接口A、B。However, in the test environment N, the interface A can only call the interface B, so the interfaces to be tested include the interfaces A and B.
通过上述过程，实现了待测试接口的自动获取，进而使得电子设备进行待测试接口的自动化场景测试得以实现。Through the above process, the automatic acquisition of the interface to be tested is realized, and then the automatic scene test of the interface to be tested by the electronic device is realized.
请参阅图4，在一示例性实施例中，步骤335可以包括以下步骤：Referring to FIG. 4, in an exemplary embodiment, step 335 may include the following steps:
步骤3351，通过系统文件确定测试环境信息的存储路径，按照所述存储路径指向的存储位置获取所述测试环境信息。Step 3351, determine the storage path of the test environment information through the system file, and acquire the test environment information according to the storage location pointed to by the storage path.
其中，所述测试环境信息用于指示所述测试任务的测试环境。Wherein, the test environment information is used to indicate the test environment of the test task.
随着测试环境在电子设备中构建，即形成了相应的测试环境信息，并存储于电子设备所配置的存储器内，那么，对于存储器而言，其用于存储测试环境信息的存储位置便会在系统文件中存储有相应的存储路径。As the test environment is built in the electronic device, that is, the corresponding test environment information is formed and stored in the memory configured by the electronic device, then, for the memory, the storage location for storing the test environment information will be in The corresponding storage path is stored in the system file.
由此，首先从系统文件确定测试环境信息的存储路径，进而方能够基于存储路径指向的存储位置从存储器内读取到测试环境信息。Thus, firstly, the storage path of the test environment information is determined from the system file, and then the test environment information can be read from the memory based on the storage location pointed to by the storage path.
步骤3353，对所述测试环境信息进行解析，得到所述测试环境中的接口逻辑关系。Step 3353: Analyze the test environment information to obtain interface logic relationships in the test environment.
如前所述，即使是同一个电子设备，不同的测试环境，各个接口之间的互相调用也会有所差别，为此，测试环境信息至少包括测试环境的接口逻辑关系，以此反映测试环境中各个接口之间存在的互相调用关系。As mentioned above, even if it is the same electronic device, different test environments, the mutual calls between interfaces will be different. Therefore, the test environment information at least includes the interface logic relationship of the test environment to reflect the test environment. The mutual calling relationship between the various interfaces in .
举例来说，对于测试环境信息而言，包含100bits，按照从前往后的顺序排列，前10bits是测试环境标识，用于唯一地表示测试环境，中间80bits是接口逻辑关系，最后10bits是保留比特位。For example, for the test environment information, it contains 100 bits, which are arranged in order from front to back. The first 10 bits are the test environment identifier, which is used to uniquely represent the test environment. The middle 80 bits are the interface logic relationship, and the last 10 bits are reserved bits. .
进一步地，关于接口逻辑关系的比特位表示，说明如下：Further, the bit-bit representation of the logical relationship of the interface is explained as follows:
例如，接口集合包含接口A、接口B和接口C，分别通过接口标识01、10、11表示。For example, the interface set includes interface A, interface B, and interface C, which are represented by interface identifiers 01, 10, and 11, respectively.
那么，接口A可以调用接口B，接口B不允许调用接口A，则表示为011010。其中，“01”表示接口A，第一个“10”表示接口A与接口B之间存在的互相调用关系，第二个“10”表示接口B。Then, interface A can call interface B, and interface B is not allowed to call interface A, which is expressed as 011010. Among them, "01" indicates interface A, the first "10" indicates the mutual calling relationship between interface A and interface B, and the second "10" indicates interface B.
接口B可以调用接口C，接口C不允许调用接口B，则表示为101011。其中，“10”表示接口B，第一个“10”表示接口B与接口C之间存在的互相调用关系，第二个“11”表示接口C。Interface B can call interface C, but interface C is not allowed to call interface B, it is expressed as 101011. Among them, "10" indicates interface B, the first "10" indicates the mutual calling relationship between interface B and interface C, and the second "11" indicates interface C.
接口A和接口C可以相互调用，即接口A可以调用接口C，接口C也可以调用接口A，则表示为011111。其中，“01”表示接口A，第一个“11”表示接口A与接口C之间存在的互相调用关系，第二个“11”表示接口C。Interface A and interface C can call each other, that is, interface A can call interface C, and interface C can also call interface A, which is expressed as 011111. Among them, "01" indicates interface A, the first "11" indicates the mutual calling relationship between interface A and interface C, and the second "11" indicates interface C.
也就是说，1表示允许调用，0表示不允许调用。That is, 1 means that the call is allowed, and 0 means that the call is not allowed.
那么，解析，实质是按照指定比特位进行接口逻辑关系的提取，例如，从测试环境信息所包含的100bits中提取11～90bits，即得到测试环境中的接口逻辑关系。Then, the essence of analysis is to extract the logical relationship of the interface according to the specified bits. For example, extract 11-90 bits from the 100 bits contained in the test environment information to obtain the logical relationship of the interface in the test environment.
步骤3355，根据所述测试环境中的接口逻辑关系对所述候选接口进行筛选，得到所述待测试接口。Step 3355: Screen the candidate interfaces according to the interface logic relationship in the test environment to obtain the interface to be tested.
在得到测试环境中的接口逻辑关系之后，便获知了测试环境中各个接口之间存在的互相调用关系，那么，对于不存在互相调用关系的候选接口，即可剔除。After obtaining the interface logic relationship in the test environment, the mutual call relationship between the various interfaces in the test environment is known. Then, the candidate interfaces that do not have the mutual call relationship can be eliminated.
例如，候选接口包括接口A、接口B和接口C，如果接口C并未与其余接口存在互相调用关系，即接口C不会被接口A和接口B调用，且接口C也不会调用接口A和接口B，那么，接口C就会从候选接口中剔除，进而得到待测试接口仅包括接口A和接口B。For example, candidate interfaces include interface A, interface B, and interface C. If interface C does not have a mutual call relationship with other interfaces, that is, interface C will not be called by interface A and interface B, and interface C will not call interfaces A and interface B, then interface C will be eliminated from the candidate interfaces, and then the interface to be tested only includes interface A and interface B.
在上述实施例的作用下，为候选接口的筛选提供了依据，进而保证进行自动化场景测试的待测试接口确实是因为接口的增加、修改或者删除而受到影响的接口，从而避免不必要的接口测试，由此进一步地提高测试效率。Under the action of the above-mentioned embodiments, a basis is provided for the screening of candidate interfaces, thereby ensuring that the interfaces to be tested for automated scenario testing are indeed interfaces affected by the addition, modification or deletion of interfaces, thereby avoiding unnecessary interface tests , thus further improving the test efficiency.
请参阅图5，在一示例性实施例中，步骤350可以包括以下步骤：Referring to FIG. 5, in an exemplary embodiment, step 350 may include the following steps:
步骤351，为所确定的待测试接口显示测试场景信息。Step 351, displaying test scenario information for the determined interface to be tested.
如前所述，基于不同测试停止条件，待测试接口存在多种不同的测试场景，为此，测试场景信息，是为了向测试人员展示待测试接口存在的多种不同的测试场景。As mentioned above, based on different test stop conditions, there are many different test scenarios for the interface to be tested. Therefore, the test scenario information is to show testers the various test scenarios for the interface to be tested.
当测试场景信息在电子设备所配置的显示屏幕上显示，进而使得测试人员获知可以为待测试接口选取哪些测试场景。When the test scenario information is displayed on the display screen configured on the electronic device, the tester can know which test scenarios can be selected for the interface to be tested.
在一实施例中，测试场景信息通过测试场景列表的形式显示在电子设备所配置的显示屏幕上。In an embodiment, the test scene information is displayed on a display screen configured by the electronic device in the form of a test scene list.
步骤353，当检测到所述测试人员在显示的测试场景信息中触发的测试场景选择操作，根据所述测试场景选择操作的指示确定所述测试场景标识。Step 353: When detecting the test scenario selection operation triggered by the tester in the displayed test scenario information, determine the test scenario identifier according to the instruction of the test scenario selection operation.
在显示的测试场景信息中，测试人员便可以针对显示的测试场景信息中选择一个测试场景，作为待测试接口的测试场景。In the displayed test scenario information, the tester can select a test scenario from the displayed test scenario information as the test scenario of the interface to be tested.
具体地，电子设备将为测试人员提供一个选择入口，如果测试人员希望进行测试场景的选择，便可通过该选择入口触发测试场景选择操作而选择测试场景。Specifically, the electronic device will provide a selection entry for the tester, and if the tester wishes to select a test scenario, the test scenario selection operation can be triggered through the selection entry to select a test scenario.
举例来说，在电子设备所配置的显示屏幕中显示测试场景列表，测试任务列表罗列了一系列可供测试人员选择的测试场景，其中，测试场景通过测试场景标识唯一地表示。For example, a test scenario list is displayed on the display screen configured by the electronic device, and the test task list lists a series of test scenarios that can be selected by a tester, wherein the test scenario is uniquely represented by a test scenario identifier.
那么，测试人员便可借由电子设备所配置的输入组件点击测试场景列表中罗列的任一项测试场景。其中，测试场景列表即为电子设备提供的选择入口，而点击操作即为测试人员在选择入口触发的测试场景选择操作。Then, the tester can click any test scenario listed in the test scenario list through the input component configured on the electronic device. Wherein, the test scene list is the selection entry provided by the electronic device, and the click operation is the test scene selection operation triggered by the tester at the selection entry.
需要说明的是，根据计算机设备所配置的输入组件(例如，显示屏幕上覆盖的触摸层、鼠标、键盘等)的不同，测试人员触发的操作也可以有所不同。例如，借由触摸层输入的智能手机而言，操作可以是点击、滑动等手势操作，而对于配置鼠标的台式电脑而言，操作则可以是拖拽、单击、双击等机械操作，在此不进行限定。It should be noted that, depending on the input components configured on the computer equipment (for example, the touch layer covered on the display screen, mouse, keyboard, etc.), the operations triggered by the tester may also be different. For example, for a smart phone with touch layer input, the operation can be gesture operations such as clicking and sliding, while for a desktop computer equipped with a mouse, the operation can be mechanical operations such as dragging, clicking, and double-clicking. Not limited.
当测试人员在选择入口触发了测试场景选择操作，电子设备便可检测到该测试场景选择操作，进而通过检测到的该测试场景选择操作确定测试人员选择的测试场景，也即是，测试场景选择操作指示了测试人员选择的测试场景对应的测试场景标识。When the tester triggers the test scene selection operation at the selection entrance, the electronic device can detect the test scene selection operation, and then determine the test scene selected by the tester through the detected test scene selection operation, that is, the test scene selection The operation indicates the test scenario ID corresponding to the test scenario selected by the tester.
在上述实施例的作用下，实现了测试场景的选择，进而使得电子设备进行待测试接口的自动化场景测试得以实现。Under the function of the above-mentioned embodiments, the selection of the test scene is realized, and then the automatic scene test of the interface to be tested by the electronic device is realized.
请参阅图6，在一示例性实施例中，步骤370可以包括以下步骤：Referring to FIG. 6, in an exemplary embodiment, step 370 may include the following steps:
步骤371，从所述场景测试用例中，提取得到所述待测试接口在所述测试场景中的测试参数。Step 371 , extracting test parameters of the interface to be tested in the test scenario from the scenario test cases.
其中，测试参数，包含于场景测试用例中，用于指示电子设备如何对待测试接口进行场景测试。此测试参数包括但不限于：测试停止条件、实参、目标数据、匹配条件等等。Wherein, the test parameter is included in the scenario test case, and is used to instruct the electronic device how to perform the scenario test on the interface to be tested. The test parameters include, but are not limited to: test stop conditions, actual parameters, target data, matching conditions, and so on.
步骤373，在所述测试场景中，根据所述测试参数调用所述待测试接口，获得所述待测试接口在场景测试过程中返回的响应数据。Step 373, in the test scenario, call the interface to be tested according to the test parameters, and obtain the response data returned by the interface to be tested during the scenario test.
在完成测试参数的提取之后，待测试接口便可基于测试参数在测试场景中进行场景测试。After the extraction of the test parameters is completed, the interface to be tested can be tested in the test scenario based on the test parameters.
场景测试，是指在测试场景中，基于测试参数对待测试接口进行调用。Scenario testing refers to invoking the interface to be tested based on the test parameters in the test scenario.
可以理解，同一测试场景中，待测试接口可能存在多个，为此，场景测试过程中，也可以理解为是对所有待测试接口进行遍历调用，即基于测试参数对每一个待测试接口进行调用。It can be understood that in the same test scenario, there may be multiple interfaces to be tested. Therefore, in the process of scenario testing, it can also be understood as traversing and calling all interfaces to be tested, that is, calling each interface to be tested based on test parameters .
那么，场景测试过程中，待测试接口便能够返回在测试场景中的响应数据。Then, during the scenario testing process, the interface to be tested can return the response data in the test scenario.
步骤375，根据所述响应数据生成所述待测试接口的测试结果。Step 375, generating a test result of the interface to be tested according to the response data.
测试结果，用于指示待测试接口是否通过场景测试。The test result is used to indicate whether the interface to be tested passes the scenario test.
例如，响应数据与测试参数中的目标数据相等，则生成指示待测试接口通过场景测试的测试结果。For example, if the response data is equal to the target data in the test parameters, a test result indicating that the interface to be tested passes the scenario test is generated.
上述过程中，实现了电子设备基于测试参数自动进行待测试接口的场景测试，避免依赖于测试人员手动执行，有效地提高了测试效率，而且节省了大量人力，降低了测试成本。In the above process, the electronic equipment can automatically perform the scene test of the interface to be tested based on the test parameters, avoiding manual execution by the tester, effectively improving the test efficiency, saving a lot of manpower, and reducing the test cost.
请参阅图7，在一示例性实施例中，步骤373可以包括以下步骤：Referring to FIG. 7, in an exemplary embodiment, step 373 may include the following steps:
步骤3731，获取所述测试参数中的多个实参。Step 3731, obtain multiple actual parameters in the test parameters.
其中，实参，包含于测试参数中，作为调用待测试接口的输入参数，进而方能够基于此输入参数进行待测试接口的调用。Wherein, the actual parameter is included in the test parameters, and is used as an input parameter for calling the interface to be tested, and then the interface to be tested can be called based on the input parameter.
步骤3733，对多个实参进行遍历，在所述测试场景中将遍历到的实参传入所述待测试接口，得到遍历到实参对应的响应值。Step 3733, traverse multiple actual parameters, pass the traversed actual parameters into the interface to be tested in the test scenario, and obtain the response values corresponding to the traversed actual parameters.
在从测试参数中获得多个实参之后，便可基于该多个实参对待测试接口进行场景测试，也即是，将实参传入待测试接口，以此进行待测试接口的调用。After obtaining multiple actual parameters from the test parameters, the interface to be tested can be tested based on the multiple actual parameters, that is, the actual parameters are passed into the interface to be tested, so as to call the interface to be tested.
那么，待测试接口在场景测试过程中，便会返回对应的响应值。Then, the interface to be tested will return the corresponding response value during the scenario test.
步骤3735，将完成遍历的实参所对应响应值打包生成所述待测试接口在场景测试过程中返回的响应数据。Step 3735, pack the response values corresponding to the actual parameters that have completed the traversal to generate the response data returned by the interface to be tested during the scenario testing process.
在完成多个实参的遍历之后，便可针对各实参对应的响应值打包生成待测试接口在场景测试过程中的相应数据。After the traversal of multiple actual parameters is completed, the response values corresponding to each actual parameter can be packaged to generate corresponding data of the interface to be tested during the scenario testing process.
进一步地，在一示例性实施例中，步骤373还可以包括以下步骤：Further, in an exemplary embodiment, step 373 may also include the following steps:
其中，获取所述测试参数中的测试停止条件。Wherein, the test stop condition in the test parameters is obtained.
测试停止条件，包含于测试参数中，用于指示待测试接口停止测试的条件，可以是轮询次数、轮询时间、实参个数、匹配条件种类等。The test stop condition is included in the test parameter and is used to indicate the condition for stopping the test of the interface to be tested, which can be the number of polls, polling time, number of actual parameters, type of matching conditions, etc.
例如，测试停止条件为轮询时间一小时，那么，当对待测试接口进行场景测试的时间达到一小时，则视为测试停止条件满足，即停止对待测试接口进行场景测试。For example, if the test stop condition is that the polling time is one hour, then when the time to perform the scenario test on the interface to be tested reaches one hour, it is deemed that the test stop condition is satisfied, that is, the scenario test on the interface to be tested is stopped.
或者，测试停止条件为轮询次数100次，那么，当对待测试接口进行场景测试的次数达到100次，则视为测试停止条件满足，即停止对待测试接口进行场景测试。Alternatively, the test stop condition is 100 polling times. Then, when the number of scenario tests performed on the interface to be tested reaches 100 times, it is deemed that the test stop condition is satisfied, that is, the scenario test on the interface to be tested is stopped.
可以理解，对于电子设备而言，针对待测试接口进行的场景测试，只有待测试接口通过场景测试，才主动停止对待测试接口的场景测试，否则，会一直持续地对待测试接口进行场景测试，直至满足测试停止条件时，才被动停止对待测试接口的场景测试。It can be understood that, for electronic equipment, the scene test for the interface to be tested is only when the interface to be tested passes the scene test, and the scene test for the interface to be tested is stopped actively; When the test stop condition is met, the scenario test of the interface to be tested is passively stopped.
也就是说，如果所述测试停止条件不满足，则跳转执行步骤3733，继续进行多个实参的遍历。That is to say, if the test stop condition is not satisfied, jump to step 3733 and continue to traverse multiple actual parameters.
直至完成所述遍历，或者，所述测试停止条件满足，则跳转执行步骤3735，进行响应数据的打包。Until the traversal is completed, or the test stop condition is satisfied, jump to step 3735 to package the response data.
通过测试停止条件的设置，避免待测试接口未通过测试时无法停止测试，以此进一步提高了测试效率。By setting the test stop condition, it is avoided that the test cannot be stopped when the interface to be tested fails the test, thereby further improving the test efficiency.
请参阅图8，在一示例性实施例中，步骤375可以包括以下步骤：Referring to FIG. 8, in an exemplary embodiment, step 375 may include the following steps:
步骤3751，获取所述测试参数中的目标数据和匹配条件。Step 3751, acquire the target data and matching conditions in the test parameters.
其中，目标数据，包含于测试参数，用于指示测试人员期望待测试接口在测试过程中返回的响应数据。Wherein, the target data, included in the test parameters, is used to indicate the response data that the tester expects the interface to be tested to return during the test process.
匹配条件，包含于测试参数，用于指示目标数据与响应数据之间存在何种关系时待测试接口通过测试，可以是全部字段匹配、部分字段匹配、指定字段匹配、数据类型匹配、响应数据不包含目标数据等关系。Matching conditions, included in the test parameters, are used to indicate what kind of relationship exists between the target data and the response data. When the interface to be tested passes the test, it can be all fields match, some fields match, specified fields match, data type Contains relationships such as target data.
需要说明的是，部分字段匹配区别于指定字段匹配，例如，对于目标数据或者响应数据而言，全部字段包括字段A、B、C、D，那么，只要字段A、B、C、D中任意一个或者多个字段匹配，均可视为部分字段匹配；假设指定字段为字段A，那么，只有字段A匹配，才视为指定字段匹配，否则，字段B、C、D中任意一个或者多个字段匹配，都不被视作指定字段匹配。It should be noted that partial field matching is different from specified field matching. For example, for target data or response data, all fields include fields A, B, C, and D. Then, as long as any of fields A, B, C, and D If one or more fields match, it can be regarded as a partial field match; assuming that the specified field is field A, then only if field A matches, it is considered as a specified field match; otherwise, any one or more of fields B, C, and D Field matches are not considered field-specific matches.
步骤3753，根据所述匹配条件进行所述响应数据与所述目标数据之间的匹配性校验。Step 3753, perform a matching check between the response data and the target data according to the matching condition.
响应于匹配条件，匹配性校验，用于校验响应数据与目标数据之间是否全部字段匹配，或者，校验响应数据与目标数据之间是否部分字段匹配，或者，校验响应数据与目标数据之间是否制定字段匹配，或者，校验响应数据与目标数据之间是否数据类型匹配，又或者，校验响应数据是否不包含目标数据等。In response to matching conditions, matching check is used to check whether all fields match between the response data and the target data, or to check whether some fields match between the response data and the target data, or to check whether the response data matches the target data Whether the fields match between the data, or whether the data types of the verification response data and the target data match, or whether the verification response data does not contain the target data, etc.
进行匹配性校验之后，便判断响应数据是否通过匹配性校验。After the matching check is performed, it is judged whether the response data passes the matching check.
如果响应数据通过匹配性校验，则跳转执行步骤3755，视为待测试接口通过场景测试。If the response data passes the matching check, jump to step 3755, and consider that the interface to be tested has passed the scenario test.
反之，如果响应数据未通过匹配性校验，则跳转执行步骤3757，视为待测试接口通过场景测试。On the contrary, if the response data does not pass the matching check, jump to step 3757, and consider that the interface to be tested has passed the scenario test.
步骤3755，如果所述响应数据通过匹配性校验，则生成指示所述待测试接口通过测试的测试结果。Step 3755, if the response data passes the matching check, generate a test result indicating that the interface to be tested passes the test.
步骤3757，如果所述响应数据未通过匹配性校验，则生成指示所述待测试接口未通过测试的测试结果。Step 3757, if the response data fails the matching check, generate a test result indicating that the interface to be tested fails the test.
通过上述实施例的配合，基于不同的测试场景，实现了针对待测试接口进行连续、频繁地自动化调用，大大提高了接口测试的自动化程度，提高了测试效率。Through the cooperation of the above embodiments, based on different test scenarios, continuous and frequent automatic calls to the interfaces to be tested are realized, which greatly improves the automation degree of interface testing and improves the testing efficiency.
下述为本发明装置实施例，可以用于执行本发明所涉及的接口测试方法。对于本发明装置实施例中未披露的细节，请参照本发明所涉及的接口测试方法的方法实施例。The following are device embodiments of the present invention, which can be used to implement the interface testing method involved in the present invention. For the details not disclosed in the device embodiment of the present invention, please refer to the method embodiment of the interface testing method involved in the present invention.
请参阅图9，在一示例性实施例中，一种接口测试装置900包括但不限于：测试请求接收模块910、待测试接口确定模块930、场景标识获取模块950、场景用例生成模块970及场景测试模块990。Referring to FIG. 9, in an exemplary embodiment, an interface testing device 900 includes, but is not limited to: a test request receiving module 910, an interface to be tested determining module 930, a scenario identification acquisition module 950, a scenario use case generation module 970, and a scenario Test module 990 .
其中，测试请求接收模块910，用于在显示的测试任务中，接收测试人员针对显示的测试任务而发起的测试请求，所述测试请求用于指示所述测试人员请求测试的测试任务。Wherein, the test request receiving module 910 is configured to receive, among the displayed test tasks, a test request initiated by a tester for the displayed test task, and the test request is used to instruct the tester to request a test task for testing.
待测试接口确定模块930，用于根据所述测试人员请求测试的测试任务确定待测试接口。The interface to be tested determination module 930 is configured to determine the interface to be tested according to the test task requested by the tester.
场景标识获取模块950，用于通过所确定的待测试接口获取对应的测试场景标识，所述测试场景标识用于表示所述待测试接口的测试场景。The scenario identification obtaining module 950 is configured to obtain a corresponding test scenario identification through the determined interface to be tested, and the test scenario identification is used to represent the test scenario of the interface to be tested.
场景用例生成模块970，用于从配置文件中读取所述待测试接口在所述测试场景中的测试参数，生成场景测试用例。The scenario use case generation module 970 is configured to read the test parameters of the interface to be tested in the test scenario from the configuration file, and generate a scenario test case.
场景测试模块990，用于基于所述场景测试用例进行所述待测试接口的场景测试。Scenario testing module 990, configured to perform scenario testing of the interface to be tested based on the scenario test case.
需要说明的是，上述实施例所提供的接口测试装置在进行接口测试处理时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即接口测试装置的内部结构将划分为不同的功能模块，以完成以上描述的全部或者部分功能。It should be noted that, when the interface test device provided by the above-mentioned embodiments performs interface test processing, it only uses the division of the above-mentioned functional modules for illustration. In practical applications, the above-mentioned functions can be assigned to different functional modules according to needs. Completion means that the internal structure of the interface testing device will be divided into different functional modules to complete all or part of the functions described above.
另外，上述实施例所提供的接口测试装置与接口测试方法的实施例属于同一构思，其中各个模块执行操作的具体方式已经在方法实施例中进行了详细描述，此处不再赘述。In addition, the interface testing device and the interface testing method embodiments provided in the above embodiments belong to the same concept, and the specific manners of performing operations of each module have been described in detail in the method embodiments, and will not be repeated here.
请参阅图10，在一示例性实施例中，一种电子设备1000，包括至少一处理器1001、至少一存储器1002、以及至少一通信总线1003。Referring to FIG. 10 , in an exemplary embodiment, an electronic device 1000 includes at least one processor 1001 , at least one memory 1002 , and at least one communication bus 1003 .
其中，存储器1002上存储有计算机可读指令，处理器1001通过通信总线1003读取存储器1002中存储的计算机可读指令。Wherein, the memory 1002 stores computer-readable instructions, and the processor 1001 reads the computer-readable instructions stored in the memory 1002 through the communication bus 1003 .
该计算机可读指令被处理器1001执行时实现上述各实施例中的接口测试方法。When the computer-readable instructions are executed by the processor 1001, the interface testing methods in the foregoing embodiments are implemented.
在一示例性实施例中，一种计算机可读存储介质，其上存储有计算机程序，该计算机程序被处理器执行时实现上述各实施例中的接口测试方法。In an exemplary embodiment, a computer-readable storage medium stores a computer program thereon, and when the computer program is executed by a processor, the interface testing methods in the above-mentioned embodiments are implemented.
上述内容，仅为本发明的较佳示例性实施例，并非用于限制本发明的实施方案，本领域普通技术人员根据本发明的主要构思和精神，可以十分方便地进行相应的变通或修改，故本发明的保护范围应以权利要求书所要求的保护范围为准。The above content is only a preferred exemplary embodiment of the present invention, and is not intended to limit the implementation of the present invention. Those skilled in the art can easily make corresponding modifications or modifications according to the main idea and spirit of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope required by the claims.
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910317832.9ACN110147320A (en) | 2019-04-19 | 2019-04-19 | Interface test method, device and electronic equipment |
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910317832.9ACN110147320A (en) | 2019-04-19 | 2019-04-19 | Interface test method, device and electronic equipment |
| Publication Number | Publication Date |
|---|---|
| CN110147320Atrue CN110147320A (en) | 2019-08-20 |
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910317832.9APendingCN110147320A (en) | 2019-04-19 | 2019-04-19 | Interface test method, device and electronic equipment |
| Country | Link |
|---|---|
| CN (1) | CN110147320A (en) |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111309624A (en)* | 2020-03-02 | 2020-06-19 | 北京创鑫旅程网络技术有限公司 | Test method, device, equipment and storage medium |
| CN111309609A (en)* | 2020-02-13 | 2020-06-19 | 北京字节跳动网络技术有限公司 | Software processing system |
| CN111475376A (en)* | 2020-03-25 | 2020-07-31 | 微民保险代理有限公司 | Method and device for processing test data, computer equipment and storage medium |
| CN111797152A (en)* | 2020-06-23 | 2020-10-20 | 北京自如信息科技有限公司 | Data scene generation method and device and computer equipment |
| CN112000579A (en)* | 2020-08-26 | 2020-11-27 | 上海移远通信技术股份有限公司 | Software interface testing method, system, equipment and medium |
| CN112055069A (en)* | 2020-08-31 | 2020-12-08 | 深圳供电局有限公司 | A method and system for testing electric power automation equipment |
| CN112148607A (en)* | 2020-09-23 | 2020-12-29 | 北京同邦卓益科技有限公司 | Interface testing method and device for service scene |
| CN112148623A (en)* | 2020-10-19 | 2020-12-29 | 青岛鹏海软件有限公司 | LIMS-based intelligent complete set of scene testing method |
| CN112181835A (en)* | 2020-09-29 | 2021-01-05 | 中国平安人寿保险股份有限公司 | Automatic testing method and device, computer equipment and storage medium |
| CN112486829A (en)* | 2020-12-04 | 2021-03-12 | 中信银行股份有限公司 | Test method, device, equipment and storage medium |
| CN112559335A (en)* | 2020-12-10 | 2021-03-26 | 中信银行股份有限公司 | Test method, device, equipment and storage medium |
| CN112597020A (en)* | 2020-12-24 | 2021-04-02 | 平安普惠企业管理有限公司 | Interface testing method and device, computer equipment and storage medium |
| CN112699020A (en)* | 2020-12-11 | 2021-04-23 | 浙江中控技术股份有限公司 | Industrial real-time database API (application program interface) interface testing method |
| CN112783779A (en)* | 2021-01-28 | 2021-05-11 | 北京达佳互联信息技术有限公司 | Test case generation method and device, electronic equipment and storage medium |
| CN113138934A (en)* | 2021-05-14 | 2021-07-20 | 杭州网易云音乐科技有限公司 | Automatic test method, medium, device and computing equipment |
| CN113609018A (en)* | 2021-08-05 | 2021-11-05 | 工银科技有限公司 | Test method, training method, device, apparatus, medium, and program product |
| CN113760697A (en)* | 2020-07-15 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Interface testing method and device, electronic equipment and storage medium |
| CN114297058A (en)* | 2021-12-23 | 2022-04-08 | 马上消费金融股份有限公司 | Test method and device |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015078248A1 (en)* | 2013-11-26 | 2015-06-04 | Tencent Technology (Shenzhen) Company Limited | Dynamic code instrumentation |
| CN107908556A (en)* | 2017-11-08 | 2018-04-13 | 中国平安人寿保险股份有限公司 | Interface test method, device, equipment and computer-readable recording medium |
| CN108710569A (en)* | 2018-05-09 | 2018-10-26 | 深圳壹账通智能科技有限公司 | Test cases generation method, data creation method, device, equipment and medium |
| CN109446099A (en)* | 2018-11-09 | 2019-03-08 | 贵州医渡云技术有限公司 | Automatic test cases generation method, device, medium and electronic equipment |
| CN109614310A (en)* | 2018-10-22 | 2019-04-12 | 中国平安财产保险股份有限公司 | Test interface management method, device, computer equipment and storage medium |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015078248A1 (en)* | 2013-11-26 | 2015-06-04 | Tencent Technology (Shenzhen) Company Limited | Dynamic code instrumentation |
| CN107908556A (en)* | 2017-11-08 | 2018-04-13 | 中国平安人寿保险股份有限公司 | Interface test method, device, equipment and computer-readable recording medium |
| CN108710569A (en)* | 2018-05-09 | 2018-10-26 | 深圳壹账通智能科技有限公司 | Test cases generation method, data creation method, device, equipment and medium |
| CN109614310A (en)* | 2018-10-22 | 2019-04-12 | 中国平安财产保险股份有限公司 | Test interface management method, device, computer equipment and storage medium |
| CN109446099A (en)* | 2018-11-09 | 2019-03-08 | 贵州医渡云技术有限公司 | Automatic test cases generation method, device, medium and electronic equipment |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111309609A (en)* | 2020-02-13 | 2020-06-19 | 北京字节跳动网络技术有限公司 | Software processing system |
| CN111309609B (en)* | 2020-02-13 | 2023-10-03 | 抖音视界有限公司 | software processing system |
| CN111309624A (en)* | 2020-03-02 | 2020-06-19 | 北京创鑫旅程网络技术有限公司 | Test method, device, equipment and storage medium |
| CN111475376B (en)* | 2020-03-25 | 2024-01-30 | 微民保险代理有限公司 | Method, apparatus, computer device and storage medium for processing test data |
| CN111475376A (en)* | 2020-03-25 | 2020-07-31 | 微民保险代理有限公司 | Method and device for processing test data, computer equipment and storage medium |
| CN111797152B (en)* | 2020-06-23 | 2024-03-19 | 北京自如信息科技有限公司 | Data scene generation method and device and computer equipment |
| CN111797152A (en)* | 2020-06-23 | 2020-10-20 | 北京自如信息科技有限公司 | Data scene generation method and device and computer equipment |
| CN113760697A (en)* | 2020-07-15 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Interface testing method and device, electronic equipment and storage medium |
| CN112000579B (en)* | 2020-08-26 | 2024-03-19 | 上海移远通信技术股份有限公司 | Software interface testing method, system, equipment and medium |
| CN112000579A (en)* | 2020-08-26 | 2020-11-27 | 上海移远通信技术股份有限公司 | Software interface testing method, system, equipment and medium |
| CN112055069A (en)* | 2020-08-31 | 2020-12-08 | 深圳供电局有限公司 | A method and system for testing electric power automation equipment |
| CN112055069B (en)* | 2020-08-31 | 2023-12-05 | 深圳供电局有限公司 | Electric power automation equipment testing method and system |
| CN112148607A (en)* | 2020-09-23 | 2020-12-29 | 北京同邦卓益科技有限公司 | Interface testing method and device for service scene |
| CN112181835A (en)* | 2020-09-29 | 2021-01-05 | 中国平安人寿保险股份有限公司 | Automatic testing method and device, computer equipment and storage medium |
| CN112181835B (en)* | 2020-09-29 | 2024-04-26 | 中国平安人寿保险股份有限公司 | Automatic test method, device, computer equipment and storage medium |
| CN112148623B (en)* | 2020-10-19 | 2024-06-14 | 青岛鹏海软件有限公司 | LIMS-based intelligent complete scene test method |
| CN112148623A (en)* | 2020-10-19 | 2020-12-29 | 青岛鹏海软件有限公司 | LIMS-based intelligent complete set of scene testing method |
| CN112486829A (en)* | 2020-12-04 | 2021-03-12 | 中信银行股份有限公司 | Test method, device, equipment and storage medium |
| CN112559335A (en)* | 2020-12-10 | 2021-03-26 | 中信银行股份有限公司 | Test method, device, equipment and storage medium |
| CN112699020A (en)* | 2020-12-11 | 2021-04-23 | 浙江中控技术股份有限公司 | Industrial real-time database API (application program interface) interface testing method |
| CN112597020A (en)* | 2020-12-24 | 2021-04-02 | 平安普惠企业管理有限公司 | Interface testing method and device, computer equipment and storage medium |
| CN112783779A (en)* | 2021-01-28 | 2021-05-11 | 北京达佳互联信息技术有限公司 | Test case generation method and device, electronic equipment and storage medium |
| CN112783779B (en)* | 2021-01-28 | 2024-06-04 | 北京达佳互联信息技术有限公司 | Method and device for generating test case, electronic equipment and storage medium |
| CN113138934A (en)* | 2021-05-14 | 2021-07-20 | 杭州网易云音乐科技有限公司 | Automatic test method, medium, device and computing equipment |
| CN113138934B (en)* | 2021-05-14 | 2024-01-19 | 杭州网易云音乐科技有限公司 | Automatic test method, medium, device and computing equipment |
| CN113609018A (en)* | 2021-08-05 | 2021-11-05 | 工银科技有限公司 | Test method, training method, device, apparatus, medium, and program product |
| CN114297058B (en)* | 2021-12-23 | 2023-03-24 | 马上消费金融股份有限公司 | Test method and device |
| CN114297058A (en)* | 2021-12-23 | 2022-04-08 | 马上消费金融股份有限公司 | Test method and device |
| Publication | Publication Date | Title |
|---|---|---|
| CN110147320A (en) | Interface test method, device and electronic equipment | |
| CN107193750B (en) | Script recording method and device | |
| US9098625B2 (en) | Viral trace | |
| CN112559086B (en) | Applet page rendering method and device, electronic equipment and readable storage medium | |
| WO2019161619A1 (en) | Automatic interface test method and apparatus, and device and computer-readable storage medium | |
| CN107688533B (en) | Application testing method, apparatus, computer equipment and storage medium | |
| CN111666201A (en) | Regression testing method, device, medium and electronic equipment | |
| CN110287696A (en) | A detection method, device and equipment for reverse shell process | |
| CN111124872A (en) | Branch detection method and device based on difference code analysis and storage medium | |
| CN103268448A (en) | Method and system for dynamically detecting safety of mobile applications | |
| CN113076257B (en) | Test script recording method, device, medium and computer equipment | |
| CN111460448B (en) | Method and device for detecting malware family | |
| US20240143482A1 (en) | Systems and methods for providing a timeline view of log information for a client application | |
| CN108563578A (en) | SDK compatibility detection method, device, equipment and readable storage medium | |
| CN113641628B (en) | Data quality detection method, device, equipment and storage medium | |
| CN106302011B (en) | Multi-terminal-based test method and terminal | |
| CN111125015B (en) | Method, device, terminal and medium for classifying dump files | |
| CN104572450B (en) | A kind of method and device for detecting resource distribution | |
| CN115033240A (en) | Processing method and device for error reporting information, computer equipment and storage medium | |
| CN111737109A (en) | A kind of cluster file system testing method and device | |
| CN118193082B (en) | Method and device for rapidly loading plug-in by Java probe and electronic equipment | |
| CN119830303B (en) | Smart contract execution overhead vulnerability detection method, device, equipment and storage medium | |
| CN115878460A (en) | Regression testing method, device, computer equipment and storage medium | |
| CN119537310A (en) | Attribution method, device, equipment and storage medium for application storage resources | |
| CN116955134A (en) | Page testing methods and related equipment |
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information | Address after:201, room 518000, building A, No. 1, front Bay Road, Qianhai Shenzhen Guangdong Shenzhen Hong Kong cooperation zone (Qianhai business secretary) Applicant after:PING AN PUHUI ENTERPRISE MANAGEMENT Co.,Ltd. Address before:518000 Guangdong city of Shenzhen province Qianhai Shenzhen Hong Kong cooperation zone before Bay Road No. 1 building 201 room A Applicant before:PING AN PUHUI ENTERPRISE MANAGEMENT Co.,Ltd. | |
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication | Application publication date:20190820 |