WO2016065753A1 - 一种测试方法、装置及系统 - Google Patents

一种测试方法、装置及系统 Download PDF

Info

Publication number
WO2016065753A1
WO2016065753A1 PCT/CN2015/071411 CN2015071411W WO2016065753A1 WO 2016065753 A1 WO2016065753 A1 WO 2016065753A1 CN 2015071411 W CN2015071411 W CN 2015071411W WO 2016065753 A1 WO2016065753 A1 WO 2016065753A1
Authority
WO
WIPO (PCT)
Prior art keywords
test
piling
module
output request
simulated
Prior art date
Application number
PCT/CN2015/071411
Other languages
English (en)
French (fr)
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 WO2016065753A1 publication Critical patent/WO2016065753A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks

Definitions

  • the present invention relates to the technical field of testing of communication equipment, and in particular to a testing method, device and system.
  • Modern communication equipment adopts an architecture in which the control plane and the forwarding plane are separated. Take routers as an example.
  • the control plane is mainly responsible for routing control and calculation, and the forwarding plane is mainly responsible for the forwarding of message traffic.
  • the control level on the one hand, it runs various protocols, such as routing protocols, MPLS (Multi-Protocol Label Switching, multi-protocol label switching) protocols, etc.; on the other hand, there are a large number of table management modules, typical Such as: routing table, LSP (Label Switched Path) table, TE (Traffic Engineering, traffic engineering) table, etc.
  • These table management modules receive the data calculated by the protocol, and send the table entries to the forwarding layer after integration. For message forwarding.
  • the conventional automated testing methods for communication equipment mainly include: automatically connecting to the device under test through an automated test system, automatically configuring the device under test, and performing functional verification of the configuration results through PING or TRACE after the protocol is converged.
  • This configuration-based automated testing method usually has the following problems in practice:
  • This related test method is often a functional level test, and the test granularity is large, and the details in the table items cannot be further verified, resulting in low fault location capabilities.
  • the purpose of the present invention is to provide a testing method, device and system.
  • a test method including:
  • the simulated output request message After triggering the simulated piling action of the protocol data and waiting for a preset delay time, the simulated output request message is issued;
  • the content of the simulated output request result and the expected output result are compared to obtain a comparison result, and the test result is output according to the comparison result.
  • the content of the test case includes: test scenario description information, protocol piling data required for the simulation scenario, and expected output results of expected output entries.
  • the step of triggering the simulated piling of the protocol data includes:
  • the piling interface of the table management module corresponding to the protocol type and piling data is called by sending an asynchronous message to simulate the sending of upstream protocol data.
  • the preset delay time is the time from when the meter management module receives the protocol data to when it converges and reaches a stable state.
  • the content of the simulation output request message includes: reading the test scenario description information and the keyword information of the expected output entry from the test case.
  • a testing device includes a receiving module, a reading module, a triggering module, a triggering module, an acquiring module, and a processing module, wherein:
  • the receiving module is configured to: receive a test instruction
  • the reading module is configured to: read the test case according to the test instruction;
  • the trigger module is configured to trigger the simulated piling of protocol data according to the test instruction received by the receiving module;
  • the request module is configured to: after the trigger module completes the simulated piling action of triggering the protocol data and waits for a preset delay time, issue an analog output request message;
  • the obtaining module is configured to: obtain an analog output request result obtained in response to the analog output request message;
  • the processing module is configured to compare the simulated output request result with the content of the expected output result to obtain a comparison result, and output the test result according to the comparison result.
  • the content of the test case includes: test scenario description information, protocol piling data required for the simulation scenario, and expected output results of expected output entries.
  • the trigger module is used to call the piling interface of the table management module corresponding to the protocol type and piling data by sending an asynchronous message according to the protocol type and piling data read from the test case to simulate upstream Distribution of protocol data.
  • the preset delay time is the time from when the meter management module receives the protocol data to when it converges and reaches a stable state.
  • the content of the simulation output request message includes: reading the test scenario description information and the keyword information of the expected output entry from the test case.
  • test server test client including test server test client:
  • the test server is configured to: read test cases and trigger simulated piling of protocol data according to the received test instruction, wait for a preset delay time, and then issue a simulated output request message; obtain and respond to the simulated output request message.
  • the obtained simulated output request result and compare the simulated output request result with the content of the expected output result to obtain a comparison result, and output the test result according to the comparison result;
  • the test client is configured to obtain the simulation output request result according to the received simulation output request message, and return the simulation output request result to the test server.
  • the content of the test case includes: test scenario description information, protocol piling data required for the simulation scenario, and expected output results of expected output entries.
  • test server is set to trigger simulated piling of protocol data in the following manner:
  • the piling interface of the table management module corresponding to the protocol type and piling data is called by sending an asynchronous message to simulate the sending of upstream protocol data.
  • the preset delay time is the time from when the meter management module receives the protocol data to when it converges and reaches a stable state.
  • the content of the simulation output request message includes: reading the test scenario description information and the keyword information of the expected output entry from the test case.
  • test client includes a transceiver module extraction module and a calling module, wherein:
  • the transceiver module is configured to: obtain the analog output request message; and return the analog output request result obtained by the invoking module to the test server;
  • the extraction module is configured to: obtain the keyword information of the expected output entry from the analog output request message;
  • the calling module is configured to call the query interface of the expected output entry according to the keyword information of the expected output entry to obtain the analog output request result.
  • the related technology requires multiple devices to simulate the test scenario, and the embodiment of the present invention is based on the protocol piling method, no matter how complicated the scenario is, only one test device is required.
  • the related technology needs to wait for the interaction of various protocols on multiple communication devices to be completed and convergence to be completed before testing.
  • the embodiment of the present invention does not require protocol interaction, and the table management module only needs to receive protocol piling data and converge. It can be tested, so the test efficiency is greatly improved.
  • the related technology is a functional level test. Even if the test fails, it is difficult to accurately locate the fault.
  • the embodiment of the present invention can verify the details of the entries one by one, and provide the corresponding specific test content. , Its test granularity is smaller, which is more conducive to fault location.
  • FIG. 1 is a schematic flowchart of a test method provided by an embodiment of the present invention
  • FIG. 5 is a schematic diagram of the structure of a testing device provided by an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of the architecture of a test system provided by an embodiment of the present invention.
  • Fig. 7 is a schematic structural diagram of a test client provided by an embodiment of the present invention.
  • the embodiment of the present invention provides a test method. As shown in FIG. 1, the implementation process of the method provided in this embodiment includes the steps:
  • test instruction can be customized and generated, or it can be actively input by the user or other third parties to trigger the test process of the test server.
  • test case content includes: test scenario description information, protocol piling data required for the simulation scenario, and expected output results of expected output entries.
  • the simulated piling of the trigger protocol data includes: according to the protocol type and piling data read from the test case, invoking the table management module corresponding to the protocol type and piling data by sending an asynchronous message
  • the piling interface simulates the delivery of upstream protocol data.
  • the stub refers to code used to replace associated code or unimplemented code.
  • the piling is to write or generate piling code.
  • the main purposes of piling are: isolation, complement, and control.
  • piling is to simulate the generation and delivery of protocol data, so that there is no need for protocol interaction between multiple communication devices.
  • the delay time is the time from when the meter management module receives the protocol data to when it converges and reaches a stable state, or in some embodiments, the delay time can also be set to an empirical value.
  • the content of the simulated output request message includes: reading the test scenario description information from the test case and the keyword information of the expected output entry.
  • the receiver of the simulated output request message is the test client. After the test client receives the simulated output request message from the test server, it obtains the keyword information of the expected output table entry, and calls the table query interface according to the keyword information to obtain the simulated output request result. After that, the test client will obtain all the results of the simulated output request.
  • the simulated output request result and the test scenario description information included in the simulated output request message are used as the message body to send a return message to the test server.
  • the test server after receiving the simulated output request result from the test client, compares the simulated output request result with the content in the expected output one by one, and if the comparison results are completely consistent, a description of the test scenario is given , The test scenario passed the mark; if the comparison results are not completely consistent, a description of the test scenario will be given, the test scenario failed mark and specific inconsistencies, so as to facilitate fault location.
  • the expected output result is part of the content of the test case, and the time point for obtaining the expected output can be obtained in step S10 or step S20.
  • the following two different implementations are respectively Explain.
  • the embodiment of the present invention discloses a computer program including program instructions.
  • the program instructions are executed by a test server, the test server can execute any of the above-mentioned test methods.
  • the embodiment of the present invention discloses a carrier carrying the computer program.
  • the timing to obtain the expected output from the test case is: after receiving the simulated output response message from the test server, the expected output is read from the test case, and it is compared with the actual simulated output. Compare.
  • test server processing flow is as follows:
  • Step 201 parse the test case carrier (such as an XML file) to obtain the first test To Trial example.
  • the carrier of the test case may also be a text file in other formats.
  • the content of the test case generally includes the description information of the test scenario, the protocol piling data required to simulate the test scenario, and the expected output of the expected output entry.
  • Step 202 Obtain protocol piling data required for the simulation test scenario in the current test case.
  • Step 203 By sending an asynchronous message, call the piling interface of the table management module corresponding to the protocol piling data to simulate the delivery of the upstream protocol data.
  • Step 204 Delay for a period of time to obtain the description information of the test scenario in the current test case and the keywords of the expected output entry.
  • the delay time is the time from when the meter management module receives the protocol data to when it converges and reaches a stable state, generally an empirical value.
  • Step 205 Using the acquired description information of the test scenario and the keywords of the expected output entry as the message body, send a simulated output request message to the test client.
  • the analog output request includes, but is not limited to, a table query request oriented to the forwarding plane and a table query request oriented to the control plane.
  • Step 206 By sending an asynchronous message, call the piling interface of the table management module corresponding to the protocol piling data to delete the simulated test scenario.
  • Step 207 Obtain the next test case located in the current test case. If it succeeds, skip to step 202; if it fails, the process ends.
  • the embodiment of the present invention discloses a computer program including program instructions.
  • the program instructions When the program instructions are executed by a test server, the test server can execute any test method as shown in FIG. 2.
  • the embodiment of the present invention discloses a carrier carrying the computer program.
  • Step 301 Obtain the key of the expected output entry from the message.
  • Step 302 Using the keyword as input, call the query interface of the expected output entry to obtain the simulated output result. It is worth noting that it is possible to return a failure when calling the query interface. This result should also become a possibility for analog output.
  • the analog output request includes, but is not limited to, a table query request for the forwarding plane and a table query request for the control plane.
  • Step 303 Use the test scenario description information contained in the message and the simulated output result obtained by calling the query interface as the message body, and send a simulated output response message to the test server.
  • the embodiment of the present invention discloses a computer program including program instructions.
  • the program instructions When the program instructions are executed by a test client, the test client can execute any test method as shown in FIG. 3.
  • the embodiment of the present invention discloses a carrier carrying the computer program.
  • Step 401 Obtain the test scenario description information and the simulation output result from the message.
  • Step 402 Re-search through the test scenario description information to obtain a test case corresponding to the test scenario description information. Then obtain the expected output results of the expected output table items included in the test case.
  • Step 403 Compare the content of the simulated output result with the expected output result, and record the inconsistencies in the content.
  • Step 404 Judge the comparison result. If the content is consistent, skip to step 405; otherwise, skip to step 406.
  • Step 405 The content is consistent and the test passes. Give the test scenario description information, and give the test case test pass mark.
  • Step 406 The content is inconsistent, and the test fails.
  • the description information of the test scenario is given, the test pass mark of the test case is given, and the inconsistent specific content is given to facilitate the user to locate the fault.
  • the embodiment of the present invention discloses a computer program including program instructions.
  • the program instructions When the program instructions are executed by a test server, the test server can execute any test method as shown in FIG. 4.
  • the embodiment of the present invention discloses a carrier carrying the computer program.
  • the timing to obtain the expected output from the test case is: when or before the test server sends a simulated output request message to the test client, the expected output has been read from the test case, and After receiving the analog output response message, there is no need to read the expected output from the test case again.
  • test server processing flow is as follows:
  • Step 201 parse the test case carrier (such as an XML file) to obtain the first test case.
  • the carrier of the test case may also be a text file in other formats.
  • the content of the test case generally includes the description information of the test scenario, the protocol piling data required to simulate the test scenario, and the expected output result of the expected output table item.
  • Step 202 Obtain protocol piling data required for the simulation test scenario in the current test case.
  • Step 203 By sending an asynchronous message, call the piling interface of the table management module corresponding to the protocol piling data to simulate the delivery of the upstream protocol data.
  • Step 204 Delay for a period of time to obtain the description information of the test scenario in the current test case, the key of the expected output entry, and the expected output result of the expected output entry.
  • the delay time is the time from when the meter management module receives the protocol data to when it converges and reaches a stable state. It is generally an empirical value.
  • Step 205 Use the acquired description information of the test scenario, the keyword of the expected output entry, and the expected output result of the expected output entry as the message body, and send a simulated output request message to the test client.
  • the analog output request includes, but is not limited to, a table query request oriented to the forwarding plane and a table query request oriented to the control plane.
  • Step 206 By sending an asynchronous message, call the piling interface of the table management module corresponding to the protocol piling data to delete the simulated test scenario.
  • Step 207 Obtain the next test case located in the current test case. If it succeeds, skip to step 202; if it fails, the process ends.
  • the embodiment of the present invention discloses a computer program including program instructions.
  • the program instructions are executed by a test server, the test server can execute any of the above-mentioned test server processing procedures.
  • the embodiment of the present invention discloses a carrier carrying the computer program.
  • Step 301 Obtain the key of the expected output entry from the message.
  • Step 302 Using the keyword as input, call the query interface of the expected output entry to obtain the simulated output result. It is worth noting that it is possible to return a failure when calling the query interface. This result should also become a possibility for analog output.
  • the analog output request includes, but is not limited to, a table query request for the forwarding plane and a table query request for the control plane.
  • Step 303 Use the test scenario description information contained in the message, the expected output result of the expected output entry, and the simulated output result obtained by calling the query interface as the message body, and send a simulated output response message to the test server.
  • the embodiment of the present invention discloses a computer program including program instructions.
  • the program instructions When the program instructions are executed by a test client, the test client can execute any of the above-mentioned test client processing procedures.
  • the embodiment of the present invention discloses a carrier carrying the computer program.
  • Step 401 Obtain the test scenario description information, the expected output result of the expected output table item, and the simulated output result from the message.
  • Step 402 Compare the content of the simulated output result with the expected output result, and record the inconsistency of the content.
  • Step 403 Judge the comparison result. If the content is consistent, skip to step 404; otherwise, skip to step 405.
  • Step 404 The content is consistent and the test passes. Give the test scenario description information, and give the test case test pass mark.
  • Step 405 The content is inconsistent and the test fails.
  • the description information of the test scenario is given, the test pass mark of the test case is given, and the inconsistent specific content is given to facilitate the user to locate the fault.
  • the embodiment of the present invention discloses a computer program including program instructions.
  • the program instructions are executed by a test server, the test server can execute any of the above-mentioned test server processing procedures.
  • the embodiment of the present invention discloses a carrier carrying the computer program.
  • the embodiment of the present invention correspondingly provides a testing device for implementing the above method, which includes:
  • the receiving module 101 is configured to: receive a test instruction
  • the reading module 102 is configured to read a test case according to the test instruction.
  • the carrier of the test case may be a text file with a certain format, such as an XML file, etc.;
  • the trigger module 103 is configured to: trigger the simulated piling of the protocol data according to the received test instruction;
  • the request module 104 is configured to issue an analog output request message after the trigger module completes the simulated piling action of the trigger protocol data and waits for a preset delay time, where the analog output request includes, but is not limited to, forwarding-oriented Table query request and control plane-oriented table query request;
  • the obtaining module 105 is configured to: obtain the analog output request result obtained in response;
  • the processing module 106 is configured to compare the simulated output request result with the content of the expected output result, and output the test result accordingly.
  • test case content includes: test scenario description information, protocol piling data required for the simulation scenario, and expected output results of expected output entries.
  • the trigger module 103 is configured to call the piling interface of the table management module corresponding to the protocol type and piling data by sending an asynchronous message according to the protocol type and piling data read from the test case To simulate the delivery of upstream protocol data.
  • the delay time is the time from when the table management module receives the protocol data to when it converges and reaches a stable state.
  • the content of the simulated output request message includes: reading the test scenario description information from the test case and the keyword information of the expected output entry.
  • the test system adopts a C/S (client/server) model, and includes a test server 10 and a test client 20, where the test The server 10 is responsible for reading test cases, triggering simulated piling of protocol data, triggering the test client 20 to simulate output, and comparing the expected output with the simulated output; the test client 20 is responsible for responding to the simulated output request of the test server 10 , The simulated output result is returned; the test server 10 and the test client 20 communicate with each other using asynchronous messages.
  • C/S client/server
  • test system includes:
  • the test server 10 is set to: read the test case and trigger the simulated piling of the protocol data according to the received test instruction, wait for a preset delay time, and then issue a simulation output request message; and further set to: get the simulation obtained by the response Output the request result, compare the simulated output request result with the expected output result, and output the test result accordingly;
  • the test client 20 is configured to obtain a simulation output request result according to the received simulation output request message, and return it to the test server 10.
  • the carrier of the test case may be a text file with a certain format, such as an XML file.
  • test case content includes: test scenario description information, protocol piling data required for the simulation scenario, and expected output results of expected output entries.
  • test server 10 triggering simulated piling of protocol data includes:
  • the piling interface of the table management module corresponding to the protocol type and piling data is called to simulate the upstream protocol by sending an asynchronous message. To Discuss the issuance of data.
  • the delay time is the time from when the table management module receives the protocol data to when it converges and reaches a stable state.
  • the content of the simulated output request message includes: reading the test scenario description information from the test case and the keyword information of the expected output entry.
  • the analog output request includes, but is not limited to, a table query request oriented to the forwarding plane and a table query request oriented to the control plane.
  • the test client 20 includes:
  • the transceiver module 201 is configured to: obtain an analog output request message, and further configured to: return the analog output request result obtained by the calling module to the test server 10;
  • the extraction module 202 is configured to: obtain the keyword information of the expected output entry from the analog output request message;
  • the calling module 203 is configured to: call the query interface of the expected output entry according to the keyword information of the expected output entry to obtain the simulated output request result.
  • All the methods, devices and systems of the present invention can be used for protocol stack table management, but can also be used for other aspects of testing, which will not be repeated here.
  • the technical scheme of the present invention can effectively reduce the test time, improve the test efficiency, and at the same time make the test granularity smaller and the fault location capability stronger. Therefore, the present invention has strong industrial applicability.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Maintenance And Management Of Digital Transmission (AREA)

