KR20190084827A - Method for automatic test of program compatibility and apparatus using the same - Google Patents

Abstract

Disclosed is a method for a program compatibility automatic test, which comprises the steps of: opening a document corresponding to a test file; performing a test if the document is opened, and handling the error and recording the result if the document is not opened; and determining whether the remaining test file exists, wherein if the remaining test file exists, executing a test target program is further included, and if not, an automatic test is terminated is further included. According to the present invention, the program compatibility test can be automatically performed.

Description

METHOD FOR AUTOMATIC TEST OF PROGRAM COMPATIBILITY AND APPARATUS USING THE SAME [0002]

The present invention relates to a program compatibility automatic test method and apparatus using the same, and more particularly, to a program compatibility automatic test method and test method for testing whether a preliminarily prepared test document including an object is executed without error, The present invention relates to a method for automatically performing a test of compatibility of a program with respect to a document and a device using the same.

Recently developed software, applications, or programs are developed to operate in various platforms and operating system environments, and include various functions according to the convergence of various technologies as compared with the past.

These programs are tested during the production stage to check whether the GUI functions properly according to the design. That is, the program performs a function that performs expected functions for input through the GUI in various platforms and operating system environments and outputs a reasonable result, and a test is performed to determine whether a device driving the program is stopped due to an infinite loop error do.

In particular, when a new version of the program is developed, the program compatibility automatic test as to whether the document created by the previous version of the program is correctly run in the new version of the program is distinguished from the GUI automatic test which tests only the functionality of the GUI.

In the program compatibility test, the actual written document is used. That is, it is a test to check whether the newly developed program correctly displays the contents of the document created by the previous version of the program, for example, size, position, color, and the like as in the previous version of the program.

However, most of the developers have to manually perform the tasks such as checking items and menu analysis for these tests. This is because the test environment is set to be the same as the environment in which the users use the program and the test is performed in the same manner as the method in which the users use the program, so that errors occurring in the actual use environment can be detected. In order to establish the reliability of the error detection, the same test method as that performed by the user in the same use environment as the user environment must be repeatedly performed.

In the manual test procedure, the developer directly schedules the inspection range, and sets the test operation by programming so that the general user is the same as the environment and method in which the program is used.

Therefore, in order to proceed with the test, the user has to set and execute all processes of using the program. The more the test items are added, the more complicated the process for preparation of the test becomes, and the preparation time is greatly increased.

Korean Patent Laid-Open No. 10-2014-0004495 (Publication date 2014.01.13) "

SUMMARY OF THE INVENTION It is an object of the present invention to provide a method and apparatus for automatically performing a program compatibility test.

It is a further object of the present invention to provide a method and apparatus for testing whether a newly developed program correctly implements a test document using a test document created in a previous version.

According to an embodiment of the present invention, there is provided an automatic program compatibility test method comprising: opening a document corresponding to a test file; Performing a test when the document is opened, if the document is not opened, processing the error, and recording the result; Determining whether there is a remaining test file, and if the remaining test file exists, executing the test target program, and if not, terminating the automatic test .

Here, the automatic test method may further include a step of providing a test file for compatibility check in an independent folder for each type before opening the document.

Here, the automatic test method may further include preparing the test file and executing a test target program before opening the document.

Fixing a size and a position of the test target program when the test target program is executed; And creating a temporary file (temp file).

Here, the method further includes the step of determining whether a history of the test file exists and recording the first execution in the initial mode ini file when the test target program is executed for the first time.

Here, the document includes a document created using a previous version of the test target program, and the test item includes a compatibility test for the document.

Here, the step of executing the test target program is characterized by executing a test target program suited to the extension of the test file.

Here, the automatic test method may further include examining a system resource occupied by the test target program in a state where one or more test files are loaded.

The automatic test method may further include closing the test files retrieved after the resource inspection in conjunction with the step of examining the system resources. The method may further include closing the previous file before the new test file is loaded, The files are fetched in a cumulative manner and closed at once.

The method may further include checking the returned system resource after closing the test file.

Here, the step of recording the result may include moving to a first page of a test document.

