CN1280727C - Human-machine order testing method - Google Patents

Abstract

A man-machine command test method of the present invention utilizes at least one general-purpose computer to realize the automated test of man-machine commands, the method includes the following steps: designing the file storage format of man-machine commands to facilitate the use of application programming interfaces to obtain the target value; design the input interface of the man-machine command, enter the man-machine command through the man-machine command input interface and save it, and generate a test case; design the automated test interface and set the automated test parameters; start the target test window and connect to the system to be tested; press It is necessary to create an automated test thread to conduct automated testing of man-machine commands; disconnect the automated test system from the man-machine command network management system. The method of the invention adopts the technical concept of "separation of program and data" and "windows message forwarding" to realize automated testing, reduce testing costs, avoid duplication of labor, reduce the pressure of testing personnel, and realize the improvement of testing work The effect of efficiency and quality.

Description

A method for man-machine command testing

technical field

The invention relates to a computer software testing technology, in particular to a general man-machine command automatic testing method for embedded software.

Background technique

At present, as a unique and powerful network management method, man-machine commands must be provided by almost all embedded software systems. With the development of embedded software systems, network management of man-machine commands is inevitable. System testing, regression testing. However, for testers, system testing or regression testing again and again means doing the same or similar work. If these repeated tasks can be improved and optimized, the test efficiency and test quality will be greatly improved. Improve, and finally achieve the purpose of improving product quality. After a detailed analysis of the testing process, it can be concluded that the factors that affect the testing efficiency and testing quality are mainly reflected in the following aspects:

1. For regression testing or failure verification testing, testers always repeat many normal operations that have been performed before.

2. For stress testing, testers always implement it manually, so it is difficult to meet the requirements in terms of frequency and quantity of execution.

3. For concurrency testing, manual methods often cannot achieve synchronization, so real concurrency testing cannot be realized.

4. For the fault recurrence test, limited by the memory ability of the testers, it is always impossible to fully realize the recurrence of some faults.

5. For the hidden trouble test, due to the need for in-depth and uninterrupted testing of the system, manual testing is almost impossible in the case of limited time.

6. Regarding time utilization, although the system under test can run 24 hours a day, testers need to rest at night.

Replacing heavy manual testing with automated testing and improving testing efficiency and quality has always been the goal of man-machine command network management system testing improvement. The current commercial capture/playback test tool can record all the interactive operations between users, applications and database servers, store them in the form of test scripts, and finally play back the operations performed by all users according to the scripts, so it is often used for system testing. Regression testing and fault verification are feasible automated testing tools, such as the Robot of Rational Corporation in the United States, which is a commercial capture/playback testing tool. However, although automatic testing of man-machine command network management with the help of Robot tool reduces the workload of testers in regression testing to a certain extent and improves certain efficiency, its disadvantages are also obvious:

1. The cost of testing is high. The installation of Robot has high requirements on software and hardware resources such as computer operating system type, memory, hard disk space, etc., which is difficult for general machines, which virtually increases the cost of testing.

2. Test scripts are difficult to share. Since Robot records various interactive operations such as mouse position, key presses, etc., it includes information related to the current computer settings, therefore, the test script recorded on one machine cannot be easily executed on other machines, and it is difficult to achieve resource sharing; in addition , The test script is not universal. Whenever the test case is changed, the tester must re-record the test script or manually modify the script, which is extremely inconvenient to use.

3. Some concurrent operations are difficult to achieve. For example, the concurrency test of the man-machine command network management of the remote login type cannot be realized on the same machine even if multiple instances of Robot are run.

4. High quality requirements for testers. Since Robot adopts scripting technology, it is necessary for testers to correct the scripts entered in time when the scripts are accidentally modified, and maintain all test scripts, and mastering Robot is an important task for testers with heavy responsibilities. huge pressure.

In view of the existence of the above-mentioned defectives in the prior art, it is obvious that the prior art needs to be improved.

Contents of the invention

The purpose of the present invention is to overcome the shortcomings in the prior art described above, and provide a man-machine command test method, that is, a man-machine command automated test method based on the Windows message mechanism. This method makes it unnecessary for testers to install and master Robot software, and without writing any test scripts. They only need to edit and customize test cases on a friendly man-machine command editing interface, and choose any machine that can run the Windows operating system to run the test. The system designed by the invention and the corresponding test cases can automatically test the man-machine command network management.

