KR20140084698A - Automatic software test system for steel processing - Google Patents

Abstract

The present invention relates to an automatic software test system for steel processes. According to an embodiment of the present invention, the automatic software test system for steel processes includes a testing model diagram editor automatically writing a testing scenario for testing software based on a diagram, a testing scenario extensible markup language (XML) generator generating a test scenario XML document by referring to the structure and content of the written testing scenario, a testing task management part generating at least one testing task in the testing scenario based on the testing scenario XML document, and a testing task executing part automatically testing the software by executing the generated testing tasks on the software.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention [0001] The present invention relates to an automatic test system for a steel process,

The present invention relates to a software automated test system for steel processes.

In the field of steel processing, software developers develop software, manually compile and run the source code for direct testing, and then statically test the software. This requires additional development of the source code for testing and thus additional cost. Also, there is a problem that testing for exceptions and fault conditions is impossible.

There is a need in the art for a software automated test system for steel processes.

In order to solve the above problems, a first aspect of the present invention provides a software automatic test system for a steel process. The automatic software testing system for the steel process includes a testing model diagram editor for automatically creating a testing scenario for software testing based on a diagram, and a testing scenario XML (eXtensible Markup Language) document A testing scenario XML generator for generating a testing scenario XML document, a testing task manager for generating at least one testing task in a testing scenario based on the generated testing scenario XML document, and automatically testing the software by executing the generated testing tasks on the software And a testing task execution unit.

In addition, the solution of the above-mentioned problems does not list all the features of the present invention. The various features of the present invention and the advantages and effects thereof will be more fully understood by reference to the following specific embodiments.

Software automated test systems for steel processes can be provided.

1 is a block diagram showing an apparatus configuration of a software automatic test system for steel processing according to an embodiment of the present invention, and Fig.
2 is a flow chart illustrating a software automatic test method of a software automated test system for a steel process in accordance with an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings. However, the embodiments of the present invention can be modified into various other forms, and the scope of the present invention is not limited to the embodiments described below. Further, the embodiments of the present invention are provided to more fully explain the present invention to those skilled in the art. The shape and size of elements in the drawings may be exaggerated for clarity.

The present invention relates to a software automatic test system for steel processes, and more particularly, to an automatic test system for automatically testing steel process middleware in terms of function and performance. In other words, it describes an automatic test system that can create a testing scenario that can test the developed middleware in an intuitive way, perform testing based on the created testing scenario, and show the function and performance results to the developer in real time . It also describes a system that allows exception and fault conditions to be automatically reflected in testing scenarios to test the incident situation thereon. Accordingly, the present invention can reduce the source code development procedure for software testing, and it is advantageous to develop and provide stable software required in the steel process by performing the test at any time during or after the software development process.

1 is a block diagram showing a configuration of an automatic software testing system for a steel manufacturing process according to an embodiment of the present invention.

As shown, a software automatic test system for a steel manufacturing process includes a testing model diagram editor 100, a testing model diagram scenario manager 102, a testing model diagram scenario evaluation engine 104, a testing model scenario file managing unit 106, The testing model script script editor 108, the testing model script scenario manager 110, the testing model script scenario evaluation engine 112, the testing scenario XML (eXtensible Markup Language) generator 114, the source code generator 116, The testing task manager 124, the testing task pool 126, the testing task handler management unit 128, the testing task execution unit 130, and the testing task execution unit 130. The testing task execution unit 118, the testing scenario XML analyzer 120, the testing simulation management kernel engine 122, A testing performance result logger 132, a performance result indicator manager 134, a testing performance result viewer 136, And a stacking unit 138, a testing performance results post-analyzer 140. The

Referring to FIG. 1, the testing model diagram editor 100 is a tool that can automatically create scenarios for testing steel process middleware based on a diagram. The testing model diagram editor 100 displays various models capable of configuring a testing scenario as a diagram on a tool screen and supports connection between diagram models using drag and drop and attribute input for the corresponding diagram model, Lt; RTI ID = 0.0 > and / or < / RTI > Accordingly, the developer can select and connect one or more diagram models through drag and drop through the above-described testing model diagram editor 100, and input attributes for the model, thereby intuitively and conveniently providing a scenario for steel process middleware testing Can be created. Here, the diagram model that can constitute the testing scenario may include a testing task diagram model indicating a testing task, a message transmission / reception diagram model responsible for sending / receiving messages between testing tasks, a timer operation A diagram of a file operation diagram that manages file related operations such as file creation, storage, management, and deletion combined with a diagram model and a testing task, a shared memory operation diagram model for sharing specific data between tasks, and a testing task A database operation diagram model for operation and communication for storing and managing data in a database, communication and data transmission / reception with PLC (programmable logic controller) or DCS (Distributed Control System) in a steel process Being should include PLC and DCS operation diagram model.

