JP6941980B2 - Test scenario execution system and test scenario execution method - Google Patents

Description

The present invention relates to a test scenario execution system and a test scenario execution method.

In the recent development of software such as Web applications, software generated through procedures such as build, test, and deployment is implemented in a computer. Building software is to generate an executable file by compiling the source code. Software testing is the execution of a built executable file to verify its operation. Also, deploying software means placing the tested executable file in the actual usage environment.

When executing a software test as described above, prepare a test scenario that defines the test procedure and a test script for executing the test scenario in advance. Since the test scenario is described in Xpath format, inconsistency occurs when the screen content is changed. In view of such problems, for example, in Patent Document 1, a keyword indicating an object name or the like of an operation target displayed on a Web screen is associated with the position information of the keyword described in the Xpath format. , When a change occurs in the Web screen, the correction part in the test scenario is output by using the above keyword as a key.

Japanese Unexamined Patent Publication No. 2014-106589

In the above-mentioned Patent Document 1, since it is necessary to predetermine a keyword indicating an object name or the like of an operation target displayed on a Web screen, if the user forgets the keyword, it takes time for the correction work as in the conventional case. It will take. Also, if the keyword is not defined, the corrected part cannot be output. Further, since the corrected portion is output separately from the Web screen, the user cannot intuitively grasp the inconsistency of the correspondence with the test scenario when the Web screen content is corrected.

The present invention provides a test scenario execution system and a test scenario execution method that can intuitively grasp the inconsistency between the parts displayed on the Web screen and the test scenario when the Web screen content is modified. The purpose is to provide.

In order to solve the above problems and achieve the object, the test scenario execution system according to the present invention is a test scenario execution system that executes a software scenario test, and is a first screen obtained from the first test scenario. A first processing unit that specifies a difference portion between the content and the second screen content obtained from the second test scenario obtained when the first screen content is modified, and the specified difference portion. , The first screen content or the second screen content is displayed based on the first test scenario or the second test scenario and the first screen content or the second screen content. It is configured as a scenario test execution system characterized by including a second processing unit that displays changed parts on the screen on the display unit.

The present invention is also understood as a test scenario execution method used in the above test scenario execution system.

According to the present invention, it is possible to intuitively grasp the inconsistency of the correspondence with the test scenario when the Web screen content is modified.

It is a figure which shows the configuration example of the test scenario execution system in this embodiment. It is a block diagram which shows the program which a main storage device stores. It is a block diagram which shows the data which an auxiliary storage device stores. It is a figure which shows the example of the screen content. It is a figure which shows the example of the virtualization information. It is a figure which shows the example of the test script. It is a figure which shows the example of the parts list. It is a flowchart which shows the processing procedure of the test scenario execution processing performed in this system. It is a figure which shows the example which displays the position of the changed part, the added part, and the deleted part on the Web screen.

Hereinafter, embodiments of the test scenario execution system and the test scenario execution method according to the present invention will be described in detail with reference to the accompanying drawings.

FIG. 1 is a diagram showing a configuration example of a test scenario execution system according to the present embodiment.
Although FIG. 1 shows an example in which the test scenario execution system is configured inside one computer, it may be configured by a plurality of computers via a network or a bus.

The computer 1000 that constitutes the test scenario execution system is a device used by the user who executes the test. As shown in FIG. 1, the computer 1000 includes a CPU (Central Processing Unit) 110, a main storage device (memory) 120, an input / output device 130, a communication interface 140, and an auxiliary storage device 150. Has been done. Each of these parts constituting the computer 100 is connected by an internal bus.

The CPU 110 is an arithmetic unit that executes a program held in the main storage device 120. The input / output device 130 is a device including an input device such as a keyboard and a mouse that provide a user interface, and a display device such as an LCD (Liquid Crystal Display). The communication interface 140 is a device composed of a communication device such as a NIC (Network Interface Card) that provides a communication interface via a network. The auxiliary storage device 150 is a device including a storage device such as an HDD (Hard Disk Drive) that holds data generated when the program is executed and data used for the program.

