WO2016180237A1

WO2016180237A1 - Northbound interface test apparatus and test method for northbound interface

Info

Publication number: WO2016180237A1
Application number: PCT/CN2016/080394
Authority: WO
Inventors: 吴高科
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-07-27
Filing date: 2016-04-27
Publication date: 2016-11-17
Also published as: CN106407061B; CN106407061A

Abstract

Disclosed is a northbound interface test apparatus, comprising a script execution module and a command execution module, wherein the script execution module is configured to execute a script case in a pre-developed script, call a corresponding request message according to the script case and send an execution command comprising the request message to the command execution module; and the command execution module is configured to execute a corresponding test operation according to the content of the request message and return an execution result to the script execution module, wherein the request message is used to test a communication interface corresponding to a currently tested northbound interface. The solution solves the problem that when a testing tool in the related art is adopted to test a northbound interface, the automated testing capability of the northbound interface is seriously limited due to the fact that a service interface of the northbound interface needs to be hard-coded in order to realize the test of a fixed function of the service interface.

Description

North direction interface test device and test method for northbound interface

Technical field

The present application relates to, but is not limited to, the field of computer testing technology, and in particular to a northbound interface testing device and a northbound interface testing method.

Background technique

The northbound interface provides the device vendor with an interface to the carrier. The northbound interface can be used to monitor the device of each device vendor and monitor the alarm, performance, and services of the device. With the development of third-generation mobile communication technology (3rd-Generation, 3G) and fourth-generation mobile communication technology (4G) network construction, the northbound interface plays an increasingly important role as a bridge between operators and equipment manufacturers. The performance of the northbound interface has become an important feature of device manufacturers.

The current mainstream northbound interface includes a Common Object Request Broker Architecture (CORBA) interface, a multi technology operations systems interface (MTOSI) interface, and a new generation of software-defined networks. The northbound direction of the Software Defined Network (SDN) is the UPS restconf northbound interface. These mainstream northbound interfaces usually define their own service interfaces based on specific protocol standards. However, due to the large number of service interfaces, when testing the service interface of the northbound interface using the test tool of the related technology, the service interface needs to be hard coded according to the function of the service interface of the northbound interface to be tested. Therefore, only the test is performed. It can automate the testing of the fixed functions of the service interface; if you need to measure the service interface whose function changes or the service interface that adds new functions, you need to change the code of the test tool or hard code the new implementation function. To automate testing of the different functions of the business interface.

When testing the northbound interface with the test tool in the related technology, the fixed function of the service interface can be tested by hard coding the service interface of the northbound interface, which results in a large limitation on the automatic test capability of the northbound interface.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the present invention provides a test method for a northbound interface test device and a northbound interface, so as to implement a service interface by hard coding a service interface of a northbound interface when testing a northbound interface by using a test tool in the related art. The fixed function is tested, which leads to a problem of large restrictions on the automated test capability of the northbound interface.

In a first aspect, an embodiment of the present invention provides a northbound interface testing device, including: a script execution module and a command execution module;

The script execution module is configured to: execute a script use case in a pre-developed script, invoke a corresponding request message according to the script use case, and send an execution command including the request message to the command execution module;

The command execution module is configured to: perform a corresponding test operation according to the content of the request message, and return an execution result to the script execution module, where the request message is used for a northbound interface of the current test. The corresponding communication interface is tested.

In a first possible implementation of the first aspect,

The script execution example currently executed by the script execution module includes a task of testing a notification, and the northbound interface testing device further includes: a notification receiving module;

The script execution module is further configured to: after executing the script use case, send a first subscription command to the notification receiving module;

The notification receiving module is configured to: obtain a test notification indicated by the first subscription command, and return the obtained test notification to the script execution module;

The script execution module is further configured to: send an unsubscribe command to the notification receiving module.

In a second possible implementation of the first aspect,

The northbound interface testing device further includes: an initialization module and a script loading module;

The initialization module is configured to: before the script execution module executes the script use case in the pre-developed script, the initialization script loading module loads the pre-developed script, initializes parameters of the command execution module, and receives the notification Module execution module The script use case of the block execution is obtained according to the script load module loading each script use case in the script, the script includes the script use case and a script method, and the script method is an execution method of the script use case ;

The notification receiving module is further configured to: continuously receive a notification sent by the server after initialization.

According to a second possible implementation manner of the first aspect, in a third possible implementation, the current test northbound interface is a Common Object Request Broker Architecture (CORBA) interface, and the initialization module is initialized by: Parameters of the command execution module: Initialize Object Request Broker (ORB);

The initialization module initializes parameters of the notification receiving module by: instructing, by an object management organization (OMG) standard, that the notification receiving module invokes receiving a notification sent by the server;

The initialization module is further configured to: before the script execution module executes the script use case, send a login command to the script execution module, where the login command includes a login script method;

The script execution module is further configured to: execute the login script method according to the login command, invoke a corresponding login request message according to the login script method, and send the login command to the command execution module. Request execution message of the message;

The command execution module is further configured to: perform a dynamic call of CORBA according to the received login request message, and return an execution result to the script execution module.

According to a second possible implementation manner of the first aspect, in a fourth possible implementation, the currently tested northbound interface is a multi-technology operating system (MTOSI) interface or a northbound direction of a software-defined network (SDN). The initialization module initializes parameters of the command execution module by initializing a uniform resource locator (URL) for constructing a hypertext transfer protocol (HTTP) request message;

The initialization module initializes parameters of the notification receiving module by: subscribing to an MTOSI notification;

The notification receiving module is further configured to: initialize the notification receiving at the initialization module After the parameter of the module, sending a second subscription command to the script execution module, where the second subscription command includes a script method of the subscription;

The script execution module is further configured to: execute the subscribed script method according to the second subscription command, invoke a corresponding subscription request message according to the subscribed script method, and send the include to the command execution module Executing a subscription request message for the subscription request message;

