JP6006577B2 - Degradation test support system, degradation test support method, and degradation test support program - Google Patents

Description

  The present invention relates to a degradation test support system, a degradation test support method, and a degradation test support system capable of testing a degradation in which the quality of the computer software is worse than that before the upgrade, or a defect or bug that has been corrected and revived. The present invention relates to a degradation test support program, and more particularly, to a degradation test support system, a degradation test support method, and a degradation test support program that can reduce the degradation test work man-hours and the investigation labor when a degradation occurs.

  In general, degrading means that when software is upgraded, the quality will be worse than before the upgrade, or defects and bugs that have been corrected will be recurred or revived. A degradation test is conducted to test whether or not.

  Documents describing the technology relating to the degradation test include the following Patent Documents 1 and 2, which include a step of executing a program before and after improvement, an execution result of the program before improvement, and its journal. Are stored in the pre-improvement DB (database) and the pre-improvement journal, the execution results of the post-improvement program and the journal are stored in the post-improvement DB (database) and the post-improvement journal, and the DB and journal before and after the improvement. A step of determining whether there is a mismatched data item name in the created improved item content DB as a result of the comparison, a step of issuing a warning when it is determined that there is a mismatched data item name, An error is displayed when it is determined that the mismatched data item name is not in the data item to be improved By executing the DB key, the data item names before and after the program improvement, and the step of outputting the contents before and after the program improvement to the degradation determination result file, the presence or absence of degradation of the program in the program before and after the improvement is efficiently verified and confirmed. The technology is described, and in Patent Document 2, the original software before the upgrade is installed in the first computer system, the inspector performs a test using the keyboard and the mouse, and the test result is converted and displayed on the display unit. Then, the test procedure and test results obtained in this way are converted and stored as an electronic file in the first computer system. If a bug is detected, the bug related information collected in the third computer system is stored in the second computer system. The original software by When learning the test contents and performing the same test by installing the upgrade software in the first computer system, the test procedure as the learning result is read and an automatic test is performed. It describes the technology to check by comparing with the test results, and to use the bug related information when detecting bugs.

JP 2005-276040 A JP-A-8-212108

  The technique described in Patent Document 1 can efficiently verify and confirm whether the program is degraded in the program before and after the modification. The technique described in Patent Document 2 converts the test contents of the program before and after the modification into an electronic file. Although it is possible to efficiently check for degradation detection, it is not considered to confirm the timing of occurrence of degradation or the location where degradation occurs, and there is a problem that it is necessary to review the program design document and analyze the source. It is not considered to check the module that refers to the method in which the error occurred, and there is a problem that there is a possibility that a leak may occur in specifying the affected range.

  In particular, in recent years, there has been an increasing demand for quick delivery and high quality in system development projects. Among them, renovation work for large-scale systems occupies a large weight in the degradation test, and the location where degradation occurs Enormous man-hours are also spent on identifying the impact and the scope of influence, and pressing the process has become an issue.

An object of the present invention, degraded test support system capable of displaying to determine the module that refers to methods degraded occurs with determining de grade generation timing or degrade occurrence point, degraded test support method and degraded test To provide a support program.

  Another object of the present invention is to provide a degrading test support system and a degrading system that can reduce the man-hours of the degrading test and prevent omission of the degrading check, and reduce the investigation work and the reworking work when the degrading occurs. To provide a test support method and a degradation test support program.

  The degradation test support system according to the present invention generates the test source code before and after the modification and the test object code before and after the modification, executes the test object code before and after the modification, and has the difference in the value of the execution result variable. Extract the previous and next test object code records, refer to the module name and method name of the extracted record, the upper module name and upper method name of the upper record of the extracted record, and refer to the hierarchy and processing order of the processing flow information The extracted module names and method names and the upper module names and upper method names are displayed on the computer in charge, and it is possible to test whether or not degradation has occurred in the modified source.

According to the present invention, in the degradation test support system according to the first feature, the execution result database stores a variable output by executing the pre-repair test object code, a post-repair execution result database, and a post-repair test. Including a post-repair execution result database that stores variables output by the execution of object code
The execution result comparison unit equally combines the module name, method name, number of lines, variable name, and value fields of the execution result database before the modification and the execution result database after the modification, and executes the records having different values fields. The second feature is that the records are extracted as records having different values.

Further, the present invention provides the pre-repair process in which the process flow database stores pre-reform process flow information including a hierarchy of modules or methods of a pre-reform source and a process order in the degradation test support system of any of the above features Including a flow database and a post-repair process flow database for storing post-repair process flow information including the hierarchy and processing order of the module or method of the source after refurbishment;
Generate a sequence diagram before modification that expresses the exchange between the module and the method along the time axis based on the hierarchy and processing order of the module or method of the source before modification stored in the processing flow database before modification, and after the modification Based on the hierarchy of the module or method of the modified source stored in the process flow database and the processing order, a sequence diagram after modification is generated that expresses the exchange between the module and the method along the time axis, and the execution result comparison unit A third feature is that it includes a sequence diagram generation unit that changes the color of a module or method of a record having a difference in the value of a variable of the extracted execution result and displays it on a responsible computer.

  Further, the present invention, in the degradation test support system of any of the above features, an upper extraction step of extracting the target module name and the target method name of the degradation occurrence location as a higher target module name and a higher target method name from the hierarchical database; A lower extraction step of extracting a lower target module name and a lower target method name having the upper target module name and upper target method name as a parent of the hierarchical structure from the hierarchical database, and the lower extraction step as the lower target module name and A repetition process that repeats until it is determined that the lower target method name is not the last line of the source, and the target module of the degradation occurrence location based on the target module name and the target method name extracted by the upper extraction process and the lower extraction process Name and target method name A fourth characteristic in that a callee list extractor to create and display a boss callee list information.

The present invention further includes a source database that is connected to a computer in charge for testing a modified source including hierarchical modules and methods, stores the source before and after the modification, and the module or method of the source before and after the modification. A processing flow database for storing processing flow information including a hierarchy and a processing order, and an execution result database for storing variables referred to by each step of the source before and after the modification, and referring to the source before and after the modification A computer system degradation test support method for testing whether degradation has occurred in a source after refurbishment,
The computer system is
Test source generation for generating a test source before and after renovation in which a processing order output function for outputting a processing execution order for each step of the source before and after the renovation and a variable value output function for outputting a variable that can be referred to in the step are embedded Process,
A compiling step for generating test object code before and after the modification from the test source before and after the modification;
The test object code before and after the modification is executed, the processing flow information output by the processing order output function is stored in the processing flow database, and the variable output by the variable value output function is stored in the execution result database A test execution process,
Extract the test object code records before and after the modification that have a difference in the value of the execution result variable from the execution result database, and extract the module name and method name of the extracted record, and the upper record of the upper record of the extracted record The module name and the upper method name are extracted by referring to the hierarchy and processing order of the processing flow information stored in the processing flow database, and the plurality of extracted module names and method names, the upper module name and the upper method name are for charge. The fifth feature is that the execution result comparison step displayed on the computer is executed.