Abstract

一种测试方法、装置及系统，所述方法包括：依据接收的测试指令读取测试用例及触发协议数据的模拟打桩，等待一预设延迟时间后，下发模拟输出请求消息；获取响应得到的模拟输出请求结果，并将模拟输出请求结果与期望输出结果的内容作比对，并据此输出测试结果。采用本发明技术方案，能有效减少测试用时，提高测试效率，同时使得测试粒度更小，故障定位能力更强。

Description

一种测试方法、装置及系统 技术领域
本发明涉及通信设备的测试技术领域，具体而言，涉及一种测试方法、装置及系统。
背景技术
现代通信设备采用控制层面与转发层面相分离的架构，以路由器为例，控制层面主要负责路由的控制与计算，而转发层面主要负责报文流量的转发。在控制层面上，一方面其运行着各种协议，例如典型的有：路由协议、MPLS(Multi-Protocol Label Switching，多协议标签交换)协议等；另一方面存在大量的表管理模块，典型的如：路由表、LSP(Label Switched Path，标签交换路径)表、TE(Traffic Engineering，流量工程)表等，这些表管理模块接收协议计算得到的数据，整合后将表项下发给转发层面用于报文转发。
目前，常规的通信设备自动化测试方法主要为：通过自动化测试系统自动连接到被测设备，对被测设备进行自动配置，协议收敛完毕后通过PING或TRACE等方式对配置结果进行功能性校验。这种基于配置的自动化测试方法在实践中通常还存在以下问题：
1)在实际测试过程中需要利用多台通信设备来模拟测试场景，设备配置过程中需要检查协议收敛进度，待各通信设备收敛完毕后方可测试，单个测试用例用时较长。
2)若转发层面的实现机制有差异，表管理模块下发给转发层面的表项细节就会不同，同一套测试用例库需要针对每一种类型的转发层面测试一次，导致测试效率更为低下。
3)该相关的测试方法往往为功能级别的测试，测试粒度大，无法进一步校验表项中的细节，导致故障定位能力较低。
发明内容
为了解决上述的其中至少一个技术问题，本发明的目的在于提供一种测试方法、装置及系统。
本发明采用以下技术方案实现：
一种测试方法，包括：
依据接收到的测试指令读取测试用例并触发协议数据的模拟打桩；
触发协议数据的模拟打桩动作并等待一预设延迟时间后，下发模拟输出请求消息；
获取响应所述模拟输出请求消息而得到的模拟输出请求结果；
将所述模拟输出请求结果与期望输出结果的内容作比对，得到比对结果，根据比对结果输出测试结果。
可选地，所述测试用例的内容包括：测试场景描述信息、模拟场景所需协议打桩数据以及期望输出表项的期望输出结果。
可选地，所述触发协议数据的模拟打桩的步骤包括：
根据从所述测试用例中读取的协议类型和打桩数据，通过发异步消息的方式调用与所述协议类型和打桩数据对应的表管理模块的打桩接口来模拟上游协议数据的下发。
可选地，所述预设延迟时间为表管理模块从接收协议数据到收敛完毕并达到稳定状态的时间。
可选地，所述模拟输出请求消息的内容包括：从所述测试用例中读取测试场景描述信息以及期望输出表项的关键字信息。
一种测试装置，包括接收模块、读取模块、触发模块、触发模块、获取模块和处理模块，其中：
所述接收模块设置成：接收测试指令；
所述读取模块设置成：依据所述测试指令读取测试用例；
所述触发模块设置成：依据所述接收模块接收到的测试指令触发协议数据的模拟打桩；
所述请求模块设置成：在所述触发模块完成触发协议数据的模拟打桩动作并等待一预设延迟时间后，下发模拟输出请求消息；
所述获取模块设置成：获取响应所述模拟输出请求消息而得到的模拟输出请求结果；
所述处理模块设置成：将模拟输出请求结果与期望输出结果的内容作比对，得到比对结果，并根据比对结果输出测试结果。
可选地，所述测试用例的内容包括：测试场景描述信息、模拟场景所需协议打桩数据以及期望输出表项的期望输出结果。
可选地，所述触发模块用于根据从测试用例中读取的协议类型和打桩数据，通过发异步消息的方式调用与所述协议类型和打桩数据对应的表管理模块的打桩接口来模拟上游协议数据的下发。
可选地，所述预设延迟时间为表管理模块从接收协议数据到收敛完毕并达到稳定状态的时间。
可选地，所述模拟输出请求消息的内容包括：从所述测试用例中读取测试场景描述信息以及期望输出表项的关键字信息。
一种测试系统，包括测试服务端测试客户端：
所述测试服务端设置成：依据接收到的测试指令读取测试用例并触发协议数据的模拟打桩，等待一预设延迟时间后，下发模拟输出请求消息；获取响应所述模拟输出请求消息而得到的模拟输出请求结果，并将所述模拟输出请求结果与期望输出结果的内容作比对，得到比对结果，根据该比对结果输出测试结果；
所述测试客户端设置成：依据接收到的模拟输出请求消息得到所述模拟输出请求结果，并将所述模拟输出请求结果返回给所述测试服务端。
可选地，所述测试用例的内容包括：测试场景描述信息、模拟场景所需协议打桩数据以及期望输出表项的期望输出结果。
可选地，所述测试服务端设置成按照如下方式触发协议数据的模拟打桩：
根据从所述测试用例中读取的协议类型和打桩数据，通过发异步消息的方式调用与所述协议类型和打桩数据对应的表管理模块的打桩接口来模拟上游协议数据的下发。
可选地，所述预设延迟时间为表管理模块从接收协议数据到收敛完毕并达到稳定状态的时间。
可选地，所述模拟输出请求消息的内容包括：从所述测试用例中读取测试场景描述信息以及期望输出表项的关键字信息。
可选地，所述测试客户端包括收发模块提取模块和调用模块，其中：
所述收发模块设置成：获取所述模拟输出请求消息；还将所述调用模块得到的所述模拟输出请求结果返回给所述测试服务端；
所述提取模块设置成：从所述模拟输出请求消息中获取期望输出表项的关键字信息；
所述调用模块设置成：依据所述期望输出表项的关键字信息调用期望输出表项的查询接口，得到所述模拟输出请求结果。
通过上述本发明提供的技术方案可以看出，相较于相关技术，本发明技术方案的有益效果在于：
1、相关技术需要多台设备模拟测试场景，而本发明实施例基于协议打桩的方法，无论场景多么复杂，仅需一台测试设备即可。
2、相关技术需要等待多个通讯设备上各种协议均交互完成且收敛完毕后才能进行测试，而本发明实施例不需要进行协议交互，表管理模块只需收到协议打桩数据并且收敛完毕后即可测试，因此测试效率大大提高。
3、相关技术为功能级别的测试，即使测试不通过，也很难对故障进行精确定位，而本发明实施例可以实现对表项的细节进行一一校验，并给出相应的具体测试内容，其测试粒度更小，从而更为有利于进行故障定位。
附图概述
图1是本发明实施例提供的测试方法流程示意图；
图2是本发明实施例1中测试服务端触发测试的流程图；
图3是本发明实施例1中测试客户端收到模拟输出请求消息时的流程图；
图4是本发明实施例1中测试服务端收到模拟输出响应消息时的流程图；
图5是本发明实施例提供的测试装置结构示意图；
图6是本发明实施例提供的测试系统架构示意图；
图7是本发明实施例提供的测试客户端的结构示意图。
本发明的实现、功能特点及优异效果，下面将结合具体实施例以及附图做进一步的说明。
本发明的较佳实施方式
下面结合附图和具体实施例对本发明所述技术方案作进一步的详细描述，但所举实施例不作为对本发明的限定。
本发明实施例提供了一种测试方法，如图1所示，本实施例提供的该方法的实施流程包括步骤：
S10、依据接收的测试指令读取测试用例及触发协议数据的模拟打桩，等待一预设延迟时间后，下发模拟输出请求消息；
S20、获取响应得到的模拟输出请求结果，并将模拟输出请求结果与期望输出结果的内容作比对，并据此输出测试结果。
本实施例中，所述测试指令可以定制生成，也可以由用户或其他第三方主动输入，来触发测试服务端的测试流程。
本实施例中，所述测试用例内容包括：测试场景描述信息、模拟场景所需协议打桩数据以及期望输出表项的期望输出结果。
本实施例中，所述触发协议数据的模拟打桩包括：根据从测试用例中读取的协议类型和打桩数据，通过发异步消息的方式调用与所述协议类型和打桩数据对应的表管理模块的打桩接口来模拟上游协议数据的下发。
本实施例中，所述桩是指用来代替关联代码或者未实现代码的代码。所述打桩就是编写或生成桩代码。打桩的目的主要有：隔离、补齐、控制。在 本实施例中，打桩是为了模拟协议数据的生成与下发，这样就不需要多台通信设备协议交互了。
本实施例中，所述延迟时间为表管理模块从接收协议数据到收敛完毕并达到稳定状态的时间，或者在某些实施例中，也可以将所述延迟时间设置为一经验值。
本实施例中，所述模拟输出请求消息的内容包括：从测试用例中读取测试场景描述信息以及期望输出表项的关键字信息。所述模拟输出请求消息的接收者为测试客户端。测试客户端在收到测试服务端的模拟输出请求消息后，从中获取期望输出表项的关键字信息，并根据该关键字信息调用表查询接口得到模拟输出请求结果，之后测试客户端将得到的所述模拟输出请求结果以及所述模拟输出请求消息中包含的测试场景描述信息等内容作为消息主体，向测试服务端发送回传消息。
本实施例中，测试服务端在收到测试客户端的模拟输出请求结果后，将所述模拟输出请求结果与期望输出中的内容一一进行比较，若比较结果完全一致，则给出测试场景描述，测试场景通过标志；若比较结果不完全一致，则给出测试场景描述，测试场景不通过标志以及具体的不一致内容，从而方便故障定位。
本实施例中，所述期望输出结果是测试用例内容的一部分，期望输出的获取时间点可以是在步骤S10中获得也可以是在步骤S20中获得，下面对该两种不同的实施方式分别进行阐述。
本发明实施例公开了一种计算机程序，包括程序指令，当该程序指令被测试服务端执行时，使得该测试服务端可执行上述任意的测试方法。
本发明实施例公开了一种载有所述的计算机程序的载体。
实施例1
在该实施例中，从测试用例中获取所述期望输出的时机是：从测试服务端收到模拟输出响应消息后再从测试用例中读取期望输出，并将其与真实得到的模拟输出进行比较。
如图2所示，触发测试后，测试服务端处理流程如下：
步骤201：对测试用例的载体(如XML文件)进行解析，获取第一个测 试用例。具体实施时，所述测试用例的载体还可以是其他格式的文本文件。
其中，测试用例的内容一般包括测试场景描述信息、模拟测试场景所需的协议打桩数据以及期望输出表项的期望输出。
步骤202：获取当前测试用例中模拟测试场景所需的协议打桩数据。
步骤203：通过发异步消息的方式，调用与所述协议打桩数据对应的表管理模块的打桩接口来模拟上游协议数据的下发。
步骤204：延时一段时间，获取当前测试用例中测试场景描述信息以及期望输出表项的关键字。延时时间为表管理模块从接收协议数据到收敛完毕达到稳定状态的时间，一般为经验值。
步骤205：以获取的测试场景描述信息以及期望输出表项的关键字为消息主体，向测试客户端发送模拟输出请求消息。其中，所述模拟输出请求包括但不局限于面向转发面的表查询请求和面向控制面的表查询请求。
步骤206：通过发异步消息的方式，调用与所述协议打桩数据对应的表管理模块的打桩接口来删除模拟测试场景。
步骤207：获取位于当前测试用例的下一个测试用例。若成功，跳至步骤202；若失败，流程结束。
本发明实施例公开了一种计算机程序，包括程序指令，当该程序指令被测试服务端执行时，使得该测试服务端可执行如图2所示的任意的测试方法。
本发明实施例公开了一种载有所述的计算机程序的载体。
如图3所示，当测试客户端收到模拟输出请求消息时，处理流程如下：
步骤301：从消息中获取期望输出表项的关键字。
步骤302：以关键字为输入，调用期望输出表项的查询接口，得到模拟输出结果。值得注意的是，这里有可能调用查询接口时返回失败，这种结果也应该成为模拟输出的一种可能。另外，模拟输出请求包括但不局限于面向转发面的表查询请求和面向控制面的表查询请求。
步骤303：以消息中包含的测试场景描述信息以及调用查询接口得到的模拟输出结果为消息主体，向测试服务端发送模拟输出响应消息。
本发明实施例公开了一种计算机程序，包括程序指令，当该程序指令被测试客户端执行时，使得该测试客户端可执行如图3所示的任意的测试方法。
本发明实施例公开了一种载有所述的计算机程序的载体。
如图4所示，当测试服务端收到模拟输出响应消息时，处理流程如下：
步骤401：从消息中获取测试场景描述信息以及模拟输出结果。
步骤402：通过测试场景描述信息，重新搜索得到与所述测试场景描述信息对应的测试用例。然后获取测试用例中包含的期望输出表项的期望输出结果。
步骤403：将模拟输出结果与期望输出结果的内容进行比对，并记录内容不一致的地方。
步骤404：对比较结果作判断。若内容一致，跳至步骤405；否则，跳至步骤406。
步骤405：内容一致，测试通过。给出测试场景描述信息，并且给出测试用例测试通过标志。
步骤406：内容不一致，测试不通过。给出测试场景描述信息，给出测试用例测试通过标志，并且给出不一致的具体内容，方便用户定位故障。
本发明实施例公开了一种计算机程序，包括程序指令，当该程序指令被测试服务端执行时，使得该测试服务端可执行如图4所示的任意的测试方法。
本发明实施例公开了一种载有所述的计算机程序的载体。
实施例2
在该实施例中，从测试用例中获取所述期望输出的时机是：在测试服务端向测试客户端发送模拟输出请求消息时或之前，即已经从测试用例中读取出了期望输出，在收到模拟输出响应消息之后，不用再次从测试用例中读取期望输出。
具体地，在本实施例中，触发测试后，测试服务端处理流程如下：
步骤201：对测试用例的载体(如XML文件)进行解析，获取第一个测试用例。同样地，具体实施时，所述测试用例的载体还可以是其他格式的文本文件。
其中，测试用例的内容一般包括测试场景描述信息、模拟测试场景所需的协议打桩数据以及期望输出表项的期望输出结果。
步骤202：获取当前测试用例中模拟测试场景所需的协议打桩数据。
步骤203：通过发异步消息的方式，调用与所述协议打桩数据对应的表管理模块的打桩接口来模拟上游协议数据的下发。
步骤204：延时一段时间，获取当前测试用例中测试场景描述信息、期望输出表项的关键字以及期望输出表项的期望输出结果。延时时间为表管理模块从接收协议数据到收敛完毕达到稳定状态的时间，一般为经验值。
步骤205：以获取的测试场景描述信息、期望输出表项的关键字以及期望输出表项的期望输出结果为消息主体，向测试客户端发送模拟输出请求消息。同样地，所述模拟输出请求包括但不局限于面向转发面的表查询请求和面向控制面的表查询请求。
步骤206：通过发异步消息的方式，调用与所述协议打桩数据对应的表管理模块的打桩接口来删除模拟测试场景。
步骤207：获取位于当前测试用例的下一个测试用例。若成功，跳至步骤202；若失败，流程结束。
本发明实施例公开了一种计算机程序，包括程序指令，当该程序指令被测试服务端执行时，使得该测试服务端可执行上述任意的测试服务端处理流程。
本发明实施例公开了一种载有所述的计算机程序的载体。
当测试客户端收到模拟输出请求消息时，处理流程如下：
步骤301：从消息中获取期望输出表项的关键字。
步骤302：以关键字为输入，调用期望输出表项的查询接口，得到模拟输出结果。值得注意的是，这里有可能调用查询接口时返回失败，这种结果也应该成为模拟输出的一种可能。另外，模拟输出请求包括但不局限于面向转发面的表查询请求和面向控制面的表查询请求。
步骤303：以消息中包含的测试场景描述信息、期望输出表项的期望输出结果以及调用查询接口得到的模拟输出结果为消息主体，向测试服务端发送模拟输出响应消息。
本发明实施例公开了一种计算机程序，包括程序指令，当该程序指令被测试客户端执行时，使得该测试客户端可执行上述任意的测试客户端处理流程。
本发明实施例公开了一种载有所述的计算机程序的载体。
当测试服务端收到模拟输出响应消息时，处理流程如下：
步骤401：从消息中获取测试场景描述信息、期望输出表项的期望输出结果以及模拟输出结果。
步骤402：将模拟输出结果与期望输出结果的内容进行比对，并记录内容不一致的地方。
步骤403：对比较结果作判断。若内容一致，跳至步骤404；否则，跳至步骤405。
步骤404：内容一致，测试通过。给出测试场景描述信息，并且给出测试用例测试通过标志。
步骤405：内容不一致，测试不通过。给出测试场景描述信息，给出测试用例测试通过标志，并且给出不一致的具体内容，方便用户定位故障。
本发明实施例公开了一种计算机程序，包括程序指令，当该程序指令被测试服务端执行时，使得该测试服务端可执行上述任意的测试服务端处理流程。
本发明实施例公开了一种载有所述的计算机程序的载体。
如图5所示，本发明实施例还相应地提供了一种用于实施上述方法的测试装置，其包括：
接收模块101，设置成：接收测试指令；
读取模块102，设置成：依据所述测试指令读取测试用例，具体实施时，所述测试用例的载体可以是具有一定格式的文本文件,如XML文件等；
触发模块103，设置成：依据接收的测试指令触发协议数据的模拟打桩；
请求模块104，设置成：在触发模块完成触发协议数据的模拟打桩动作并等待一预设延迟时间后，下发模拟输出请求消息，其中，所述模拟输出请求包括但不局限于面向转发面的表查询请求和面向控制面的表查询请求；
获取模块105，设置成：获取响应得到的模拟输出请求结果；
处理模块106，设置成：将模拟输出请求结果与期望输出结果的内容作比对，并据此输出测试结果。
本实施例中，所述测试用例内容包括：测试场景描述信息、模拟场景所需协议打桩数据以及期望输出表项表项的期望输出结果。
本实施例中，所述触发模块103设置成：根据从测试用例中读取的协议类型和打桩数据，通过发异步消息的方式调用与所述协议类型和打桩数据对应的表管理模块的打桩接口来模拟上游协议数据的下发。
本实施例中，所述延迟时间为表管理模块从接收协议数据到收敛完毕并达到稳定状态的时间。
本实施例中，所述模拟输出请求消息的内容包括：从测试用例中读取测试场景描述信息以及期望输出表项的关键字信息。
本发明实施例还相应地提供了一种测试系统，参考图6所示，所述测试系统采用C/S(客户端/服务器)模型，包括测试服务端10和测试客户端20，其中，测试服务端10负责测试用例的读取、触发协议数据的模拟打桩、触发测试客户端20模拟输出、以及将期望输出与模拟输出对比校验；测试客户端20负责响应测试服务端10的模拟输出请求，回传模拟输出结果；测试服务端10与测试客户端20采用异步消息进行通信。
具体地，继续参考图6所示，所述测试系统，包括：
测试服务端10，设置成：依据接收的测试指令读取测试用例及触发协议数据的模拟打桩，等待一预设延迟时间后，下发模拟输出请求消息；以及进一步设置成：获取响应得到的模拟输出请求结果，并将模拟输出请求结果与期望输出结果的内容作比对，并据此输出测试结果；
测试客户端20，设置成：依据接收的模拟输出请求消息得到模拟输出请求结果，并将其返回给测试服务端10。
本实施例中，所述测试用例的载体可以是具有一定格式的文本文件，如XML文件等。
本实施例中，所述测试用例内容包括：测试场景描述信息、模拟场景所需协议打桩数据以及期望输出表项的期望输出结果。
本实施例中，所述测试服务端10触发协议数据的模拟打桩包括：
根据从测试用例中读取的协议类型和打桩数据，通过发异步消息的方式调用与所述协议类型和打桩数据对应的表管理模块的打桩接口来模拟上游协 议数据的下发。
本实施例中，所述延迟时间为表管理模块从接收协议数据到收敛完毕并达到稳定状态的时间。
本实施例中，所述模拟输出请求消息的内容包括：从测试用例中读取测试场景描述信息以及期望输出表项的关键字信息。
本实施例中，所述模拟输出请求包括但不局限于面向转发面的表查询请求和面向控制面的表查询请求。
本实施例中，参考图7所示，所述测试客户端20包括：
收发模块201，设置成：获取模拟输出请求消息，以及进一步设置成：将调用模块得到的模拟输出请求结果返回给测试服务端10；
提取模块202，设置成：从所述模拟输出请求消息中获取期望输出表项的关键字信息；
调用模块203，设置成：依据所述期望输出表项的关键字信息调用期望输出表项的查询接口，得到模拟输出请求结果。
本发明所有的方法、装置和系统都可以用于协议栈表管理，但是也可以用于其他方面的测试，在此不再赘述。
以上所述仅为本发明的优选实施例，并非因此限制本发明的专利范围，凡是利用本发明说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本发明的专利保护范围内。
工业实用性
采用本发明技术方案，能有效减少测试用时，提高测试效率，同时使得测试粒度更小，故障定位能力更强。因此本发明具有很强的工业实用性。

