JP7279497B2 - TEST CODE GENERATOR, TEST CODE GENERATION METHOD AND PROGRAM - Google Patents

Description

The present invention relates to a test code generation device, test code generation method and program.

Several techniques have been proposed for program or system testing.
For example, in the method described in Patent Literature 1, a plurality of independent test cases related to an application are executed in different operating environments for each test case. An operating environment for each test case is indicated by a test document called a test master document.

Japanese Patent Application Laid-Open No. 2018-139106

One method of building a system using a program is to build a system using a declarative model. A system built from a declarative model may not work correctly for various reasons, such as model creation errors, parameter errors, or execution environment problems. For this reason, it is necessary to check whether the system constructed from the declarative model is constructed as declared (intended) and operates correctly.

If test code is generated by manual test design (determination of test items, etc.) every time a system is tested, a high level of skill is required for appropriate test design and test code generation. Depending on the skill of the person, it may not be possible to perform test design and test code generation appropriately. Also, if a mistake occurs in test design or test code creation, the test cannot be performed properly.

An object of the present invention is to provide a test code generation device, a test code generation method, and a program that can solve the above-described problems.

According to the first aspect of the present invention, a test code generation device includes: an information acquisition unit for extracting information on a component of the declarative model from information on the declarative model; and a template acquisition unit that acquires a test code template declaratively declaratively declaratively sets parameter values to be applied to the template in accordance with a rule that is linked to the information of the component and indicates that the parameter value is required. A parameter value acquisition unit that acquires from the model orchestration device , and a parameter value application unit that applies the acquired parameter values to the template to acquire a test code.

According to a second aspect of the present invention, a test code generation method includes the step of extracting, from information of a declarative model, information of a component of the declarative model; a declarative model for setting parameter values to be applied to the template according to a rule that is linked to the information of the component and indicates that parameter values are required; The steps of obtaining from an orchestration device and applying the obtained parameter values to the template to obtain test code are performed .

According to a third aspect of the present invention, a program comprises, in a computer, a step of extracting information of a component of the declarative model from information of the declarative model; A declarative model orchestration device for obtaining a template of test code , and setting parameter values to be applied to the template according to a rule linked to the information of the component and indicating a request for parameter values. and applying the obtained parameter values to the template to obtain test code.

According to the present invention, a system built using a declarative model can be tested more appropriately.

It is a schematic block diagram which shows the example of arrangement|positioning of the test code generation apparatus which concerns on embodiment. 1 is a schematic block diagram showing an example of a functional configuration of a declarative model orchestration device according to an embodiment; FIG. 1 is a schematic block diagram showing an example of a functional configuration of a test code generation device according to an embodiment; FIG. FIG. 5 is a diagram showing an example of template information stored in a test information storage unit according to the embodiment; It is a figure which shows the example of the test information which the test information storage part which concerns on embodiment memorize|stores. FIG. 4 is a diagram illustrating an example of a declarative model according to an embodiment; It is a figure which shows the component which concerns on embodiment, and the extraction example of server information. It is a figure which shows the acquisition example of the parameter value which concerns on embodiment. It is a figure which shows the 1st example of the test code which the test code production|generation part which concerns on embodiment produces|generates. It is a figure which shows the 2nd example of the test code which the test code production|generation part which concerns on embodiment produces|generates. FIG. 4 is a diagram illustrating an example of a processing procedure for generating test code by the test code generation device according to the embodiment; It is a figure which shows the example of a structure of the test code generation apparatus which concerns on embodiment. It is a figure which shows the example of the procedure of a process in the test code generation method which concerns on embodiment. 1 is a schematic block diagram showing a configuration of a computer according to at least one embodiment; FIG.

Embodiments of the present invention will be described below, but the following embodiments do not limit the invention according to the claims. Also, not all combinations of features described in the embodiments are essential for the solution of the invention.
FIG. 1 is a schematic configuration diagram showing an arrangement example of a test code generation device according to an embodiment. In the configuration shown in FIG. 1, a declarative model orchestration device 100, a test code generation device 200, and an execution environment 500 are connected to a communication network 900. FIG. The declarative model orchestration device 100 , the test code generation device 200 and the execution environment 500 communicate via a communication network 900 .