Further, the present invention provides the degradation test support method according to the fifth feature, wherein the execution result database stores a variable output by executing the pre-repair test object code, and a post-repair test. Including a post-repair execution result database that stores variables output by the execution of object code
In the execution result comparison step, the computer system equally combines the module name, method name, number of lines, variable name, and value fields of the execution result database before the modification and the execution result database after the modification. A sixth feature is that different records are extracted as records having different values of execution result variables.

Further, the present invention provides the pre-repair process in which the process flow database stores pre-reform process flow information including a hierarchy of modules or methods of a source or a process before refurbishment in the degradation test support method of any of the above features Including a flow database and a post-repair process flow database for storing post-repair process flow information including the hierarchy and processing order of the module or method of the source after refurbishment;
The computer system generates a pre-repair sequence diagram that expresses the exchange between the module and the method along the time axis based on the hierarchy and processing order of the module or method of the pre-repair source stored in the pre-repair process flow database. , Generating a modified sequence diagram that expresses the exchange between the module and the method along the time axis based on the hierarchy and processing order of the module or method of the modified source stored in the modified processing flow database, and executes the execution A seventh feature is to execute a sequence diagram generation step of changing the color of a module or method of a record having a difference in the value of a variable of an execution result extracted in the result comparison step and causing the computer in charge to display it.

  According to the present invention, in the degradation test support method according to any one of the above features, the computer system extracts the target module name and the target method name of the degradation occurrence location from the hierarchical database as the upper target module name and the upper target method name. An upper extraction step, a lower extraction step for extracting a lower target module name and a lower target method name having the upper target module name and the upper target method name as a parent of the hierarchical structure from the hierarchical database, and the lower extraction step Iterative process is repeated until it is determined that the lower target module name and the lower target method name are not the last line of the source, and the degradation is performed based on the target module name and the target method name extracted by the upper extraction process and the lower extraction process. Target module name and location To make a call destination list extraction to perform the steps of the target method name to display to create the affect call destination list information is a feature of the eighth.

The present invention further includes a source database that is connected to a computer in charge for testing a modified source including hierarchical modules and methods, stores the source before and after the modification, and the module or method of the source before and after the modification. A processing flow database for storing processing flow information including a hierarchy and a processing order, and an execution result database for storing variables referred to by each step of the source before and after the modification, and referring to the source before and after the modification A computer system degradation test support program that tests whether degradation has occurred in the source after refurbishment,
In the computer system,
Test source generation for generating a test source before and after renovation in which a processing order output function for outputting a processing execution order for each step of the source before and after the renovation and a variable value output function for outputting a variable that can be referred to in the step are embedded Function and
A compile function for generating test object code before and after the modification from the test source before and after the modification;
The test object code before and after the modification is executed, the processing flow information output by the processing order output function is stored in the processing flow database, and the variable output by the variable value output function is stored in the execution result database A test execution function to
Extract the test object code records before and after the modification that have a difference in the value of the execution result variable from the execution result database, and extract the module name and method name of the extracted record, and the upper record of the upper record of the extracted record The module name and the upper method name are extracted by referring to the hierarchy and processing order of the processing flow information stored in the processing flow database, and the plurality of extracted module names and method names, the upper module name and the upper method name are for charge. A ninth feature is that an execution result comparison function displayed on a computer is realized.

According to the present invention, in the degradation test support program according to the ninth feature, the execution result database stores a variable output by executing the object code for the test before modification, a test result after modification, and a test after modification. Including a post-repair execution result database that stores variables output by the execution of object code
In the execution result comparison function, the computer system includes a function for combining the module name, method name, number of lines, variable name, and value fields of the execution result database before the modification and the execution result database after the modification, A tenth feature is to realize a function of extracting records having different fields as records having variable values of execution results.

Further, the present invention provides the pre-repair process in which the process flow database stores pre-repair process flow information including a hierarchy of modules or methods of the source or the process and the process order in the degradation test support program of any of the above features Including a flow database and a post-repair process flow database for storing post-repair process flow information including the hierarchy and processing order of the module or method of the source after refurbishment;
The computer system generates a pre-repair sequence diagram that expresses the exchange between the module and the method along the time axis based on the hierarchy of the pre-reform source module or method stored in the pre-reform process flow database and the processing order. Function to generate a sequence diagram after modification that represents the exchange between modules and methods along the time axis based on the function and the hierarchy and processing order of the module or method of the modified source stored in the post-repair processing flow database And a function for displaying on the computer in charge a sequence diagram in which the color of the module or method of the record having a difference in the value of the variable of the execution result extracted by the execution result comparison function is realized. And

  Further, according to the present invention, in the degradation test support program having any one of the above characteristics, the target system name and the target method name of the degradation occurrence location are extracted from the hierarchical database as the upper target module name and the upper target method name in the computer system. An upper extraction function, a lower extraction function for extracting a lower target module name and a lower target method name having the upper target module name and the upper target method name as a parent in a hierarchical structure from the hierarchical database, and the lower extraction function The lower function module name and the lower target method name are repeatedly executed until it is determined that the name is not the last line of the source, and the degradation is performed based on the target module name and the target method name extracted by the upper extraction function and the lower extraction function. Target module of occurrence location And twelfth feature of that filename and target method name to realize callee list extraction function according to the display function by creating influence callee list information.

Degraded test support system according to the present invention, degraded test support method and the degraded test support program can determine the de-grade generation timing or degrade occurrence location.

Furthermore, the present invention can target module name and the subject method name of degraded occurrence point creates affect callee list information based on the module name and the subject method name that issued extracted.