Technical scheme of the present invention is as follows:

A kind of man-machine order testing method, it utilizes at least one general-purpose computer, realizes the automation test of man-machine order, and this method comprises the following steps:

a) Design the file storage format of the man-machine command, the file storage format is section/keyword/value;

b) Design the input interface of the man-machine command, enter the man-machine command through the man-machine command input interface and save it to the specified command file according to the file storage format, and finally save it to the project file as the entry parameter of the automated test;

c) Design the automated test interface, and set the automated test parameters, each automated test corresponds to a project file;

d) Start the target test window and connect to the system under test;

e) Create an automated test thread as needed to perform automated testing of man-machine commands;

f) Disconnect the automated test system from the man-machine command network management system.

The test method, wherein, the file storage format is section/keyword/value, and the section is divided into two categories, one is used to represent the number of commands in the command file, and the other is to record the actual command .

Described testing method, wherein, described step b) also comprises the following steps:

b1) Enter the man-machine command in the input interface of the man-machine command, specify the parameter name, the number of parameters, the number of operations, and the delay of the man-machine command at the same time, and realize the random number, IP address, and MAC address through the macro form Automatic generation, and support for dynamic acquisition of command parameter values;

b2) According to the storage format designed in step a), save the entered man-machine command into the specified command file. The command file name contains two parts of information: the use case name itself and the execution times information of the command file. In the command file All commands are executed once;

b3) Save the command files to be included in the form of project files.

Described test method, wherein, the described automation interface in the described step c) comprises: at least one required project file path name edit box of automation test, to Telnet network management type, also needs login user name, password, target system Edit boxes such as IP address, concurrent test number, etc., each automated test corresponds to a project file; and at least one start automated test button, pause automated test button, stop automated test button.

Described testing method, wherein, described step e) also comprises the following steps:

e1) Obtaining parameters from the automated test interface, and calling an API to start a corresponding test thread according to the obtained parameters;

e2) The test thread obtains the final man-machine command from the project file, and caches the man-machine command;

e3) The test thread preprocesses the obtained man-machine commands;

e4) The test thread converts the preprocessed man-machine command into a character message, that is, an operating system message sequence;

e5) automatically mailing the message in the converted character sequence to the target window by calling the information mailing application program interface, that is, performing an automated test;

e6) Repeat the steps after e3) until the test process is interrupted or ended.

The test method, wherein, the section used to represent the actual command in the command file, its name is the command number, and it contains two keywords at the same time, one of which is the command itself, and also includes the command Specific execution information; the second keyword is used to indicate whether the command should be executed.

A man-machine command test method of the present invention adopts the technical concept of "separation of program and data" and "Windows message forwarding" to realize automated testing. Compared with the prior art, the method of the present invention avoids the use of capturing /Playback test tools have disadvantages such as huge scripts, difficult script maintenance, and high test costs brought about by recording scripts. A good man-machine interface enables testers to flexibly create, modify, and maintain test cases. The system allows testers to choose any machine that can run the Windows operating system to run the system and test cases, which ultimately reduces the cost of testing, avoids duplication of work, reduces the pressure of testers, and improves the efficiency and quality of test work. Effect.

Brief description of the drawings

The present invention will be described in further detail below through specific embodiments and in conjunction with the accompanying drawings.

In the attached picture,

Fig. 1 is the overall flowchart diagram of a kind of man-machine order testing method of the present invention;

Fig. 2 is the man-machine command input interface design of the inventive method and the input flow diagram;

Fig. 3 is the Windows message forwarding mode flowchart of the inventive method;

Fig. 4 is the target window positioning program flowchart of the inventive method;

Fig. 5 is a flow chart of the automated test interface design and the automated test program of the method of the present invention.

Detailed ways

Below in conjunction with accompanying drawing, the embodiment of technical scheme is described in further detail:

The main core idea of the inventive method is to combine " program and data separation " and " Windows message forwarding ", and " program and data separation " idea is that man-machine command is not bound together with program: design a man-machine command entry program (interface ), edit the man-machine command through this interface, and save the man-machine command in the configuration file format——in the file storage format "section (section)/keyword (key)/value (string)" to a command file, and The automatic test program realizes that it has nothing to do with specific commands. It obtains the man-machine commands stored in the command file by accessing the command file, performs command preprocessing on the acquired man-machine commands, and converts the preprocessed The final man-machine command is converted into a corresponding character message (that is, the Windows message of the operating system) sequence, and finally, the character message sequence is mailed to the target test window by using the "Windows message forwarding" mechanism provided by the operating system. In order to achieve the purpose of automated testing.

A kind of man-machine command test method of the present invention, as shown in Figure 1, before implementing the present invention, must at first design the file storage format of man-machine command, concrete format can be " section (section)/keyword (key) /value (string)”; after designing the file storage format of the man-machine command, design the man-machine command input interface, enter the man-machine command edited by the man-machine command input interface, and save it in the command file with the file storage format ; Afterwards, design the automated test interface, and set various necessary parameters on the automated test interface, such as project file information, login parameters necessary to connect to the tested system, etc.; Test the system, obtain the target test window handle, otherwise (Telnet type network management) automatically connect according to the login parameters by the automated test program, and obtain the target test window handle; finally, according to the number of concurrent tests, create the required automated test thread, and the The parameters required for the above-mentioned automated test thread are provided by the previous steps. The automated test thread uses the information in the project file as the entry point to obtain specific man-machine commands, preprocess the man-machine commands, convert the man-machine commands into character messages and put them in Into the message queue of the system, the system completes the mailing and distribution of the messages in the message queue to the target test window, and the automated test process continues until the test end condition is met.

The following is a detailed description of the concrete steps of the method of the present invention:

The first step is to design the file storage format of man-machine commands. The man-machine command storage format adopted in the present invention is "section (section)/keyword (key)/value (string)", so that APIs such as WritePrivateProfileString and GetPrivateProfileString can be conveniently used to obtain the target value. There are two categories, one is used to indicate the total number of commands in this command file; the other is used to indicate the actual command. At this time, the section name is the command number and contains two keywords at the same time. One of the names can be Cmd, the keyword value is the command itself, it also contains the specific execution information of the command: execution times, delay, etc. Then, it is divided into sections according to the same interval symbol; the name of the second keyword can be RunFlag, which is used to indicate whether the command is to be executed.

In the second step, the man-machine command input interface is designed, and the man-machine command is entered through the input interface of the man-machine command. The purpose of designing the input interface of man-machine commands is to facilitate testers to intuitively input and edit the man-machine commands to be tested. For testers, the process of man-machine command input is the process of generating a test case.

This step may further include the following steps:

1. In addition to being able to input HMI commands, the designed HMI command input interface must also meet the following requirements: First, specify the parameter name, number of parameters, running times, and delay of the HMI command. Second, the automatic generation of random numbers, IP addresses, and MAC addresses is realized in the form of "macro". Third, it supports dynamic acquisition of command parameter values, which is especially important in associated command tests.

2. Save the entered HMI command to the specified command file according to the file storage format, first judge whether the command file exists, if it does not exist, create a new command file; if an existing command file exists, overwrite it The existing command file. The file name of the command file includes two parts of information: the test case name itself and the execution times information of the command file; the default execution times is 1, that is, all the commands in the command file must be executed at least once.

3. Save the command file to be included in the form of "project file", first judge whether the project file exists, if not, create a new project file, and overwrite the existing project file if there is an existing project file; The information in the above project file is the entry information for automated testing, the man-machine command is the content of the automated test, and the command file is introduced to classify the man-machine commands, and the entered man-machine commands are stored in a certain format in the command file. Order.