The declarative model orchestration device 100 is a device that interprets a declarative model of a target system (system to be executed by the execution environment 500), converts it into a processing format according to the execution environment, and performs provisioning processing. In a declarative model, the model describes the properties of the target system (in particular, the properties or content of the system's outputs).
Examples of the declarative model orchestration apparatus 100 include, but are not limited to, the OASIS (Organization for the Advancement of Structured Information Standards) TOSCA (Topology and Orchestration Specification for Cloud Applications) reference implementation and the OpenStack Heat implementation. not.

The execution environment 500 is the execution environment for operating the target system. The execution environment 500 may use any of virtual machines, containers, physical servers, or a combination thereof. Examples of execution environment 500 can include, but are not limited to, OpenStack, AWS, and VMware.

The test code generation device 200 automatically generates test code for testing the target system. Specifically, the test code generation device 200 acquires the code of the target system from the declarative model orchestration device 100 and extracts the information of the components of the target system. The test code generation device 200 generates test code by applying parameter values acquired based on information on the components of the target system to templates prepared in advance for each component.

The communication network 900 mediates communication between the declarative model orchestration device 100 , the test code generation device 200 and the execution environment 500 . Communication network 900 is not limited to any particular type of network. For example, the communication network 900 may be the Internet and the test code generation device 200 may provide a cloud service, but is not limited to this.

FIG. 2 is a schematic block diagram showing an example of the functional configuration of the declarative model orchestration device 100. As shown in FIG. With the configuration shown in FIG. 2 , the declarative model orchestration device 100 includes a first communication unit 110 , a first storage unit 180 and a first control unit 190 . The first control unit 190 includes a declarative model orchestrator unit 191 and a provisioning processing execution unit 192 .
The first communication unit 110 communicates with other devices. In particular, the first communication unit 110 transmits a command for provisioning the target system to the execution environment 500 for execution. Also, the first communication unit 110 transmits the code of the target system to the test code generation device 200 .

The first storage unit 180 stores various information. The first storage unit 180 is configured using a storage device included in the declarative model orchestration device 100 .
In particular, the first storage unit 180 stores (memorizes) a declarative model, components of the declarative model, and runtime parameters. For example, in OASIS TOSCA, the declarative model is a definition that represents the entire system configuration called Service Template, and the constituent elements are type definitions called Types such as Node Type and Relationship Type. The declarative model is based on this type definition. Also, runtime parameters are values supplied by the user, such as those specified in the inputs of a Topology Template (part of a Service Template), or values obtained from the execution environment.

The first control unit 190 controls each unit of the declarative model orchestration device 100 to execute various processes. The functions of the first control unit 190 are executed by a CPU (Central Processing Unit) of the declarative model orchestration device 100 reading out a program from the first storage unit 180 and executing it.

The declarative model orchestrator unit 191 converts the declarative model and the parameter values applied to the declarative model into the data format of the internal interpreter that performs execution processing. For example, the declarative model orchestrator unit 191 operates to convert the declarative model and parameter values into a workflow having instructions corresponding to the execution environment 500 as components.

The provisioning processing execution unit 192 executes the data in the internal interpreter format generated by the declarative model orchestrator unit 191 to perform provisioning processing of the target system to the execution environment 500 . For example, the provisioning processing execution unit 192 has the function of executing the workflow as described above.

FIG. 3 is a schematic block diagram showing an example of the functional configuration of the test code generation device 200. As shown in FIG. With the configuration shown in FIG. 3 , the test code generation device 200 includes a second communication section 210 , a second storage section 280 and a second control section 290 . The second storage section 280 has a test information storage section 281 . The second control section 290 includes an information acquisition section 291 and a test code generation section 292 . The test code generation section 292 includes a template acquisition section 293 , a parameter value acquisition section 294 and a parameter value application section 295 .
The second communication unit 210 communicates with other devices. In particular, the second communication unit 210 receives the code of the target system from the declarative model orchestration device 100 . The second communication unit 210 also receives parameter values from the declarative model orchestration device 100 .

The second storage unit 280 stores various information. The second storage unit 280 is configured using a storage device included in the test code generation device 200 .
The test information storage unit 281 stores (memorizes) test code templates and parameter replacement rules for the components of the declarative model. The test information storage unit 281 stores test code templates for the components of the declarative model in the form of template information, which will be described later. In addition, the test information storage unit 281 stores test information, which will be described later, including parameter replacement rules.
The second control unit 290 controls each unit of the test code generation device 200 to execute various processes. The functions of the second control unit 290 are executed by the CPU included in the test code generation device 200 reading a program from the second storage unit 280 and executing it.

The information acquisition unit 291 communicates with the declarative model orchestration device 100 via the second communication unit 210 and acquires information stored in the first storage unit 180 .
The test code generation unit 292 generates a system (target system).

The template acquisition unit 293 acquires test code templates for the components of the declarative model. Specifically, the template acquisition unit 293 reads from the test information storage unit 281 a test code template for testing the component based on the information on the component of the declarative model.

The parameter value acquisition unit 294 acquires the parameter values of the parameters included in the test code template for the components of the declarative model. Specifically, the test information storage unit 281 stores, for each test code template, a rule for obtaining parameter values of the template. The parameter value acquisition unit 294 acquires parameter values based on the acquisition rule. The parameter value acquisition rule may specify the parameter value as a fixed value (constant), or may instruct to acquire the parameter value from the declarative model orchestration device 100 . Alternatively, the parameter value acquisition unit 294 may acquire parameter values from the runtime environment 500 .

The parameter value application unit 295 applies the parameter value acquired by the parameter value acquisition unit 294 to the template acquired by the template acquisition unit 293 . As a result, the parameter value application unit 295 acquires test code for the components of the declarative model.
With the above configuration, the test code generation device 200 can create a function of automatically generating test code.

Processing performed by the test code generation device 200 will be described in more detail.
First, preparation in advance will be explained.
The user stores test code templates and parameter replacement rules for the components of the declarative model in the test information storage unit 281 . A test code template for a declarative model component is also referred to as a test code template, or simply a template.

FIG. 4 is a diagram showing an example of template information stored in the test information storage unit 281. As shown in FIG.
In the example of FIG. 4, the template information is configured as tabular information, and the template ID, template name, and template source code (program) are shown for each template.

A template ID is identification information that identifies a template. Although a serial number is used as the template ID in the example of FIG. 4, it is not limited to this.
The template name is the name given to the template. As identification information for identifying a template, a template name can be used in addition to or instead of the template ID.
In the test code in the "template" column, the parameter name is shown in the form of ": (parameter name):" sandwiched between two ":". The part in which this parameter name is described is replaced with a parameter value by the parameter value applying unit 295 .

FIG. 5 is a diagram showing an example of test information stored in the test information storage unit 281. As shown in FIG.
In the example of FIG. 5, the test information is configured as tabular information, including a test ID, a type name associated with one or more test IDs, a test name for each test ID, a template ID, and Parameters (replacement rules for parameter values) are shown.
The type name (information in the "Type name" column) indicates the component of the declarative model, and the test information is the correspondence between the component of the declarative model and the test code template used for that component. shows a list of

For example, "tosca.nodes.DBMS.MySQL" in the "type name" column and 4 of "1", "2", "3" and "4" in the "template ID" column are associated with one column. As a result, four templates with template IDs "1", "2", "3" and "4" among the templates in FIG. 4 can be used for the component tosca.nodes.DBMS.MySQL. It is shown.

The "parameter" column stores information on the parameter name and value to be replaced. Here, in addition to fixed values, parameter values at runtime can also be designated as parameter values. For example, in the example of FIG. 5, the notations "prop" and "req" respectively indicate properties and requirements for linked components. These indicate that the information acquisition unit 291 acquires values from the declarative model orchestration device 100 . For example, the notation "prop.port" indicates that the value specified in the "port" property of the component is obtained at runtime.
Descriptions for acquiring parameter values at runtime are not limited to “prop” and “req”, and may be descriptions according to the type of declarative model orchestration device 100 .

Next, execution of processing by the test code generation device 200 will be described.
The information acquisition unit 291 acquires from the declarative model orchestration device 100 declarative model information indicating a system to be tested (target system).
FIG. 6 is a diagram showing an example of a declarative model.
The test code generator 292 extracts the components of the declarative model from the declarative model illustrated in FIG. The configuration elements include provisioning destination server information (virtual server, container, or physical server), and function information such as middleware or applications that operate on the server indicated by the server information.

FIG. 7 is a diagram showing an example of extraction of component and server information.
In the example of FIG. 7, the node name extracted from the declarative model of FIG. 6 by the test code generator 292, the type name (component) of the node, and the server information provisioned by the node are shown. .

The test code generation unit 292 converts the labels "wrodpress", "apache", "web_server", "wordpress_db", "mysql", and "db_server" shown under the label "node_templates" in the example of FIG. It is extracted as a notation of a node name and written in the "node name" column in FIG.
The test code generation unit 292 also extracts the type name (component) indicated by "type:..." for each node, and writes it to the "type name" column in FIG.

Also, the test code generation unit 292 detects the description of “host: . For example, the test code generation unit 292 detects the description of "host:apache" in the "wordpress" node, traces the node "appache", and detects the description of "host:web_server". Furthermore, when the "web_server" node is traced, there is no description of "host:...", so the test code generation unit 292 determines that the server name is "web_server", and the "server" column in FIG. Fill in the appropriate fields.

Similarly, the test code generation unit 292 detects the server names "web_server", "db_server", and "db_server" for the nodes "apache", "wordpress_db", and "myspl", respectively, and generates "server" in FIG. is written in the corresponding column of the column.
On the other hand, for each node of "web_server" and "db_server", the server name is not detected because "host:..." is not described. In the example of FIG. 7, "-" indicates that the server name is not detected.

Furthermore, the test code generation unit 292 determines a test that needs to be performed based on the extracted information and the test information (FIG. 5).
In the example of FIG. 7, the test code generation unit 292 determines to perform the test associated with the type name in FIG. 5 for each type name (component) shown in FIG. For example, the test code generator 292 determines to perform tests with test IDs "1", "2", "3" and "4" for the mysql node on db_server. Also, the test code generation unit 292 determines to perform the test with the test ID “5” on the wordpress_db node. Also, the test code generator 292 determines to perform tests with test IDs "6", "7" and "8" for the apache node on web_server. Furthermore, the test code generator 292 determines to test the wordpress node with test IDs "9" and "10".

Further, the test code generation unit 292 acquires information required for parameter replacement from the declarative model orchestration device 100 through the information acquisition unit 291 . Then, the test code generation unit 292 replaces the target portion of the template of the test code with the obtained information to generate the test code.

FIG. 8 is a diagram illustrating an example of parameter value acquisition.
In the example of FIG. 8, examples of parameter values acquired by the test code generation unit 292 are shown for each parameter name. For example, the test code generator 292 acquires "wordpress" as the value of the wp_db_name parameter.

FIG. 9 is a diagram showing a first example of test code generated by the test code generator 292. As shown in FIG. FIG. 9 shows an example of test code for db_server generated by the test code generation unit 292 .
In the example of FIG. 9, the test code generator 292 generates the template IDs of the test IDs "1", "2", "3", "4" and "5" determined as described above as tests for db_server. "1", "2", "3", "4" and "5" are read from the test information illustrated in FIG.

Then, the test code generation unit 292 reads the template of the read template ID from the template information illustrated in FIG.
Further, the test code generator 292 inserts parameter values into the read template according to the rules shown in FIG.

For example, the test code generation unit 292 replaces the description of ":package:" in the template with the template ID "1" with "mysql" according to the rules in FIG. In addition, the test code generation unit 292 replaces the description of ":port:" in the template with the template ID "3" with the value "3306" obtained from db_server ("mysql_port" row in FIG. 8) according to the rule in FIG. see).
As a result, the test code generator 292 acquires the test code shown in FIG. 9 as the test code for db_server.

