Message queue system test method and device, electronic equipment, medium and product
Through the adaptation plug-in, unified configuration management and automation adaptation of multiple test tools, the problem of users needing to learn a variety of test tools is solved, and the efficiency of message queue system testing and maintenance simplicity is improved.
Patent Information
- Application Number
- CN202410989370.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-23
- Publication Date
- 2024-11-22
AI Technical Summary
In message queue system testing, users need to learn and adapt to unfamiliar testing tools, resulting in increased learning costs and affecting testing efficiency.
Provide a message queue system testing method, which realizes unified configuration management through adaptation plug-ins, and automatically adapts to a variety of performance testing tools to simplify user operations and reduces learning costs and difficulty in use. The method includes obtaining configuration parameters entered by the user, building system interaction code, and executing test data to generate test results.
Simplify user operations, reduce learning costs and difficulty in use, improve testing efficiency, ensure smooth progress of testing, and simplify maintenance and development work through high scalability and reusability.
Smart Images

Figure CN119003335A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the technical field of performance testing, and in particular to a message queue system testing method, device, electronic device, medium and product. Background Art
[0002] A message queue system is a middleware used to asynchronously transfer data between different applications or services. It allows applications to send messages to a queue without having to wait for the recipient to process the messages immediately, thereby improving the efficiency and scalability of the system. In order to ensure that the message queue system can withstand the expected load in actual applications, and to promptly discover and resolve potential performance issues, thereby ensuring efficient operation and long-term stability of the system, performance testing tools are generally used to test the message queue system.
[0003] In actual testing scenarios, due to some objective reasons, such as project-specific requirements, tool advantages, customer or partner requirements, etc., users may need to choose unfamiliar testing tools for testing. Therefore, users need to learn and adapt to the use of new testing tools, which increases the learning cost and has a certain impact on the testing efficiency of the message queue system. Therefore, it is urgent to solve this technical problem. Summary of the invention
[0004] In view of the above situation, the embodiments of the present disclosure provide a message queue system testing method, device, electronic device, medium and product, which are intended to solve the above problems or at least partially solve the above problems.
[0005] In a first aspect, an embodiment of the present disclosure provides a message queue system testing method, the method is implemented based on an adapter plug-in, the adapter plug-in includes configuration classes corresponding to a plurality of test tools, the configuration class is used to encapsulate the following configuration parameters: the IP address and listening port number of the message queue system to be tested, the name of the message acquisition queue, and the name of the message sending queue; the method includes:
[0006] Using the target configuration class corresponding to the current test tool, obtain multiple configuration parameters input by the user;
[0007] Based on the multiple configuration parameters, construct a system interaction code, wherein the system interaction code is used to implement interaction with the message queue system to be detected;
[0008] Based on the multiple configuration parameters and the system interaction code, test data to be executed is constructed; the test data to be executed is executed to generate a test result for the message queue system to be tested, wherein the test data to be executed includes all configuration information and logic instructions required for the test.
[0009] In a second aspect, the embodiment of the present disclosure further provides a message queue system testing device, the device is implemented based on an adapter plug-in, the adapter plug-in includes configuration classes corresponding to a plurality of test tools, the configuration class is used to encapsulate the following configuration parameters: the IP address and listening port number of the message queue system to be tested, the name of the message acquisition queue, and the name of the message sending queue;
[0010] The device comprises:
[0011] The acquisition module is used to obtain multiple configuration parameters input by the user using the target configuration class corresponding to the current test tool;
[0012] A construction module, used to construct a system interaction code based on the multiple configuration parameters, wherein the system interaction code is used to implement interaction with the message queue system to be detected;
[0013] The test module is used to construct the test data to be executed based on the multiple configuration parameters and the system interaction code; execute the test data to be executed to generate a test result for the message queue system to be tested, wherein the test data to be executed contains all the configuration information and logic instructions required for the test.
[0014] In a third aspect, an embodiment of the present disclosure further provides an electronic device, comprising: a processor; and a memory arranged to store computer executable instructions, wherein when the executable instructions are executed, the processor executes the steps of the above-mentioned message queue system testing method.
[0015] In a fourth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium, which stores one or more programs. When the one or more programs are executed by an electronic device including multiple applications, the electronic device executes the steps of the above-mentioned message queue system testing method.
[0016] In a fifth aspect, an optional implementation of the present disclosure further provides a computer program product, wherein the computer program product carries a program code, and the program code includes instructions that can be used to execute the steps of the above-mentioned message queue system testing method.
[0017] By means of the above technical scheme, the message queue system testing method, device, electronic device, medium and product provided by the embodiment of the present disclosure, the method provides an adapter plug-in, the adapter plug-in includes configuration classes corresponding to a plurality of test tools, and the configuration class is used to encapsulate the following configuration parameters: the IP address and listening port number of the message queue system to be tested, the name of the message acquisition queue, and the name of the message sending queue. During implementation, the target configuration class corresponding to the current test tool can be used to obtain a plurality of configuration parameters input by the user; based on the plurality of configuration parameters, a system interaction code for interacting with the message queue system to be detected is constructed; finally, based on the plurality of configuration parameters and the system interaction code, the test data to be executed is constructed, and the test data to be executed is executed to generate the test results for the message queue system to be tested. It can be seen that the embodiment of the present disclosure provides a set of standardized configuration schemes for parameters, which can uniformly configure and manage the configuration parameters, automatically adapt to a variety of performance testing tools, greatly simplify the user operation, reduce the user's learning cost and difficulty of use, improve the test efficiency, and ultimately ensure the smooth progress of the test work. At the same time, the code design is highly scalable and reusable. The new test tool support only requires the implementation of the tool configuration class and can be quickly integrated into the adapter plug-in; the unified architecture design makes maintenance easier, and any improvements and fixes can be made in one code base, reducing the workload of development and maintenance.
[0018] The above description is only an overview of the technical solution of the present disclosure. In order to more clearly understand the technical means of the present disclosure, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present disclosure more obvious and easy to understand, the specific implementation methods of the present disclosure are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The drawings described herein are used to provide a further understanding of the present disclosure and constitute a part of the present disclosure. The illustrative embodiments of the present disclosure and their descriptions are used to explain the present disclosure and do not constitute an improper limitation on the present disclosure. In the drawings:
[0020] Figure 1 A schematic diagram of a process flow of a message queue system testing method provided by an embodiment of the present disclosure is shown;
[0021] Figure 2 A schematic diagram showing the structure of a message queue system testing device provided by an embodiment of the present disclosure is shown;
[0022] Figure 3 A schematic structural diagram of an electronic device provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION
[0023] In order to make the purpose, technical solutions and advantages of the present disclosure clearer, the technical solutions of the present disclosure will be clearly and completely described below in combination with the specific embodiments of the present disclosure and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present disclosure.
[0024] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.
[0025] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that such usage is interchangeable where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. In addition, the term "including" and its variants are to be interpreted as open-ended terms meaning "including but not limited to".
[0026] As mentioned above, in actual testing scenarios, due to some objective reasons, such as project-specific requirements, tool advantages, customer or partner requirements, etc., users may need to choose unfamiliar testing tools for testing. Therefore, users need to learn and adapt to the use of new testing tools, which increases the user's learning cost and has a certain impact on the testing efficiency of the message queue system. Based on this, the present invention proposes a message queue system testing method, device, electronic device, medium and product, and the present disclosure is described in detail through specific embodiments below.
[0027] To facilitate understanding of this embodiment, a message queue system testing method disclosed in the embodiment of the present disclosure is first introduced in detail. The execution subject of the message queue system testing method provided in the embodiment of the present disclosure is generally a computer device with certain computing capabilities, and the computer device includes, for example: a terminal device or a server or other processing device, and the terminal device can be a user equipment (User Equipment, UE), a mobile device, a user terminal, a terminal, a personal digital assistant (Personal Digital Assistant, PDA), etc. In some possible implementations, the message queue system testing method can be implemented by a processor calling a computer-readable instruction stored in a memory.
[0028] Figure 1 A schematic diagram of the process flow of the message queue system testing method provided by the embodiment of the present disclosure is shown. Figure 1It can be seen that the embodiment of the present disclosure at least includes steps S101 to S103:
[0029] Step S101: using the target configuration class corresponding to the current test tool, obtaining multiple configuration parameters input by the user.
[0030] This method is implemented based on an adapter plug-in, which includes configuration classes corresponding to multiple test tools. The configuration class is used to encapsulate the following configuration parameters: the IP address and listening port number of the message queue system to be tested, the name of the message acquisition queue, and the name of the message sending queue.
[0031] Step S102: constructing a system interaction code based on the multiple configuration parameters, wherein the system interaction code is used to implement interaction with the message queue system to be detected.
[0032] Step S103: constructing test data to be executed based on the multiple configuration parameters and the system interaction code; executing the test data to be executed to generate a test result for the message queue system to be tested, wherein the test data to be executed includes all configuration information and logic instructions required for the test.
[0033] After research, it was found that when using different performance testing tools to test various message queues, different JAR packages or plug-ins are used. Different JAR packages or plug-ins have independent parameter configuration schemes, and users need to spend a lot of learning costs to adapt to the configuration method of the test tool. Figure 1 It can be seen from the method shown that the embodiment of the present disclosure provides an adapter plug-in, which includes configuration classes corresponding to a variety of test tools, and the configuration class is used to encapsulate the following configuration parameters: the IP address and listening port number of the message queue system to be tested, the name of the message acquisition queue, and the name of the message sending queue. During implementation, the target configuration class corresponding to the current test tool can be used to obtain multiple configuration parameters input by the user; based on the multiple configuration parameters, a system interaction code for interacting with the message queue system to be detected is constructed; finally, based on the multiple configuration parameters and the system interaction code, the test data to be executed is constructed, and the test data to be executed is executed to generate test results for the message queue system to be tested. It can be seen that the embodiment of the present disclosure provides a set of standardized configuration schemes for parameters, which can uniformly configure and manage the configuration parameters, automatically adapt to a variety of performance testing tools, greatly simplify user operations, reduce the user's learning cost and difficulty of use, improve test efficiency, and ultimately ensure the smooth progress of the test work. At the same time, the code design is highly scalable and reusable. The new test tool support only requires the implementation of the tool configuration class and can be quickly integrated into the adapter plug-in; the unified architecture design makes maintenance easier, and any improvements and fixes can be made in one code base, reducing the workload of development and maintenance.
[0034] The above S101-S104 are described in detail below.
[0035] Regarding S101 above:
[0036] Here, in a possible implementation, the multiple test tools include at least two of the following: LoadRunner, Gatling, JMeter, Neoload. During implementation, the test tool is a tool that can test the message queue system, which is not limited in the embodiments of the present disclosure. For example, the test tool can also be K6, etc.
[0037] The adapter plug-in includes several configuration classes corresponding to various test tools. For the several configuration classes provided by the adapter plug-in for each test tool, the following configuration parameters are encapsulated: the IP address and listening port number of the message queue system to be tested, the name of the message acquisition queue, and the name of the message sending queue. During implementation, configuration parameters such as user name, password, channel name, etc. can also be encapsulated. This is not limited in the embodiments of the present disclosure and can be set according to actual needs.
[0038] It should be noted that the written adaptation plug-in can be compiled and packaged into a jar package, and the jar package can be placed in the corresponding path of the current test tool. After the test tool is started, it will be loaded into the memory. Users can import the contents of the jar package in the tool and use it.
[0039] During implementation, the user can input the configuration parameters limited by the configuration class of the adapter plug-in through methods such as a command line terminal, a graphical user interface, a configuration file, a script, etc. Based on this, the execution subject of this embodiment can receive the user's parameter input operation and then extract multiple configuration parameters.
[0040] Specifically, in a possible implementation, if the current test tool is LoadRunner or Gatling, the target configuration class corresponding to the current test tool is used to obtain multiple configuration parameters input by the user, including: instantiating the target configuration class to obtain a target configuration object; calling a parameter configuration method in the target configuration class to store the multiple configuration parameters input by the user in corresponding positions in the target configuration object.
[0041] In specific implementation, for example, the current test tool is the LoadRunner test tool, and the target configuration class corresponding to the LoadRunner test tool is the MQLRConfig class. After starting LoadRunner, the user can create a test script on LoadRunner, instantiate the MQLRConfig class in the test script, and obtain the target configuration object. The configuration parameters in the target configuration object can be default values; then, call the parameter configuration method defined in the MQLRConfig class, and replace the default values of the corresponding positions in the target configuration object with the input multiple configuration parameters, thereby realizing the acquisition of configuration parameters.
[0042] For another example, the current test tool is the Gatling test tool, and the target configuration class corresponding to the Gatling test tool is the MQGatlingConfig class. After starting Gatling, users can create a Gatling project on Gatling and write a Gatling test script. The MQGatlingConfig class can be instantiated in the Gatling script to obtain the target configuration object, in which the configuration parameters can be default values. Then, the parameter configuration method defined in the MQGatlingConfig class is called to replace the default values of the corresponding positions in the target configuration object with the input multiple configuration parameters, thereby obtaining the configuration parameters. It should be noted that before instantiating the target configuration class, the target configuration class can be imported first. If the target configuration class depends on other classes or components to perform its functions, the classes or components on which it depends are imported.
[0043] In a possible implementation, if the current test tool is JMeter, the adapter plug-in further includes a sampler class, and the sampler class inherits the AbstractSampler abstract class of JMeter, and is used to implement the interaction logic with the message queue system to be tested;
[0044] The target configuration class includes a first implementation class and a second implementation class, the first implementation class inherits JMeter's AbstractSamplerGui abstract class; the second implementation class inherits JMeter's AbstractConfigGui abstract class; the use of the target configuration class corresponding to the current test tool to obtain multiple configuration parameters input by the user includes: receiving multiple input configuration parameters through the graphical user interface provided by the target configuration class.
[0045] In this embodiment, the sampler class is used to implement the interaction logic with the message queue system to be tested. The first implementation class and the second implementation class are used to provide a graphical user interface to receive configuration parameters input by the user. It can be understood that some methods are defined in the sampler class, such as a method for sending messages, a method for receiving messages, a method for creating connections, a method for closing connections, etc. The first implementation class also defines some methods, such as createTestElement(), which is used to create a sampler instance; modifyTestElement(), which is used to modify an existing sampler instance; configure(): used to configure GUI components, such as text boxes, drop-down menus, etc. The second implementation class also defines some methods, such as createTestElement(), which is used to create a configuration element instance; modifyTestElement(), which is used to modify an existing configuration element instance; configure(): used to configure GUI components.
[0046] In specific implementation, after starting JMeter, the user can create a test plan on JMeter and add a thread group to the test plan to set the number of concurrent users and execution logic. Then, add the sampler provided by the sampler class in this embodiment to the thread group. The target configuration class provides a parameter configuration interface for the sampler, and the user can input configuration parameters on the graphical user interface presented by the target configuration class. Based on this, this embodiment can use the graphical user interface to receive the user's parameter input operation, and then extract multiple configuration parameters in the parameter input operation.
[0047] In a possible implementation, if the current test tool is Neoload, the target configuration class implements the com.neotys.extensions.action.Action interface; the use of the target configuration class corresponding to the current test tool to obtain multiple configuration parameters input by the user includes: receiving multiple input configuration parameters through a graphical user interface provided by the target configuration class.
[0048] In this embodiment, it is understandable that several methods are also defined in the target configuration class, such as methods for configuring GUI components, etc. Exemplarily, after starting Neoload, the user can create a new project on Neoload, add the adapter plug-in in Advanced actions of the project, and the target configuration class in the adapter plug-in provides a parameter configuration interface. The user can input configuration parameters on the graphical user interface presented by the target configuration class. Based on this, this embodiment can use the graphical user interface to receive the user's parameter input operation, and then extract multiple configuration parameters in the parameter input operation.
[0049] Regarding S102 above:
[0050] After obtaining multiple configuration parameters, system interaction codes for interacting with the message queue system to be detected can be constructed based on the multiple configuration parameters. When constructing the system interaction code, specifically, when writing the logic of creating / closing a connection and sending / receiving a message, the multiple configuration parameters are referenced.
[0051] In actual application scenarios, different JAR packages or plug-ins are used when testing various message queue systems using different performance testing tools. Specifically, for example, when using LoadRunner and Gatling to test the IBM MQ message queue system, the support of com.ibm.mq.allclient.jar (a Java client library provided by IBM MQ, used to interact with IBM MQ message queues in Java applications) is required; when using JMeter to test the IBM MQ message queue system, the support of the IBM MQ Support plug-in is required; when using Neoload to test the IBM MQ message queue system, the support of advanced-action-ibm.jar (a plug-in of the Neoload performance testing tool, specially designed for testing the IBM MQ message queue system) is required. When using LoadRunner and Gatling to test the ActiveMQ message queue system, you need the support of activemq-all.jar (a client library of Apache ActiveMQ, which contains all the classes and resources required to interact with the ActiveMQ message queue system); when using JMeter to test the ActiveMQ message queue system, you need the support of the JMS plug-in; when using Neoload to test the ActiveMQ message queue system, you need the support of advanced-action-jms.jar (a plug-in of Neoload, which provides support for Java Message Service, allowing Neoload to interact with the message queue system using the JMS protocol). When using LoadRunner and Gatling to test the RabbitMQ message queue system, you need the support of amqp-client.jar (Java client library of RabbitMQ, which implements the AMQP 0-9-1 protocol and allows Java applications to communicate with RabbitMQ servers); when using JMeter to test the RabbitMQ message queue system, you need the support of the AMQP plug-in.
[0052] Therefore, users need to import, configure, and use them separately. Based on this, in a possible implementation of the present disclosure, the adapter plug-in also includes an abstract class and functional classes corresponding to multiple test tools; the abstract class is inherited by multiple subclasses, and the multiple subclasses are used to implement the function of interacting with multiple types of message queue systems, and the subclass defines at least one of the following methods: create connection method, send message method, receive message method, and close connection method; the functional class is used to implement the interactive function with the message queue system to be tested, including methods in the multiple subclasses; based on the multiple configuration parameters, the system interaction code is constructed, including: obtaining the system type of the message queue system to be tested; instantiating the target functional class corresponding to the current test tool, and constructing the system interaction code based on the method corresponding to the system type in the target functional class.
[0053] In this embodiment, multiple abstract methods for interacting with the message queue system are defined in the abstract class. Exemplarily, the abstract class can be created as follows:
[0054] public abstract class MessageQueue{
[0055] protected abstract void createConnection(String mqType,Map<String,Object> params);
[0056] protected abstract void sendMessage(String queueName,Object message);
[0057] protected abstract Object receiveMessage(String queueName);
[0058] protected abstract void closeConnection();
[0059] }
[0060] For each message queue type, a corresponding subclass can be created to implement the abstract method in the abstract class. In a possible implementation, the multiple types of message queue systems include at least two of the following: IBMMQ, ActiveMQ, and RabbitMQ.
[0061] During implementation, the adapter plug-in may also provide subclasses that support the following types of message queue systems: Kafka, RocketMQ, ZeroMQ, etc., which are not limited in the embodiments of the present disclosure. For example, multiple types of message queue systems include IBMMQ, ActiveMQ, and RabbitMQ, and subclasses IBMMessageQueue, ActiveMQMessageQueue, and RabbitMQMessageQueue may be created respectively. For example, the subclass IBMMessageQueue may be created according to the following method:
[0062] public class IBMMessageQueue extends MessageQueue{
[0063] @Override
[0064] public void createConnection(){
[0065] / / Use the IBM MQ API to set connection parameters, create and connect to MQQueueManager, and open the send and receive queues.
[0066] System.out.println("IBM MQ connection created");
[0067] }
[0068] @Override
[0069] public void sendMessage(String message){
[0070] / / Use the IBM MQ API to create and configure an IBMMQMessage instance and send the message to the specified queue
[0071] System.out.println("IBM MQ sends message: "+message);
[0072] }
[0073] @Override
[0074] public String receiveMessage(){
[0075] / / Use the IBM MQ API to create and configure an MQMessage instance, get the message from the receiving queue, and return the message content;
[0076] String receivedMessage = "Message received from IBM MQ";
[0077] System.out.println("IBM MQ received message: "+receivedMessage);
[0078] return receivedMessage;
[0079] }
[0080] @Override
[0081] public void closeConnection(){
[0082] / / Use IBM MQ API to close the send and receive queues and disconnect from MQQueueManager
[0083] System.out.println("IBM MQ connection closed");
[0084] }
[0085] }
[0086] Similarly, you can create subclasses of ActiveMQMessageQueue and RabbitMQMessage Queue. When creating a subclass of ActiveMQMessageQueue, you can use the Java API of ActiveMQ to set connection parameters, create and connect to the Connection; create a session, send queue, and receive queue; create a TextMessage and send the message to the specified queue; create a TextMessage, get the message from the receive queue, and return the message content; close the queue, session, and connection. When creating a subclass of RabbitMQMessageQueue, you can use the Java API of RabbitMQ to set connection parameters, create and connect to the Connection and Channel, declare the send queue and receive queue; convert the message to a byte array and send it to the specified queue to implement the message sending function; use the basicGet method to receive the message and return the message content; close the Channel and Connection.
[0087] During implementation, for example, the configuration parameter of the system type of the message queue system can be encapsulated in the configuration class, and the system type of the message queue system to be tested input by the user can be obtained by using the target configuration class corresponding to the current test tool. After obtaining the system type of the message queue system to be tested, the target function class corresponding to the current test tool can be instantiated, and the method corresponding to the system type in the target function class can be called to build the system interaction code. For example, if the system type of the message queue system to be tested is IBM MQ, the system interaction code can be built by instantiating the target function class and calling the method in the subclass IBMMessageQueue in the target function class.
[0088] In this embodiment, the adapter plug-in also includes an abstract class and functional classes corresponding to various test tools. Among them, the abstract class is inherited by multiple subclasses, and the multiple subclasses are used to implement the function of interacting with various types of message queue systems. The subclass defines at least one of the following methods: creating a connection method, sending a message method, receiving a message method, and closing a connection method; the functional class is used to implement the interactive function with the message queue system to be tested, and contains the methods in the multiple subclasses, that is, the adapter plug-in has been configured with different performance testing tools to test various message queue systems. Different JAR packages or plug-ins are required. During implementation, the target functional class corresponding to the current test tool can be instantiated, and the system interaction code is constructed based on the method corresponding to the system type of the message queue system to be tested in the target functional class. It can be seen that the adapter plug-in provided in the embodiment of the present disclosure can automatically adapt to multiple message queue types. Users only need this plug-in to configure and use multiple message queue systems, which greatly simplifies the management and use complexity of message queue types. At the same time, the code design is highly scalable and reusable. The new message queue system supports rapid integration into adapter plug-ins by simply creating response subclasses. The unified architecture design makes maintenance easier, and any improvements and fixes can be made in one code base, reducing the workload of development and maintenance.
[0089] In actual application scenarios, there may be a situation where the user does not input the system type of the message queue system to be detected. Based on this, in a possible implementation of the present disclosure, the obtaining of the system type of the message queue system to be detected includes: for any target system in the multiple types of message queue systems that has not attempted to establish a connection, using the multiple configuration parameters, calling the creation connection method corresponding to the system type of the target system in the target function class, establishing a connection with the target system, and obtaining a connection result; if the connection result is a successful connection, calling the disconnection method corresponding to the system type of the target system in the target function class, disconnecting the target system, and determining the system type of the target system as the system type of the message queue system to be tested; if the connection result is a connection failure, returning to the step of calling the creation connection method corresponding to the system type of the target system in the target function class for any target system in the multiple types of message queue systems that has not attempted to establish a connection, using the multiple configuration parameters, establishing a connection with the target system, and obtaining a connection result, until there is no system in the multiple types of message queue systems that has not attempted to establish a connection; if each of the connection results is a connection failure, returning an error message.
[0090] It can be seen that this embodiment can automatically identify the system type of the message queue system to be tested when the user does not input the system type.
[0091] Regarding S103 above:
[0092] In this step, the test data to be executed contains all the configuration information and logic instructions required for the test. After being processed by the test tool, the test data to be executed is converted into actual test activities, so that the performance of the message queue system can be evaluated.
[0093] During implementation, if the current test tool is a Gatling test tool, after creating a Gatling project and writing a Gatling script to obtain multiple configuration parameters and system interaction codes, the test data to be executed can be obtained.
[0094] In a possible implementation, if the current test tool is the LoadRunner, constructing the test data to be executed based on the multiple configuration parameters and the system interaction code includes: generating a test script according to the multiple configuration parameters and the system interaction code; setting a test scenario, and generating the test data to be executed according to the set test scenario and the test script.
[0095] If the current test tool is LoadRunner, then in this embodiment, a test script can be written, and the script contains multiple configuration parameters and system interaction codes. After the script is written, the script is integrated into the Controller of LoadRunner, and the test scenario is set in the Controller, such as the number of concurrent users, test duration, thinking time, etc., so as to generate test data to be executed.
[0096] In a possible implementation, if the current testing tool is the JMeter, constructing the test data to be executed based on the multiple configuration parameters and the system interaction code includes: replacing the sampler class with a target sampler class, wherein the target sampler class contains the system interaction code for implementing interaction with the message queue system to be tested; generating the test data to be executed based on the multiple configuration parameters, the target sampler class, and the added listener.
[0097] If the current test tool is JMeter, then in this embodiment, the sampler supported by the target sampler class containing the system interaction code can be used to replace the sampler supported by the aforementioned sampler class. The samplers supported by the target sampler class, the obtained configuration parameters and the added listeners together constitute the test data to be executed, that is, the test plan configured in JMeter. During implementation, components such as assertions can also be added as needed, which is not limited in the embodiment of the present disclosure.
[0098] In a possible implementation, if the current test tool is NeoLoad, the adaptation plug-in also includes an action engine class, the action engine class includes the system interaction code, and the action engine class implements the com.neotys.extensions.action.engine.ActionEngine interface; the construction of the test data to be executed based on the multiple configuration parameters and the system interaction code includes: setting a test scenario, and generating the test data to be executed based on the test scenario, the multiple configuration parameters, and the action engine class.
[0099] If the current test tool is NeoLoad, then in this embodiment, the adapter plug-in in Advancedactions added to the Neoload project provides an action engine class containing the system interaction code. The action engine class implements the com.neotys.extensions.action.engine.ActionEngine interface, and can be recognized by the tool. During implementation, you can set test scenarios, such as the number of concurrent users, pressure increase method, test duration, etc. Finally, the set test scenarios, multiple configuration parameters, and the interaction logic provided by the action engine class constitute the test data to be executed.
[0100] The present disclosure also provides a message queue system testing method, comprising the following steps:
[0101] First of all, it should be noted that this embodiment is implemented based on an adapter plug-in. The adapter plug-in includes configuration classes corresponding to the LoadRunner, Gatling, JMeter, and Neoload test tools, respectively. The configuration class is used to encapsulate the following configuration parameters: the IP address and listening port number of the message queue system to be tested, the name of the message acquisition queue, and the name of the message sending queue. The adapter plug-in also includes an abstract class and functional classes corresponding to each test tool; the abstract class is inherited by multiple subclasses, and the multiple subclasses are used to implement the function of interacting with three types of message queue systems: IBM MQ, ActiveMQ, and RabbitMQ. Each subclass defines: creating a connection method, sending a message method, receiving a message method, and closing a connection method; the functional class is used to implement the interactive function with the message queue system to be tested, and contains methods in multiple subclasses.
[0102] Step S1: using the target configuration class corresponding to the current test tool, obtaining multiple configuration parameters input by the user.
[0103] In specific implementation, if the current test tool is LoadRunner or Gatling, the target configuration class corresponding to the current test tool is used to obtain multiple configuration parameters input by the user, including: instantiating the target configuration class to obtain a target configuration object; calling the parameter configuration method in the target configuration class to store the multiple configuration parameters input by the user in the corresponding positions in the target configuration object.
[0104] If the current test tool is JMeter, the adapter plug-in also includes a sampler class, which inherits JMeter's AbstractSampler abstract class and is used to implement the interaction logic with the message queue system to be tested; the target configuration class includes a first implementation class and a second implementation class, the first implementation class inherits JMeter's AbstractSamplerGui abstract class; the second implementation class inherits JMeter's AbstractConfigGui abstract class; using the target configuration class corresponding to the current test tool, obtain multiple configuration parameters input by the user, including: receiving multiple input configuration parameters through the graphical user interface provided by the target configuration class.
[0105] If the current test tool is Neoload, the target configuration class implements the com.neotys.extensions.action.Action interface; using the target configuration class corresponding to the current test tool, multiple configuration parameters input by the user are obtained, including: receiving multiple input configuration parameters through a graphical user interface provided by the target configuration class.
[0106] Step S2: Obtain the system type of the message queue system to be detected.
[0107] During implementation, the system type of the message queue system to be tested is obtained, which specifically includes the following steps: for any target system in the multiple types of message queue systems that has not attempted to establish a connection, using multiple configuration parameters, calling the create connection method corresponding to the system type of the target system in the target function class, establishing a connection with the target system, and obtaining a connection result; if the connection result is a successful connection, calling the disconnection method corresponding to the system type of the target system in the target function class, disconnecting the target system, and determining the system type of the target system as the system type of the message queue system to be tested; if the connection result is a connection failure, returning to the step of calling the create connection method corresponding to the system type of the target system in the target function class, establishing a connection with the target system, and obtaining a connection result for any target system in the multiple types of message queue systems that has not attempted to establish a connection, using multiple configuration parameters, until there is no system in the multiple types of message queue systems that has not attempted to establish a connection; if the connection results are all connection failures, returning an error message.
[0108] Step S3: Instantiate the target function class corresponding to the current test tool, and construct the system interaction code based on the method corresponding to the system type in the target function class, wherein the system interaction code is used to implement the interaction with the message queue system to be tested.
[0109] Step S4: Based on multiple configuration parameters and system interaction codes, construct the test data to be executed; execute the test data to be executed to generate test results for the message queue system to be tested. The test data to be executed includes all the configuration information and logic instructions required for the test.
[0110] Specifically, if the current test tool is LoadRunner, the test data to be executed is constructed based on multiple configuration parameters and system interaction codes, including: generating a test script according to the multiple configuration parameters and system interaction codes; setting a test scenario, and generating the test data to be executed according to the set test scenario and test script.
[0111] If the current test tool is JMeter, the test data to be executed is constructed based on multiple configuration parameters and system interaction codes, including: replacing the sampler class with the target sampler class, wherein the target sampler class contains the system interaction code for realizing the interaction with the message queue system to be tested; based on multiple configuration parameters, the target sampler class, and the added listener, the test data to be executed is generated.
[0112] If the current test tool is NeoLoad, the adapter plug-in also includes an action engine class, which contains system interaction code and implements the com.neotys.extensions.action.engine.Action Engine interface. Based on multiple configuration parameters and system interaction code, the test data to be executed is constructed, including: setting a test scenario, and generating the test data to be executed based on the test scenario, multiple configuration parameters, and the action engine class.
[0113] It can be seen that the disclosed embodiment can automatically adapt four stress testing tools, namely LoadRunner, JMeter, Gatling and Neoload, through configuration classes, function classes, sampler classes and action engine classes, and also provides a standardized configuration scheme for parameters. This simplifies user operations and greatly reduces the user's learning cost and difficulty of use. Users only need this plug-in to conveniently use different stress testing tools, which simplifies the complexity of managing and using stress testing tools. It allows users to focus on the test itself, rather than tool and plug-in management. It also automatically adapts three message queue types, namely IBM MQ, ActiveMQ and RabbitMQ, through a unified abstract class. Users only need this plug-in to configure and use a variety of message queue systems, which greatly simplifies the management and use complexity of message queue types. At the same time, the code design is highly scalable and reusable. New test tool support and message queue system support only need to inherit or implement the support class or interface of the tool and implement the various functions of the message queue, and can be quickly integrated into the adaptation plug-in. The unified architecture design makes maintenance easier, and any improvements and repairs can be made in a code base, reducing the workload of development and maintenance.
[0114] Those skilled in the art will appreciate that, in the above method of the specific implementation manner, the writing order of the steps does not mean a strict execution order, but does not constitute any limitation on the implementation process. The specific execution order of the steps should be determined by their functions and possible internal logic.
[0115] It should be noted that, in practical applications, all possible implementations described above can be combined in any manner to form possible embodiments of the present disclosure, which will not be described one by one here.
[0116] Based on the same concept, the embodiment of the present disclosure also provides a message queue system testing device, Figure 2 A schematic diagram of the structure of the message queue system testing device provided by the embodiment of the present disclosure is shown. Figure 2 As shown, the message queue system testing device 200 provided in the embodiment of the present disclosure is implemented based on an adapter plug-in, and the adapter plug-in includes configuration classes corresponding to a plurality of test tools, respectively, and the configuration class is used to encapsulate the following configuration parameters: the IP address and listening port number of the message queue system to be tested, the name of the message acquisition queue, and the name of the message sending queue; the device includes:
[0117] The acquisition module 201 is used to acquire multiple configuration parameters input by the user using the target configuration class corresponding to the current test tool;
[0118] A construction module 202 is used to construct a system interaction code based on the multiple configuration parameters, wherein the system interaction code is used to implement interaction with the message queue system to be detected;
[0119] The test module 203 is used to construct the test data to be executed based on the multiple configuration parameters and the system interaction code; execute the test data to be executed to generate a test result for the message queue system to be tested, wherein the test data to be executed includes all the configuration information and logic instructions required for the test.
[0120] In a possible implementation, in the above device, the multiple testing tools include at least two of the following: LoadRunner, Gatling, JMeter, and Neoload.
[0121] In a possible implementation, in the above-mentioned device, if the current test tool is the LoadRunner or the Gatling, the acquisition module 201 is used to: instantiate the target configuration class to obtain a target configuration object; call the parameter configuration method in the target configuration class to store multiple configuration parameters entered by the user in corresponding positions in the target configuration object.
[0122] In a possible implementation, in the above-mentioned device, if the current test tool is JMeter, the adapter plug-in also includes a sampler class, and the sampler class inherits the AbstractSampler abstract class of JMeter, and is used to implement the interaction logic with the message queue system to be tested; the target configuration class includes a first implementation class and a second implementation class, and the first implementation class inherits the AbstractSamplerGui abstract class of JMeter; the second implementation class inherits the AbstractConfigGui abstract class of JMeter; the acquisition module 201 is used to: receive multiple configuration parameters input through the graphical user interface provided by the target configuration class.
[0123] In a possible implementation, in the above-mentioned device, if the current test tool is Neoload, the target configuration class implements the com.neotys.extensions.action.Action interface; the acquisition module 201 is used to: receive multiple input configuration parameters through the graphical user interface provided by the target configuration class.
[0124] In a possible implementation, in the above-mentioned device, the adapter plug-in also includes an abstract class and functional classes corresponding to multiple test tools respectively; the abstract class is inherited by multiple subclasses, and the multiple subclasses are used to implement the function of interacting with multiple types of message queue systems, and the subclass defines at least one of the following methods: creating a connection method, sending a message method, receiving a message method, and closing a connection method; the functional class is used to implement the interaction function with the message queue system to be tested, and includes the methods in the multiple subclasses; the construction module 202 is used to: obtain the system type of the message queue system to be tested; instantiate the target functional class corresponding to the current test tool, and construct the system interaction code based on the method in the target functional class corresponding to the system type.
[0125] In a possible implementation, in the above device, the multiple types of message queue systems include at least two of the following: IBM MQ, ActiveMQ, and RabbitMQ.
[0126] In a possible implementation, in the above-mentioned device, the construction module 202 is used to: for any target system in the multiple types of message queue systems that has not attempted to establish a connection, use the multiple configuration parameters to call the creation connection method corresponding to the system type of the target system in the target function class, establish a connection with the target system, and obtain a connection result; if the connection result is a successful connection, call the disconnection method corresponding to the system type of the target system in the target function class to disconnect the target system, and determine the system type of the target system as the system type of the message queue system to be tested; if the connection result is a connection failure, return to the step of calling the creation connection method corresponding to the system type of the target system in the target function class for any target system in the multiple types of message queue systems that has not attempted to establish a connection, establish a connection with the target system, and obtain a connection result, until there is no system in the multiple types of message queue systems that has not attempted to establish a connection; if each of the connection results is a connection failure, return an error message.
[0127] In a possible implementation, in the above-mentioned device, if the current test tool is the LoadRunner, the test module 203 is used to: generate a test script based on the multiple configuration parameters and the system interaction code; set a test scenario, and generate the test data to be executed based on the set test scenario and the test script.
[0128] In a possible implementation, in the above-mentioned device, if the current test tool is the JMeter, the test module 203 is used to: replace the sampler class with the target sampler class, wherein the target sampler class contains the system interaction code for realizing the interaction with the message queue system to be tested; and generate the test data to be executed based on the multiple configuration parameters, the target sampler class, and the added listener.
[0129] In a possible implementation, in the above-mentioned device, if the current test tool is the Neo Load, the adaptation plug-in also includes an action engine class, the action engine class contains the system interaction code, and the action engine class implements the com.neotys.extensions.action.engine.ActionEngine interface; the test module 203 is used to: set the test scenario, and generate the test data to be executed based on the test scenario, the multiple configuration parameters, and the action engine class.
[0130] It should be noted that any of the above-mentioned message queue system testing devices can implement the above-mentioned message queue system testing method one by one, which will not be repeated here.
[0131] Figure 3 FIG. 1 shows a schematic diagram of the structure of an electronic device provided by an embodiment of the present disclosure. Figure 3 As shown, at the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. Among them, the memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage, etc. Of course, the electronic device may also include hardware required for other services.
[0132] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.
[0133] The memory is used to store programs. Specifically, the program may include program code, and the program code includes computer operation instructions. The memory may include internal memory and non-volatile memory, and provides instructions and data to the processor.
[0134] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a message queue system test device at the logical level. The processor executes the program stored in the memory and is specifically used to execute the above method.
[0135] The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The disclosed methods, steps and logic block diagrams in the embodiments of the present disclosure may be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present disclosure may be directly embodied as being executed by a hardware decoding processor, or may be executed by a combination of hardware and software modules in a decoding processor. The software module may be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
[0136] The electronic device can execute the message queue system testing method provided by the embodiments of the present disclosure, and realize the message queue system testing device in Figure 3 The functions of the illustrated embodiments will not be described in detail in the embodiments of the present disclosure.
[0137] The embodiments of the present disclosure also propose a computer-readable storage medium, which stores one or more programs, and the one or more programs include instructions. When the instructions are executed by an electronic device including multiple application programs, the electronic device can execute the message queue system testing method provided by multiple embodiments of the present disclosure.
[0138] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0139] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0140] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0141] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0142] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0143] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.
[0144] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
[0145] The embodiments of the present disclosure also provide a computer program product, which carries a program code. The instructions included in the program code can be used to execute the data processing method described in the above method embodiments, or the steps of the intelligent driving control method. Please refer to the above method embodiments for details, which will not be repeated here.
[0146] The computer program product may be implemented in hardware, software or a combination thereof. In one optional embodiment, the computer program product is implemented as a computer storage medium. In another optional embodiment, the computer program product is implemented as a software product, such as a software development kit (SDK).
[0147] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity or device including the element.
[0148] It will be appreciated by those skilled in the art that the embodiments of the present disclosure may be provided as methods, systems or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0149] The above are only embodiments of the present disclosure and are not intended to limit the present disclosure. For those skilled in the art, the present disclosure may have various modifications and variations. Any modification, equivalent substitution, improvement, etc. made within the spirit and principle of the present disclosure shall be included in the scope of the claims of the present disclosure.
Claims
1. A message queue system testing method, It is characterized in that The method is implemented based on an adapter plug-in, which includes configuration classes corresponding to a variety of test tools, and the configuration class is used to encapsulate the following configuration parameters: the IP address and listening port number of the message queue system to be tested, the name of the message acquisition queue, and the name of the message sending queue; The method comprises: Using the target configuration class corresponding to the current test tool, obtain multiple configuration parameters input by the user; Based on the multiple configuration parameters, construct a system interaction code, wherein the system interaction code is used to implement interaction with the message queue system to be detected; Based on the multiple configuration parameters and the system interaction code, test data to be executed is constructed; the test data to be executed is executed to generate a test result for the message queue system to be tested, wherein the test data to be executed includes all configuration information and logic instructions required for the test.
2. The method according to claim 1, It is characterized in that The multiple testing tools include at least two of the following: LoadRunner, Gatling, JMeter, and Neoload.
3. The method according to claim 2, It is characterized in that If the current test tool is the LoadRunner or the Gatling, the target configuration class corresponding to the current test tool is used to obtain multiple configuration parameters input by the user, including: Instantiating the target configuration class to obtain a target configuration object; The parameter configuration method in the target configuration class is called to store the multiple configuration parameters input by the user in corresponding positions in the target configuration object.
4. The method according to claim 2, It is characterized in that If the current test tool is JMeter, the adapter plug-in further includes a sampler class, which inherits the AbstractSampler abstract class of JMeter and is used to implement the interaction logic with the message queue system to be tested; The target configuration class includes a first implementation class and a second implementation class, wherein the first implementation class inherits the AbstractSamplerGui abstract class of JMeter; the second implementation class inherits the AbstractConfigGui abstract class of JMeter; The target configuration class corresponding to the current test tool is used to obtain multiple configuration parameters input by the user, including: A plurality of configuration parameters are received through a graphical user interface provided by the target configuration class.
5. The method according to claim 2, It is characterized in that If the current test tool is Neoload, the target configuration class implements the com.neotys.extensions.action.Action interface; The target configuration class corresponding to the current test tool is used to obtain multiple configuration parameters input by the user, including: A plurality of configuration parameters are received through a graphical user interface provided by the target configuration class.
6. The method according to claim 4, It is characterized in that The adapter plug-in also includes an abstract class and functional classes corresponding to multiple test tools; the abstract class is inherited by multiple subclasses, and the multiple subclasses are used to implement the function of interacting with multiple types of message queue systems. The subclass defines at least one of the following methods: a connection creation method, a message sending method, a message receiving method, and a connection closing method; the functional class is used to implement the interaction function with the message queue system to be tested, and includes the methods in the multiple subclasses; The constructing the system interaction code based on the multiple configuration parameters includes: Obtaining the system type of the message queue system to be detected; Instantiate the target function class corresponding to the current test tool, and construct the system interaction code based on the method in the target function class corresponding to the system type.
7. A message queue system testing device, It is characterized in that The device is implemented based on an adapter plug-in, which includes configuration classes corresponding to a variety of test tools, respectively, and the configuration class is used to encapsulate the following configuration parameters: the IP address and listening port number of the message queue system to be tested, the name of the message acquisition queue, and the name of the message sending queue; The device comprises: The acquisition module is used to obtain multiple configuration parameters input by the user using the target configuration class corresponding to the current test tool; A construction module, used to construct a system interaction code based on the multiple configuration parameters, wherein the system interaction code is used to implement interaction with the message queue system to be detected; The test module is used to construct the test data to be executed based on the multiple configuration parameters and the system interaction code; execute the test data to be executed to generate a test result for the message queue system to be tested, wherein the test data to be executed contains all the configuration information and logic instructions required for the test.
8. An electronic device, include: processor; as well as A memory arranged to store computer executable instructions, wherein when the executable instructions are executed, the processor is caused to perform the steps of the method according to any one of claims 1 to 6.
9. A computer-readable storage medium storing one or more programs, It is characterized in that When the one or more programs are executed by an electronic device including a plurality of application programs, the electronic device executes the steps of the method as claimed in any one of claims 1 to 6.
10. A computer program product, It is characterized in that The computer program product carries a program code, and the program code includes instructions that can be used to execute the steps of any one of the methods according to claims 1 to 6.