As shown in Figure 2, it is the input interface design and input flow chart of man-machine command, the input interface of described man-machine command must be designed before implementing the patent of the present invention, the designed man-machine command input interface must include the following several Factors in two aspects: first, the ability to edit simple man-machine commands without parameters; second, to edit man-machine commands with parameters; third, to be able to edit nested and associated commands, which are reflected in: static editing One man-machine command can dynamically execute multiple commands. For example, statically edit a man-machine command containing a special separation symbol - "∧" as "Command1∧Command2∧Command3", then these three man-machine commands will be executed sequentially during dynamic execution : Command1, Command2, Command3; and the associated command is reflected in the parameter value reference, the latter command can use the macro "PARAM(n)" to obtain the value of the nth parameter of the previous command, where n is the parameter number. Prerequisites for using this method: the associated command itself must be a nested command editor as described above. In order to realize nesting and association, the present invention adopts a three-stage command, that is, the front part of the command—the middle part of the command is the parameter—the rear part of the command, wherein the middle part of the command and the rear part of the command are optional, and the reference of the parameter value of the associated command is only Can appear after the command. Fourth, it can support "macro" applications, that is, when editing commands, the agreed symbols can be converted into expected values during dynamic execution, and the conversion part is completed in the command preprocessing part of the automated test thread, such as DELAY (1000) means execution After the command is delayed for 1000 milliseconds, RAND_IP automatically generates a legal IP address, and RAND_MAC automatically generates a legal MAC address. Fifth, it is possible to specify the running times and delay of man-machine commands.

After the man-machine command is entered and edited, it is saved in the command file in the storage format described in the method of the present invention, so that it can be used in automated testing, or be modified when the command file is reloaded in the future. After all man-machine commands are classified, they are stored in the form of command files, and finally saved to the project file as one of the entry parameters of the automated test thread. While the automated test procedure is in progress, the HMI commands are accessed in the opposite direction.

As shown in Figure 3 is the pattern diagram of Windows message forwarding in the inventive method, and message forwarding is to realize one of core technology of the present invention, and automated test system of the present invention is a Windows application program in essence, for this reason, must fully grasp The principle of Windows message mechanism.

Windows is an object-oriented architecture. The Windows environment and applications interact through messages, and the system maintains one or more message queues. All messages generated by applications will be put or inserted into the queues. Then the system will automatically distribute the messages in the queue to the message loop of the application program, that is, take out each message from the message queue, and send the message to the message loop of the program corresponding to the window according to the receiving handle of the message. Each running program has its own message loop, in which it gets its own message and calls the corresponding window procedure function according to the handle of the receiving window. The message loop returns control to the system when there is no message.

The structure (MSG) of the message in the message queue can be:

typedef struct tagMSG{

HWND hwnd;

UINT message;

WPARAM wParam;

LPARAM lParam;

DWORD time;

POINT pt;

} MSG;

Among them, the first member variable is the window handle used to identify the window receiving the message; the second parameter is the message identification number; the specific meanings of the third and fourth parameters are related to the message value, both of which are message parameters. The latter two parameters represent the time of sending and mailing the message and the cursor position respectively.

Corresponding to the message structure, in actual operation, the value of the first parameter is the handle of the target test window, while the message parameter refers to the man-machine command, and the last two parameters take the default value.

The third step is to design the automated test interface and set the automated test parameters. This interface mainly includes several elements: the edit box for the project file path name required for automated testing (multiple are allowed), and for the Telnet network management type, it also needs to include the login user name, password, target system IP address, and the number of concurrent tests (per need to correspond to a project file). In addition, the button to start the automated test, the button to pause the automated test, and the button to stop the automated test are also necessary. Finally, set the automated test parameters through the automated test interface.

The fourth step is to start the target test window and connect to the system under test. According to the actual situation, for the Telnet-type man-machine command network management system, the user needs to provide the user name and password to connect to the network management system, and the test program automatically starts one or more Telnet programs to log in and connect to the network management system according to the number of concurrency required, and at the same time through FindWindow The API searches and locates each Telnet window, and saves the window handle in an array, so as to distinguish the correct target test window when the HMI command message is mailed; for non-Telnet type HMI command network management, the tester needs to manually start the test first Window and connect to the network management system under test, then use the WindowFromPoint and ChildWindowFromPointEx API search functions to locate the target test window, and save the target test window handle.

As shown in Figure 4 is the target window positioning flow chart, from the members of the message structure, we must first obtain the handle of the target test window when forwarding a message, and target window positioning solves this problem. There are two ways to get the target window handle:

1. If the man-machine command network management type is Telnet network management, you only need to provide the system with the user name, password and IP address to connect to the Telnet network management, and the test program starts one or more Telnet applications according to the number of concurrent applications, and then Connect and log in the man-machine command network management system in the generated Telnet window. At the same time, use FindWindowAPI to obtain the handles of each Telnet window and save the Telnet window handles into an array for use by the automated test thread.