It is a figure which shows the structure of the degradation test support system by embodiment of this invention. It is a figure for demonstrating schematic operation | movement of the degradation test assistance system by this embodiment. It is a figure which shows the processing flow of the source analysis part by this embodiment. It is a figure which shows the processing flow of the module related analysis part by this embodiment. It is a figure which shows the processing flow of the module hierarchy analysis part by this embodiment. It is a figure which shows the processing flow of the test source production | generation part by this embodiment. It is a figure which shows the processing flow of the execution result comparison part by this embodiment. It is a figure which shows the processing flow of the sequence diagram production | generation part by this embodiment. It is a figure which shows the processing flow of the list extraction function part of the call destination by this embodiment. It is a figure for demonstrating the source database by this embodiment. It is a figure for demonstrating the variable database by this embodiment. It is a figure for demonstrating the related database by this embodiment. It is a figure for demonstrating the hierarchy database by this embodiment. It is a figure for demonstrating the processing flow database by this embodiment. It is a figure for demonstrating the execution result database by this embodiment. It is a screen image figure which displays as a list the information from which the output result by this embodiment differs. It is a display screen image figure of the sequence diagram by this embodiment. A source content display screen image diagram of this embodiment. It is an extraction list screen image figure of the call destination by this embodiment. It is a screen transition diagram by this embodiment.

  Hereinafter, an embodiment of a degradation test support method and a degradation test support system according to the present invention will be described in detail with reference to the drawings.