The command execution module is further configured to: execute an HTTP request call according to the subscription request message, and return an execution result to the script execution module.

According to the first aspect, the first to fourth possible implementation manners of the first aspect, in a fifth possible implementation, the northbound interface testing device further includes a result generating module;

The script execution module is further configured to: after the command execution module returns the execution result to the script execution module, transmit the execution result to the result generation module;

The result generating module is configured to: output the execution result, wherein the execution result includes all northbound interfaces that have been tested, and the number of tests and the test time of each of the northbound interfaces.

According to the first aspect, any one of the first to fourth possible implementation manners of the first aspect, in a sixth possible implementation manner,

The script execution module executes the script use case in the following manner: in order of each script use case in the script; and/or,

The northbound interface test device further includes a recording module, and the script execution module is further configured to: send the execution information and the abnormality information of the script use case to the recording module during execution of the script use case;

The recording module is configured to: record and display execution information and abnormality information of the script use case.

In a second aspect, an embodiment of the present invention provides a test method for a northbound interface, including:

The script execution module executes a script use case in a pre-developed script, invokes a corresponding request message according to the script use case, and sends an execution command including the request message to the command execution module;

The command execution module performs a corresponding test operation according to the content of the request message, and The execution result is returned to the script execution module, and the request message is used to test the communication interface corresponding to the currently tested northbound interface.

In a first possible implementation manner of the second aspect, the script execution example currently executed by the script execution module includes a task of testing a notification, and after the script executes the script use case, the test method further includes:

The script execution module sends a first subscription command to the notification receiving module;

The notification receiving module acquires the test notification indicated by the first subscription command, and returns the obtained test notification to the script execution module;

The script execution module sends an unsubscribe command to the notification receiving module.

In a second possible implementation of the second aspect,

Before the script execution module executes the script use case in the pre-developed script, the test method further includes:

The initialization module initialization script loading module loads the pre-developed script, initializes the parameters of the command execution module and the parameters of the notification receiving module, wherein the script use case executed by the script execution module is loaded according to the script loading module Obtained by each script use case in the script, the script includes the script use case and a script method, and the script method is an execution method of the script use case;

After the initialization module initializes the parameters of the notification receiving module, the testing method further includes:

The notification receiving module continuously receives the notification sent by the server after initialization.

According to a second possible implementation manner of the second aspect, in a third possible implementation, the current test northbound interface is a Common Object Request Broker Architecture (CORBA) interface, and the command execution module is initialized. Parameters, including: Initialization Object Request Broker (ORB);

The initializing the parameter of the notification receiving module includes: instructing, by an object management organization (OMG) standard, that the notification receiving module invokes receiving a notification sent by the server;

The initialization module sends a login command to the script execution module, where the login command includes a login script method;

The script execution module executes the login script method according to the login command, invokes a corresponding login request message according to the login script method, and sends an execution including the login request message to the command execution module. Login command

The command execution module performs a dynamic call of CORBA according to the received login request message, and returns an execution result to the script execution module.

According to a second possible implementation manner of the second aspect, in a fourth possible implementation manner, the currently tested northbound interface is a multi-technology operating system (MTOSI) interface or a northbound direction of a software-defined network (SDN). Initializing parameters of the command execution module, including: initializing a uniform resource locator (URL) for constructing a hypertext transfer protocol (HTTP) request message;

The initializing the parameters of the notification receiving module includes: subscribing to an MTOSI notification;

The notification receiving module sends a second subscription command to the script execution module, where the second subscription command includes a subscribed script method;

The script execution module executes the subscribed script method according to the second subscription command, invokes a corresponding subscription request message according to the subscribed script method, and sends the subscription request message to the command execution module. Execute the subscription command;

The command execution module executes an HTTP request call according to the subscription request message, and returns an execution result to the script execution module.

According to the second aspect, any one of the first to fourth possible implementation manners of the second aspect, in a fifth possible implementation, the command execution module returns an execution result to the script execution module Thereafter, the test method further includes:

The script execution module transmits the execution result to the result generation module;

The result generation module outputs the execution result, the execution result including all northbound interfaces that have been tested, and the number of tests and the test time of each of the northbound interfaces.

According to the second aspect, any one of the first to fourth possible implementations of the second aspect In a sixth possible implementation manner, the script execution module executes the script use case, including: the script execution module sequentially executes in the order of each script use case in the script; and/or,

In the process of executing the script use case by the script execution module, the test method further includes:

The script execution module sends the execution information and the abnormality information of the script use case to the recording module;

The recording module records and displays execution information and exception information of the script use case.

The embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, which are implemented when the computer executable instructions are executed.

The northbound interface test device and the northbound interface test method provided by the embodiment of the present invention execute a script use case in a pre-developed script through a script execution module, and call a corresponding request message according to the script use case, thereby sending the command execution module to the command execution module. The execution command of the request message, and the command execution module performs a corresponding test operation according to the content of the request message, and returns the execution result to the script execution module. The request message in this embodiment is used for the current test. The communication interface corresponding to the northbound interface is tested. In the embodiment of the present invention, the test logic of the script use case is executed by the script execution module, and the request text for executing the corresponding test function on the northbound interface is invoked, thereby executing the request text of the call by calling the command execution module. The task of testing the northbound interface edited in the script use case is implemented. When the northbound interface is tested by using the test tool in the related art, the service interface of the northbound interface can be hard coded to implement the service interface. Fixed function Test, which led to a big problem to the north limit automated testing capabilities of the interface.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

The drawings are used to provide a further understanding of the technical solutions of the present application, and constitute a part of the specification, which is used together with the embodiments of the present application to explain the technical solutions of the present application, and does not constitute a limitation of the technical solutions of the present application.

FIG. 1 is a schematic diagram of an application scenario of a northbound interface;

2 is a schematic structural diagram of a northbound interface testing device according to an embodiment of the present invention;