Here, the step of recording the result may further include a step of executing a preview mode of the test document.

The step of recording the result may further include recording a current document state through a page down process of a page of the test document.

Here, the automatic test method may further include outputting a test result for the test document.

Here, the step of recording the result may include a count record indicating the number of times the test is performed.

Here, the step of recording the result may include recording the processing result of the error when the error window is displayed.

Here, the step of processing the error may further include the step of checking the error window and recording an error and an exception that have not been processed.

Here, the step of recording the result may include recording the size of the program, the class of the program, the execution position of the program, and the style of the program.

Here, the automatic test method may further include a plurality of additional cycles performed after the cycle including the series of steps is completed.

Here, the step of recording the result may be compared with an evaluation of a test item performed in a previous cycle.

Here, the step of recording the result may include recording the comparison result of the image captured during the test cycle performed in one cycle and the image captured during the test cycle performed in the other cycle.

Here, the step of recording the result may be performed by performing a test on the color of the program execution possibility, the program GUI function, and the program GUI, and recording the result thereof.

A program compatibility automatic test apparatus according to an embodiment of the present invention includes a program control module for controlling an operation of a test target program required to open a test file prepared for compatibility automatic testing; Test module that performs automatic testing of increasingly compatible test files through target test program operation control including open, screen scrolling, and preview execution of test files containing various objects of drawings and shapes; And an image processing module for capturing an image generated in an automatic compatibility test process and processing a captured image, wherein the test module compares the image with a reference image or images captured by the number of tests, It is characterized by the fact that errors are caused by execution errors, functional errors, and comparison results that occur during the test process.

Here, the program compatibility automatic test apparatus may further include a result recording module for recording a result of the automatic test.

According to the present invention, compatibility testing of a program can be performed automatically.

In addition, a test can be performed automatically to check whether a newly developed program correctly implements a test document using a test document created in a previous version.

1 is a schematic block diagram of a program compatibility automatic test apparatus according to an embodiment of the present invention.
2 is an exemplary diagram of a system environment including a program compatibility automatic test apparatus according to an embodiment of the present invention.
Fig. 3 is a detailed illustration according to Fig.
4 is a block diagram of a program compatibility automatic test apparatus according to an embodiment of the present invention.
5 is a detailed block diagram of the control unit of FIG.
6 is a block diagram of a computing device corresponding to a program to be tested according to an embodiment of the present invention.
FIG. 7 is a flowchart of a method of automatic program compatibility test according to an embodiment of the present invention.
FIG. 8 is a flowchart of repetitive execution of one cycle shown in FIG. 7; FIG.
Figs. 9A, 9B, and 9C are exemplary views related to Fig.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings.

Like reference symbols in the drawings denote like elements. It should also be understood that the specific structural and functional descriptions for one embodiment of the present invention are presented for purposes of describing an embodiment of the present invention only and that, unless otherwise defined, all terms used herein, including technical or scientific terms, The terms have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the contextual meaning of the related art and are to be interpreted as ideal or overly formal in the sense of the art unless explicitly defined herein .

1 is a schematic block diagram of a program compatibility automatic test apparatus according to an embodiment of the present invention.

1, the program compatibility automatic test apparatus 100 according to an exemplary embodiment of the present invention includes an operating system 176, a test program module 175, and a test target program module 179 in a standalone manner. 177).

In addition, the program compatibility automatic test apparatus 100 can test the compatibility of the test target program module 275 driven by a plurality of computing devices 200 through a network.

2 is an exemplary diagram of a system environment including a program compatibility automatic test apparatus according to an embodiment of the present invention.

2, a system environment 1 according to an embodiment of the present invention includes a program compatibility automatic test apparatus 100, a plurality of test target program driving apparatuses 200, a database 300, and a network 400 . FIG. 2 is shown in detail in FIG.

Fig. 3 is a detailed illustration according to Fig.