2. For the man-machine command network management is non-Telnet network management type, such as super terminal and other network management with Windows windows, you need to manually start and connect to the network management program, and then use WindowFromPoint, ChildWindowFromPointEx API to locate the target test window and save the target test window handle into a variable for use by the automated test thread.

The fifth step is to create an automated test thread as needed to conduct automated testing of man-machine commands.

This step may further include the following steps:

1. Obtain parameters from the automated test interface, and call AfxBeginThread to start the corresponding test thread according to the obtained parameters.

2. The test thread obtains the final man-machine command from the project file and caches the man-machine command

3. The test thread preprocesses the obtained HMI commands.

4. The test thread converts the preprocessed man-machine commands into character messages, that is, Windows message sequences.

5. Call the PostMessage API to automatically post the converted character sequence message to the target window, that is, the automated test.

6. Repeat the steps after 3 until the test is interrupted or ended.

As shown in Figure 5 is the automated testing flowchart in the inventive method, described automated testing is final goal, must provide the required parameter of automated testing before automated testing, for this reason, at first design automated testing interface, to Telnet Network management type, the automated test interface must contain the following elements: the edit box for the path name of the project file required for the automated test (multiple are allowed), and the login user name, password, IP address of the target system, and the number of concurrent tests (per need to correspond to a project file). For non-Telnet network administrators, the automated test interface must include an edit box for the project file path name required by the automated test. In addition, regardless of the type of network management, the automated test interface must include: a button to start the automated test, a button to pause the automated test, and a button to stop the automated test.

Then, set up the necessary information in the designed automated test interface.

When the preconditions are met, call the AfxBeginThread API to create and start one or more automated test threads, and the automated test threads will complete the automatic test operation. The automated testing thread first finds the project file, then finds the command file included in the project file, and finally extracts the corresponding man-machine commands from the command file. In order to reduce time-consuming operations such as frequently opening and closing files during the test, the automated test thread caches the obtained command file and the man-machine command, and subsequently accesses the command file and the man-machine command fetched from cache.

Whenever a man-machine command is obtained, the automatic test thread preprocesses the man-machine command, and completes the character conversion of man-machine command editing in macro form, such as automatic random number generation, random IP address generation, random MAC address , nested command processing, associated command processing. After the man-machine command preprocessing, the automatic test thread converts the man-machine command into a Windows message, and according to the target test window handle value, by means of the Windows message forwarding mechanism, calls PostMessage (message mailing) to mail the man-machine command to the target test window , to achieve the purpose of automatic testing.

This automatic test process continues until the command files contained in the project file and the commands contained in the command files are all tested or stopped halfway. number of file executions and the number of times the command itself was executed, etc.).

Introduce a specific implementation case of adopting the inventive method to carry out automated testing to a man-machine command with three parameters at last:

The automated testing system that utilizes the method of the present invention to realize is a Windows application program independent of the product under test and the product operating platform, and its method of use is as follows:

Assume that the network management system is Telnet, and the HMI command is "Config Board". This command has three parameters: frame, ranging from 1 to 255; shelf, ranging from 1 to 2; slot, ranging from 1 to 8. The network management system is tested concurrently by three Telnet terminals.

First, design the man-machine command input interface according to the requirements, enter the man-machine command "Config Board" on the man-machine command input interface, and specify the number of parameters as 3, and specify parameter 1 as frame, the minimum value is 1, and the maximum value is 255, the step size is 1; the parameter 2 is shelf, the minimum value is 1, the maximum value is 2, and the step size is 1; the parameter 3 is slot, the minimum value is 1, the maximum value is 8, and the step size is 1. Repeat the command test 1000 times, save it to the test.cmd command file in the required storage format, and save the test.cmd command file to the project file test.ctp; design the automated test interface according to the requirements, and enter the connection to the Telnet network management in the automated test interface User name test, password test, select the project file test.ctp, because it is a Telnet network management, so select the number of concurrent tests as 3, the program will automatically start three Telnet applications, click the start button, you can enter the automated test, at this time , you can see that three Telnet terminals are testing the system under test concurrently. To the end of this automated test, this automated test system will actually send 1000 times to the Telnet network manager with 255*2*8 kinds of parameter combinations, a total of 255*2*8*1000 commands, it can be seen that in the test method of the present invention automated testing efficiency.