3 is a schematic diagram of testing of a northbound interface test device provided by the embodiment shown in FIG. 2;

4 is a schematic structural diagram of another northbound interface testing device according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of still another northbound interface testing device according to an embodiment of the present disclosure;

FIG. 6 is a flowchart of a method for testing a northbound interface according to an embodiment of the present invention;

FIG. 7 is a flowchart of another method for testing a northbound interface according to an embodiment of the present invention;

FIG. 8 is a flowchart of still another method for testing a northbound interface according to an embodiment of the present invention.

Embodiments of the invention

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

The steps illustrated in the flowchart of the figures may be executed in a computer system such as a set of computer executable instructions. Also, although logical sequences are shown in the flowcharts, in some cases the steps shown or described may be performed in a different order than the ones described herein.

Figure 1 shows a schematic diagram of an application scenario of a northbound interface. The unfilled squares represent the server side, and the filled squares represent the client. In the docking process of the northbound interface, the interface definition provided by the device manufacturer is directly visible to the user, that is, the northbound interface service interface in FIG. For the CORBA interface, it is the interface cluster defined by the Interface Description Language (IDL). For the MTOSI interface, it is the interface cluster defined by the Web Service Description Language (referred to as: WSDL) for SDN. The northbound interface is a model definition voice defined in a series of Request For Comments (RFC) 6020, that is, an interface cluster defined by YANG. The northbound interface service interface can also be other forms. The business interface, the client calls the interface definition generated by the special compiler of the northbound interface. It should be noted that the principle of the northbound interface protocol is similar to the seven-layer communication protocol of the Open System Interconnection (OSI), that is, the northbound interface is also a layer model, and the above interface cluster is defined as the uppermost layer, and the interface cluster is There are one or more layers of other communication protocols, which can be collectively referred to as communication interfaces.

In the application scenario shown in Figure 1, in order to implement a certain function, that is, the northbound interface client implementation, the northbound interface service interface needs to be invoked, and the northbound interface service interface inputs the conversion and invokes the communication connection. The server-side communication interface receives the request to invoke the communication interface, and converts it into a call request of the northbound interface service interface, and then invokes the northbound interface server side implementation.

The technical solutions of the present application are described in detail in the following embodiments. The embodiments of the present application can be applied to the application scenario of the northbound interface shown in FIG. The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be described in some embodiments.

FIG. 2 is a schematic structural diagram of a northbound interface testing device according to an embodiment of the present invention. In the case where the northbound interface test device provided in this embodiment is suitable for testing a northbound interface service interface, the northbound interface test device is usually implemented in hardware and software, for example, integrated in a processor of the test device, and is used by the processor. carried out. As shown in FIG. 2, the northbound interface testing apparatus provided in this embodiment includes: a script execution module 11 and a command execution module 12.

The script execution module 11 is configured to execute a script use case in a pre-developed script, call a corresponding request message according to the script use case, and send an execution command including the request message to the command execution module 12.

In this embodiment, the script execution module 11 can execute a pre-developed script, which is a script voice written by the tester for the automation test of the northbound interface after developing the northbound interface test device, and is used for automatically testing the northbound interface. The script usually includes a plurality of script use cases. When the script execution module 11 executes the script use case, the script can be called from the request message set according to the specific script use case, that is, the script and the request message in this embodiment. The text has been developed before the automated test. Generally, the test logic can be edited through the script use case, that is, the specific script use case can call a specific request message, that is, the script use case and the request message are corresponding relationships. The command execution module 12 is configured to send an execution command including the request message by executing the corresponding request message, and the command execution module 12 processes the called request message.

It should be noted that, when the script execution module 11 in this embodiment executes the script use case, for example, each script use case may be sequentially executed in the order of each script use case in the pre-developed script; the script execution module 11 invokes the request message. The method is: according to the content of the currently executed script use case, that is, each time a script use case is executed, the called request message is usually different; in addition, the requested request message is in a text format, for example, Extensible markup language (Extensible Markup Language, referred to as: XML) formatted text.

The command execution module 12 is configured to: perform a corresponding test operation according to the content of the request message, and return the execution result to the script execution module 11, where the request message is used to perform communication interface corresponding to the currently tested northbound interface. test.

In this embodiment, after the command execution module 12 receives the execution command sent by the script execution module 11, the corresponding test operation may be performed according to the request message indicated in the execution command, and the request message is used for the current test. The ability of the northbound interface to correspond to the communication interface is tested. In a specific implementation, the script and the request message set that the tester has developed on the client for testing the function of testing the northbound interface service interface are actually based on the northbound interface service interface in the application scenario shown in FIG. After the input is converted, the corresponding communication interface is called, and the communication interface called after the conversion is tested. In this embodiment, the test of the uppermost interface cluster of the northbound interface is converted into the test of the lower layer communication interface, specifically by pre-definition. The script and the request message collection are implemented together, that is, the execution script use case is to obtain the request message for the current script use case through the script use case, and the test plan is specifically defined in the request message, and the command execution module 12 executes the request message. Perform tests on the features of the tests indicated by the current script use case.

It should be noted that the script execution module 11 in this embodiment executes the script use case, in fact, by repeatedly calling the command execution module 12 to execute the request message that the script execution module 11 calls through the script use case; The execution module 11 is sequentially executed in the order of each script use case in the script. Therefore, the order in which the command execution module 12 executes the request message is also sequentially executed in the order in which the script execution module 11 calls the request message.

The northbound interface test device provided by this embodiment is tested for the function of the northbound interface service interface. In fact, after the conversion, the corresponding communication interface is automatically tested, and the script execution module 11 is required to execute the pre-developed script use case first. The execution of the script use case calls the request message related to the test, that is, the two factors that test the communication interface are the script use case and the request message. FIG. 3 is a schematic diagram showing the test of the northbound interface test apparatus provided in the embodiment shown in FIG. 2. Similar to the application scenario shown in FIG. 1, the unfilled square represents the server side, and the filled square represents the client, and the northbound interface. The test device tests the communication interface corresponding to the northbound interface service interface of the client by executing the script use case and calling the request message corresponding to the current script use case, that is, testing the corresponding communication interface of the server through the client, thereby according to the test result. Life The execution module 12 performs the execution result of the request message to verify the function of the client interface and the server-side northbound interface service interface.