3, the program compatibility automatic test apparatus 100 loads the operating system 176 and the test program module 175 into the memory 177, and the target program drive apparatus 200 loads the operating system 276 and the test program The program module 275 is loaded into the memory 277. [

The network 400 may be a wired and wireless network such as the Internet, an intranet and an extranet, a cellular such as a wireless telephone network, a local area network (LAN), a wide area network ), A WiFi network, an ad hoc network, and combinations thereof.

The database 300 may include a reference image for comparing GUI configuration, GUI execution, GUI color, etc. according to the program version and a database about images obtained in the previously performed test.

Network 400 may include connections of network elements such as hubs, bridges, routers, switches and gateways. The network 400 may include one or more connected networks, such as a multi-network environment, including a public network such as the Internet and a private network such as a secure corporate private network. Access to the network 400 may be provided via one or more wired or wireless access networks. Hereinafter, the program compatibility automatic test apparatus 100 will be described according to the configuration shown in FIG.

4 is a block diagram of a program compatibility automatic test apparatus according to an embodiment of the present invention.

4, the program compatibility automatic test apparatus 100 includes an input device 110, a display device 120, an output device 130, a storage device 140, a communication device 150, a power supply device 160, And a control unit 170. The control unit 170 includes a test program module 175. The communication device 150 includes a transmitting unit 151 and a receiving unit 152.

The input device 110 includes a keyboard, a touch screen, a mouse, an electronic pen, and a voice input device, such as a microphone, for performing the input necessary to operate and operate the test program module to test the target program module, But is not limited thereto.

The display device 120 may include a cathode-ray tube (CRT), a liquid crystal display (LCD), a plasma display panel (PDP), and a plasma display panel But are not limited to, light emitting diode (LED) displays, organic light emitting diode (OLED) displays, and the like.

The output device 130 includes, but is not limited to, a printer, a plotter, a beam projector, a text to sound (TTS) device, a speaker and an earphone.

The storage device 140 may be any type of detachable / non-removable from the program compatibility automatic test apparatus 100 and may be a magnetic tape such as a magnetic tape, a magnetic drum, a floppy disk, a ZIP drive, and a hard disk drive An electronic storage device and a CD-ROM drive using a flash memory such as an SD card, a USB memory and a solid state drive (SSD), a DVD-ROM drive, a blu-ray disc ) Drives. ≪ / RTI >

The communication device 150 includes a communication module corresponding to various communication networks of the network 400, for example, a Bluetooth module, a WiFi module, an Ethernet interface card, a USB module, a cellular wireless communication module, a modem and a wireless router. It is not. The communication device 150 includes a transmitting unit 151 and a receiving unit 152 therein.

The power supply 160 may include, but is not limited to, a power supply that converts AC to DC, an adapter, a secondary battery such as a SMPS and a lithium ion battery, a lead acid battery, a fuel cell, and a bioethanol battery, It is not.

The control unit 170 includes a memory area in which the processor and the operating system and the test program module 175 are loaded. The control unit 170 executes a command set included in the test program module according to user selection or setting. Hereinafter, the control unit 170 will be described in detail.

5 is a detailed block diagram of the control unit of FIG.

5, the control unit 170 includes a central processing unit (CPU) 178, an operating system 176, and a test program module 175 for a program compatibility automatic test method according to an embodiment of the present invention. And a loaded memory 177. Specifically, the control unit 170 includes a program control module 171, a test module 172, and a video control unit 173 including a set of computer instructions for performing the program compatibility automatic test method according to an embodiment of the present invention, Processing module 173 and result module 174.

The control unit 170 controls each component and modules in the program compatibility automatic test apparatus 100 such that a program compatibility automatic test method according to an embodiment of the present invention is implemented.

The operating system 176 is a computer operating program for managing the file system of the program compatibility automatic test apparatus 100, managing various interfaces, and controlling operations of the components. The operating system 176 includes, but is not limited to, an operating system of a wired and mobile device, such as MS Windows, Unix, Linux, XOS, Android, iOS operating systems.

The test program module 175 is an executable program configured to run on the operating system 176 to provide various functions as described in the present invention. The test program module 175 includes a program control module 171, a test module 172, an image processing module 173 and a result recording module 174. Details of the various modules 171 to 174 included in the test program module 175 will be described later.