FIG. 10 is a diagram showing a second example of the test code generated by the test code generator 292. As shown in FIG. FIG. 10 shows an example of test code for web_server generated by the test code generation unit 292 .
For the test for web_server, the test code generation unit 292 generates template IDs "1", "2", "3", "6" and "7" are read from the test information illustrated in FIG.

Then, the test code generation unit 292 reads the template of the read template ID from the template information illustrated in FIG.
Further, the test code generator 292 inserts parameter values into the read template according to the rules shown in FIG.
As a result, the test code generator 292 acquires the test code shown in FIG. 10 as the test code for web_server.

Next, operation of the test code generation device 200 will be described with reference to FIG.
FIG. 11 is a diagram showing an example of a processing procedure for the test code generation device 200 to generate test code.
In the process of FIG. 11, the information acquisition unit 291 acquires component element information indicating components of the declarative model (step S101). Specifically, the information acquisition unit 291 analyzes the code of the declarative model (the code of the target system) acquired by the first communication unit 110 from the declarative model orchestration device 100, and extracts the component element information.

Next, the template acquisition unit 293 acquires a test code template for the components of the declarative model (step S102). Specifically, the test code generation unit 292 refers to the test information stored in the test information storage unit 281 to determine the test for the components of the declarative model (components of the target system). Then, the template acquisition unit 293 acquires a test code template linked to the determined test.