In this embodiment, the automatic test of the function of the northbound interface service interface is established on the corresponding communication interface. The input that can be recognized by the communication interface is usually a binary stream of text or text encoding. For example, for the CORBA interface, it is based on the Internet. The internal object request proxy protocol (Internet Inter-ORB Protocol, IIOP) CORBA dynamic call interface, for MTOSI and SDN, is the HyperText Transfer Protocol (HTTP); the test plan is The IDL or WSDL request message is saved first, such as the northbound interface request message in FIG. 3, so that the test logic is edited by the script, that is, the tester writes the test sequence in the script in the form of a script use case to complete the test. The use case test of the item function, as shown in the northbound interface automation test script of Figure 3. The northbound interface test device provided in this embodiment is independent of the specific northbound interface service interface definition in the process of performing the test, and is only responsible for executing the test script use case to implement automatic test of the northbound interface service interface.

The northbound interface test apparatus provided in this embodiment executes a script use case in a pre-developed script through a script execution module, and invokes a corresponding request message according to the script use case, thereby transmitting an execution command including the request message to the command execution module. Then, the command execution module performs a corresponding test operation according to the content of the request message, and returns the execution result to the script execution module. The request message in this embodiment is used to perform the communication interface corresponding to the currently tested northbound interface. The test, that is, the test logic of the script use case is executed by the script execution module, and the request text for executing the corresponding test function on the northbound interface is invoked, thereby executing the call request text by calling the command execution module to implement the edited northward direction in the script use case. The test is performed on the interface. This example solves the problem of testing the fixed function of the service interface by hard coding the service interface of the northbound interface. Automated measurement Capacity constraints bigger problem.

The northbound interface test device provided by the present embodiment solves the northbound interface service interface and the northbound interface test device, as compared with the test tool in the related art, which implements the test of the fixed function of the northbound interface service interface in a hard-coded manner. Coupling, that is, the automated test is established on the communication interface corresponding to the northbound interface service interface to be tested, so that the automated test development becomes the development of the request message and the script use case, and the request message is a text input that the communication interface can recognize, which is reduced. Automation The threshold for use case development, before testing the communication interface, the tester can develop according to the test requirements, develop a script use case for testing; and if the script use case passes the test, the function of the northbound interface service interface corresponding to the communication interface is explained. Verification passed. The northbound interface test device provided in this embodiment has the characteristics of rapid and flexible development in the development of automated test cases, can double the efficiency of development and test, thereby improving product quality, and is particularly suitable for agile development.

Optionally, FIG. 4 is a schematic structural diagram of another northbound interface testing device according to an embodiment of the present invention. In this embodiment, the script execution module 11 currently executes the task of the test notification, and the device provided in this embodiment further includes a notification receiving module 13 based on the northbound interface test device shown in FIG. The script execution module 11 is further configured to: after executing the script use case, send a first subscription command to the notification receiving module 13; correspondingly, the notification receiving module 13 is configured to: obtain a test notification indicated by the first subscription command, and Returning the obtained test notification to the script execution module 11; subsequently, after obtaining the required test notification in the script use case, that is, after completing the task of the test notification, the script execution module 11 may further send the unsubscribe command to the notification receiving module 13 To cancel the test notification task.

It should be noted that the notification receiving module 13 in this embodiment can always receive the notification sent by the server after being started. When the script execution module 11 subscribes to the notification, the notification receiving module 13 needs to test according to the first subscription command. The notification is obtained from the notification received by the server, and the notification of the subscription by the script execution module 11 is found, and is returned to the script execution module 11; that is, the operation of the subscription notification in the embodiment is between the internal modules of the northbound interface test device. Notification subscription. In addition, the script execution module 11 in this embodiment executes the script use case, and not only needs to execute the request message that the script execution module 11 calls by repeatedly calling the command execution module 12, but also needs to subscribe by repeatedly calling the notification receiving module 13. The script execution module 11 currently executes a notification in the script use case that needs to be tested.

Optionally, the northbound interface test apparatus shown in FIG. 4 may further include: an initialization module 14 and a script loading module 15, wherein the initialization module 14 is configured to: before the script execution module 11 executes the script use case in the pre-developed script The initialization script loading module 15 loads the pre-developed script, and initializes the parameters of the command execution module 12 and the parameters of the notification receiving module 13, wherein the script use case executed by the script execution module 11 is loaded according to the script loading module 15 Obtained by each script use case, the script includes script use cases and script methods, the script method The execution method of the script use case; correspondingly, the notification receiving module 13 is further configured to: continuously receive the notification sent by the server after the initialization. It should be noted that, the embodiment does not limit the order in which the initialization module 14 initializes the script loading module 15, the command execution module 12, and the notification receiving module 13, and may be executed sequentially or in parallel.

In this embodiment, the script loaded by the script loading module 15 is, for example, a script based on an object-oriented programming language Java virtual machine programming language (Groovy), that is, a Groovy script, since the Groovy language is an extension to the Java language, Therefore, the workload of developing Groovy scripts is small; and the Groovy script loaded by the script loading module 15 is divided into two parts, one is the Groovy script method, and the other is the Groovy script use case, wherein the Groovy script method can be some commonly used or one by one. Or a method common to multiple Groovy script use cases, such as a Groovy script method for initializing the login of module 14.