[Constitution]
The degradation test support system according to the present embodiment is constructed in a server 001 connected to a computer (PC) 021 for degradation testing via a network 90 as shown in FIG. , A source database (DB) 015 that stores information, a variable database (DB) 016 that stores the contents of variables referred to by the source module or method, and information on the caller and callee from the module or method. It includes a related database (DB) 017, a hierarchical database (DB) 018 for storing hierarchical information from the highest module to the lowest module of the modules constituting the program, and the hierarchy and processing order of modules or methods before and after the modification. Process for storing process flow information A raw database (DB) 019, an execution result database (DB) 020 for storing variable values that can be referred to in each step, a source analysis unit 002 for registering source contents and variable contents from sources before and after the modification, and a modification A module relation analysis unit 003 for registering module relation information obtained by extracting method call locations from the previous and subsequent sources, a module hierarchy analysis part 004 for registering hierarchical information of each module from the relation DB 017, and a test source from the sources before and after the refurbishment The test source generation unit 005 for generating the test, the compile unit 006 for generating the test object code from the test source using the existing technology, and comparing the execution results to extract the portion where the difference in the execution results has occurred Execution result comparison unit 007, and a sequence diagram for generating sequence diagrams before and after the modification. Comprising the cans view generation unit 008, and a call destination list extraction unit 009 that extracts the call destination of the corresponding module. The program described in this embodiment includes hierarchical modules and methods, and a group of these modules and methods is called a source (code), and exchanges between hierarchical modules and methods are expressed along a time axis. This figure is called a sequence diagram.

  The source DB 015 stores a source (code) of a program to be subjected to a degradation test. As shown in FIG. 10A, an ID that is a uniquely assigned identifier, an upgrade, etc. A classification for distinguishing between before modification (flag “0”) and after modification (flag “1”), a source module name, a method name of a method representing “behavior” of the source, the number of source lines, Each item information including the code for storing the source of the corresponding line, specifically, as shown in FIG. 10B, the source of ID “1” has the classification “0”, and the module name “XXX” ”, The method name is“ XXX01 ”, the number of lines is“ 1 ”, the code is“ XXX01_step01 ”, the source of the ID“ 2 ”is the classification“ 0 ”, the module name is“ XXX ”, and the method name is XXX01 ", the number of rows is" 2 ", the code is stored as" XXX01_step02 ".

  The variable DB 016 stores variable names and variable values referred to by the source during execution. As shown in FIG. 11A, an ID that is a uniquely assigned identifier, version upgrade, and the like. Class to distinguish between before (flag “0”) and after modification (flag “1”), the module name of the source, the method name of the method representing the “behavior” of the source, and the number of source lines , The variable name referenced by the source of the corresponding line, the data type declared by the source, and the level indicating the range to be referenced (“1” can be referenced from other modules, “can be referenced only within the same module” 2 ”, which can be referred to only within the method is“ 3 ”). Specifically, as shown in FIG. 11B, the source of ID“ 3 ”has a classification of“ 0 ”. ”And the module name is“ YYY The method name is “yyyy01”, the number of rows is “4”, the variable name is “v_yyy — 02”, the data type is “String”, the level is “3”, the source of the ID “4” is the classification is “0” The module name is “YYY”, the method name is “yyy02”, the number of rows is “9”, the variable name is “v_yyy — 03”, the data type is “String”, and the level is “3”.

  The relation DB 017 stores the relation between the call-source parent module or parent method and the call-destination child module or child method. As shown in FIG. 12A, the relation DB 017 is a uniquely assigned identifier. A certain ID, a classification for distinguishing before modification (flag “0”) and after modification (flag “1”) by version upgrade, the parent module name of the caller, the parent method name of the caller, It consists of the number of parent_lines that represents the number of rows of the parent module, the child_module name that is the module name of the callee, and each item information of the child_method name that is the method name of the callee. 12B, the parent method name of the module of the parent module name “XXX” with ID “1” and category “0” is “xxx01”, the parent_row number is “4”, and the child_module. The name is “YYY”, the child_method name is “yyyy01”, the parent method name of the module with ID “5” and the parent module name “WWW” of category “0” is “www01”, and the parent_row count is “ 10 ”, the child_module name is“ ZZZ ”, and the child_method name is“ zzzz01 ”.

  The hierarchical DB 018 stores modules constituting the source and a hierarchical structure from the highest module in the method, the highest method to the lowest module, and the lowest method. As shown in FIG. Uniquely assigned identifier ID, classification for distinguishing before modification (flag “0”) and after modification (flag “1”) due to version upgrade, etc., and the highest module name in the program hierarchy The reference_module name indicating the reference, the reference_method name that is the highest method name of the program hierarchy, the hierarchy indicating the hierarchy position of the program (“1” for the highest module), and the module name of the caller Parent_module name that represents, parent_method name that represents the method name of the caller, parent_row number that represents the number of caller rows, and call destination Each item information includes a child_module name representing a module name and a child_method name representing a callee method name. Specifically, as shown in FIG. 13B, an ID “1” and a classification “ The standard_module name of the module “0” is “XXX”, the standard_method name is “xxx01”, the hierarchy is “1”, the parent_module name is “XXX”, the parent_method name is “xxx01”, and the parent_row The number is stored as “4”, the child_module name is “YYY”, and the child_method name is “yy01”.

  The processing flow DB 019 stores processing flow information including the hierarchy of modules or methods before and after the modification and the processing order of steps. As shown in FIG. 14 (a), the processing flow DB 019 is a unique numbered identifier. A certain ID, a classification for distinguishing before modification (flag “0”) and after modification (flag “1”) due to version upgrade, etc., and a hierarchy indicating the hierarchical position of the program (the highest module is “1”, the next The hierarchy is “2”..., The process number (process number) indicating the serial number assigned in the order in which the processes are executed, and the upper process number (upper process number) indicating the process number of the caller are executed. The module name of the method, the method name of the executed step, the number of lines of the executed step, and the pre-processing F which is a flag indicating a record registered before the step is executed; It consists of post-processing F, which is a flag indicating a record registered after the step is executed, and item information of time indicating the processing time of each step in ms units. Specifically, FIG. As shown in FIG. 4, after the method “xxx01” having the number of rows “2” of the module name “XXX” of the ID “1”, the category “0”, the hierarchy “1”, and the process number “1” is first executed, Process flow information before and after the modification such as the method “yyy01” of the module name “YYY” of “2” to “5”, the category “0”, the hierarchy “2”, the process numbers “2” and “3” is executed. Is stored.

  The execution result DB 020 stores variable values that can be referred to in each step. As shown in FIG. 15, the ID, which is a uniquely assigned identifier, and before refurbishment by version upgrade or the like (flag “ 0 ”) and after modification (flag“ 1 ”), a serial number assigned in the order in which the processes were executed, the module name of the executed method, and the method name of the executed step , The number of executed steps, the name of the variable to be output by step execution, the number of elements for identifying the value of each element when the variable to be output by step execution is the number of elements, and the value of the variable It consists of each item information, and is specifically stored as shown in FIGS. 15 (a) and 15 (b).

[Operation]
[Overall operation]
Next, the overall operation of the degradation test support system configured as described above will be described. This degradation test support processing is performed at the time of compilation or test execution described later when a large error is included in the modified source. These are targets for degradation tests that are detected and not discovered at the time of compilation or test execution. The degradation flow is listed from the processing flow DB 019 before and after the modification and the execution result DB 020, and the sequence diagram 030 before and after the modification. 031 is generated, the user can easily identify the location of occurrence by changing the color of the location where the difference has occurred, and the list of module callees that will cause degradation is displayed and affected. It is intended to clarify the scope.

  In the degradation test support system according to the present embodiment, first, as shown in FIG. 2, the degradation test staff inputs a pre-repair source 028 and a post-repair source 029 via a network 022 using a computer (PC) 021. A process, a step of analyzing the input source 028 and post-reform source 029 and the variable determined by the variable declaration unit by the source analysis unit 002 and registering them in the source DB 015 and the variable DB 016, and the module relation analysis unit 003 A module hierarchy of analyzing and storing the relationship (the relationship between the call-source parent module or parent method and the call-destination child module or child method) of the pre-repair source 028 and the post-repair source 029, and the module hierarchy The analysis unit 004 creates a module hierarchy (The hierarchical structure from the highest module to the lowest module constituting the program) is stored in the hierarchical DB 018, and the test source generation unit 005 tracks the processing execution order for each source step before and after the modification. Pre-repair source (for testing) 010 and post-repair source (test) embedded with a processing order output function (subprogram) for outputting information and a variable value output function (subprogram) for outputting variable values that can be referenced in the above steps For generating) 011, the pre-repair source code (for test) 011 and the pre-repair object code (for test) 012 generated by the compiling unit 006 and the post-repair object Before and after refurbishment by executing the process of generating code (for testing) 013 Operative to generate object code for testing embedded processing order output function and variable values output function to the source.

  Next, the degradation test support system according to the present embodiment executes a test case in which the test execution units 022 and 023 execute predetermined test cases on the programs (object codes 012 and 013) before and after the modification, and executes the test cases. The processing order output function and the variable value output function, the processing execution order for each step output from the test object code and the variable values that can be referenced in the corresponding step are stored in the processing flow DB 019 and the execution result DB 020. Based on the storing process and the execution order of each step stored in the processing flow DB 019 and the execution result DB 020 by the execution result comparison unit 007 and the value of the variable that can be referred to in the corresponding step, the presence or absence of degradation is determined by the process described later. List of different output results before and after renovation 024 and the sequence diagram generation unit 008 generates a sequence diagram of the program before and after the refurbishment by the processing described later when it is determined that the degradation has occurred, and the execution result is obtained so that the location where the degradation has occurred can be seen at a glance. The process of displaying 025 by changing the color of the different part and the process of displaying the list of call destinations of the module that becomes the debug occurrence part by the call destination list extracting unit 009 by the process described later.

  For example, as shown in FIG. 16, the display screen by the process of displaying a list of information with different output results before and after the refurbishment has a module and method “XXX.xxx01 ()” as the module and method “YYY. yyy02 () "is called, and the module and method" YYY.yyy02 () "call the module and method" ZZZ.zzzz01 () "indicated by a broken line, and this module and method" ZZZ.zzzz01 () "are Different things are displayed by color coding or the like.

  As shown in FIG. 17, the process before and after the refurbishment is performed by changing the color of the part where the execution result is different so that the degradation occurrence part can be seen at a glance. XXX ”,“ YYY ”,“ ZZZ ”, and the variable value of the method“ zzz01 ”in the module“ ZZZ ”as a processing result of the method“ yyy01 ”to the method“ yyy03 ”between the module“ XXX ”and the module“ YYY ” When the sequence is to output, the fact that the variable value of the method “zzzz01” indicated by the broken line is different from that before the modification is displayed by color coding or the like as shown in the sequence after the modification.

  As shown in FIG. 20, these screen displays are performed by “display sequence diagram display screen” 025 and “display call destination list screen” 026 first after “display information list screen with different output results” 024. Finally, it is displayed so as to transit to “display source content display screen” 027 shown in FIG. As shown in FIG. 18, the display screen by the “display source content display screen” 027 displays each record of the method “zzzz01” before the modification and each record of the method “zzz01” before the modification on the right side of the screen. In the case of this example, the result of step 02 executed by the modified method “zzzz01” is displayed in different colors (bold in the drawing).

  As described above, the degradation test support system, the degradation test support method, and the degradation test support program according to the present embodiment generate test object codes 012 and 013 in which the processing order output function and the variable value output function are embedded in the source before and after the modification. Then, the generated test object code 012 and 013 are executed, and when the test case is executed, the test order code output from the test object code in which the processing order output function and the variable value output function are embedded. The process execution order and the value of the variable that can be referred to in the corresponding step are stored in the process flow DB 019 and the execution result DB 020. The process execution order for each step output from the object code before and after the modification and the variable that can be referred to in the corresponding step Deg by comparing values Determining whether or not a failure has occurred, and displaying the sequence diagrams and call destinations shown in FIGS. 16 to 19, it is possible to determine the degradation occurrence timing, the location where the degradation occurred, and the module that refers to the method where the degradation occurred. Can be displayed.