FIG. 2 is a block diagram showing a program stored in the main storage device 120.
As shown in FIG. 2, the main storage device 120 stores a browser display unit 1201, a test scenario generation unit 1202, a test script execution unit 1204, and a comparison determination unit 1205.

The browser display unit 1201 outputs the screen content 1501 and the modified screen content 1502 stored in the auxiliary storage device 150 in advance to the display device. The test scenario generation unit 1202 generates a test scenario from the information input from the input device. The test script execution unit 1204 executes the test script and displays the screen content 1501 on the display device. When the test script is executed, the comparison determination unit 1205 compares the latest screen content with the latest screen content and determines the correction portion. The comparison determination unit 1205 functionally has a first processing unit and a second processing unit. The specific processing performed by each of the above parts will be described later. Subsequently, returning to FIG. 1, the auxiliary storage device 150 will be described.

FIG. 3 is a block diagram showing data stored in the auxiliary storage device 150.
As shown in FIG. 3, the auxiliary storage device 150 stores the screen content 1501, the test scenario 1503, the parts list 1504, the correction screen contents 1505, and the correction parts list 1508.

The screen content 1501 is, for example, a document described by XML (Extensible Markup Language) or HTML (HyperText Markup Language). The screen content 1501 displays a Web screen that can be operated by the user on the browser display unit 1201. In the above document, each element is described by the DOM representation. The DOM (Document Object Model) is a specification for accessing each element of xml and html.

FIG. 4 is a diagram showing an example of the screen content 1501.
FIG. 4A is a diagram showing a description example of HTML, and FIG. 4B is a diagram showing a Web screen example described in HTML. As shown in FIG. 4A, the screen content 1501 describes various elements surrounded by tags. FIG. 4B is a diagram showing an example of a Web screen in which the screen content 1501 described in HTML shown in FIG. 4A is displayed in full screen on a display device. As shown in FIG. 4B, the display device displays the screen content 1501 having the title “Excel”. Further, it can be seen that the screen content 1501 includes the input field 1301 and the search button 1302 as parts. The component is a component displayed on a Web screen such as an input field, a button, and a check box.

The test scenario 1503 is a document describing a test procedure of software such as a Web application (hereinafter, simply referred to as a Web application). The test procedure of the Web application is input in advance by the user from the input device and stored in the auxiliary storage device 150.

FIG. 5 is a diagram showing an example of test scenario 1503.
As shown in FIG. 5, the test scenario 1503 describes the test scenario in the Xpath format. In FIG. 6, for example, as a test procedure for shooting a business portal screen, a test scenario in which a user ID (user1) and a password (password) are input on the login screen and the login button is pressed is described in Xpath format and DOM expression. .. The elements described in the test scenario 1503 are associated with the Xpath format and DOM representation of the elements in advance.

As shown in FIG. 6, the test scenario 1503 may be described not only by specifying Xpath but also by specifying id, or a mixture of these may be described. In FIG. 6, for example, as step 1, top. After opening html, enter "user1" in the input field (input) as step 2, press the button (button) as step 3, and URL (Uniform Resource Locator) is "http: // xxx /" as step 4. "Resource.html" is displayed as the search result, and user1 @ mail. It is described to display com. In FIG. 5, it can be seen that the operation for the input field 1301 and the search button 1302 shown in FIG. 4 is included in the test scenario.

The parts list 1504 is a list showing the correspondence between parts used in the test scenario and screen contents.