In an application scenario of testing a northbound interface by using the device provided by the embodiment of the present invention, FIG. 5 is a schematic structural diagram of another northbound interface testing device according to an embodiment of the present invention. This embodiment can be used to test the CORBA interface. The script execution module 11 executes the request message that is invoked by the script use case as a CORBA request message, and the CORBA request message is also a text file in XML format. In this embodiment, in an implementation, on the one hand, the initialization module 14 initializes the parameters of the command execution module 12 by: initializing the object requesting proxy according to the network protocol (IP) of the server and the naming service port (Object) Request Broker, referred to as: ORB); on the other hand, the initialization module 14 initializes the parameters of the notification receiving module 13 by: according to the service port notified by the server, through the Object Management Group (OMG) standard, The notification notification receiving module 13 continues to receive the notification sent by the server.

In a specific implementation, the command execution module 12 may be a CORBA command execution module 12, and the notification receiving module 13 may notify the OMG notification receiving module 13 that the OMG notification receiving module 13 is in the state of receiving the OMG notification after initialization. An interface for subscribing and unsubscribing can be provided. For example, when the script execution module 11 executes the script use case, if a situation in which a certain notification is to be tested is encountered, the first subscription command is sent to the notification receiving module 13 to subscribe to the notification. The notification receiving module 13 finds the test notification of the subscription indicated by the first subscription command in the notification received from the server, thereby returning the required test notification to the script execution module 11 to complete You can cancel the notification subscription after you have tested the notification's tasks.

It should be noted that, in this embodiment, the script loaded by the script loading module 15 is also taken as an example of a Groovy script, which includes a Groovy script method and a Groovy script use case. For the CORBA interface, the definition in the 814 standard needs to be followed. The login method for obtaining getEmsSession using EmsSessionFactory is defined; optionally, before each Groovy script use case is executed, a login operation is required first, and the Groovy script method corresponding to the Groovy script use case to be executed is the initialization module 14 instructing execution. Log in to the Groovy script method. In a specific implementation, the initialization module 14 is further configured to: before the script execution module 11 executes the script use case, send a login command to the script execution module 11, where the login command includes a login script method. For example, the registered Groovy script method; the script execution module 11 is further configured to: execute the logged-in Groovy script method according to the login command, and invoke the corresponding login request message according to the logged-in Groovy script method, for example, a login CORBA request. The message, the logged-in CORBA request message is also a text file stored in an XML format, thereby sending an execution login command including the logged-in CORBA request message to the command execution module 12; accordingly, the command execution module 12 also sets The dynamic call of the CORBA is performed according to the received CORBA request message, and the execution result is returned to the script execution module 11 after the execution is completed.

It should be noted that the embodiment shown in FIG. 5 is different from the embodiment shown in FIG. 4 in that the test of the CORBA interface in this embodiment needs to follow the definition in the 814 standard, that is, before the script execution module 11 executes the script use case, The login operation is first performed, in which the initialization module 14 is required to send a login command to the script execution module 11. Therefore, in the embodiment shown in FIG. 5, the initialization module 14 and the script execution module 11 have a connection relationship for transmitting signaling. In addition, the request message in the embodiment of the present invention may all be stored in a text file in an XML format. After receiving the login command, the command execution module 12 reads the registered CORBA request message in the command, and passes the read after the reading is completed. The ORB calls the dynamic call interface of CORBA. After the call is completed, the execution result is re-saved as a text file in XML format for subsequent use by the script execution module 11. Furthermore, the script execution module 11 in this embodiment can execute the script use case loaded by the script loading module 15 by using the unit test case framework.

In another application scenario of testing a northbound interface by using the device provided by the embodiment of the present invention, Refer to the structural schematic diagram of the northbound interface test device shown in FIG. The northbound interface test device provided in this embodiment may be used to test the northbound direction of the MTOSI interface or the SDN, and the script execution module 11 uses the request message that is invoked by the script use case to be an HTTP request message, and the HTTP request message may also be an XML. Formatted text file. In this embodiment, in an implementation, on the one hand, the initialization module 14 initializes the parameters of the command execution module 12 by: initializing a Uniform Resource Locator (URL) parameter of the server, that is, initializing for constructing The URL of the HTTP request message, because the script execution module 11 in this embodiment executes the HTTP request message when the script use case is executed, the HTTP request message needs to include a URL, and the HTTP request message can be, for example, a simple object access protocol (Simple Object Access). Protocol, abbreviated as: SOAP) request message, the SOAP request message may be a specific application of the HTTP request message; on the other hand, the initialization module 14 initializes the parameter of the notification receiving module 13 by subscribing to the MTOSI notification, thereby indicating The notification receiving module 13 continuously receives the notification sent by the server. In a specific implementation, the command execution module 12 may be, for example, an HTTP request execution module, and the notification receiving module 13 may notify the receiving module, for example, a Jetty (Java-based network container), the Jetty notification receiving module is always in after the initialization. Receiving the status of the MTOSI notification, the interface for subscribing and unsubscribing can be provided, and the manner in which the script execution module 11 notifies the receiving module of the subscription notification and the cancellation notification subscription to the Jetty is the same as the above embodiment, and belongs to the internal module of the northbound interface test device. Notification subscription.

It should be noted that, in this embodiment, the script loaded by the script loading module 15 is taken as an example of a Groovy script, which includes a Groovy script method and a Groovy script use case. After the initialization module 14 initializes the parameters of the Jetty notification receiving module, That is, after the MTOSI notification is subscribed, the subscription notification is sent to the server by calling the subscribed Groovy script method. The specific implementation is as follows: the notification receiving module 13 is further configured to: send a second subscription command to the script execution module 11, where the second The subscription command includes a subscribed script method, such as a subscription to the Groovy script method; the script execution module 11 is further configured to execute the subscription's Groovy script method according to the second subscription command, and invoke the corresponding according to the subscription's Groovy script method. Subscribing to the request message, for example, a subscribed SOAP request message, the subscribed SOAP request message is also a text file stored in an XML format, thereby transmitting an execution subscription command including the subscribed SOAP request message to the command execution module 12. Correspondingly, the command execution module 12 is further configured to: Read the SOAP request message to perform HTTP requests to call, after the completion of the implementation of the results returned The module 11 is executed for the script.