[Detailed operation]
Next, the detailed operation of each processing unit described above will be described.

[Operation of source analysis unit 002]
The steps of storing the pre-repair source 028 and the post-repair source 029 analyzed by the source analysis unit 002 in the source DB 015 and registering the variable analyzed by the variable declaration unit in the variable DB 016 reads the source file as shown in FIG. It is determined whether or not the source record read in step S301 is the last line, step S302 that terminates the processing when it is determined to be the last line, and if it is determined that the record is not the last line in step S302, the current Step S303 for reading a (current) line, Step S304 for storing the contents of the current line read in Step S303 in the source DB 015, and determining whether the current line is a variable declaration part and not a variable declaration part Step S30 is returned to Step S302. When it is determined in step S306 that it is a variable declaration part, the contents of the variable declared by the variable declaration part are stored in the variable DB 016 and executed in step S307, so that the source and variable before and after the modification are Can be extracted and registered in the source DB 015 and the variable DB 016 as shown in FIGS.

[Module-related analysis unit 003 operation]
The module relation analysis unit 003 analyzes the relation of the modules of the source 028 before modification and the module 029 after modification (relation between the parent module or parent method of the call source and the child module or child method of the call destination), and stores it in the relation DB 017 As shown in FIG. 4, the process includes step S401 for reading a source file, step S402 for determining whether or not the source record read in step S401 is the last line, and ending the process when the last line is determined. In step S402, when it is determined that the current line is not the last line, step S403 reads the current line, and determines whether or not the current line read in step S403 is a method call location for calling a lower mall, and is not a lower mall call. When it is determined that Returning to step S402, and when it is determined in step S404 that the call is a lower mall call, the module name and method name of the call source, the module name and method name of the call destination included in the current line are transferred to the related DB 017. By storing and executing step S405 that returns to step S402, the parent-child module and the module relation can be stored in the relation DB 017 as shown in FIG.

[Operation of module hierarchy analysis unit 004]
As shown in FIG. 5, the module hierarchy analyzing unit 004 stores the path of the module hierarchical structure (hierarchical structure from the highest module to the lowest module constituting the program) in the hierarchical DB 018. Step S501 for declaring a variable [v_Kaisou], Step S502 for substituting the value “1” for the variable [v_Kaisou] for initialization of the variable, and extracting the top module from the related DB 107 and aliasing the related DB “Related DB1” and “Related DB2” are set, and “Parent_Module Name”, “Parent_Method Name” of “Related DB1” and “Child_Module Name” and “Child_Method Name” of “Related DB2” are set. Records that are not related to the record of "Related DB2" to the record of "Related DB1" To run and step S504 to be out. The process of extracting the top module from the related DB 107 in step S504 is, for example, when “parent_module” of “related DB1” and “child_module” of “related DB2” are combined in a parent-child relationship. This is performed by determining that the “parent_module” of the “related DB 1” is not coupled to a higher-order module.

  Next, in the hierarchical path extraction processing according to the present embodiment, the module hierarchy analysis unit 004 determines whether or not the highest-order module extracted in step S504 is the last record, and the last record in step S505. When it is determined that it is not, the value of the variable [v_Kaisou] is stored in the “hierarchy” field of the hierarchy DB 018, and the process returns to the step S505 to return to the step S505. Step S508 for incrementing the variable value by adding “1” to the current value, and extracting the current hierarchy module from the hierarchy DB 018 (if the first execution, the first hierarchy data is extracted and the second and subsequent executions are performed sequentially Count up and make this current Step S510 for setting a layer), Step S511 for determining whether or not a record can be extracted from the hierarchical DB 018 in Step S510, and ending the process when it is determined that a record cannot be extracted, and that a record can be extracted for Step S511. When it is determined, it is determined whether or not it is the last record. When it is determined that the record is the last record, step S512 returns to step S508. Step S514 for extracting lower modules is executed.

  In the extraction of the lower modules in step S514, the “parent_module name” and “parent_method name” of the related DB are narrowed down from the current modules (“child_module name” and “child_method name”) extracted in step S510. Thus, in this example, the determination is made by determining “child_module name” and “child_method name” of the related DB 2 illustrated in step S504.

  Next, in the hierarchical path extraction process according to the present embodiment, it is determined whether or not the lower module extracted in step S514 is the last record, and when it is determined to be the last record, the process returns to step S512. If it is determined in S515 that the record is not the last record, the value of the variable [v_Kaisou] is stored in the “hierarchy” field of the hierarchy DB 018, and step S516 is returned to step S515.

  Through this series of processing, the module hierarchy analysis unit 004 according to the present embodiment passes the hierarchical structure path from the highest module to the lowest module constituting the program included in the source program before and after modification stored in the related DB 107 by the module and method. Based on the parent-child relationship, it can be stored in the hierarchical DB 018.

  The test source generation process by the test source generation unit 005 includes a processing order output function for registering data in the processing flow DB 019 before and after each step of the source file, and the contents of variables that can be referenced after each step process. A test source to which a variable value output function to be registered is added is generated. As shown in FIG. 6, step S601 for reading a source file and step S602 for determining whether or not the read source file is the last line. Step S603 for reading the current line when it is determined in step S602 that it is not the last line, step S604 for determining whether or not the current line read in step S603 is a processing step, and the current line in step S604 When it is determined that it is a processing step, Step S605 for storing the start step for the flow (processing order output function) in the temporary storage area of the test source 600, and when it is determined in step S605 or step S604 that it is not a processing step, the source (step) of the current row Is stored in the temporary storage area of the test source 600, and it is determined whether the current line is a processing step. If it is determined that the current line is not a processing step, the process returns to the previous step S602, and the current line is processed in step S609. Step S610 for storing the processing flow (processing order output function) end step in the test source 600 temporary storage area, step S613 for extracting a variable that can be referred to in the current row from the variable DB 016, and the step S It is determined whether or not the current line extracted in step 13 is the last record. When it is determined that the current record is the last record, step S614 returns to step S602, and when it is determined that the current record is not the last record in step S614, the value of the variable is output. When the variable value output function is stored in the temporary storage area of the test source 600 and when it is determined that the source file read in the step S602 is the last line, the processing order output function and the variable value output from the test source 600 By executing step S618 for outputting the test sources 010 and 011 in which the functions are embedded, it is possible to generate a test source for outputting a processing flow and variables associated with the source execution.

