JP7534865B2 - Test automation equipment - Google Patents

Description

The present invention relates to a test automation device.

In order to prevent omissions in test scenarios and increase the comprehensiveness of tests, a method is known in which tests are designed in the form of a tabular program checklist and then tested based on this. To automate tests that involve screen operations using a tabular program checklist, steps 1 to 3 below are required.

In step 1, a test script is created manually while referring to a tabular program checklist. In step 2, the test script is automatically executed by an automatic screen test tool. In step 3, the output results are referred to and entered in the tabular program checklist. At this time, steps 1 and 3 are performed manually. For example, Patent Document 1 describes technology related to automatic test tools.

JP 2001-256077 A

In the above conventional technology, test scripts are created manually. This poses issues related to the burden of acquiring knowledge about how to write test scripts, the burden of creating test scripts, and the accuracy of accurately reflecting the contents of the program checklist in the test script. Another issue is the labor required to reflect the output results in a tabular program checklist.

The object of the present invention is to automatically execute screen automation tests using a tabular program checklist in a test automation system.

The test automation device of one aspect of the present invention is characterized by having a test script analysis unit that analyzes test script character strings written in a test script, a program checklist generation unit that formats the analyzed test script character strings into a tabular program checklist having a test scenario, a screen automation test tool unit that executes a screen automation test tool based on the test script and outputs an execution result file, an execution result file analysis unit that analyzes the execution result file, and a test result reflection unit that reflects the analysis results of the execution result file in the program checklist.

The test automation device of one aspect of the present invention is characterized by having a test script generation unit that generates a test script by extracting test script character strings from a tabular program checklist in which a test scenario is described, a screen automation test tool unit that executes a screen automation test tool based on the generated test script and outputs an execution result file, an execution result file analysis unit that analyzes the execution result file, and a test result reflection unit that reflects the analysis result of the execution result file in the program checklist.

According to one aspect of the present invention, a test automation system can automatically perform screen automation testing using a tabular program checklist.

FIG. 1 illustrates an overall configuration of a test automation system. FIG. 4 is a flow chart showing the operation of the test automation device according to the embodiment. FIG. 2 is a conceptual diagram showing the operation of the test automation device according to the embodiment. FIG. 4 is a flow chart showing the operation of the test automation device according to the embodiment. FIG. 2 is a conceptual diagram showing the operation of the test automation device according to the embodiment. FIG. 13 is a diagram illustrating an example of the contents of a test script. FIG. 13 is a diagram showing the contents of a program checklist in table format. FIG. 13 is a diagram showing a correspondence table between a tabular program checklist and a test script. FIG. 11 is a diagram showing the correspondence between a tabular program checklist and a test script. FIG. 13 is a diagram showing the contents of an execution result file. FIG. 13 is a diagram showing the contents of a program checklist with results recorded. FIG. 13 is a diagram showing a correspondence table between an execution result file and a tabular program checklist with results entered therein. FIG. 11 is a diagram showing the correspondence between the execution result file and a tabular program checklist with results entered therein.

The following describes the examples using the drawings.

Figure 1 shows the overall configuration of a test automation system. The test automation system converts test scripts to tabular program checklists and vice versa.

The test automation system has an application execution terminal 100 and a test automation device 200. The application execution terminal 100 and the test automation system device 200 are connected via a network 300. The application execution terminal 100 has a program 110.

The test automation device 200 has a storage device 210, a computing device 220, a memory 230, an input device 240, and a display device 250. The storage device 210 has a screen automatic test tool unit 211, a test script analysis unit 212, a program checklist generation unit 213, an execution result file analysis unit 214, a test result reflection unit 215, and a test script generation unit 216.

The storage device 210 also stores a test script 260 (see FIG. 6), a tabular program checklist 261 (see FIG. 7), an execution result file 262 (see FIG. 10), a program checklist with results 263 (see FIG. 11), and browser element data 264.

The operation of the test automation device of the embodiment will be described with reference to FIG.
A test script 260, browser element data 264, an execution result file 262, and a tabular program checklist 261 are input via the input device 240 in FIG.
A tabular program checklist 261, an execution result file 262, and a result-described program checklist 263 are output via the display device 250 in FIG.

Next, the process flow will be described.
In process 1, the test script analysis unit 212 reads the test script 260 and the browser element data 264 and analyzes the test script character string (S201).
In process 2, the program checklist generating unit 213 formats and generates the character string analyzed by the test script analyzing unit 212 into a tabular program checklist 261 (S202). Here, FIG. 9 shows the correspondence between the tabular program checklist 261 in the test script analyzing unit 212 and the test script 260.
In process 3, the screen automatic test tool unit 211 executes the screen automatic test tool and outputs the execution result file 262 (S203).
In process 4, the execution result file analysis unit 214 reads and analyzes the execution result file 262 (S204).
In process 5, the test result reflection unit 215 writes the analyzed execution results in a tabular program checklist 261 (S205). Figure 11 shows the contents of the program checklist 263 with results written in it. In the third line of the confirmation contents in Figure 11, when the scenario name is PCL-003, an x mark is written indicating that the result is "failure". Figure 13 shows the correspondence between the execution result file 262 in the test result reflection unit 215 and the tabular program checklist 263 with results written in it.