FIG. 7 is a diagram showing an example of the parts list 1504.
As shown in FIG. 7, the component list 1504 includes a component representation that is a component described in the test scenario 1503, a component position that is a position in the screen content 1501 of the component, and a DOM representation that is the DOM of the component. An image piece, which is an image when the component is displayed on the screen content 1501, is stored in association with the image piece. In FIG. 7, for example, in the test scenario 1503, button [id = search] is described as a part representation, the button which is the part is arranged at the coordinates (x1, y1) of the screen content 1501, and the size of the button is width w1. It can be seen that the height is h1. Further, it can be seen that the DOM representation of this part is defined by the <button> search </ button>, and the screen content 1501 displays the image α representing the part. The parts list 1504 is automatically created at the time of performing the test and stored in the auxiliary storage device 150.

The modified screen content 1505 and the modified component list 1508 are the latest version of the screen content 1501 and the component list 1504 after being modified by the user, respectively. Since the modified screen content 1505 and the modified parts list 1508 are the same as the screen contents 1501 and the parts list 1504, respectively, the description thereof will be omitted here.

In this example, the modification screen content 1505 and the modification component list 1508 are stored one by one, but these files may be retained in chronological order each time they are changed. By storing these files each time they are changed, it is possible to retroactively identify the changed part. Next, the processing performed by this system will be described.

FIG. 8 is a flowchart showing a processing procedure of the test scenario execution process performed in this system. In the following, it is assumed that the test scenario generation unit 1202 generates the test scenario 1503 by the operation from the user, then the screen content 1501 and the test scenario 1503 are changed, and the modified screen content 1505 is stored.

As shown in FIG. 8, in the test scenario execution process, the first processing unit of the comparison determination unit 1205 compares the screen content 1501 with the modified screen content 1505 and determines whether or not there is a difference in the HTML. (Step S801). For example, in the first processing unit of the comparison determination unit 1205, if the DOM expression of the screen content 1501 is changed, added, or deleted, the changed, added, or deleted portion becomes the difference portion on the HTML.

When the first processing unit of the comparison determination unit 1205 compares the screen content 1501 and the correction screen content 1505 and determines that there is a difference in HTML (step S801; Yes), the test script execution unit 1204 is all. It is determined whether or not the following processing has been executed for the difference portion of (step S802). When the first processing unit of the comparison determination unit 1205 compares the screen content 1501 and the correction screen content 1505 and determines that there is no difference in HTML in the test script execution unit 1204 (step S801; No). , End this process without doing anything.

When the test script execution unit 1204 determines that the following processing has not been executed for all the difference points (step S802; No), the second processing unit of the comparison judgment unit 1205 makes a difference from the unprocessed difference points. The parts to be used are specified, and it is determined whether or not the specified parts are in the parts list 1504 or the modified parts list 1508 (steps S803 and S804). For example, the second processing unit of the comparison determination unit 1205 determines the difference portion from the HTML shown in FIG. 4A, represents the difference portion, and represents the DOM of the parts list 1504 shown in FIG. 7. And, it is determined whether or not there is a matching DOM expression, and if it is determined that there is a matching DOM expression, it is determined that the difference part is a difference due to a part, and the component that is the difference is specified. ..

When the second processing unit of the comparison determination unit 1205 determines that the component to be the difference is in the component list 1504 or the modified component list 1508 on HTML (step S804; Yes), the component representation corresponding to the component is further performed. Is in the test scenario (step S805). For example, the second processing unit of the comparison determination unit 1205 reads and reads the component representation corresponding to the DOM representation of the component specified in step S803 with reference to the component list 1504 or the modified component list 1508 shown in FIG. The test scenario 1503 is referred to by using the expression as a key, and it is determined whether or not the component expression used as the key is included in the test scenario 1503.

When the second processing unit of the comparison determination unit 1205 determines that the component representation corresponding to the component is included in the test scenario 1503 (step S805; Yes), the component representation is used in the test scenario 1503. It is determined that the part is represented (changed part) (step S806), and the browser display unit 1201 displays the description part of the part in the test scenario and the part position of the part on the Web screen (first). (Display) (step S807). A display example will be described later with reference to FIG. The component positions are, for example, component positions corresponding to the DOM representation specified in step S803 and the component representation keyed in step S805 in the component list 1504 shown in FIG. 7.