Claims (16)

  1. 一种测试方法，包括：
    依据接收到的测试指令读取测试用例并触发协议数据的模拟打桩；
    触发协议数据的模拟打桩动作并等待一预设延迟时间后，下发模拟输出请求消息；
    获取响应所述模拟输出请求消息而得到的模拟输出请求结果；
    将所述模拟输出请求结果与期望输出结果的内容作比对，得到比对结果，根据比对结果输出测试结果。
  2. 如权利要求1所述的测试方法，其中，所述测试用例的内容包括：测试场景描述信息、模拟场景所需协议打桩数据以及期望输出表项的期望输出结果。
  3. 如权利要求1所述的测试方法，其中，所述触发协议数据的模拟打桩的步骤包括：
    根据从所述测试用例中读取的协议类型和打桩数据，通过发异步消息的方式调用与所述协议类型和打桩数据对应的表管理模块的打桩接口来模拟上游协议数据的下发。
  4. 如权利要求1所述的测试方法，其中，所述预设延迟时间为表管理模块从接收协议数据到收敛完毕并达到稳定状态的时间。
  5. 如权利要求1所述的测试方法，其中，所述模拟输出请求消息的内容包括：从所述测试用例中读取测试场景描述信息以及期望输出表项的关键字信息。
  6. 一种测试装置，包括接收模块、读取模块、触发模块、触发模块、获取模块和处理模块，其中：
    所述接收模块设置成：接收测试指令；
    所述读取模块设置成：依据所述测试指令读取测试用例；
    所述触发模块设置成：依据所述接收模块接收到的测试指令触发协议数据的模拟打桩；
    所述请求模块设置成：在所述触发模块完成触发协议数据的模拟打桩动作并等待一预设延迟时间后，下发模拟输出请求消息；
    所述获取模块设置成：获取响应所述模拟输出请求消息而得到的模拟输出请求结果；
    所述处理模块设置成：将模拟输出请求结果与期望输出结果的内容作比对，得到比对结果，并根据比对结果输出测试结果。
  7. 如权利要求6所述的测试装置，其中，所述测试用例的内容包括：测试场景描述信息、模拟场景所需协议打桩数据以及期望输出表项的期望输出结果。
  8. 如权利要求6所述的测试装置，其中，所述触发模块用于根据从测试用例中读取的协议类型和打桩数据，通过发异步消息的方式调用与所述协议类型和打桩数据对应的表管理模块的打桩接口来模拟上游协议数据的下发。
  9. 如权利要求6所述的测试装置，其中，所述预设延迟时间为表管理模块从接收协议数据到收敛完毕并达到稳定状态的时间。
  10. 如权利要求6所述的测试装置，其中，所述模拟输出请求消息的内容包括：从所述测试用例中读取测试场景描述信息以及期望输出表项的关键字信息。
  11. 一种测试系统，包括测试服务端测试客户端：
    所述测试服务端设置成：依据接收到的测试指令读取测试用例并触发协议数据的模拟打桩，等待一预设延迟时间后，下发模拟输出请求消息；获取响应所述模拟输出请求消息而得到的模拟输出请求结果，并将所述模拟输出请求结果与期望输出结果的内容作比对，得到比对结果，根据该比对结果输 出测试结果；
    所述测试客户端设置成：依据接收到的模拟输出请求消息得到所述模拟输出请求结果，并将所述模拟输出请求结果返回给所述测试服务端。
  12. 如权利要求11所述的测试系统，其中，所述测试用例的内容包括：测试场景描述信息、模拟场景所需协议打桩数据以及期望输出表项的期望输出结果。
  13. 如权利要求11所述的测试系统，其中，所述测试服务端设置成按照如下方式触发协议数据的模拟打桩：
    根据从所述测试用例中读取的协议类型和打桩数据，通过发异步消息的方式调用与所述协议类型和打桩数据对应的表管理模块的打桩接口来模拟上游协议数据的下发。
  14. 如权利要求11所述的测试系统，其中，所述预设延迟时间为表管理模块从接收协议数据到收敛完毕并达到稳定状态的时间。
  15. 如权利要求11所述的测试系统，其中，所述模拟输出请求消息的内容包括：从所述测试用例中读取测试场景描述信息以及期望输出表项的关键字信息。
  16. 如权利要求11所述的测试系统，其中，所述测试客户端包括收发模块提取模块和调用模块，其中：
    所述收发模块设置成：获取所述模拟输出请求消息；还将所述调用模块得到的所述模拟输出请求结果返回给所述测试服务端；
    所述提取模块设置成：从所述模拟输出请求消息中获取期望输出表项的关键字信息；
    所述调用模块设置成：依据所述期望输出表项的关键字信息调用期望输出表项的查询接口，得到所述模拟输出请求结果。