The contents of the program checklist 263 with results entered are displayed on the display device 250. The user checks the contents of the program checklist 263 with results entered displayed on the display device 250. If an X mark is entered indicating that the result is "failed," the user, for example, modifies the program 110 of the application execution terminal 100 in FIG. 1 and performs the test again.

A usage image in which a test script is input will be described with reference to FIG.
First, the user prepares a test script 260 and browser element data 264 as a pre-processing step.
Next, in processes 1 and 2, a tabular program checklist 261 is generated using the test script 260 and the browser element data 264.
Next, in process 3, an execution result file 262 is generated based on the test script 260 using the screen automatic test tool of the screen automatic test tool unit 211.
Next, in processes 4 and 5, the tabular program checklist 261 and the execution result file 262 are used to generate a result-described program checklist 263.

The operation of the test automation device of the embodiment will be described with reference to FIG.
A tabular program checklist 261, a test script 260, browser element data 264, an execution result file 262, and the tabular program checklist 261 are input via the input device 240 in FIG.
A test script 260, an execution result file 262, and a program checklist with results 263 are output via the display device 250 in FIG.

Next, the process flow will be described.
In process 1, the test script generation unit 216 reads the tabular program checklist 261 and generates a test script character string (S401).
In process 2, the screen automatic test tool unit 211 executes the screen automatic test tool and outputs the execution result file 262 (S402).
In process 3, the execution result file analysis unit 214 reads the execution result file 262 and analyzes the execution result file 262 (S403).
In process 4, the test result reflection unit 215 writes the analyzed execution results in the program checklist 261 in tabular form (S404).

Figure 11 shows the contents of the program checklist with results 263. In the third line of the confirmation contents in Figure 11, when the scenario name is PCL-003, an X is written to indicate that the result is "failure." Figure 13 shows the correspondence between the execution result file 262 in the test result reflection unit 215 and the tabular program checklist with results 263.

The contents of the program checklist 263 with results entered are displayed on the display device 250. The user checks the contents of the program checklist 263 with results entered displayed on the display device 250. If an X mark is entered indicating that the result is "failed," the user, for example, modifies the program 110 of the application execution terminal 100 in FIG. 1 and performs the test again.

Referring to Figure 5, we will explain how to use the system with a tabular program checklist as input.

First, the user prepares a tabular program checklist 261 and browser element data 264 as pre-processing.
Next, in process 1, a test script 260 is generated using the tabular program checklist 261.
Next, in process 2, an execution result file 262 is generated based on the test script 260 using the screen automatic test tool of the screen automatic test tool unit 211.
Next, in processes 3 and 4, the tabular program checklist 261, the browser element data 264, and the execution result file 262 are used to generate a program checklist 263 with results described therein.

FIG. 6 is a diagram showing an example of the description content of the test script 260. As shown in FIG.
FIG. 6 illustrates an example of a library search operation.

As a prerequisite (Background), set the browser size to (1200, 800) and open "/ja/login/" in the browser.

In the case of scenario (PCL-001), a search is performed for "books".
In this case, as the "check conditions", press the "Login" button, then press "book-search. Book search". Then, enter "Book" in "book-search. Book name". Next, press the "Search" button.

As the "confirmation content", confirm that the first item in "book-search.book list" is "History of Libraries, Volume 1."
As the "Post-condition", press "book-search.main menu".

In the case of scenario (PCL-002), a search is performed for "author".
In this case, as the "check condition", press the "Login" button, then press "book-search.Book search". Then, enter "Author" in "book-search.Book name". Next, press the "Search" button.

As the "confirmation content", confirm that the first item in "book-search.book list" is "Author's History, Volume 1."
As the "Post-condition", press "book-search.main menu".

In the case of scenario (Scenario: PCL-003), a search is performed by "Name".
In this case, as the "check condition", press the "Login" button, then press "book-search. Book search". Then, enter your "Name" in "book-search. Book name". Next, press the "Search" button.

As the "confirmation content", confirm that the first item in "book-search.book list" is "History of Names, Vol. 1."
As the "Post-condition", press "book-search.main menu".

FIG. 7 is a diagram showing the contents of the program checklist 261 in table format.
In FIG. 7, a library search operation will be described as an example.

The "test scenario description" describes the prerequisites, check conditions, confirmation contents, and post-conditions.

The prerequisite states that the browser size is set to (XX, △△). In this case, "XX" is 1200 and "△△" is 800.

The prerequisite also states that "XX" should be opened in a browser. In this case, "XX" is "/ja/login/".

The check condition is to press the "XX" button. In this case, "XX" is "Login".

The check condition is also written as "press XX". In this case, XX is "book-search. Book search".

The check condition states that "△△" is entered into "〇〇". In this case, "〇〇" is "book-search.Book name". "△△" is "Book", "Author", and "Name".