Also, the parameter value acquisition unit 294 acquires parameter values to be applied to the template acquired by the template acquisition unit 293 (step S103). Specifically, the parameter value acquisition unit 294 acquires parameter values according to the parameter value acquisition rule linked to the test determined by the test code generation unit 282 .

The parameter value application unit 295 applies the parameter values acquired by the parameter value acquisition unit 294 to the template acquired by the template acquisition unit 293 (step S104). Thereby, the parameter value application unit 295 obtains test code for testing the declarative model.
After step S104, the test code generation device 200 ends the processing of FIG.

As described above, the information acquisition unit 291 extracts the information of the constituent elements of the declarative model from the information of the declarative model. The template acquisition unit 293 acquires a test code template linked to the information of the component. The parameter value acquisition unit 294 acquires parameter values to be applied to the template according to the rules linked to the information on the constituent elements. The parameter value application unit 295 applies the obtained parameter values to the template to acquire test codes.

According to the test code generation device 200, it is possible to automatically generate test code for a system constructed using a declarative model, according to the configuration of the system. In that the test code can be automatically generated, the test code generation device 200 does not require the human burden of generating the test code, nor does it require human skill. Therefore, the test code generation device 200 can avoid a situation in which an appropriate test code cannot be generated due to lack of human skill. In addition, the test code generation device 200 can avoid a situation in which an appropriate test code cannot be generated due to human error.
Thus, according to the test code generation device 200, it is possible to more appropriately test a system constructed using a declarative model.