It should be noted that, in the above embodiment, whether the initialization notification receiving module 13 is tested when testing the CORBA interface, or the northbound time initialization notification receiving module 13 of the MTOSI interface or the SDN is tested, the purpose is to receive a notification from the server, and the subscription notification is The operation is a notification subscription between the northbound interface test device and the server.

Optionally, the northbound interface testing device in the embodiment shown in FIG. 4 and FIG. 5 may further include a result generating module 16, and the script executing module 11 is further configured to: return the execution result to the script execution module at the command execution module 12. After 11 , the execution result is transmitted to the result generation module 16; correspondingly, the result generation module 16 is configured to: output an execution result, wherein the execution result includes all northbound interfaces that have been tested, and the number of tests of each northbound interface And test time. In addition, the northbound interface test apparatus in the embodiment shown in FIG. 4 and FIG. 5 may further include a recording module 17, and the script execution module 11 is further configured to: execute execution information and an exception of the script use case in the process of executing the script use case. The information is sent to the recording module 17; accordingly, the recording module 17 is configured to record and display execution information and exception information of the script use case.

In a specific implementation, after the script execution module 11 executes the script use case, the result may be output by the result generation module 16 by using a webpage, a text, or an Excel, for the tester to view the execution result, and the execution result may be reflected. The execution of each script use case, including which northbound interfaces were tested, and the number of tests and test times for each northbound interface tested. In addition, when the script use case fails to execute, the related abnormal running state can be viewed through the information recorded by the recording module 17.

The northbound interface test device provided by the embodiment of the present invention performs the automatic use case test based on the underlying protocol of the northbound interface protocol, that is, the communication interface, from the characteristics of the northbound interface, so that only the request message is required after the script development is completed. By writing script use cases, you can quickly complete changes to old script use cases and the development of new script use cases. It can be closely integrated with the agile development model to multiply the efficiency of development testing and facilitate integration into a continuous integration system. In addition, the northbound interface test device provided by the embodiment of the present invention can provide a stable northbound interface, and is applicable to automatic test development of script use cases in various application scenarios, and can correspondingly reduce the maintenance required for the northbound interface test device. Labor costs.

FIG. 6 is a flowchart of a method for testing a northbound interface according to an embodiment of the present invention. This implementation In the case where the method provided is applicable to testing the service interface of the northbound interface, the method can be performed by a northbound interface test device, which is usually implemented in hardware and software, for example, a processor integrated in the test device. In, for the processor to call execution. As shown in FIG. 6, the method provided in this embodiment includes the following steps:

Step S110, the script execution module executes the script use case in the pre-developed script, and invokes the corresponding request message according to the script use case;

Step S120: The script execution module sends an execution command including the request message to the command execution module.

Step S130, the command execution module performs a corresponding test operation according to the content of the request message;

In step S140, the command execution module returns the execution result to the script execution module, where the request message is used to test the capability of the communication interface corresponding to the currently tested northbound interface.

The application scenario of testing the service interface of the northbound interface through the northbound interface test device in this embodiment can also refer to the application scenario shown in FIG. 1 above. The test mode can also refer to the test schematic diagram shown in FIG. 3 above. The test method of the northbound interface provided by the embodiment is independent of the specific northbound interface service interface definition during the test process, and is only responsible for executing the automated test script use case.

The test method of the northbound interface provided by the embodiment of the present invention can be performed by the northbound interface test device provided by the embodiment shown in FIG. 2, and the steps of the method correspond to the functions of the devices in the northbound interface test device provided by the embodiment of the present invention. The implementation principle and technical effect are similar, and will not be described here.

Optionally, on the basis of the foregoing embodiment shown in FIG. 6, if the script execution example currently executed by the script execution module includes the task of the test notification, the method provided by the embodiment further includes:

Step S111, the script execution module sends a first subscription command to the notification receiving module.

Step S112, the notification receiving module acquires the test notification indicated by the first subscription command;

In step S113, the notification receiving module returns the obtained test notification to the script execution module, and the test notification obtained in this embodiment is a notification received from the server.

In step S114, the script execution module sends an unsubscribe command to the notification receiving module.

It should be noted that the embodiment does not limit the execution sequence of step S111 to step S114 and step S120 to step S140, and FIG. 6 is illustrated by taking steps S111 to S114 before step S120 to step S140 as an example.

Optionally, the method provided in this embodiment further includes: before step S110:

Step S101, the initialization module initializes the script loading module;

Step S102, the script loading module loads the script use case in the pre-developed script. Optionally, the script use case executed by the script execution module is obtained according to each script use case in the script loading module loading script, and the script includes a script use case. And a script method that is an execution method of the script use case;

Similarly, the above method further includes:

Step S103, the initialization module initializes a parameter of the command execution module;

Step S104, the initialization module initializes the parameters of the notification receiving module.

It should be noted that the embodiment does not limit the order in which the initialization module performs steps S101 to S102 and performs step S103 or step S104. FIG. 6 shows an execution manner in the order of steps S101 to S104 as an example.

In a specific application of the test method of the northbound interface provided by the embodiment of the present invention, FIG. 7 is a flowchart of another test method of the northbound interface according to the embodiment of the present invention. This embodiment is used to test the CORBA interface. In step S110, the script execution module calls the request message to be a CORBA request message by executing the script use case. On the basis of the foregoing embodiment shown in FIG. 6, step S103 may be replaced by: initializing the ORB according to the IP address of the server and the naming service port; step S104 may be replaced by: indicating the notification receiving by the OMG standard according to the service port notified by the server. The module is instructed to receive the notification sent by the server, that is, to subscribe to the OMG notification. The notification receiving module in this embodiment is in the state of receiving the OMG notification after the initialization. The specific implementation is the same as that in the foregoing embodiment, and therefore is not described here.