When the second processing unit of the comparison determination unit 1205 determines that the component representation corresponding to the component is not in the test scenario (step S805; No), the component representation is not used in the test scenario 1503 (step S805; No). It is determined that the component is a modified component (step S808), and the browser display unit 1201 displays the component position of the component on the Web screen (second display) (step S809). A display example will be described later with reference to FIG. The component positions are, for example, component positions corresponding to the DOM representation specified in step S803 and the component representation keyed in step S805 in the component list 1504 shown in FIG. 7.

In step S804, when the second processing unit of the comparison determination unit 1205 determines that the component to be the difference on the HTML is not in the component list 1504 or the modified component list 1508 (step S804; No), the component is further added. It is determined whether or not the corresponding component representation is in the test scenario (step S810). Since the determination method is the same as in step S805, the description thereof will be omitted here.

When the second processing unit of the comparison determination unit 1205 determines that the component representation corresponding to the component is in the test scenario (step S810; Yes), the component representation is the component representation used in the test scenario 1503 (step S810; Yes). (Step S811), the browser display unit 1201 displays the description location of the part in the test scenario and the part position of the part on the Web screen (third display). (Step S812). A display example will be described later with reference to FIG. The component positions are, for example, component positions corresponding to the DOM representation specified in step S803 and the component representation keyed in step S805 in the component list 1504 shown in FIG. 7.

When the second processing unit of the comparison determination unit 1205 determines that the component representation corresponding to the component is not in the test scenario (step S810; No), the component representation is not used in the test scenario 1503 (step S810; No). It is determined that the component is a new component (step S813), and the browser display unit 1201 displays the component position of the component on the Web screen (fourth display) (step S814). A display example will be described later with reference to FIG. The component positions are, for example, component positions corresponding to the DOM representation specified in step S803 and the component representation keyed in step S805 in the component list 1504 shown in FIG. 7.

In step S802, when the second processing unit of the comparison determination unit 1205 determines that the following processing has been executed for all the difference points (step S802; Yes), the parts list 1504 and the correction parts list 1508 are compared. , A component that does not exist in the modified component list 1508 is determined to be a lost component (step S815). For example, when the image piece of the parts list 1504 is not stored in the image piece of the modified parts list 1508, the comparison determination unit 1205 determines that the part displayed by the image piece has been deleted.

Then, the browser display unit 1201 displays (fifth display) the position of the component on the Web screen determined to be the lost component (step S816). A display example will be described later with reference to FIG. The component positions are, for example, component positions corresponding to the DOM representation specified in step S803 and the component representation keyed in step S805 in the component list 1504 shown in FIG. 7. When the process of step S816 is completed, the test scenario execution process shown in FIG. 8 is completed.

FIG. 9 is a diagram showing an example of displaying the positions of changed parts, additional parts, and deleted parts on a Web screen. As shown in FIG. 9, on the Web screen, the component positions indicating the changed parts determined in steps S806 and S808, the new parts determined in steps S811 and S813, and the deleted parts determined in step S815 are displayed. There is.

In FIG. 9, since the display position of the input field 1301 shown in FIG. 4B has been changed, the input field 1301 displayed at the part position of the parts list 1504 shown in FIG. 7 is a dotted line as the input field 1301A. It shows that it is displayed as a rectangle. Further, since the DOM expression of the search button 1302 has been changed to "search execution", the search button 1302 displayed at the part position of the parts list 1504 shown in FIG. 7 is used as the search button 1302A and is of the same type as the input field 1301A. It shows that it is displayed as a dotted rectangle.

Further, since the input field 1301 and the search button 1302 are also used for the scenario test, in the test scenario 1503 shown in FIG. 5, the part representation corresponding to the DOM representation of the parts list 1504 shown in FIG. 7 is used. , Is surrounded by a dotted rectangle of the same type as the input field 1301A and the search button 1302A. As described above, in step S807 of FIG. 8, the Web screen and the test scenario in which the changed parts are clearly shown are displayed on the display device. Regarding the display method, for example, by displaying the Web screen in which the changed parts are clearly shown and the test scenario in which the changed parts are shown in parallel on the display device, the user can display the changed parts on the Web screen and the test scenario. You can see at a glance which parts need to be changed above.