The configuration in the test program module 175 in the configuration of the program compatibility automatic test apparatus 100 shown in FIG. 4 and FIG. 5 is a functionally separated configuration for convenience of description, and is processed by one processor in hardware And the present invention is not limited by the presented division.

In addition, the connection relationship between the respective components is shown as a connection line, or the connection relationship between the components is not expressed individually, but communication or transmission for control or data exchange may occur between configurations in which the connection line is not shown. The present invention is not limited thereto.

The test target program driving device 200 according to an embodiment of the present invention may correspond to the computing device 500. [ Hereinafter, the test target program driving apparatus 200 according to an embodiment of the present invention corresponding to the computing apparatus 500 may be described in more detail with reference to embodiments.

The computing device 500 may include a computing system comprised of one or more central processing units (CPUs), a memory, a mass storage, an input interface device, and an output interface device. The elements of the computing system may communicate with each other via a bus.

The hardware platform of a computing device may be a distributed computing environment, such as a personal computer, a handheld or laptop device, a multiprocessor system, a microprocessor-based system, a program product, and any of the above systems or devices, And the like.

6 is a block diagram of a computing device corresponding to a target program drive apparatus according to an embodiment of the present invention.

6, a computing device 500 includes an input interface device 510, an output interface device 520, a memory 531, a storage device 532, a power supply 540, a processor 550, Device 560, a wireless communication device 570, and a bus 580.

The input interface device 510 inputs characters or objects necessary for document creation according to the input of the user. The input interface device 510 includes, but is not limited to, a keyboard, a touch screen, a mouse, a stylus pen, and a pen tablet.

The output interface device 520 includes a display for displaying a user interface related to a document editing program module and a printer for printing out a document. The output interface device 520 also includes a speaker, a head-phone, and a head-set for outputting the characters in the document by voice using a text to speech (TTS) engine. do.

The processor 550 may include a computer instruction set 534 that includes a document editing program / server module 174/274 associated with a data backup method in accordance with an embodiment of the present invention stored in memory 531 and / . The processor 550 may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which the methods according to the present invention are performed. The memory 531 and the storage device 532 may be composed of a volatile storage medium and / or a non-volatile storage medium. For example, the memory 531 may be comprised of read only memory (ROM) and / or random access memory (RAM).

The wireless communication device 570 includes devices for short-range wireless communication, wireless data communication, and wireless voice communication.

Each component included in computing device 500 is connected by bus 580 to communicate with each other.

4 and 5, a program compatibility automatic test method according to an embodiment of the present invention, which is executed by the above-described program compatibility automatic test apparatus 100 through the operation of a computer instruction set included in the test program module 175, And Figs. 7 to 11. Fig.

First, a test file for compatibility check is prepared in the independent folder for each type (S110). The automatic test apparatus 100 creates an independent folder for each kind of test file, that is, an extension, and stores the test file in the folder. The test file used here may include a document file created by a word processor for document editing, a file created by a presentation program, and a file created by a spreadsheet program.

Next, the program compatibility automatic test apparatus 100 executes the automatic test program module 175 shown in FIG. 5 (S120).

Next, the automatic test program module 175 executes the test target program module 275 (S130). Step S130 includes steps S131 to S133. Since the subsequent steps are performed by the automatic test program module 175, the subject of execution will be omitted.

When the test target program is executed, the size and position of the test target program are fixed (S131). Here, the size means the size of the main window in which the program to be tested is executed, and the position means the position of the main window. When the program under test is run with the largest size window, the maximum size execution is recorded in the test result.

Next, a temporary file is generated (S132). The purpose of the temporary file is to record information about occurrence of various events occurring during the test process. When the test is terminated, a file name is automatically assigned to the temporary file, and the temporary file is permanently stored in the storage device 140 as a regular file.

Next, the history of the test file is searched. If the test target program is executed for the first time, the first execution fact is recorded in the initial mode ini file (S133). The history of the test file can be retrieved by referring to the open view list of the program to be tested. The record of the minimum execution proves that it is the first test later.

The document corresponding to the test file is opened in the next step (S140). That is, the execution of the test target program and the opening of the document are performed in a divided manner. This is to determine at which stage an error occurred when an error occurred.

When the document is opened, the program compatibility automatic test apparatus 100 performs the test. If the document is not opened, the error is processed and then the result is recorded (S150).

If the document is opened after step S140, the document may not be opened due to an error or the like. Even if the document is not opened due to an error, the error window or the exception window is opened, or the error window or exception window is not opened There may be cases.

When a document is opened, the time it takes to open the document is measured and displayed on the screen as a time message. Then, the time result value is input to the temporary file.

Here, the document includes a document created using a previous version of the test target program. That is, the compatibility test is performed using the document created by the previous program of the current test target program.

If the document does not open, an error window or an exception window is opened, error handling and a message are displayed. An error handling message is entered in the temporary file. If the error window or exception window is not opened, unhandled errors and exceptions are checked, and unhandled errors and exceptions are entered in the temporary file.

After the document is opened, the test procedure will be described in detail.

If the test was performed in the previous cycle, the location where the document was opened by the program under test may be the last page. Therefore, we need to move to the first page of the test document. Page up scrolling is performed until there is no change in the screen by controlling the input device 110 to move to the first page.

And a preview mode of the test document can be executed. Objects previewed in the document are displayed in the document. The status of the current document is recorded through the page down process of the test document.

The test file can also be stored as an original data array. The process of saving without error also belongs to the check item of compatibility test. The current document state is recorded. If the test being performed is the first run mode, the first run in the file is recorded in the first mode ini file. If it is not the initial execution mode, the image captured by the image processing module 173 is compared with the image captured in the previous test or the original image.

Results recording module 174 Records the results of the compatibility test execution as a file. The items recorded here include information on the size of the program, the class of the program, the execution position of the program, and the style of the program. And the record includes a count record indicating the number of tests performed.

 Finally, the test result is output. When the compatibility test for the test file is completed, the program to be tested is terminated (product execution termination).

If there are remaining test files that have not been tested, the program compatibility automatic test apparatus 100 performs steps S120 to S150, and otherwise ends the automatic test (S160). This completes one cycle of the program compatibility automatic test procedure. The program compatibility automatic test apparatus 200 may further perform the program compatibility automatic test of the second cycle, the third cycle, and the Nth cycle.

According to an embodiment of the present invention, the test target program may be terminated immediately when the test for one test file is terminated. However, in some cases, for the system resource measurement occupied by the test target program, It may be terminated at once. The system resource measurement is measured before the end of the program, and the resources returned after the end can also be measured.

FIG. 8 is a flowchart of repetitive execution of one cycle shown in FIG. 7; FIG.

Referring to FIG. 8, the program compatibility automatic test method of the first cycle shown in FIG. 7 is performed, and then the second cycle to Nth cycle program compatibility automatic test method is performed.

Items to be tested for each turn can be adjusted. For example, it is possible to test whether the program is executable in the first cycle, test whether the program GUI function is realized in the second cycle, and test the color of the program GUI in the third cycle. In this case, if a test regarding a specific GUI color does not proceed, such as a GUI functionality test, a black-and-white image or a binarized image may be used as an image to be captured for screen comparison, instead of a color image.

Figs. 9A, 9B, and 9C are exemplary views related to Fig.

9A, 9B, and 9C, the process of starting the execution of the test program module and ending the test is exemplarily shown together with the name of the test target program to be actually tested.

As described above, according to an embodiment of the present invention, compatibility testing of a program can be performed automatically.

In addition, a test can be performed automatically to check whether a newly developed program correctly implements a test document using a test document created in a previous version.

It will be understood by those skilled in the art that the foregoing description of the present invention is for illustrative purposes only and that those of ordinary skill in the art can readily understand that various changes and modifications may be made without departing from the spirit or essential characteristics of the present invention. will be. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive. For example, each component described as a single entity may be distributed and implemented, and components described as being distributed may also be implemented in a combined form.

The scope of the present invention is defined by the appended claims rather than the detailed description and all changes or modifications derived from the meaning and scope of the claims and their equivalents are to be construed as being included within the scope of the present invention do.

100: Program Compatibility Automatic Test Device
110: input device
120: Display device
140: Storage device
170:
171: Program control module
172: test module
173: Image processing module
174: Result recording module
175: Automatic test program module
200: Test program drive device

Claims (24)

Opening a document corresponding to the test file;
Performing a compatibility test when the document is opened, and if the document is not opened, processing the error and recording the result; And
Determining whether a remaining test file exists,
Further comprising the step of: if the remaining test file exists, executing the test target program; and if not, ending the test. The method according to claim 1,
The program compatibility automatic test method includes:
Further comprising the step of providing a test file for compatibility check in an independent folder for each type before opening the document. The method of claim 2,
The programmable garland automatic test method includes:
Further comprising the step of preparing the test file and executing the program to be tested before opening the document. The method of claim 3,
When the test target program is executed,
Fixing a size and a position of the test target program; And
Further comprising the step of generating a temporary file (temp file). The method of claim 4,
Further comprising the step of determining whether a history of the test file exists and recording the initial execution in the initial mode ini file when the test target program is executed for the first time. The method according to claim 1,
The document,
Contains documents created using previous versions of the program under test,
The test items include:
And a compatibility check for the document. The method of claim 3,
Wherein the step of executing the test target program comprises:
And a test target program corresponding to the extension of the test file is executed. The method according to claim 1,
The program compatibility automatic test method includes:
Further comprising the step of examining the system resources occupied by the test target program in a state that the one or more test files are loaded. The method of claim 8,
The program compatibility automatic test method includes:
Further comprising closing the test files retrieved after the examination of the resources in conjunction with the step of examining the system resources, wherein before closing the previous test file, the previous file is closed, the test files are cumulatively retrieved, And closing the program test program. The method of claim 9,
Further comprising examining returned system resources after closing said test file. ≪ RTI ID = 0.0 > 31. < / RTI > The method according to claim 1,
The step of recording the result includes:
And moving to the first page of the test document. The method of claim 11,
The step of recording the result includes:
Further comprising the step of: executing a preview mode of the test document. The method of claim 12,
The step of recording the result includes:
Further comprising the step of recording a current document status through a page down process of a page of the test document. 14. The method of claim 13,
The program compatibility automatic test method includes:
Further comprising the step of outputting a test result for the test document. 15. The method of claim 14,
The step of recording the result includes:
And a count record indicating the number of times the test has been performed. The method according to claim 1,
The step of recording the result includes:
And recording the result of processing the error condition when an error window is displayed. 18. The method of claim 16,
Wherein the step of processing the error comprises:
And if the error window does not appear, check it and record unprocessed errors and exceptions. The method according to claim 1,
The step of recording the result includes:
And recording information on the size of the program, the class of the program, the execution position of the program, and the style of the program. The method according to claim 1,
The program compatibility automatic test method includes:
Further comprising a plurality of additional cycles performed after the cycle including the series of steps is completed. The method of claim 19,
The step of recording the result includes:
And comparing the test item with an evaluation of the test item performed in the previous cycle. The method of claim 19,
The step of recording the result includes:
And recording the result of the comparison of the captured image of the test process performed in one cycle and the captured image of the test process performed in the other cycle. The method according to claim 1,
The step of recording the result includes:
A program execution possibility, a program GUI function, and a color of a program GUI, and records the result. A program control module for controlling an operation of a test target program necessary for opening a test file prepared for a program compatibility test;
A test module for performing a program compatibility test of a test file through object test program operation control including opening, screen scrolling, and preview execution of a test file including various objects of pictures and figures; And
And an image processing module that captures an image generated in the program compatibility test process and processes the captured image,
The test module includes:
Comparing the images with the reference image or comparing images captured by the number of tests with each other, and processing errors due to differences in execution errors, functional errors, and comparison results generated during the testing process, Automatic test equipment. 24. The method of claim 23,
And a result recording module for recording the result of the test.

Images