It should be noted that, in this embodiment, the script loaded by the script loading module is also taken as an example of a Groovy script, which includes a Groovy script method and a Groovy script use case. This embodiment tests the CORBA interface, that is, executes each Before the Groovy script use case, the login operation needs to be performed first. Optionally, the method provided in this embodiment is further included before step S110. include:

Step S105, the initialization module sends a login command to the script execution module, where the login command includes a login Groovy script method;

Step S106, the script execution module executes the logged-in Groovy script method according to the login command, and invokes the corresponding logged-in CORBA request message according to the logged-in Groovy script method;

Step S107, the script execution module sends an execution login command including the registered CORBA request message to the command execution module.

Step S108, the command execution module performs a dynamic call of the CORBA according to the received CORBA request message.

In step S109, the command execution module returns the execution result to the script execution module.

The test method of the northbound interface provided by the embodiment of the present invention can be performed by the northbound interface test device provided by the embodiment shown in FIG. 5, and the steps of the method correspond to the functions of the devices in the northbound interface test device provided by the embodiment of the present invention. The implementation principle and technical effect are similar, and will not be described here.

Similarly, in another specific application of the test method of the northbound interface provided by the embodiment of the present invention, FIG. 8 is a flowchart of still another test method of the northbound interface according to the embodiment of the present invention. The present embodiment is used to test the northbound direction of the MTOSI interface or the SDN. In the step S110, the script execution module invokes the request message sent by the script use case as an HTTP request message. On the basis of the foregoing embodiment shown in FIG. 6, step S103 may be replaced by: initializing a URL for constructing an HTTP request message; step S104 may be replaced by: subscribing to the MTOSI notification, thereby instructing the notification receiving module to continuously receive the notification sent by the server. .

It should be noted that, in this embodiment, the script loaded by the script loading module is also taken as an example of a Groovy script, which includes a Groovy script method and a Groovy script use case, and the notification is received after the initialization module initialization notification receiving module subscribes to the MTOSI notification. The module needs to invoke the scripting method of the subscription. Optionally, the method provided in this embodiment further includes after step S104:

Step S105, the notification receiving module sends a second subscription command to the script execution module, where the second subscription command includes a subscribed Groovy script method;

Step S106, the script execution module executes the subscribed Groovy script method according to the second subscription command, and invokes the corresponding subscribed SOAP request message according to the subscribed Groovy script method.

Step S107: The script execution module sends an execution subscription command including a subscribed SOAP request message to the command execution module.

Step S108, the command execution module performs an HTTP request call according to the subscribed SOAP request message;

The test method of the northbound interface provided by the embodiment of the present invention can be performed by the northbound interface test device provided by the embodiment shown in FIG. 4, and the steps of the method correspond to the functions of the devices in the northbound interface test device provided by the embodiment of the present invention. The implementation principle and technical effect are similar, and will not be described here.

Optionally, on the basis of the testing method of the northbound interface provided by the foregoing embodiments, after step S140 and step S109, the following steps may be performed:

Step S150, the script execution module transmits the execution result to the result generation module;

In step S160, the result generation module outputs an execution result, which includes all the northbound interfaces that have been tested, and the number of tests and the test time of each northbound interface.

In addition, in the process of executing the script use case, the script execution module further includes: the script execution module transmitting the execution information and the abnormality information of the script use case to the recording module; and subsequently, the recording module Record and display execution information and exception information for script use cases.

In addition, an embodiment of the present invention further provides a computer readable storage medium, where computer executable instructions are stored, and the test method of the northbound interface is implemented when the computer executable instructions are executed.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be performed by a program to instruct related hardware, such as a processor, which may be stored in a computer readable storage medium, such as a read only memory, disk or optical disk. Wait. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, being executed by a processor and stored in a memory. Programs/instructions to implement their respective functions. This application is not limited to any specific combination of hardware and software.

The embodiments disclosed in the present application are as described above, but the description is only for the purpose of understanding the present application, and is not intended to limit the present application. Any modifications and changes in the form and details of the embodiments may be made by those skilled in the art without departing from the spirit and scope of the disclosure. The scope defined by the appended claims shall prevail.

Industrial applicability

The embodiment of the present invention provides a test method for the northbound interface test device and the northbound interface, and solves the problem that the test interface of the related art is used to test the northbound interface, and the service interface of the northbound interface needs to be hard coded to implement the service interface. The fixed function is tested, which leads to a problem of large restrictions on the automated test capability of the northbound interface.

Claims

A northbound interface testing device includes: a script execution module and a command execution module;

The script execution module is configured to: execute a script use case in a pre-developed script, invoke a corresponding request message according to the script use case, and send an execution command including the request message to the command execution module;

The command execution module is configured to: perform a corresponding test operation according to the content of the request message, and return an execution result to the script execution module, where the request message is used for a northbound interface of the current test. The corresponding communication interface is tested.
The northbound interface test apparatus according to claim 1, wherein

The script execution case currently executed by the script execution module includes a task of testing notifications.

The device further includes: a notification receiving module;

The script execution module is further configured to: after executing the script use case, send a first subscription command to the notification receiving module;

The notification receiving module is configured to: obtain a test notification indicated by the first subscription command, and return the obtained test notification to the script execution module;

The script execution module is further configured to: send an unsubscribe command to the notification receiving module.
The northbound interface testing device according to claim 1, further comprising: an initialization module and a script loading module;

The initialization module is configured to: before the script execution module executes the script use case in the pre-developed script, the initialization script loading module loads the pre-developed script, initializes parameters of the command execution module, and receives the notification a parameter of the module, wherein the script use case executed by the script execution module is obtained according to the script load module loading each script use case in the script, the script including the script use case and a script method, The script method is an execution method of the script use case;

The notification receiving module is further configured to: continuously receive a notification sent by the server after initialization.
The northbound interface test apparatus according to claim 3, wherein