Further, in FIG. 9, since the display position of the text 1303 shown in FIG. 4B has been changed, the text 1303 displayed at the component position stored in the component list 1504 is represented by a solid rectangle as the text 1303A. Indicates that it is displayed. The text 1303 is not used for the scenario test. Therefore, in step S809 of FIG. 8, a Web screen in which the changed parts are clearly displayed is displayed on the display device. Regarding the display method, for example, by displaying the Web screen in which the changed parts are specified and the test scenario in which the changed parts are not specified in parallel on the display device, the user can test the changed parts on the Web screen. You can see at a glance that there are no parts that need to be changed in the scenario.

Further, in FIG. 9, since the text 1304 that was not displayed in FIG. 4B is displayed, it is shown that the text 1304 is displayed as the text 1304 at the component position in the component list 1504 as a double-line rectangle. There is. Further, since the text 1304 is also used for the scenario test, in the test scenario 1503, the part representation corresponding to the DOM representation of the parts list 1504 is surrounded by a double-line rectangle similar to the text 1304. As described above, in step S812 of FIG. 8, the Web screen and the test scenario in which the newly added parts are clearly displayed are displayed on the display device. Regarding the display method, for example, by displaying the Web screen in which the additional parts are specified and the test scenario in which the additional parts are specified in parallel on the display device, the user can display the additional parts on the Web screen and the test scenario. You can see at a glance which parts need to be added above.

Further, in FIG. 9, since the text 1305 that was not displayed in FIG. 4B is displayed, the text 1305 is displayed as the text 1305 in the rectangular shape of the alternate long and short dash line at the component position stored in the component list 1504. Is shown. The text 1303 is not used for the scenario test. Therefore, in step S814 of FIG. 8, a Web screen in which newly added parts are clearly indicated is displayed on the display device. Regarding the display method, for example, by displaying the Web screen in which the additional parts are specified and the test scenario in which the additional parts are not specified in parallel on the display device, the user can test the changed parts on the Web screen. You can see at a glance that there are no parts that need to be added in the scenario.

Further, in FIG. 9, since the text 1306 displayed in FIG. 4B has been deleted and is no longer displayed, the rectangular chain line rectangle as the text 1306A at the original component position stored in the component list 1504. Indicates that it is displayed as.

As for the deleted parts, the Web screen and the test scenario can be displayed in parallel in the same manner as the gun rest changing parts and the additional parts depending on whether or not they are used in the scenario test.

For example, when the text 1306 is used for the scenario test, the part representation corresponding to the DOM representation of the parts list 1504 is surrounded by a two-dot chain rectangle of the same type as the text 1306. In this way, the Web screen and the test scenario in which the deleted parts are clearly displayed are displayed on the display device. For example, by displaying the Web screen in which the additional parts are specified and the test scenario in which the additional parts are specified in parallel on the display device, the user can delete the deleted parts on the Web screen and the test scenario. You can check at a glance which parts are required.

When the text 1306 is not used in the scenario test, a Web screen clearly showing the deleted parts is displayed on the display device. For example, by displaying the Web screen in which the deleted parts are specified and the test scenario in which the deleted parts are not specified in parallel on the display device, the user can delete the changed parts on the Web screen and the test scenario. It can be confirmed at a glance that there are no parts that require.

As described above, in this system, by executing the test scenario execution process as described above, it is possible to intuitively grasp the inconsistency of the correspondence with the test scenario when the Web screen content is modified. ..