In addition, the testing model diagram editor 100 supports the random generation of testing scenarios, so that when a random occurrence of a testing scenario is required by a developer, one or more diagram models can be randomly selected and linked to create a testing scenario have. As a result, the developer can randomly generate a testing scenario through a randomly generated menu selection or command input, without having to select and link diagram models separately.

The testing model diagram scenario manager 102 analyzes a testing scenario created by the testing model diagram editor 100 and maintains and manages the contents and structure in real time in a data structure that the computer can understand internally. That is, the connection between the diagram models applied to the testing scenario and the attributes of the corresponding diagram model are maintained and managed in real time in a computer-understandable data structure. The data structure has a key value of the names of the diagram models applied to the testing scenario, and the diagram models are automatically aligned based on the key values. The testing model diagram scenario manager 102 can efficiently manage data through a tree structure and a linked list structure.

The testing model diagram scenario evaluation engine 104 performs verification and evaluation of a testing scenario created by the testing model diagram editor 100. [ That is, starting from the testing task diagram model, it is evaluated whether the task number and the task name are properly set, and whether the testing task diagram model and other diagrammatic models connected thereto are appropriately connected and whether the property of each diagrammodel is set properly . Also, the testing model diagram scenario evaluation engine 104 can automatically notify the developer of the verification and evaluation results through a message or the like.

The testing model scenario file management unit 106 extracts the contents and structure of a testing scenario maintained and managed by the testing model diagram scenario manager 102, and stores and manages the contents and structure through a file and a database. That is, information about connection between diagram models applied to a testing scenario and information about attributes of the corresponding diagram model are stored and managed through a file and a database. Also, the testing model scenario file management unit 106 extracts the contents and structure of a testing scenario maintained and managed by the testing model script scenario manager 110, and stores and manages the contents and structure through a file and a database. Accordingly, the testing model diagram editor 100 and the testing model script editor 108 can reload the pre-stored testing scenarios through file and database searches and use them for middleware testing.

The testing model script editor 108 is a tool capable of creating scenarios for testing steel process middleware based on a script. The testing model script editor 108 creates a testing scenario with a script input by the developer on the tool screen.

The testing model script scenario manager 110 analyzes a testing scenario created by the testing model script editor 108 and maintains and manages the contents and structure in real time in a data structure that the computer can understand internally.

The testing model script scenario evaluation engine 112 performs verification and evaluation of a testing scenario created by the testing model script editor 108. [ That is, it evaluates whether the grammar of the testing scenario is appropriate and verifies and evaluates whether there is no problem in operation internally. In addition, the testing model script scenario evaluation engine 112 can automatically notify the developer of the verification and evaluation results through a message or the like.

The testing scenario XML generator 114 refers to the contents and structure of a testing scenario maintained and managed by the testing model diagram scenario manager 102 to generate an XML document representing the testing scenario. Here, the XML document includes connection information between diagram models applied to a testing scenario and attribute information about the corresponding diagram model. That is, the XML document includes attribute information (e.g., task name and task number, server information on which middleware is operated, etc.) of the testing task diagram model, connection information between the testing task diagram model and other diagram models, As shown in FIG. The testing scenario XML generator 114 refers to the contents and structure of a testing scenario maintained and managed by the testing model script scenario manager 110 to generate an XML document representing the testing scenario.

The source code generator 116 analyzes and parses the XML document generated by the testing scenario XML generator 114 to automatically generate source code that can be compiled and executed in the middleware. Also, the source code generator 116 can automatically test the middleware based on the generated source code by automatically executing a compilation script and compiling and executing the generated source code.

The fault scenario generator 118 creates a fault scenario for the testing task diagram model and the other diagram models associated therewith through the fault scenario creator provided by the testing model diagram editor 100. That is, create fault scenarios that indicate exception and fault conditions for software testing of exceptions and fault conditions. Also, the fault scenario generator 118 can create a fault scenario through the testing model script editor 108. [ The content and the structure of the fault scenario thus created are maintained and managed in real time with a data structure understandable by a computer by the testing model diagram scenario manager 102 and the testing model script scenario manager 110, And is stored and managed by the management unit 106 through a file and a database. Accordingly, the testing scenario XML generator 114 refers to the contents and structure of the fault scenario managed and maintained by the testing model diagram scenario manager 102 and the testing model script scenario manager 110 to determine the corresponding fault scenario You can generate an XML document to represent. The XML document representing the fault scenario includes fault operation information for the testing task diagram model and other diagram models connected thereto.

The testing scenario XML analyzer 120 analyzes and parses a testing scenario XML document and a fault scenario XML document generated by the testing scenario XML generator 114 and combines the information on the basis of each testing task to perform a testing simulation To the management kernel engine 122. In addition, the testing scenario XML analyzer 120 checks the content change and update status of the testing scenario XML document and the fault scenario XML document generated by the testing scenario XML generator 114, The test scenario XML document and the fault scenario XML document are analyzed and parsed again so that the changed or updated contents can be reflected and the test simulation management kernel engine 122 combines the information on the basis of each testing task, .

The testing simulation management kernel engine 122 controls the testing task manager 124 based on the information received from the testing scenario XML analyzer 120 so that at least one testing task in the testing scenario and each testing task And generates a plurality of OFP (Operation, Fault and Performance) information associated with the OFP. Here, the OFP information includes operation information, fault information, and performance information. That is, the testing task manager 124 generates a corresponding testing task based on the attribute information of the testing task diagram model, and stores connection information between the testing task diagram model and other diagram models, and attribute information on the other diagram models And generates fault information including fault operation information for the testing task diagram model and other diagrammatic models connected to the testing task diagram model. The performance information is generated by acquiring and including information on performance result parameters dynamically selected by the performance result indicator management unit 134. [ The testing task manager 124 registers the testing tasks and the plurality of OFP information related to each testing task in the testing task pool 126. If the contents are changed, the testing task pool 124 ), And if the OFP information is no longer needed, the corresponding information can be deleted.

When the testing task is registered in the testing task pool 126, the testing task handler management unit 128 assigns a testing task handler mapped to the registered testing task 1: 1.

The testing task execution unit 130 automatically tests the middleware by executing the corresponding testing tasks by referring to the related OFP information and the testing task function collection on the middleware through the testing task handler mapped to each testing task. The testing task execution unit 130 has a testing task function collection that wraps a programming development API (application programming interface) provided by the middleware with an appropriate internal structure. The testing task execution unit 130 can call the related API function have.

The testing performance result logger 132 obtains a performance result corresponding to the performance result parameters dynamically selected by the performance result indicator manager 134 and outputs it as a performance testing result for the middleware to the testing performance result viewer 136. [ And the testing performance result accumulating unit 138. [

The performance result indicator manager 134 selects a desired performance indicator from the developer, dynamically selects performance result parameters according to the selected performance indicator, and transfers the selected performance result parameters to the testing task manager 124. Here, the performance index includes system stability (Reliability), scalability, robustness, processing capability, and the like. It is also possible to monitor performance performance parameters and related parameters The combination is fixed. Alternatively, the performance result parameters corresponding to the performance indicator may be dynamically changed by the developer.

The testing performance result viewer 136 receives performance results from the testing performance result logger 132 and displays the results on the screen in numerical values or graphs so that the developer can check the current performance testing results of the middleware.

The testing performance result accumulator 138 receives performance results from the testing performance result logger 132 and stores the results through a file or a database or a shared memory.

The testing performance result post analyzer 140 refers to performance results stored in the testing performance result accumulating unit 138 and performs post-analysis based on the stored performance results for a predetermined period of time.

2 is a flow chart illustrating a software automatic test method of a software automated test system for a steel process according to an embodiment of the present invention.

Referring to FIG. 2, in step 201, a software automatic test system for a steel manufacturing process automatically creates a testing scenario and a fault scenario for middleware testing based on a diagram or a script.

In step 203, the system maintains and manages the contents and structure of the test scenario and the fault scenario in real time in a data structure that can be understood by a computer.

In step 205, the system generates a testing scenario XML document and a fault scenario XML document by referring to the contents and structure of the testing scenario and the fault scenario.

Thereafter, the system analyzes and parses the testing scenario XML document and the fault scenario XML document in step 207, and combines the information on the basis of each testing task to generate at least one testing task and each testing task in the testing scenario And generates a plurality of related OFP information.

In step 209, the system assigns a testing task handler for each testing task.

Then, the system automatically tests the middleware by referring to the related OFP information and the testing task function collection on the middleware through the testing task handler mapped to each testing task in step 211 and executing the corresponding testing tasks.

Then, in step 213, the system displays the performance test result of the middleware as a numerical value or a graph on the screen.

The system then terminates the algorithm according to the invention.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, but, on the contrary, It will be obvious to those of ordinary skill in the art.

100: Testing Model Diagram Editor
102: Testing Model Diagram Scenario Manager
104: Testing model diagram scenario assessment engine
106: Testing Model Scenario File Manager
108: Testing Model Script Editor
110: Testing model script script manager
112: Testing model script script scenario evaluation engine
114: Testing scenario XML generator
116: Source Code Generator
118: Fault scenario generator
120: Testing scenario XML parser
122: Testing Simulation Management Kernel Engine
124: Testing task manager
126: Testing Task Pool
128: Testing task handler manager
130: Testing task execution unit
132: Testing Performance Results Logger
134: Performance result indicator management part
136: Testing Performance Results Viewer
138: Testing performance result integration section
140: Testing Performance Results Post-Analyzer

Claims (11)

A testing model that automatically creates testing scenarios for diagram-based software testing. Diagram editor,
A testing scenario XML generator for generating a testing scenario XML (eXtensible Markup Language) document by referring to the contents and structure of the created testing scenario,
A testing task manager for generating at least one testing task in the testing scenario based on the generated testing scenario XML document,
And a testing task execution unit for executing the generated testing tasks on software to automatically test the software.
The method according to claim 1,
Wherein the software is middleware.
The method according to claim 1,
The testing model diagram editor displays various models capable of configuring a testing scenario on a screen, supports connection between diagram models using drag and drop and input of attributes for the corresponding diagram model, And creating a testing scenario with one or more diagrammodels connected to the automated test system.
The method of claim 3,
Wherein the testing model diagram editor is configured to randomly select and connect one or more diagram models to generate a testing scenario when a random occurrence of a testing scenario is required by the developer.
The method of claim 3,
The diagrammodel displayed on the screen includes a diagram model representing a testing task, a diagrammodel responsible for sending and receiving messages between the testing tasks, a diagrammodel responsible for setting the operating cycle and time of the testing task, A diagrammodel responsible for data sharing between tasks, a diagrammodel responsible for operations and communication for storing and managing data in a database in combination with a testing task, a programmable logic controller (PLC) in a steel process, Or a diagram model that is responsible for communication with DCS (Distributed Control System) and data transmission / reception.
6. The method of claim 5,
The testing model diagram editor creates a fault scenario that represents an exception and a fault situation based on a diagram,
The testing scenario XML generator generates a fault scenario XML document by referring to the contents and structure of the fault scenario created above,
Here, the testing scenario XML document includes attribute information for a testing task diagram model, connection information between a testing task diagram model and other diagram models, and attribute information about other diagram models,
Wherein the fault scenario XML document includes fault operation information for a testing task diagram model and other diagrammatic models connected thereto.
The method according to claim 6,
A performance result indicator manager for selecting a desired performance indicator from the developer and dynamically selecting performance result parameters according to the selected performance indicator,
Here, the testing task manager may include at least one testing task in the testing scenario and an operation, fault, and performance (API) related to each testing task based on the generated testing scenario XML document, the fault scenario XML document, ) Information,
Here, the OFP information includes operation information, fault information, and performance information,
Here, the testing task manager may generate a testing task based on attribute information of the testing task diagram model, and may include attribute information about connection information between the testing task diagram model and other diagram models and other diagram models, Generates fault information including fault operation information for the testing task diagram model and other diagrammatic models connected thereto, and generates performance information including information on the performance result parameters Software automated test system for steel processes.
8. The method of claim 7,
A testing performance result logger to obtain a performance result corresponding to the performance result parameters,
A testing performance result viewer for displaying the obtained performance result as a numerical value or a graph on a screen,
A testing performance result accumulating unit for storing the obtained performance results,
Further comprising a testing performance result post-analyzer for performing post-analysis based on the stored performance results for a predetermined period of time with reference to the stored performance results.
The method according to claim 1,
And a testing task handler management unit for assigning a testing task handler for each testing task,
Herein, the testing task execution unit refers to the OFP information and the testing task function collection in software through the testing task handler mapped to each testing task, and executes the corresponding testing task to automatically test the software. Software automatic test system for.
The method according to claim 1,
A testing model diagram that analyzes the testing scenarios created by the testing model diagram editor and maintains and manages the contents and structure in real time in a data structure that can be understood by a computer. Scenario manager,
A testing model that automatically creates testing scenarios based on scripts Script editor,
And a test model script script manager for analyzing a test scenario created by the test model script editor and maintaining and managing the contents and structure in real time in a data structure that can be understood by a computer, .
The method according to claim 1,
Analyzing and parsing a testing scenario XML document generated by the testing scenario XML generator to automatically generate source code that can be compiled and executed in software and automatically execute the compilation script to compile and execute the generated source code , And further comprising a source code generator for testing the software.

Images