PCT/CN2015/071411 2014-10-28 2015-01-23 一种测试方法、装置及系统 WO2016065753A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410588259.2A CN105634838A (zh) 2014-10-28 2014-10-28 用于协议栈表管理的测试方法、装置及系统
CN201410588259.2 2014-10-28

Publications (1)

Publication Number Publication Date
WO2016065753A1 true WO2016065753A1 (zh) 2016-05-06

Family

ID=55856483

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/071411 WO2016065753A1 (zh) 2014-10-28 2015-01-23 一种测试方法、装置及系统

Country Status (2)

Country Link
CN (1) CN105634838A (zh)
WO (1) WO2016065753A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107294807B (zh) * 2017-07-04 2020-02-11 中国联合网络通信集团有限公司 协议互操作性测试方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060085157A1 (en) * 2004-10-01 2006-04-20 Credence Systems Corporation Synchronization of multiple test instruments
CN101145954A (zh) * 2007-06-20 2008-03-19 中兴通讯股份有限公司 通讯功能打桩类实现方法
CN102420891A (zh) * 2011-09-23 2012-04-18 展讯通信（上海）有限公司 移动终端及其测试方法、测试设备及测试系统
CN102955740A (zh) * 2012-12-13 2013-03-06 中国航空无线电电子研究所 一种基于Perl的驱动函数和桩函数生成方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080222463A1 (en) * 2007-03-05 2008-09-11 Interdigital Technology Corporation Apparatus, method and product for testing communications components
CN101272211B (zh) * 2008-05-21 2012-09-26 中兴通讯股份有限公司 业务交叉软件测试方法及系统
CN101577713B (zh) * 2009-06-02 2012-07-04 中兴通讯股份有限公司 虚拟用户识别模块的实现方法、装置及测试系统
CN102214140B (zh) * 2011-06-21 2017-02-15 中兴通讯股份有限公司 软件自动测试的方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060085157A1 (en) * 2004-10-01 2006-04-20 Credence Systems Corporation Synchronization of multiple test instruments
CN101145954A (zh) * 2007-06-20 2008-03-19 中兴通讯股份有限公司 通讯功能打桩类实现方法
CN102420891A (zh) * 2011-09-23 2012-04-18 展讯通信（上海）有限公司 移动终端及其测试方法、测试设备及测试系统
CN102955740A (zh) * 2012-12-13 2013-03-06 中国航空无线电电子研究所 一种基于Perl的驱动函数和桩函数生成方法