That is, in the test scenario execution system that executes the scenario test of the software, the first processing unit constituting the comparison determination unit 1205 selects the screen content before modification and the screen content before modification obtained from the test scenario before modification. The difference part with the modified screen content obtained from the modified test scenario obtained at the time of modification is specified, and the second processing unit constituting the comparison judgment unit 1205 is the specified difference part and the uncorrected difference part. Based on the test scenario of the test scenario or the test scenario after the modification and the screen content before the modification or the screen content after the modification, the display part displays the changed part on the screen displayed by the screen content before the modification or the screen content after the modification. Since it is displayed in, the above-mentioned inconsistent part can be easily grasped.

Further, the second processing unit includes a parts list before modification in which the parts included in the screen content before modification and the positions of the parts are associated with each other, or a parts included in the screen content after modification and the positions of the parts. Based on the modified parts list associated with, the position of the component in the screen content before modification or the screen content after modification, and the description part of the component in the test scenario before modification or the test scenario after modification. Since it is displayed on the display unit, it is possible to easily determine whether the difference part of the screen content is caused by the correction of the part, and if the difference part is caused by the correction of the part, the corresponding scenario Parts can be easily found.

The second processing unit determines whether or not the component of the description location is described by the DOM pseudo-class nth-child representation, and the component of the description location is described by the nz-child representation. If it is determined that the parts have been described, the parts described by other nth-child expressions may be searched and displayed on the display unit together with the above-mentioned description parts as parts to be changed. For example, when the description of a certain part is changed from nth-child (even) to nth-child (odd), the description of another part is changed from nth-child (odd) to nth-child (even). As shown above, it may be displayed on the display unit. With such a display, the user can easily grasp the part described in the nth-child representation related to the modified part and how to modify it.

Further, the second processing unit determines whether or not the part of the description location is described in the Xpath format, and when it is determined that the component of the description location is described in the Xpath format, the second processing unit of the description location A modified proposal in which the description is modified to a description in another format corresponding to the above-mentioned Xpath format defined in advance may be displayed on the display unit. For example, the parts described in the Xpath format are rewritten to other formats such as the id format and the nth-of-type format. Regarding what kind of format to rewrite, it is sufficient to register in advance a format that is considered to be highly convenient for the user.

In addition, the second processing unit is the screen content before modification or the screen content after modification in which the same parts as the parts described above are described from among the plurality of screen contents before modification or screen content after modification. May be specified, and the description portion of the same part of the specified screen content before modification or screen content after modification may be displayed on the display unit. For example, using a part included in the screen content before modification as a key, search for other screen content before modification that uses the same component as that part, and display the screen content and its description on the screen. .. By performing such a display, the user can easily grasp the screen content and its position that need to be modified as well.

In addition, the second processing unit includes a component position or component description location indicating the difference location caused by the change of the component, and a component position or component description location indicating the difference location caused by the addition of the component. And the position of the part indicating the difference point caused by the deletion of the part or the description part of the part, for example, as shown in FIG. 9, line types different from each other as shown in the first display to the fifth display. Display with. Therefore, the user can grasp at a glance whether the modification of the part is due to a change, an addition, or a deletion.

For example, the second processing unit determines whether or not the difference portion is a part included in the parts list before modification or the parts list after modification, and the difference portion is the parts list before modification or after modification. If it is determined that the part is included in the parts list of, it is determined whether or not the part is used in the test scenario before modification or the test scenario after modification, and the part is in the test scenario before modification or after modification. If it is determined that it is used in the test scenario of, the part of the part is displayed in the screen content before modification or the screen content after modification, and the test scenario before modification or test scenario after modification. If it is determined that the part is not used in the test scenario before modification or the test scenario after modification, the part of the component is displayed in the screen content before modification or the screen content after modification. Perform a second display.