Further, when the parameter value acquisition rule indicates that the parameter value is required, the parameter value acquisition unit 294 acquires the parameter value from the declarative model orchestration device 100 according to the rule.
As a result, the test code generation device 200 can automatically generate test code corresponding to the case where the parameter value is determined according to the node.

FIG. 12 is a diagram illustrating an example of the configuration of a test code generation device according to the embodiment; A test code generation device 400 shown in FIG. 12 includes an information acquisition unit 401 , a template acquisition unit 402 , a parameter value acquisition unit 403 , and a parameter value application unit 404 .

With such a configuration, the information acquisition unit 401 extracts information about the components of the declarative model from the information about the declarative model. The template acquisition unit 402 acquires a test code template linked to the information of the component. The parameter value acquisition unit 403 acquires parameter values to be applied to the template according to the rules linked to the information on the constituent elements. A parameter value application unit 404 applies the obtained parameter values to the template to acquire test codes.

According to the test code generation device 400, it is possible to automatically generate test code for a system built using a declarative model according to the system configuration. Since the test code can be automatically generated, the test code generation device 400 does not require the human burden of generating the test code, nor does it require human skill. Therefore, the test code generation device 400 can avoid a situation in which an appropriate test code cannot be generated due to lack of human skill. In addition, the test code generation device 400 can avoid a situation in which an appropriate test code cannot be generated due to human error.
Thus, according to the test code generation device 400, it is possible to more appropriately test a system constructed using a declarative model.

FIG. 13 is a diagram illustrating an example of a processing procedure in the test code generation method according to the embodiment; The test code generation method shown in FIG. 13 includes a component element information and server information acquisition step (step S201), a template acquisition step (step S202), a parameter value acquisition step (step S203), and a parameter value application step (step S204).

In the component element information and server information acquisition step (step S201), the component information of the declarative model is extracted from the information of the declarative model. In the template acquisition step (step S202), a template of the test code linked to the information of the component is acquired. In the parameter value acquisition step (step S203), parameter values to be applied to the template are acquired according to the rules linked to the information on the constituent elements. In the parameter value applying step (step S204), the obtained parameter values are applied to the template to obtain the test code.