Also Published As

Publication number Publication date
CN105634838A (zh) 2016-06-01

Similar Documents

Publication Publication Date Title
WO2020029375A1 (zh) 接口测试方法、系统、计算机设备和存储介质
WO2020119434A1 (zh) 接口数据处理方法、自动化测试方法、装置、设备和介质
US9672137B1 (en) Shadow test replay service
US9483386B2 (en) Information interaction test device and method based on automatic generation of associated test cases
US20170300402A1 (en) Mock server and extensions for application testing
CN107241315B (zh) 银行网关接口的接入方法、装置及计算机可读存储介质
WO2017181591A1 (zh) 测试方法及系统
CN107633016B (zh) 数据处理方法及装置和电子设备
US9442822B2 (en) Providing a visual representation of a sub-set of a visual program
WO2019001312A1 (zh) 实现告警关联的方法、装置以及计算机可读存储介质
KR102488582B1 (ko) 애플리케이션 실행 상태 검증 방법 및 장치
CN108664521B (zh) 一种提供序列号的方法、装置、电子设备和可读存储介质
EP3884620A1 (en) Fast session restoration for latency sensitive middleboxes
CN103457770A (zh) 网络事务控制方法及执行方法及网络控制器及转发设备
WO2018000918A1 (zh) 一种基于网络的机顶盒测试方法及系统
US11025481B1 (en) Network alert correlation
CN106033422A (zh) 一种数据库操作控制方法、装置及系统
US20180359317A1 (en) System and method for non-intrusive context correlation across cloud services
WO2016165461A1 (zh) 一种电信网网管系统软件自动化测试方法和装置
US9329960B2 (en) Methods, systems, and computer readable media for utilizing abstracted user-defined data to conduct network protocol testing
WO2016065753A1 (zh) 一种测试方法、装置及系统
CN109408272A (zh) 一种存储故障处理方法与装置
CN110362294A (zh) 开发任务执行方法、装置、电子设备及存储介质
US11474794B2 (en) Generating mock services based on log entries
US10063567B2 (en) System for cross-host, multi-thread session alignment

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15855763

Country of ref document: EP

Kind code of ref document: A1