[Execution result comparison unit 007 operation]
The execution result comparison unit 007 determines whether or not degradation has occurred based on the processing execution order (processing flow information) for each step stored in the execution result DB 020 and the value of a variable that can be referred to in the corresponding step, by the processing described later. As shown in FIG. 7, the process of displaying a list of information with different output results before and after the modification, first, declares a variable [v_WorkNo] (variable name of the variable), an execution result DB 020A before and after the modification, and 020B is compared, and step S704 for extracting a record having a difference in the value of the variable of the processing result is executed.

  In this step S704, the execution result DB is set to the alias “execution result (before modification)” and “execution result (after modification)”. In “execution result (before modification)”, the “classification” field is “0: The data of “before renovation” is the target, and in the “execution result (after renovation)”, the “classification” field is the data of “1: after renovation”, and the “module name”, “method name”, “row” of each table Equal coupling is performed in the “number”, “variable name”, and “number of elements” fields, and the “execution result (before modification)” and “execution result (after modification)” fields are identified by different records and extracted.

  This will be specifically described with reference to before and after the modification of the execution result DB in FIG. 15. In step S704, IDs “16” to “18” of the execution result DB 020A before the modification shown in FIG. The method “v_xxxx — 01”, the method “v_zzzz — 01”, and the method “v_zzzz — 02” of the module “ZZZ” are executed, and the value of the variable of the method “v_zzzz — 02” is “z_value — 02”, whereas FIG. The method “v_xxxx_01”, the method “v_zzzz_01”, and the method “v_zzzz_02” of the module “ZZZ” with the IDs “16” to “18” in the execution result DB 020B shown in FIG. If "z_value_03" is output, this method Since the value of the variable v_zzz_02 "are different, determines a record of the method" v_zzz_02 "is the" value "field as different records.

  Next, in the step of displaying a list 024 of information with different output results before and after the renovation according to the present embodiment, step S705 for determining whether or not the record having a different “value” field extracted in step S704 is the last record, and the step When it is determined in S705 that the record is not the last record, step S706 for storing (substituting) the process NO acquired in step S704 for variable [v_WorkNo], and whether or not the value of variable [v_WorkNo] stored in step S706 is empty. When it is determined that the value of the variable [v_WorkNo] is not empty in step S707, the process flow DB019 changes to the process NO of the process flow DB019. Is a variable [v_Work Step S709 for obtaining the upper process NO of the record equal to the value of “No”, Step S710 for storing (substituting) the process NO obtained in Step S709 for the variable [v_WorkNo] obtained in Step S709, and Step S710 In step S711, the module name and method name of the higher-level module stored in step S711 are stored in a temporary storage area for screen display and the process returns to step S707. When it is determined in step S705 that the record is the last record, By executing step S713 for displaying an information list display screen with different output results based on the contents of the temporary storage area, the upper modules of the modules with different execution results are extracted based on the data with different execution results. To display the screen as shown in Kill.

[Operation of Sequence Diagram Generation Unit 008]
As shown in FIG. 8, the sequence diagram generation unit 008 generates a sequence diagram of the program before and after the refurbishment and displays 025 by changing the color of the location where the execution result is different so that the degradation occurrence location can be seen at a glance. Step S802 for extracting processing flow information (FIG. 14) from the pre-repair processing flow DB 019A, step S803 for determining whether or not the record of the extracted processing flow information is the last row, and determining that the record is not the last row in step S803 Step S804 for generating the sequence diagram 811 before modification based on the information of the current record (left side diagram of FIG. 17), and the execution result before and after the modification in the current record are extracted from the execution result DBs 020A and 020B before and after the modification. Step S808 to compare, and the result of the comparison, execution results before and after the renovation When there is no difference, step S809 returns to step S803 when it is determined that there is no difference, and when it is determined that there is a difference in step S809, the current (current) step in which there is a difference is determined. It is determined for each step whether or not there has been a change in the execution result values for all the lines of the pre-repair process flow by generating the sequence diagram 811 before modification with the color changed and executing step S810 that returns to step S803. Then, the color of the step where the change has occurred can be changed.

  Next, the process of changing the display color of the part where the execution result is different by the sequence diagram generation unit 008 according to the present embodiment and displaying 025 is determined to be the last line in the step S803, the process flow information from the post-repair process flow DB 019B , Step S814 for determining whether or not the record of the extracted processing flow information is the last line, and when it is determined in step S814 that the record is not the last line, a sequence diagram after modification based on the information of the current record Step S815 for generating 816 (right side of FIG. 17), Step S819 for extracting and comparing the execution results before and after the modification in the current record from the execution result DBs 020A and 020B before and after the modification, and the result of the comparison, before and after the modification Judge whether there is a difference in the execution results of When it is determined that there is no difference, Step S820 returns to Step S814, and when it is determined that there is a difference in Step S820, a modified sequence diagram 822 in which the color of the current (current) step where there is a difference is generated is generated. By executing step S821 which returns to step S814, it is determined for each step whether or not there has been a change in the execution result value for all the lines in the post-repair processing flow, and the color of the step having the change is changed. be able to.

  That is, the sequence diagram generation unit 008 according to the present embodiment generates a process flow diagram before and after the modification based on the process flow information before and after the modification illustrated in FIG. The execution result difference (within the variable) is determined based on the execution result DBs 020A and 020B, and the corresponding part of the step that outputs the variable value having the difference (for example, the broken line portion on the right side of FIG. 17) is displayed in different colors. The degradation occurrence timing and the degradation occurrence location can be displayed visually to the administrator.

[Operation of Called Party List Extraction Unit 009]
The step of displaying a list of call destinations of modules that are debug occurrence locations by the call destination list extracting unit 009 by a process described later is a step of declaring a variable [v_Module] and a variable [v_Method] as shown in FIG. S901, and from the hierarchy DB 018 to deliver the target module name and target method name of the degradation occurrence location to the argument of this process, the hierarchy DB. Child_module name = [target module name (target module name where degradation occurred)] and hierarchical DB. Step S903 for extracting a record satisfying the condition child_method name = [target method name (target method name where degradation has occurred)] as an upper module, and step S904 for determining whether or not the extracted record is the last row. When it is determined in step S904 that it is not the last line, step S905 for storing the callee module name and method name in the callee module list 906, which is a temporary storage area for screen display, and step S903 for extracting the upper module. Step S907 for storing (substituting) the parent_module name and the parent_method name acquired in step 4 into the variables [v_Module] and [v_Method], respectively, and either the variable [v_Module] or the variable [v_Method] stored in the step S907. One Determines whether is empty, the step S908 back to step S904 when it is determined that the blank, when it is determined that not blank in the step S908, the hierarchy DB018, hierarchical DB. Child_module name = variable [v_Module] and hierarchical DB. Step S910 for extracting a higher-level module that matches the condition of child_method name = variable [v_Method], and the module name and method name of the call destination extracted in step S910 are call destination modules that are temporary storage areas for screen display In step S911 stored in the list 912, the parent_module name and the parent_method name acquired in the upper module extraction process extracted in step S907 are stored in variables [v_Module] and [v_Method], respectively, and the process returns to step S908. Step S913 and Step S914 for generating a list display screen 915 for the call destination based on the contents of the temporary storage area for screen display are executed when the record extracted from the hierarchical DB 018 in Step S904 is determined to be the last line. Do As shown in FIG. 19, the module and the method “WWW.www01 ()” which are affected by referring to the module and method “ZZZ.zzz01 ()” indicated by the broken line as the debug occurrence location are displayed. it can. In other words, by extracting the hierarchically related module names and method names starting from the location where the declade is generated, it is possible to easily display other module names and method names affected by the degradation.

  As described above, the degradation test support system and the degradation test support system that realizes the degradation test support method according to the present embodiment can be referred to in the processing order output function for outputting the processing execution order for each source step before and after the renovation and the above steps. A test source generation unit 005 for generating a test source before and after the modification in which a variable value output function for outputting a variable is embedded, and processing flow information output when the test object code before and after the modification is executed are stored in the process DB 019. Test execution units 022 and 023 that store and output variables stored in the execution result DB 020, and records of test object codes before and after the repair that have a difference in values of execution result variables from the execution result DB 020, Module name and method name of the extracted record, The upper module name and upper method name of the upper record of the extracted record are extracted by referring to the hierarchy and processing order of the processing flow information stored in the processing flow database, and the extracted module names, method names, and upper module names are extracted. And the execution result comparison unit 007 for displaying the upper method name on the display unit of the responsible computer 021, it is possible to determine the degradation occurrence timing and the degradation occurrence location, and the target module of the degradation occurrence location from the hierarchical DB 018. Name and target method name are extracted as upper target module name and upper target method name, lower target module name and lower target method name are extracted from the extracted upper target module name and upper target method name, and these Extracted module name and It can easily display the degrade influence range by degrading target module name occurrence location and target method name provided callee list extraction unit 009 to display a range affects based on elephants method name. Therefore, according to the present invention, it is possible to reduce the man-hours for the degradation test and to prevent the degradation check from being omitted, and to reduce the investigation work and the rework work when the degradation occurs.

000 Degradation support system, 001 server, 002 source analysis unit,
003 module-related analysis unit, 004 module hierarchy analysis unit,
005 source generation function unit, 006 compilation unit, 007 execution result comparison unit,
008 sequence diagram generator, 009 callee list extractor,
010 Source before renovation (for testing), 011 Source after renovation (for testing),
012 Object code, 021 Computer for degradation test,
022 Test execution part, 90 network, 028 source before renovation,
029 Refurbished source

Claims (12)

Degradation test support that is connected to the computer in charge for testing the modified source including hierarchical modules and methods, and tests whether degradation has occurred in the modified source by referring to the source before and after the modification A system,
A source database for storing the source before and after the renovation;
A processing flow database for storing processing flow information including the hierarchy and processing order of the source module or method before and after the modification;
An execution result database for storing variables referred to by each step of the source before and after the renovation;
Test source generation for generating a test source before and after renovation in which a processing order output function for outputting a processing execution order for each step of the source before and after the renovation and a variable value output function for outputting a variable that can be referred to in the step are embedded And
A compiling unit that generates test object code before and after the modification from the test source before and after the modification;
The test object code before and after the modification is executed, the processing flow information output by the processing order output function is stored in the processing flow database, and the variable output by the variable value output function is stored in the execution result database A test execution unit to perform,
Extract the test object code records before and after the modification that have a difference in the value of the execution result variable from the execution result database, and extract the module name and method name of the extracted record, and the upper record of the upper record of the extracted record The module name and the upper method name are extracted by referring to the hierarchy and processing order of the processing flow information stored in the processing flow database, and the plurality of extracted module names and method names, the upper module name and the upper method name are for charge. Lud grade test support system comprising an execution result comparison unit to be displayed on the computer. The execution result database stores the variables output by executing the pre-repair test object code and the post-reformation execution result database storing the variables output by the execution of the post-repair test object code. Including
The execution result comparison unit equally combines the module name, method name, number of lines, variable name, and value fields of the execution result database before the modification and the execution result database after the modification, and executes the records having different values fields. degraded test support system of 請 Motomeko 1, wherein you extracted as record values there is a difference in the variable. The processing flow database stores a pre-repair processing flow database that stores pre-repair processing flow information including the hierarchy and processing order of the module or method of the pre-repair source, and a hierarchy and processing order of the module or method of the renovated source Including a post-repair process flow database that stores post-repair process flow information,
Generate a sequence diagram before modification that expresses the exchange between the module and the method along the time axis based on the hierarchy and processing order of the module or method of the source before modification stored in the processing flow database before modification, and after the modification Based on the hierarchy of the module or method of the modified source stored in the process flow database and the processing order, a sequence diagram after modification is generated that expresses the exchange between the module and the method along the time axis, and the execution result comparison unit any one of the extracted execution result of values there is a difference in the record of variable modules or methods 請 Motomeko 1 and claim 2, wherein Ru with a diagram generation unit to be displayed on representative computer by changing the color Degradation test support system described in An upper extraction step of extracting the target module name and target method name of the degradation occurrence location from the hierarchical database as the upper target module name and upper target method name, and the upper target module name and upper target method name from the hierarchical database in a hierarchical structure A sub-extraction step for extracting a subordinate target module name and a subordinate target method name as a parent, and a repetition step of repeating the subextraction step until it is determined that the subordinate target module name and the subordinate target method name are not the last line of the source, To create and display call destination list information that is affected by the target module name and target method name at the occurrence of degradation based on the target module name and target method name extracted by the upper extraction step and the lower extraction step. Ru with a call destination list extraction unit for 請 Degraded test support system according to 3 any one of claim 1. A source database connected to a computer in charge for testing a modified source including a module and a method having a hierarchical structure, storing a source before and after the modification, and a hierarchy and processing order of the module or method of the source before and after the modification; Including a processing flow database for storing processing flow information including an execution result database for storing variables referred to by each step of the source before and after the modification, and degrading the source after the modification with reference to the source before and after the modification A computer system degradation test support method for testing whether or not an error has occurred,
The computer system is
Test source generation for generating a test source before and after renovation in which a processing order output function for outputting a processing execution order for each step of the source before and after the renovation and a variable value output function for outputting a variable that can be referred to in the step are embedded Process,
A compiling step for generating test object code before and after the modification from the test source before and after the modification;
The test object code before and after the modification is executed, the processing flow information output by the processing order output function is stored in the processing flow database, and the variable output by the variable value output function is stored in the execution result database A test execution process,
Extract the test object code records before and after the modification that have a difference in the value of the execution result variable from the execution result database, and extract the module name and method name of the extracted record, and the upper record of the upper record of the extracted record The module name and the upper method name are extracted by referring to the hierarchy and processing order of the processing flow information stored in the processing flow database, and the plurality of extracted module names and method names, the upper module name and the upper method name are for charge. Lud grade test support method to perform an execution result comparison step to be displayed on the computer. The execution result database stores the variables output by executing the pre-repair test object code and the post-reformation execution result database storing the variables output by the execution of the post-repair test object code. Including
In the execution result comparison step, the computer system equally combines the module name, method name, number of lines, variable name, and value fields of the execution result database before the modification and the execution result database after the modification. 請 Motomeko 5 degraded test support method according you extracted as a record there is a difference different records the value of the execution result variable. The processing flow database stores a pre-repair processing flow database that stores pre-repair processing flow information including the hierarchy and processing order of the module or method of the pre-repair source, and a hierarchy and processing order of the module or method of the renovated source Including a post-repair process flow database that stores post-repair process flow information,
The computer system generates a pre-repair sequence diagram that expresses the exchange between the module and the method along the time axis based on the hierarchy and processing order of the module or method of the pre-repair source stored in the pre-repair process flow database. , Generating a modified sequence diagram that expresses the exchange between the module and the method along the time axis based on the hierarchy and processing order of the module or method of the modified source stored in the modified processing flow database, and executes the execution result comparison step 請 Motomeko 5 and claim 6, wherein that perform diagram generation step of displaying the representative computer to change the color of the modules or method there are differences in the value of the extracted execution result variable record by The degradation test support method according to any one of the above. An upper extraction step in which the computer system extracts a target module name and a target method name of a degradation occurrence location from a hierarchical database as an upper target module name and an upper target method name; and the upper target module name and an upper target method from the hierarchical database A lower-level extraction step for extracting a lower-level target module name and a lower-level target method name whose name is the parent of the hierarchical structure, and determining that the lower-level extraction step is not the last line of the source Call destination list information affected by the target module name and target method name of the occurrence of degradation based on the target module name and target method name extracted by the upper extraction step and the lower extraction step. Create and display Degraded test support method according the call destination list extracted from the line jar請 Motomeko 5 7 any one of claims 1 to run the door. A source database connected to a computer in charge for testing a modified source including a module and a method having a hierarchical structure, storing a source before and after the modification, and a hierarchy and processing order of the module or method of the source before and after the modification; Including a processing flow database for storing processing flow information including an execution result database for storing variables referred to by each step of the source before and after the modification, and degrading the source after the modification with reference to the source before and after the modification A computer system degradation test support program for testing whether or not
In the computer system,
Test source generation for generating a test source before and after renovation in which a processing order output function for outputting a processing execution order for each step of the source before and after the renovation and a variable value output function for outputting a variable that can be referred to in the step are embedded Function and
A compile function for generating test object code before and after the modification from the test source before and after the modification;
The test object code before and after the modification is executed, the processing flow information output by the processing order output function is stored in the processing flow database, and the variable output by the variable value output function is stored in the execution result database A test execution function to
Extract the test object code records before and after the modification that have a difference in the value of the execution result variable from the execution result database, and extract the module name and method name of the extracted record, and the upper record of the upper record of the extracted record The module name and the upper method name are extracted by referring to the hierarchy and processing order of the processing flow information stored in the processing flow database, and the plurality of extracted module names and method names, the upper module name and the upper method name are for charge. Lud grade test support program to realize the execution result comparison function to be displayed on the computer. The execution result database stores the variables output by executing the pre-repair test object code and the post-reformation execution result database storing the variables output by the execution of the post-repair test object code. Including
In the execution result comparison function, the computer system includes a function for combining the module name, method name, number of lines, variable name, and value fields of the execution result database before the modification and the execution result database after the modification, 請 Motomeko 9 wherein degraded test support program of field Ru to realize a function to extract a record there is a difference in the value of the execution result different record variable. The processing flow database stores a pre-repair processing flow database that stores pre-repair processing flow information including the hierarchy and processing order of the module or method of the pre-repair source, and a hierarchy and processing order of the module or method of the renovated source Including a post-repair process flow database that stores post-repair process flow information,
The computer system generates a pre-repair sequence diagram that expresses the exchange between the module and the method along the time axis based on the hierarchy of the pre-reform source module or method stored in the pre-reform process flow database and the processing order. Function to generate a sequence diagram after modification that represents the exchange between modules and methods along the time axis based on the function and the hierarchy and processing order of the module or method of the modified source stored in the post-repair processing flow database When the execution result comparison function 請 Motomeko 9 and Ru is achieving the function of displaying the charge computer a sequence diagram of changing the color of the modules or method there are differences in the value of the extracted execution result variable record by The degradation test support program according to claim 10. In the computer system,
A higher-level extraction function that extracts the target module name and target method name of the occurrence of degradation from the hierarchical database as the upper target module name and upper target method name, and the upper target module name and upper target method name from the hierarchical database in a hierarchical structure A lower-level extraction function that extracts a lower-level target module name and a lower-level target method name as a parent, and a repetition function that repeats the lower-level extraction function until it is determined that the lower-level target module name and the lower-level target method name are not the last line of the source And execute
A display function for creating and displaying call destination list information affected by the target module name and the target method name of the occurrence of degradation based on the target module name and the target method name extracted by the upper extraction function and the lower extraction function; The degradation test support program according to claim 9, further comprising a call destination list extraction function for executing

Images