The check condition is also written as "press the "〇〇" button. In this case, "〇〇" is "search."

The confirmation details state that "XX" is "△△" and ◎◎. In this case, "XX" is "book-search. Book listing number 1." "△△" is "The History of Libraries, Vol. 1," "The History of Authors, Vol. 1," and "The History of Names, Vol. 1." "◎◎" means "there is."

The post-condition is written as "press XX". In this case, XX is "book-search.main-menu".

On the right side of the program checklist, a search is described for "Books" in the scenario (Scenario: PCL-001). A search is also described for "Authors" in the scenario (Scenario: PCL-002). A search is also described for "Names" in the scenario (Scenario: PCL-003).

Figure 8 shows a correspondence table between the tabular program checklist 261 and the test script 260 in the test script analysis unit 212 and the test script generation unit 216.

The correspondence table contains the number, a tabular program checklist, a test script, and description content.

Number 1 describes "a set of test cases for one function" as the sheet, feature, and description. Number 2 describes "a set of operations for one test case" as the column, scenario, and description.

Number 3 contains the prerequisite line, Background, and the description "prerequisites for the test case." Number 4 contains the check condition line, the step before the Then step, and the description "input conditions and screen operation contents for the test case."

Number 5 contains a confirmation content line, a Then step, and the description "Test case verification items." Number 6 contains a post-condition line, the step after the Then step, and the description "Screen operations to be performed before the test case ends."

FIG. 10 is a diagram showing the contents of the execution result file 262. As shown in FIG.
As shown in FIG. 10, the execution result file includes a feature name, a scenario name, a result, a failed line, an execution date and time, and a browser.

For example, if the feature name is PCL and the scenario name is PCL-001, the result is "Success", the execution date and time is "2019/10/01", and the browser is "Browser A".

Also, if the feature name is PCL and the scenario name is PCL-003, the result is "Failed", the failed line is "7", the execution date and time is "2019/10/01", and the browser is "Browser A".

FIG. 12 shows a correspondence table between the execution result file 262 and the tabular program checklist 263 with results entered in it in the test result reflecting section 215.
As shown in FIG. 12, the correspondence table includes a number, a result file, and a tabular program checklist with results entered.

For example, in number 1, the result file is the feature name and the tabular program checklist with results is the sheet. In number 2, the result file is the scenario name and the tabular program checklist with results is the column.

In number 3, the result file is the result, and the tabular program checklist with results is whether or not to change the "O" in each column to an "X." In number 4, the result file is the failure row, and the tabular program checklist with results is the position to change the "O" in each column to an "X."

In number 5, the result file is the execution date and the tabular program checklist with the results is the check date. In number 6, the result file is the browser and the tabular program checklist with the results is the browser.

In this manner, in the above embodiment, the test scenario described in the tabular program checklist 261 and the test script 260 required to execute the automatic screen test are automatically converted into each other. In addition, the automatic screen test is executed from the tabular program checklist 261, and the execution results are recorded in the tabular program checklist 261.

According to the above embodiment, among the procedures for automatic screen testing using the tabular program checklist 261, the procedure for creating a test script 260 while referring to the tabular program checklist 261 and the procedure for entering the results in the tabular program checklist 261 while referring to the output results can be automatically executed.

This reduces the burden on the screen automatic test creator of acquiring knowledge of how to write the test script 260 and the burden on the creator of the test script 260. It also improves the accuracy with which the contents of the tabular program checklist 261 are reflected in the test script 260. It also reduces the amount of work required for the test result writer to reflect the output results in the tabular program checklist 261.

100 Application execution terminal 110 Program 200 Test automation device 300 Network 210 Storage device 211 Screen automatic test tool section 212 Test script analysis section 213 Program checklist generation section 214 Execution result file analysis section 215 Test result reflection section 216 Test script generation section 220 Arithmetic device 230 Memory 240 Input device 250 Display device 260 Test script 261 Tabular program checklist 262 Execution result file 263 Result-described program checklist 264 Browser element data

Claims (4)

a test script analysis unit that analyzes a test script character string written in a test script;
a program checklist generation unit that formats the analyzed test script character string into a tabular program checklist having a test scenario;
a test script generation unit that extracts the test script character string from the program checklist in which the test scenario is described and generates the test script;
a screen automatic test tool unit that executes a screen automatic test tool based on the test script and outputs an execution result file;
an execution result file analysis unit that analyzes the execution result file;
a test result reflecting unit that reflects an analysis result of the execution result file in the program checklist;
having
A test automation device which converts the test script and the program checklist into each other . The program checklist generation unit,
2. The test automation device according to claim 1, wherein the test script character string described in the test script is converted into the test scenario and described in the program checklist. The execution result file includes:
For each of the test scenarios, success or failure information is described as an execution result;
The test result reflection unit is
2. The test automation device according to claim 1, wherein the success information or the failure information is written in the program checklist, thereby reflecting the analysis result of the execution result file in the program checklist. The test script generation unit
2. The test automation device according to claim 1 , wherein the test scenario described in the program checklist is converted into the test script character string and described in the test script.

Images