The sixth step is to disconnect the automated test system from the man-machine command network management system.

The man-machine command automatic testing method and system based on Windows message mechanism of the present invention have the following advantages:

1. Low cost of testing. This automated test system directly utilizes the message forwarding function provided by the Windows operating system, and can run directly and perform automated tests without any third-party software (such as Robot). In addition, this test system has no special requirements for computer software and hardware. It can run on any general-purpose computer with Windows operating system installed.

2. Test cases are easy to share. The test cases customized on different machines can be copied to other machines without any modification, using this automated test system for automated testing.

3. Simple and efficient. This automated test system has encapsulated the test script - the automated test program, without the intervention of testers. Moreover, the man-machine command editing interface is simple, friendly, and powerful, and testers can really focus on man-machine commands. In terms of customization of test cases, "what you see is what you get".

4. Easy to promote. Since this automated test provides a good man-machine interface, and the whole system contains only one executable file, it is extremely convenient to use, and thus it is easy to promote in the project. In addition, due to the "separation of program and data", as long as a new test case is entered, the man-machine command network management of other projects can be automatically tested, which is easy to promote among projects.

5. Provide a model for the development of automated testing software.

The embodiment of the present invention achieves the purpose of the present invention, and achieves the effect of reducing the burden of testers and avoiding duplication of labor in the actual test work. It is more concise and flexible than simple application capture/playback test tools, and greatly improves test efficiency. and test quality.

It should be noted that those skilled in the art can make equivalent changes or substitutions according to the technical solutions and concepts of the present invention, and all these changes or substitutions should fall within the protection scope of the appended claims of the present invention.

Claims (6)

1, a kind of man-machine command test method, it utilizes at least one general-purpose computer, realizes the automation test of man-machine command, and this method comprises the following steps: a) Design the file storage format of the man-machine command, the file storage format is section/keyword/value; b) Design the input interface of the man-machine command, enter the man-machine command through the man-machine command input interface and save it to the specified command file according to the file storage format, and finally save it to the project file as the entry parameter of the automated test; c) Design the automated test interface, and set the automated test parameters, each automated test corresponds to a project file; d) Start the target test window and connect to the system under test; e) Create an automated test thread as needed to perform automated testing of man-machine commands; f) Disconnect the automated test system from the man-machine command network management system. 2. The test method according to claim 1, wherein the file storage format is section/keyword/value, and the section is divided into two categories, one category is used to represent the number of commands in the command file , another class that logs the actual command. 3. The testing method according to claim 2, characterized in that, said step b) further comprises the following steps: b1) Enter the man-machine command in the input interface of the man-machine command, specify the parameter name, the number of parameters, the number of operations, and the delay of the man-machine command at the same time, and realize the random number, IP address, and MAC address through the macro form Automatic generation, and support for dynamic acquisition of command parameter values; b2) According to the storage format designed in step a), save the entered man-machine command into the specified command file. The command file name contains two parts of information: the use case name itself and the execution times information of the command file. In the command file All commands are executed once; b3) Save the command files to be included in the form of project files. 4. The testing method according to claim 3, characterized in that, the automated testing interface in the step c) includes: at least one required project file path name edit box for automated testing, for the Telnet network management type, also User name, password, IP address of the target system, edit box for the number of concurrent tests need to be logged in, and each automated test corresponds to a project file; and at least one button to start the automated test, button to pause the automated test, and button to stop the automated test. 5. The test method according to claim 4, wherein said step e) further comprises the following steps: e1) Obtaining parameters from the automated test interface, and calling an API to start a corresponding test thread according to the obtained parameters; e2) The test thread obtains the final man-machine command from the project file, and caches the man-machine command; e3) The test thread preprocesses the obtained man-machine commands; e4) The test thread converts the preprocessed man-machine command into a character message; e5) automatically mailing the converted character message to the target window by calling the information mailing application program interface, that is, performing an automated test; e6) Repeat the steps after e3) until the test process is interrupted or ended. 6. The test method according to claim 2, characterized in that, the section used to represent the actual command in the command file is called the command number, which contains two keywords at the same time, and one of the keyword values is the The command itself also includes the specific execution information of the command; the second keyword is used to indicate whether the command is to be executed.