According to this test code generation method, test code for a system constructed using a declarative model can be automatically generated according to the system configuration. This test code generation method does not require the human burden of generating the test code, nor does it require human skill, in that the test code can be generated automatically. Therefore, with this test code generation method, it is possible to avoid a situation in which an appropriate test code cannot be generated due to lack of human skill. In addition, this test code generation method can avoid a situation in which an appropriate test code cannot be generated due to human error.
Thus, according to this test code generation method, a system constructed using a declarative model can be tested more appropriately.

FIG. 14 is a schematic block diagram showing the configuration of a computer according to at least one embodiment;
With the configuration shown in FIG. 14, computer 700 includes CPU 710 , main storage device 720 , auxiliary storage device 730 , and interface 740 .
Any one or more of the test code generation apparatuses 200 and 400 described above may be implemented in the computer 700 . In that case, the operation of each processing unit described above is stored in the auxiliary storage device 730 in the form of a program. The CPU 710 reads out the program from the auxiliary storage device 730, develops it in the main storage device 720, and executes the above processing according to the program. In addition, the CPU 710 secures storage areas corresponding to the storage units described above in the main storage device 720 according to the program. Communication between each device and another device is executed by the interface 740 having a communication function and performing communication under the control of the CPU 710 .

When the test code generation device 200 is implemented in the computer 700, the operations of the second control unit 290 are stored in the auxiliary storage device 730 in the form of programs. The CPU 710 reads out the program from the auxiliary storage device 730, develops it in the main storage device 720, and executes the above processing according to the program.
Further, the CPU 710 secures a storage area corresponding to the second storage section 280 in the main storage device 720 according to the program. Communication performed by the second communication unit 210 is performed by the interface 740 having a communication function and performing communication according to the control of the CPU 710 .

When the test code generation device 400 is implemented in the computer 700, the operations of the information acquisition unit 401, the template acquisition unit 402, the parameter value acquisition unit 403, and the parameter value application unit 404 are stored in the auxiliary storage device 730 in the form of programs. remembered. The CPU 710 reads out the program from the auxiliary storage device 730, develops it in the main storage device 720, and executes the above processing according to the program.

A program for executing all or part of the processing performed by the test code generation devices 200 and 400 is recorded on a computer-readable recording medium, and the program recorded on this recording medium is read by the computer system, You may process each part by executing. It should be noted that the "computer system" referred to here includes hardware such as an OS and peripheral devices.
In addition, "computer-readable recording medium" refers to portable media such as flexible discs, magneto-optical discs, ROM (Read Only Memory), CD-ROM (Compact Disc Read Only Memory), hard disks built into computer systems It refers to a storage device such as Further, the program may be for realizing part of the functions described above, or may be capable of realizing the functions described above in combination with a program already recorded in the computer system.

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design and the like are included within the scope of the gist of the present invention.

100 declarative model orchestration device 110 first communication unit 180 first storage unit 190 first control unit 191 declarative model orchestrator unit 192 provisioning processing execution unit 200, 400 test code generation device 210 second communication unit 280 second storage Section 290 Second Control Section 291, 401 Information Acquisition Section 292 Test Code Generation Section 293, 402 Template Acquisition Section 294, 403 Parameter Value Acquisition Section 295, 404 Parameter Value Application Section 500 Execution Environment 900 Communication Network

Claims (3)

an information acquisition unit that extracts information about the components of the declarative model from the information about the declarative model;
a template acquisition unit that acquires a test code template linked to the information of the component;
a parameter value acquisition unit that acquires , from a declarative model orchestration device, parameter values to be applied to the template according to a rule that is linked to the information of the component and indicates that the parameter values are requested ;
a parameter value application unit that applies the obtained parameter value to the template to obtain a test code;
A test code generator comprising: the computer
extracting information of the components of the declarative model from the information of the declarative model;
obtaining a test code template linked to the information of the component;
a step of acquiring parameter values to be applied to the template from a declarative model orchestration device, according to a rule linked to the information of the component and indicating a request for parameter values ;
applying the resulting parameter values to the template to obtain test code;
A test code generation method that includes executing to the computer,
extracting information of the components of the declarative model from the information of the declarative model;
obtaining a test code template linked to the information of the component;
a step of acquiring parameter values to be applied to the template from a declarative model orchestration device, according to a rule that is linked to the information of the component and indicates that parameter values are required ;
applying the resulting parameter values to the template to obtain test code;
program to run the

Images