The northbound interface of the current test is a public object requesting proxy architecture CORBA interface,

The initialization module initializes parameters of the command execution module by: initializing an object requesting agent ORB;

The initialization module initializes parameters of the notification receiving module by: instructing, by the object management organization, an OMG standard, that the notification receiving module invokes receiving a notification sent by the server;

The initialization module is further configured to: before the script execution module executes the script use case, send a login command to the script execution module, where the login command includes a login script method;

The script execution module is further configured to: execute the login script method according to the login command, invoke a corresponding login request message according to the login script method, and send the login command to the command execution module. Request execution message of the message;

The command execution module is further configured to: perform a dynamic call of CORBA according to the received login request message, and return an execution result to the script execution module.
The northbound interface test apparatus according to claim 3, wherein

The northbound interface of the current test is a northbound direction of a multi-technology operating system MTOSI interface or a software-defined network SDN.

The initialization module initializes parameters of the command execution module by: initializing a uniform resource locator URL for constructing a hypertext transfer protocol HTTP request message;

The initialization module initializes parameters of the notification receiving module by: subscribing to an MTOSI notification;

The notification receiving module is further configured to: after the initialization module initializes the parameter of the notification receiving module, send a second subscription command to the script execution module, where the second subscription command includes a subscribed script method;

The script execution module is further configured to: execute the subscribed script method according to the second subscription command, invoke a corresponding subscription request message according to the subscribed script method, and send the include to the command execution module Executing a subscription request message for the subscription request message;

The command execution module is further configured to: execute an HTTP request call according to the subscription request message, and return an execution result to the script execution module.
The northbound interface test apparatus according to any one of claims 1 to 5, further comprising a result generation module; the script execution module further configured to: return the execution result to the command execution module to After the script executes the module, transmitting the execution result to the result generation module;

The result generating module is configured to: output the execution result, wherein the execution result includes all northbound interfaces that have been tested, and the number of tests and the test time of each of the northbound interfaces.
The northbound interface test apparatus according to any one of claims 1 to 5, wherein the script execution module executes the script use case in the following manner: in order of each script use case in the script; and or,

The device further includes a recording module, and the script execution module is further configured to: send the execution information and the abnormality information of the script use case to the recording module during execution of the script use case; the recording module Set to: record and display execution information and exception information of the script use case.
A test method for a northbound interface, including:

The script execution module executes a script use case in a pre-developed script, invokes a corresponding request message according to the script use case, and sends an execution command including the request message to the command execution module;

The command execution module performs a corresponding test operation according to the content of the request message, and returns an execution result to the script execution module, where the request message is used to perform a communication interface corresponding to the currently tested northbound interface. test.
The method of testing a northbound interface according to claim 8, wherein

The script execution case currently executed by the script execution module includes a task of testing notifications.

After the script executes the script use case, the test method further includes:

The script execution module sends a first subscription command to the notification receiving module;

The notification receiving module acquires the test notification indicated by the first subscription command, and returns the obtained test notification to the script execution module;

The script execution module sends an unsubscribe command to the notification receiving module.
The method for testing a northbound interface according to claim 8,

Before the script execution module executes the script use case in the pre-developed script, the test method further includes:

The initialization module initialization script loading module loads the pre-developed script, initializes the parameters of the command execution module and the parameters of the notification receiving module, wherein the script use case executed by the script execution module is loaded according to the script loading module Obtained by each script use case in the script, the script includes the script use case and a script method, and the script method is an execution method of the script use case;

After the initialization module initializes the parameters of the notification receiving module, the testing method further includes:

The notification receiving module continuously receives the notification sent by the server after initialization.
The method for testing a northbound interface according to claim 10, wherein

The northbound interface of the current test is a public object requesting proxy architecture CORBA interface, and the parameters of the initialization command execution module include: an initialization object requesting agent ORB;

The initializing the parameter of the notification receiving module includes: instructing, by the object management organization, an OMG standard, that the notification receiving module invokes receiving a notification sent by the server;

Before the script execution module executes the script use case in the pre-developed script, the test method further includes:

The initialization module sends a login command to the script execution module, where the login command includes a login script method;

The script execution module executes the login script method according to the login command, invokes a corresponding login request message according to the login script method, and sends an execution including the login request message to the command execution module. Login command

The command execution module performs a dynamic call of CORBA according to the received login request message, and returns an execution result to the script execution module.
The method for testing a northbound interface according to claim 10, wherein

The northbound interface of the current test is a multi-technology operating system MTOSI interface or software In the north direction of the network SDN, the initializing the parameters of the command execution module includes: initializing a uniform resource locator URL for constructing a hypertext transfer protocol HTTP request message;

The initializing the parameters of the notification receiving module includes: subscribing to an MTOSI notification;

After the initialization module initializes the parameters of the notification receiving module, the testing method further includes:

The notification receiving module sends a second subscription command to the script execution module, where the second subscription command includes a subscribed script method;

The script execution module executes the subscribed script method according to the second subscription command, invokes a corresponding subscription request message according to the subscribed script method, and sends the subscription request message to the command execution module. Execute the subscription command;

The command execution module executes an HTTP request call according to the subscription request message, and returns an execution result to the script execution module.
The test method of the northbound interface according to any one of claims 8 to 12, after the command execution module returns an execution result to the script execution module, the test method further includes:

The script execution module transmits the execution result to the result generation module;

The result generation module outputs the execution result, the execution result including all northbound interfaces that have been tested, and the number of tests and the test time of each of the northbound interfaces.
The test method of the northbound interface according to any one of claims 8 to 12, wherein the script execution module executes the script use case, comprising: the script execution module follows the order of each script use case in the script Execute sequentially; and/or,

In the process of executing the script use case by the script execution module, the test method further includes:

The script execution module sends the execution information and the abnormality information of the script use case to the recording module;

The recording module records and displays execution information and exception information of the script use case.