Further, when the second processing unit determines that the difference portion is not a part included in the parts list before modification or the parts list before modification, the relevant part is set to the test scenario before modification or the test scenario after modification. If it is determined whether or not the part is used and it is determined that the part is used in the test scenario before modification or the test scenario after modification, the screen content before modification or the screen content after modification and the modification When a third display is executed to display the location of the part in the previous test scenario or the modified test scenario, and it is determined that the component is not used in the unmodified test scenario or the modified test scenario. Executes a fourth display for displaying the portion of the component in the screen content before the modification or the screen content after the modification.

Further, the second processing unit determines whether or not there is a part that does not exist in either the parts list before the correction or the parts list after the correction, and determines that there is a part that does not exist in any of them. , The fifth display for displaying the location where the component exists in the screen content before the modification or the screen content after the modification is executed.

Therefore, by executing these display processes, it is possible to easily grasp whether or not the component needs to be modified not only in the screen content but also in the test scenario.

Each process executed in this system is actually realized by executing a program installed in the device. The above program may be provided by being embedded in a ROM or the like in advance, or may be recorded and provided on a recording medium in an installable format or an executable format file, or may be distributed.

1000 computer 110 CPU
120 Main storage device (memory)
1201 Browser display unit 1202 Test scenario generation unit 1204 Test script execution unit 1205 Comparison judgment unit 130 Input / output device 140 Communication interface 150 Auxiliary storage device 1501 Screen content 1503 Test scenario 1504 Parts list 1505 Modified screen content 1508 Modified parts list.

Claims (7)

A test scenario execution system that executes software scenario tests.
A first that identifies a difference between the first screen content obtained from the first test scenario and the second screen content obtained from the second test scenario obtained when the first screen content is modified. Processing part and
The first screen content or the first screen content based on the identified difference portion, the first test scenario or the second test scenario, and the first screen content or the second screen content. A second processing unit that displays the changed part on the screen displayed by the screen content of 2 on the display unit, and
A scenario test execution system characterized by being equipped with. The second processing unit determines whether or not the component of the description portion in the first test scenario or the second test scenario is described by the nth-child representation which is a pseudo class of DOM (Document Object Model). When the determination is made and it is determined that the part described by the description part is described by the nth-child expression, the part described by another ntth-child expression is searched and displayed as a part to be changed together with the description part. Display in the section,
The scenario test execution system according to claim 1. The second processing unit determines whether or not the component of the description portion in the first test scenario or the second test scenario is described in the Xpath format, and the component of the description portion is described in the Xpath format. If it is determined that the description has been made, a proposed change in which the description of the part is modified to the description of another format corresponding to the predetermined Xpath format is displayed on the display unit.
The scenario test execution system according to claim 1 or 2. In the second processing unit, the same parts as the parts described in the first test scenario or the second test scenario are described from among the plurality of the first screen contents or the second screen contents. The first screen content or the second screen content is specified, and the description portion of the same component of the specified first screen content or the second screen content is displayed on the display unit.
The scenario test execution system according to any one of claims 1 to 3. The second processing unit includes a first parts list in which a part included in the first screen content and a position of the part are associated with each other, or a part included in the second screen content and a position of the part. The position of the component in the first screen content or the second screen content and the component in the first test scenario or the second test scenario based on the second component list associated with the above. Is displayed on the display unit.
The scenario test execution system according to any one of claims 1 to 4, wherein the scenario test execution system is characterized. The second processing unit is the position of the component or the description location of the component indicating the difference portion caused by the change of the component, and the position of the component indicating the difference portion caused by the addition of the component or the said portion. The description part of the part and the position of the part indicating the difference part caused by the deletion of the part or the description part of the part are displayed differently from each other.
The scenario test execution system according to claim 5. A test scenario execution method in which a computer executes a software scenario test.
The processor of the computer
The difference between the first screen content obtained from the first test scenario and the second screen content obtained from the second test scenario obtained when the first screen content is modified is specified.
The first screen content or the first screen content based on the identified difference portion, the first test scenario or the second test scenario, and the first screen content or the second screen content. Display the changed part on the screen displayed by the screen content of 2 on the display part,
Scenario test run wherein a call.

Images