TWI911647B - Electronic device, method performed by electronic device, and non-transitory computer-readable recording medium for managing keyword related to execution of test case - Google Patents

Abstract

This invention proposes an electronic device for managing and testing the execution of keywords related to test cases. The electronic device of the present invention may include: one or more processors; and one or more memories, which store commands to be executed by the one or more processors; when executing the commands, the one or more processors are configured to: obtain source code corresponding to one or more candidate keywords related to the execution of one or more test cases; generate attribute information corresponding to each of the one or more candidate keywords based on parsing the source code; receive target information for searching recommended keywords; and search for recommended keywords that match the target information from the one or more candidate keywords by comparing the attribute information corresponding to each of the one or more candidate keywords with the target information.

Description

Electronic devices for managing and testing the execution of related keywords, methods implemented by the electronic devices, and non-temporary computer-readable recording media.

This invention relates to a technique for managing and test case execution-related keywords. More specifically, this invention relates to a technique for parsing keyword source code to efficiently manage and test case execution-related keywords.

Software testing demonstrates whether software behaves as the developer intended. Multiple test cases can be executed to perform software testing. A test case represents a set of conditions or variables designed to verify whether the software conforms to specific design specifications. Test cases may include information related to the specific scenario to be tested, test data (e.g., input values), execution conditions, and expected results. Developers can use automated testing frameworks to optimize the test case generation process. For example, automated testing frameworks can provide keyword-based access, where keywords represent a predefined, reusable set of tasks or commands. When designing test cases, developers can use keywords instead of directly entering command code. The use of keywords provides the advantage of speeding up the generation of test cases.

[Problem Solved by the Invention] This invention discloses a technique for managing and executing test cases related to keywords. [Technical Means for Solving the Problem]

This invention discloses a technique for managing and executing keywords related to test cases. One embodiment of this invention may include the following steps: obtaining source code corresponding to one or more candidate keywords related to the execution of one or more test cases; generating attribute information corresponding to each of the candidate keywords based on parsing the source code; receiving target information for retrieving recommended keywords; and retrieving recommended keywords matching the target information from the candidate keywords by comparing the attribute information corresponding to each of the candidate keywords with the target information.

In one embodiment, each of the above-mentioned test cases represents a test case associated with a page, and the steps to obtain the above-mentioned source code may include the following steps: identifying the above-mentioned source code from the resource file corresponding to the above-mentioned page.

In one embodiment, the step of generating attribute information corresponding to each of the above-mentioned candidate keywords may include the following steps: responding to the first pull request that wishes to merge the above source code into the main branch, triggering the parsing of the above source code.

In one embodiment, the above method may include the following steps: identifying from the above source code a portion of the source code corresponding to each of the above candidate keywords; and generating, based on analyzing the portion of the source code corresponding to each of the above candidate keywords, partial information of each of the above candidate keywords' keyword attributes (the partial information of each of the above candidate keywords' keyword attributes constitutes the attribute information corresponding to each of the above candidate keywords).

In one embodiment, the steps of generating attribute information corresponding to each of the above-mentioned candidate keywords may include the following steps: identifying one or more columns in the above-mentioned source code that do not begin with a space, and determining each of the above-mentioned columns as the starting column of the portion of source code corresponding to the candidate keywords.

In one embodiment, the above-mentioned one or more keyword attributes may include at least one of the following: page name, keyword name, keyword description, keyword tag, and keyword argument.

In one embodiment, for a specific keyword attribute among the above-mentioned one or more keyword attributes, a marker is pre-set to distinguish it from other keyword attributes. The step of generating partial information of each of the above-mentioned candidate keyword's one or more keyword attributes may include the following steps: based on retrieving the marker from the partial source code corresponding to each of the above-mentioned candidate keywords, partial information of the above-mentioned specific keyword attribute of each of the above-mentioned candidate keywords is generated.

In one embodiment, the above method may further include the following steps: receiving a second fetch request to update the source code based on the changes to the source code; in response to receiving the second fetch request, identifying the changed code portion in the source code; and updating the attribute information corresponding to each of the one or more candidate keywords based on the analysis of the identified code portion.

In one embodiment, the above method may further include the following steps: setting credibility for each of the above-mentioned candidate keywords.

In one embodiment, the steps of setting the confidence level for each of the above-mentioned candidate keywords may include the following steps: in the above-mentioned test cases, executing a specific test case, determining whether the execution of at least one candidate keyword related to the execution of the specific test case is successful; and adjusting the confidence level corresponding to each of the above-mentioned candidate keywords based on whether the execution of the at least one candidate keyword is successful.

In one embodiment, the steps for retrieving the recommended keywords may include the following steps: identifying keyword attributes that map to the target information; calculating the matching degree between each candidate keyword and the target information by comparing partial information of the identified keyword attributes of each candidate keyword with the target information; and retrieving the recommended keywords from the candidate keywords based on the calculated matching degree.

In one embodiment, the step of searching for the recommended keyword among the above-mentioned candidate keywords may include the following steps: among the above-mentioned candidate keywords, the candidate keywords whose matching degree with the target information is above a critical value are identified as the recommended keywords.

In one embodiment, the above method may further include the following steps: when there are multiple recommended keywords, determining the recommended value of each of the multiple recommended keywords; and displaying the multiple recommended keywords in descending order of the recommended values.

In one embodiment, the step of determining the recommendation value of each of the plurality of recommended keywords may include the following steps: calculating the value obtained by applying a first weight to the matching degree of the target information corresponding to the recommended keyword and adding a second weight to the credibility corresponding to the recommended keyword, and using this value as the recommendation value.

In one embodiment, the first weighted value may be greater than or equal to the second weighted value.

In one embodiment, the step of calculating the matching degree between each candidate keyword and the target information may include the following steps: calculating the partial information of the identified keyword attributes of each candidate keyword and the degree of duplication between the target information.

In one embodiment, the step of calculating the matching degree between each candidate keyword and the target information may include the following steps: calculating the overlap between partial information of the identified keyword attributes of each candidate keyword and the target information; and calculating the matching degree between each candidate keyword and the target information based on the calculated overlap.

In one embodiment, the step of calculating the repetition between the partial information of the identified keyword attributes of each candidate keyword and the target information is characterized by the following: the ratio is calculated as the repetition, which is the ratio of the number of words that are repeated between the partial information of the identified keyword attributes of each candidate keyword and the target information to the total number of words included in the partial information.

The present invention provides an electronic device for managing and testing the execution of related keywords. The electronic device of the present invention may include: one or more processors; and one or more memories, which store commands for execution by the one or more processors. When executing the above command, the above-mentioned processor can be configured as follows: obtain source code corresponding to one or more candidate keywords related to the execution of one or more test cases; generate attribute information corresponding to each of the above-mentioned candidate keywords based on parsing the source code; receive target information for searching recommended keywords; and search for recommended keywords that match the target information from the above-mentioned candidate keywords by comparing the attribute information corresponding to each of the above-mentioned candidate keywords with the target information.

The present invention provides a non-transitory computer-readable recording medium that records commands for automatically recovering failed test cases. In one embodiment of the present invention, the commands recorded on the recording medium can be commands that can be executed by one or more processors or implemented on a computer. These commands can be configured as follows: when executed by one or more processors, the processor obtains source code corresponding to one or more candidate keywords related to the execution of one or more test cases; based on parsing the source code, it generates attribute information corresponding to each of the candidate keywords; it receives target information for retrieving recommended keywords; and based on comparing the attribute information corresponding to each of the candidate keywords with the target information, it retrieves the recommended keywords that match the target information from among the candidate keywords. [Effects of the Invention]

According to this invention, recommended keywords that match target information provided by a user terminal are retrieved by using attribute information generated by analyzing the source code of each keyword, thereby retrieving recommended keywords that match target information more efficiently.

According to this invention, one or more recommended keywords that match the target information are arranged in descending order of recommendation value and provided to the user terminal, thereby making it easier for users on the user terminal to find suitable keywords to generate test cases.

The effects based on the technical concept of this invention are not limited to the effects mentioned above. Those skilled in the art can clearly understand other effects not mentioned based on the description in the manual.

The various embodiments described herein are illustrated for the purpose of clearly illustrating the technical concept of the invention and are not intended to limit them to any particular embodiment. The technical concept of the invention includes various modifications, equivalents, alternatives, and embodiments obtained by selectively combining all or part of the embodiments described herein. Furthermore, the scope of the patent application for the technical concept of the invention is not limited to the various embodiments presented below or their specific descriptions.

The terms used in this invention, including technical or scientific terms, shall, unless otherwise defined, have the meanings commonly understood by a person of common knowledge in the field to which this invention pertains.

The use of terms such as "including," "may include," "possibly possess," "has," "may have," and "may have" in this invention implies the presence of object features (e.g., functions, actions, or constituent elements), and does not exclude the existence of other additional features. That is, the above-mentioned expressions should be understood as open-ended terms that have the possibility of including other embodiments.

The singular expressions used in this invention may include the meaning of the plural form unless the context otherwise requires, and this also applies to the singular expressions recorded in the scope of the patent application.

The terms “first,” “second,” “first,” “second,” etc., used in this specification are, unless otherwise specified, used to distinguish one object from others when referring to multiple objects of the same kind, and are not used to define the order or importance of such objects.

The expressions “A, B and C”, “A, B or C”, “A, B and/or C”, “at least one of A, B and C”, “at least one of A, B or C”, “at least one of A, B and/or C”, etc., used in this invention may refer to each of the listed items or all possible combinations of the listed items. For example, “at least one of A or B” may refer to (1) at least one A, (2) at least one B, (3) at least one A and at least one B.

The term "based on" as used in this invention is used to describe one or more factors that affect the determination, judgment, or action described in the sentence or text that includes the term, and the term does not exclude other factors that affect the determination, judgment, or action.

The expression used in this invention to say that a certain constituent element (e.g., the first constituent element) is "connected" or "linked" to another constituent element (e.g., the second constituent element) may not only mean that the aforementioned constituent element is directly connected or linked to the aforementioned other constituent element, but may also mean that it is connected or linked to the aforementioned other constituent element through a new other constituent element (e.g., the third constituent element).

The phrase "configured to" as used in this invention can have meanings such as "configured in a ~ manner," "possessing ~ capabilities," "modified in a ~ manner," "made in a ~ manner," and "capable of ~ operations," depending on the context. This phrase is not limited to the meaning of "specially designed in hardware." For example, a processor configured to perform a specific action can refer to a general-purpose processor that can perform a specific action by executing software, or a special-purpose computer that performs that specific action through programming.

The embodiments described herein will now be described with reference to the accompanying drawings. In the drawings and their descriptions, identical or substantially equivalent constituent elements are assigned the same reference numerals. Furthermore, in the following descriptions of the embodiments, repeated descriptions of identical or corresponding constituent elements may be omitted, but this does not mean that the constituent element is not included in the embodiment.

Figure 1 illustrates the environment in which an electronic device of one embodiment of the present invention can be applied.

Test cases can represent a series of conditions or variables designed to verify whether software conforms to specific design specifications. To execute a test case, more than one keyword can be required. Each step of a test case can be performed by calling more than one keyword. A keyword can represent a predefined set of reusable actions or commands. The following description uses keywords stored in electronic device 110 as candidate keywords.

In one embodiment, electronic device 110 may be a device for storing one or more keywords. More specifically, electronic device 110 may store source code corresponding to one or more candidate keywords. Electronic device 110 may parse and store source code corresponding to one or more candidate keywords.

In one embodiment, electronic device 110 can be implemented by more than one computing device. For example, all functions of electronic device 110 can be implemented in a single computing device. As another example, a first function of electronic device 110 can be implemented in a first computing device, and a second function can be implemented in a second computing device. As another example, a plurality of computing devices can be used to implement all or specific functions of electronic device 110. The aforementioned computing devices can be desktop computers, laptop computers, application servers, proxy servers, or cloud servers, but are not limited to these; all types of devices with computing capabilities can be computing devices.

In one embodiment, user terminal 120 may represent a device for generating test cases. A user of user terminal 120 can transmit target information to electronic device 110 via user terminal 120 to generate test cases. Electronic device 110 can receive target information from user terminal 120 and can retrieve recommended keywords matching the target information from a pool of candidate keywords stored in electronic device 110 and provide them to user terminal 120. Electronic device 110 can parse and store source code corresponding to candidate keywords to facilitate retrieval of recommended keywords matching the target information.

In one embodiment, user terminal 120 may be implemented as a terminal capable of sending and receiving various information with electronic device 110 via a network. For example, user terminal 120 may be one of a computer, laptop, portable communication terminal (smartphone, etc.), portable multimedia device, wearable device, or HMD (Head-Mounted Display). However, the type of user terminal 120 is not limited to these, and user terminal 120 may be any device including an input/output interface capable of receiving or sending information to a user, and capable of communicating with electronic device 110 or other devices via a network.

In one embodiment, user terminal 120 can provide information received from electronic device 110 to the user, and can receive input from the user and transmit it to electronic device 110. Specifically, user terminal 120 can receive input from the user indicating calls to various pages, and respond to the received input by generating commands indicating calls to various pages. User terminal 120 can transmit commands indicating calls to various pages to electronic device 110. Input received from the user may include various forms of input such as mouse clicks, touch controls using a touchpad or touchscreen, voice recognition, and other electronic inputs. User terminal 120 can receive various pages from electronic device 110 and output the received pages.

The network enables the connection of electronic device 110 to user terminal 120 or other external devices. For example, the network provides connection paths so that user terminal 120 or other external devices can connect to electronic device 110 and send and receive packet data with electronic device 110. The network can be implemented as any type of wired or wireless network, such as a Local Area Network (LAN), a Wide Area Network (WAN), a Mobile Radio Communication Network, or Wibro (Wireless Broadband Internet).

In one embodiment, the electronic device 110 and the user terminal 120 may operate as a single device. The user terminal 120 may be included as all or part of the constituent elements of the electronic device 110. In this case, for example, the various information transmitted and received between the electronic device 110 and the user terminal 120 via a network may be various information transmitted and received between the constituent elements of a single device.

Figure 2 is a block diagram of an electronic device according to one embodiment of the present invention. The electronic device 200 (e.g., the electronic device 110 in Figure 1) can parse and store source code corresponding to candidate keywords. In one embodiment, the electronic device 200 may include one or more processors 210, one or more memory units 220, and a communication interface 230 as constituent elements. In one embodiment, at least one of the constituent elements of the electronic device 200 may be omitted, or other constituent elements may be added to the electronic device 200. In one embodiment, a portion of the constituent elements may be additionally or alternatively integrated to implement, or implemented as a single or multiple entities. In the present invention, one or more processors 210 may be referred to as processor 210. Unless otherwise specified in the text, the term "processor 210" may refer to a collection of one or more processors. In this invention, one or more memory units 220 may be referred to as memory 220. Unless otherwise specified in the text, the term "memory unit 220" may refer to a collection of one or more memory units. In one embodiment, at least some of the internal/external components of the electronic device 200 are interconnected via buses, GPIO (General Purpose Input/Output), SPI (Serial Peripheral Interface), or MIPI (Mobile Industry Processor Interface), thereby enabling the transmission and reception of information (data, signals, etc.).

The processor 210 can control at least one component of the electronic device 200 connected to the processor 210 via driver software (e.g., commands, programs, etc.). Furthermore, the processor 210 can perform various actions related to the present invention, such as calculation, processing, data generation, and manipulation. Additionally, the processor 210 can load data from or store data in memory 220. In one embodiment, the processor 210 can control the communication interface 230 to request various information from a user terminal (e.g., user terminal 120 in FIG. 1) and receive various information from the user terminal.

Memory 220 can store various information (data). The information stored in memory 220 is information that can be obtained, processed, or used by at least one component of electronic device 200, including software (e.g., commands, programs, etc.). Memory 220 may include volatile and/or non-volatile memory. In this invention, commands or programs are software stored in memory 220, and may include an operating system for controlling the resources of electronic device 200, applications, and/or intermediate software that provides various functions to applications so that applications can utilize the resources of electronic device 200. In one embodiment, memory 220 may store commands that, when executed by processor 210, cause processor 210 to perform calculations. Memory 220 may store at least a portion of information received from a database via communication interface 230 and/or information sent to a database via communication interface 230. Specifically, memory 220 may store commands executed by processor 210.

The communication interface 230 enables wireless or wired communication between the electronic device 200 and a database or other external electronic devices. For example, the communication interface 230 can utilize eMBB (enhanced Mobile Broadband), URLLC (Ultra Reliable Low-Latency Communications), MMTC (Massive Machine Type Communications), LTE (Long-Term Evolution), LTE-A (LTE Advance), NR (New Radio), UMTS (Universal Mobile Telecommunications System), GSM (Global System for Mobile communications), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), WiBro (Wireless Broadband), WiFi (Wireless Fidelity), Bluetooth, and NFC (Near Field Communication). Wireless communication can be implemented via methods such as short-range wireless communication, GPS (Global Positioning System), or GNSS (Global Navigation Satellite System). For example, the communication interface 230 can implement wired communication via USB (Universal Serial Bus), HDMI (High Definition Multimedia Interface), RS-232 (Recommended Standard-232), or POTS (Plain Old Telephone Service). In one embodiment, the electronic device 200 can also be integrated with other devices. In this case, the communication interface 230 functions as a connection circuit and interface for connecting the electronic device 200 to the other device.

Hereinafter, it can be understood that the actions performed by the electronic device as described in Figures 3 to 10 are performed by the processor 210 of the electronic device 200 described in Figure 2.

Figure 3 shows a flowchart of a method for retrieving recommended keywords by analyzing the source code of candidate keywords in one embodiment of the present invention.

In action S310, electronic device 110 can obtain source code corresponding to one or more candidate keywords related to the execution of one or more test cases.

In one embodiment, each of the more than one test case may represent a test case used to perform tests on a specific software. More specifically, each of the more than one test case may represent a test case related to a page provided in the specific software (e.g., a login page, a member registration page, a customer support page, a homepage, etc.). For example, test cases related to a login page may include a user authentication test case attempting to log in by entering a username and password, a password recovery test case related to resetting the password, and an account locking test case locking the account in the event of consecutive password errors. Test cases related to the login page can include not only the front-end test cases illustrated in the above examples, but also back-end test cases, such as password storage test cases that use hash algorithms to verify whether passwords are securely stored in the database.

In one embodiment, each of the more than one candidate keyword may represent a keyword associated with the execution of one or more test cases. Each of the more than one candidate keyword may represent a keyword indicating an action to be performed based on the execution of at least one of the more than one test cases. For example, in order to execute a user authentication test case that attempts to log in by entering a username and password, the execution of a first action of entering a username, a second action of entering a password, and a third action of performing connection authentication using the entered username and password may be required. Therefore, candidate keywords related to the execution of user authentication test cases can be the first keyword indicating the first action, the second keyword indicating the second action, and the third keyword indicating the third action.

In one embodiment, the electronic device 110 can obtain source code corresponding to one or more candidate keywords related to the execution of one or more test cases from a resource file corresponding to a page associated with one or more test cases. The resource file corresponding to a page is explained in more detail in Figure 4.

In action S320, electronic device 110 can generate attribute information corresponding to each of the candidate keywords based on parsing the source code corresponding to one or more candidate keywords.

In one embodiment, electronic device 110 can identify portions of source code corresponding to each of the candidate keywords from the source code corresponding to the candidate keywords. In other words, the source code may include more than one portion of source code. Electronic device 110 can analyze the portion of source code corresponding to each candidate keyword. Electronic device 110 can generate attribute information corresponding to each candidate keyword based on the analysis of the portion of source code corresponding to each candidate keyword. The attribute information can be distinguished according to more than one keyword attribute. Electronic device 110 can analyze the portion of source code corresponding to each candidate keyword as more than one keyword attribute, thereby generating attribute information corresponding to each candidate keyword. One or more keyword attributes may include at least one of the following: page name, keyword name, keyword description, keyword tag, and keyword argument.

In action S330, electronic device 110 can receive target information for searching recommended keywords.

In one embodiment, electronic device 110 may receive target information from user terminal 120 for searching recommended keywords. User terminal 120 may be a device for generating test cases. A user of user terminal 120 may transmit target information to electronic device 110 through user terminal 120 in order to receive recommended keywords required for test case generation from electronic device 110.

In action S340, electronic device 110 can search for recommended keywords that match the target information from among the candidate keywords by comparing the attribute information and target information corresponding to each of the candidate keywords.

In one embodiment, electronic device 110 can use attribute information corresponding to one or more candidate keywords to retrieve recommended keywords that match target information. When a recommended keyword matching the target information is found among one or more candidate keywords, electronic device 110 can provide the retrieved recommended keyword to user terminal 120. Electronic device 110 can transmit a portion of the source code corresponding to the recommended keyword to user terminal 120. The user of user terminal 120 can use the recommended keyword received from electronic device 110 to generate test cases.

In one embodiment, electronic device 110 may retrieve recommended keywords that match target information from a plurality of candidate keywords stored in electronic device 110. However, for the sake of explanation below, the focus will be on how electronic device 110 retrieves recommended keywords that match target information from one or more candidate keywords associated with a page.

Figure 4 is a diagram illustrating the process of obtaining the source code of candidate keywords in one embodiment of the present invention.

In one embodiment, electronic device 110 can obtain a resource file 401 corresponding to a page. The resource file 401 corresponding to a page may be generated by an external user. The resource file 401 corresponding to a page may include source code 410 of test cases associated with a page, source code 420 of test data used in the test cases associated with a page, and source code 430 of one or more candidate keywords related to the execution of the test cases. Each of the one or more candidate keywords may be a keyword that indicates an action to be performed based on the execution of the test cases associated with a page. As mentioned above, test cases associated with a page can represent test cases that can be implemented for a page, such as front-end test cases and back-end test cases.

In one embodiment, electronic device 110 can identify the source code 401 of one or more candidate keywords from a resource file 401 corresponding to a page. More specifically, electronic device 110 can retrieve a first identifier in the resource file 401 corresponding to a page to identify the source code 430 of one or more candidate keywords. The first identifier can be an identifier corresponding to the starting column of the source code 430 of one or more candidate keywords. Electronic device 110 can identify the codes below the column where the first identifier is located in the resource file 401 as the source code 430 of one or more candidate keywords. Furthermore, the electronic device 110 can retrieve the identifier, i.e., the second marker, corresponding to the terminal column of the source code 430 of one or more candidate keywords in the resource file 401 corresponding to a page. In this case, the electronic device 110 can identify the code in the resource file 401 from the column where the first marker exists to the column where the second marker exists as the source code 430 of one or more candidate keywords.

Figure 5 is a diagram illustrating an embodiment of the present invention that identifies the portion of source code corresponding to each candidate keyword in the source code of one or more candidate keywords.

In one embodiment, the electronic device 110 can obtain a resource file 501 corresponding to a page, and can identify the source code 530 of one or more candidate keywords from the resource file 501 corresponding to the page. The electronic device 110 can retrieve the identifier, i.e., the first marker 540, corresponding to the starting column of the source code 530 of one or more candidate keywords in the resource file 501 corresponding to the page, and can identify the code below the column where the first marker 540 exists as the source code 530 of one or more candidate keywords.

In one embodiment, electronic device 110 can parse the source code 530 of more than one candidate keyword. Electronic device 110 can respond to receiving a first pull request to merge the source code 530 of more than one candidate keyword into the master branch, triggering the parsing of the source code 530 of the more than one candidate keyword. For example, the first pull request may include a resource file 501 corresponding to a page. Alternatively, after receiving a first pull request to merge the source code 530 of one or more candidate keywords into the master branch, the electronic device 110 may respond by triggering the parsing of the source code 530 of one or more candidate keywords upon deciding to merge the first pull request.

In one embodiment, electronic device 110 can identify portions of source code (e.g., portion source code 550, portion source code 560) corresponding to each of one or more candidate keywords in order to parse the source code 530 of one or more candidate keywords. Electronic device 110 can generate attribute information corresponding to each candidate keyword based on parsing the portions of source code corresponding to each candidate keyword (e.g., portion source code 550, portion source code 560).

In one embodiment, the electronic device 110 can identify columns (e.g., column 1 571 and column 2 572) in the source code 530 of one or more candidate keywords that do not begin with a space. The electronic device 110 can determine the columns (e.g., column 1 571 and column 2 572) that do not begin with a space as the start line of the portion of source code corresponding to the candidate keywords (e.g., portion source code 550 and portion source code 560). In other words, the resource file 501 corresponding to a page can have a specification set, namely, the start line of the portion of source code corresponding to the candidate keywords cannot begin with a space.

For example, referring to Figure 5, the electronic device 110 can identify the first column 571, which does not begin with a space, in the source code 530 of one or more candidate keywords as the starting column of the portion of source code 550 corresponding to the first candidate keyword. Similarly, the electronic device 110 can identify the second column 572, which does not begin with a space, in the source code 560 of one or more candidate keywords as the starting column of the portion of source code 560 corresponding to the second candidate keyword. The electronic device 110 can identify the code from the first column 571 to the column 573 preceding the second column 572 as the portion of source code 550 corresponding to the first candidate keyword, where the second column 572 is a column that does not begin with a space following the first column 571.

Figure 6 is a diagram illustrating an example of analyzing the source code of one or more candidate keywords in one embodiment of the present invention.

In one embodiment, electronic device 110 can identify and parse the source code 630 of one or more candidate keywords from a resource file 601 corresponding to a page. Electronic device 110 can identify portions of the source code corresponding to each of the candidate keywords from the source code 630. For example, referring to FIG6, electronic device 110 can identify the portion of the source code 650 corresponding to the third candidate keyword from the source code 630 of the candidate keywords. The electronic device 110 can generate partial information of one or more keyword attributes for each candidate keyword by analyzing the partial source code corresponding to each candidate keyword (e.g., partial source code 650). The partial information of one or more keyword attributes for each candidate keyword can constitute attribute information corresponding to each candidate keyword.

In one embodiment, one or more keyword attributes may include at least one of page name, keyword name, keyword description, keyword tag, and keyword argument. The following describes in detail the process by which electronic device 110 uses partial source code corresponding to each candidate keyword to generate partial information of one or more keyword attributes for each candidate keyword.

In one embodiment, electronic device 110 may generate a third candidate keyword page name (e.g., login) based on the file name of a resource file 601 corresponding to a page (e.g., Login_page.robot). The resource file 601 corresponding to a page may have a specification setting that the file name of the resource file 601 corresponding to a page must include the name of the page.

In one embodiment, electronic device 110 may generate the keyword name of the third candidate keyword (e.g., login the store app) based on the starting column 671 of the partial source code 650 corresponding to the third candidate keyword. As described above, electronic device 110 may identify the starting column 671 of the partial source code 650 corresponding to the third candidate keyword by retrieving columns that do not begin with a space. On the starting column of the partial source code corresponding to any candidate keyword, code corresponding to the keyword name of any candidate keyword may be written. Therefore, the electronic device 110 can generate code (e.g., login the store app) 651 written in the starting column 671 of the partial source code 650 corresponding to the third candidate keyword as part of the keyword name (e.g., login the store app) of the third candidate keyword.

In one embodiment, the electronic device 110 may pre-configure a marker to distinguish a specific keyword attribute (e.g., keyword description, keyword tag, or keyword argument) from other keyword attributes within one or more keyword attributes. The electronic device 110 may generate partial information of the specific keyword attribute of each candidate keyword based on retrieving the pre-configured marker from the portion of source code corresponding to each candidate keyword.

For example, the electronic device 110 may pre-configure a third tag (e.g., [Documentation]) to distinguish keyword descriptions from other keyword attributes, a fourth tag (e.g., [Tags]) to distinguish keyword tags from other keyword attributes, and a fifth tag (e.g., [Arguments]) to distinguish keyword arguments from other keyword attributes. Here, keyword descriptions may represent descriptions of actions performed by candidate keyword indicators, keyword tags may represent words describing the actions performed by candidate keyword indicators, and keyword arguments may represent parameters or input values required to perform the actions performed by candidate keyword indicators. Keyword descriptions, keyword tags, and keyword arguments serve as annotations to aid user understanding, rather than source code executed by the electronic device. The electronic device 110 can retrieve default-specific markers for keyword attributes from the portion of source code 650 corresponding to the third candidate keyword, and can use the code below the column where the retrieved markers are located to generate partial information about the specific keyword attributes of the third candidate keyword. Specifically, the electronic device 110 can use code written from the column where the retrieved markers are located to the column where other markers are located and the column where the executed code is located, before the first column, to generate partial information about the specific keyword attributes of the third candidate keyword.

Referring to Figure 6, the electronic device 110 can retrieve the third marker (e.g., [Documentation]) in the portion of source code 650 corresponding to the third candidate keyword, and can use the code below the column where the third marker exists to generate partial information of the keyword description of the third candidate keyword. For example, the electronic device 110 can use the code 652 written from the column where the third marker exists to the column before the other marker, i.e., the column where the fourth marker exists, to generate partial information of the keyword description of the third candidate keyword. Similarly, the electronic device 110 can retrieve the fourth tag (e.g., [Tags]) from the portion of source code 650 corresponding to the third candidate keyword, and can use the code below the column where the fourth tag exists to generate partial information of the keyword tag of the third candidate keyword. The electronic device 110 can use the code 653 written from the column where the fourth tag exists to the column before the other tags, i.e., the column where the fifth tag exists, to generate partial information of the keyword tag of the third candidate keyword. The electronic device 110 can retrieve the fifth tag (e.g., [Arguments]) from the portion of source code 650 corresponding to the third candidate keyword, and can use the code below the column where the fifth tag exists to generate partial information of the keyword arguments of the third candidate keyword. The electronic device 110 can use code 654, written from the column where the 5th marker exists down to the column where the execution code exists, to generate partial information of the keyword arguments of the 3rd candidate keyword.

In one embodiment, the identifiers for other keyword attributes (e.g., keyword descriptions, keyword tags, or keyword arguments) used to distinguish a specific keyword attribute may not be found in the portion of source code corresponding to a candidate keyword. In this case, the electronic device 110 may not generate partial information for a specific keyword attribute of a candidate keyword. For example, referring to FIG5, the fifth identifier (e.g., [Arguments]) corresponding to the keyword arguments may not be found in the portion of source code 550 corresponding to the first candidate keyword. In this case, when generating attribute information corresponding to the first candidate keyword, the electronic device 110 may not generate partial information about the keyword arguments of the first candidate keyword.

In one embodiment, when the source code of more than one candidate keyword is changed, the electronic device 110 can update the attribute information corresponding to each of the candidate keywords. More specifically, a particular user can modify or add the source code of more than one candidate keyword, and the particular user can transmit a second pull request to the electronic device 110 via a user terminal to update the source code of more than one candidate keyword. For example, the second pull request may include the particular user changing the source code of more than one candidate keyword. In this case, the electronic device 110 can respond to receiving the second pull request by identifying the changed code portion in the source code of the more than one candidate keyword. Electronic device 110 can compare the source code of one or more candidate keywords stored in existing electronic devices 110 with the source code of one or more candidate keywords included in the second fetch request, thereby identifying the changed code portion. Electronic device 110 can update the attribute information corresponding to each of the one or more candidate keywords based on the analysis of the identified code portion. For example, when the keyword name of a specific candidate keyword changes, electronic device 110 can update the keyword name to the changed keyword name, and further store the keyword name before the change as part of the keyword name information of the specific candidate keyword.

Figure 7 is a diagram illustrating an example of storing attribute information corresponding to one or more candidate keywords in one embodiment of the present invention.

In one embodiment, electronic device 110 may store attribute information corresponding to a plurality of candidate keywords. Figure 7 illustrates, exemplarily, a table 701 representing the attribute information corresponding to the plurality of candidate keywords stored in electronic device 110. Table 701 may include: attribute information 721 corresponding to a first candidate keyword associated with the home page, and attribute information 722 corresponding to a third candidate keyword associated with the login page. That is, table 701 may include attribute information of candidate keywords associated with various pages.

In one embodiment, the attribute information corresponding to the candidate keyword (e.g., attribute information 721, attribute information 722) may include partial information of each of the keyword attributes of the candidate keyword (e.g., page name 711, keyword name 712, keyword description 713, keyword tag 714, or keyword quote 715) and the credibility 730 of the candidate keyword. The electronic device 110 may use a credibility score (e.g., 82 points) to represent the credibility 730 of the candidate keyword.

In one embodiment, electronic device 110 can set the confidence level for one or more candidate keywords. Electronic device 110 can adjust the confidence level of one or more candidate keywords. More specifically, electronic device 110 can execute a specific test case in one or more test cases and can provide feedback to adjust the confidence level of at least one candidate keyword associated with the execution of the specific test case based on the execution of the specific test case. Here, each of the at least one candidate keyword can represent a keyword indicating an action to be performed based on the execution of the specific test case. Since the electronic device 110 executes at least one candidate keyword in order to perform a specific test case, it can determine whether the execution of the at least one candidate keyword is successful. The electronic device 110 can adjust the confidence level corresponding to the at least one candidate keyword based on whether the execution of the at least one candidate keyword is successful.

In one embodiment, when a candidate keyword is successfully executed according to a specific test case, the electronic device 110 may increase the confidence level of the candidate keyword. For example, the electronic device 110 may increase the confidence score representing the confidence level of a candidate keyword to a preset value (e.g., "1"). Conversely, when a candidate keyword is not successfully executed according to a specific test case, the electronic device 110 may decrease the confidence level of the candidate keyword. For example, the electronic device 110 may decrease the confidence score representing the confidence level of a candidate keyword to a preset value (e.g., "1"). Furthermore, when the confidence level corresponding to one or more candidate keywords is adjusted based on implementation feedback, and the confidence level corresponding to multiple candidate keywords decreases to below the critical confidence level, the electronic device 110 can be configured to request the administrator to update part of the source code corresponding to the specific candidate keyword, or delete part of the source code of the specific candidate keyword, in order to delete the attribute information corresponding to the specific candidate keyword, so that the specific candidate keyword is no longer recommended.

In one embodiment, electronic device 110 can individually set the confidence level of candidate keywords based on each test environment. A test environment can refer to the hardware, software, network, and other operating environments configured to execute test cases for software. A candidate keyword may work successfully in one test environment but may not work successfully in other test environments. Therefore, electronic device 110 can manage the confidence level of candidate keywords individually based on each test environment. For example, the first confidence score of the electronic device 110 representing the confidence of a candidate keyword in the first test environment and the second confidence score representing the confidence of a candidate keyword in the second test environment may be different from each other.

Figure 8 shows a flowchart of the process of searching and recommending keywords in one embodiment of the present invention.

In one embodiment, the electronic device 110 can search for recommended keywords that match the target information from among the candidate keywords by comparing attribute information and target information corresponding to each of the candidate keywords. Actions S841, S842, and S843 in Figure 8 can be at least a portion of actions S340 in Figure 3. The actions S841, S842, and S843 shown in Figure 8 will be explained in detail below.

In action S841, electronic device 110 can identify the keyword attributes mapped to target information.

In one embodiment, while receiving target information, electronic device 110 may simultaneously receive information from user terminal 120 regarding keyword attributes mapped to the target information. For example, the keyword attributes mapped to the target information may be at least one of keyword name, keyword description, keyword tag, and keyword arguments. In other embodiments, the target information may already include information regarding keyword attributes mapped to the target information.

In action S842, the electronic device 110 can calculate the matching degree between each candidate keyword and the target information by comparing partial information of the identified keyword attributes of each candidate keyword with the target information. For example, the matching degree can have a value between 0 and 1. In other words, the maximum value of the matching degree between each candidate keyword and the target information can be set to 1, and the minimum value can be set to 0.

For example, electronic device 110 can identify keyword attributes mapped to target information as keyword tags. In this case, electronic device 110 can compare partial information of the keyword tags of each candidate keyword with the target information. Based on the comparison of partial information of the keyword tags of each candidate keyword with the target information, electronic device 110 can calculate the matching degree between each candidate keyword and the target information.

In one embodiment, the electronic device 110 can calculate the matching degree between each candidate keyword and the target information based on the degree of overlap between partial information of the identified keyword attributes of each candidate keyword and the target information. For example, the higher the overlap between the candidate keywords and the target information, the higher the matching degree that the electronic device 110 can calculate. Conversely, the lower the overlap between the candidate keywords and the target information, the lower the matching degree that the electronic device 110 can calculate.

In one embodiment, the electronic device 110 can calculate a ratio as the degree of overlap between each candidate keyword and target information. This ratio is the ratio of the number of words that overlap between the partial information of the identified keyword attribute of each candidate keyword and the target information to the total number of words included in the partial information. For example, the keyword attribute mapped to the target information is a keyword tag, and the partial information of the keyword tag of the candidate keyword may include "store" and "common". When the word that overlaps between the partial information of the keyword tag of the candidate keyword and the target information is identified as "store", the electronic device 110 can calculate that the degree of overlap between the candidate keyword and the target information is 1/2 (=0.5). However, the method for calculating the duplication between candidate keywords and target information is not limited to this; various other methods can be used to calculate the duplication between candidate keywords and target information.

In action S843, electronic device 110 can calculate the result based on the matching degree and search for the recommended keyword among one or more candidate keywords.

In one embodiment, when at least one of the candidate keywords has a match degree with the target information that is above a critical value, the electronic device 110 can determine that the recommended keyword is searchable. In other words, the electronic device 110 can identify the candidate keywords with a match degree with the target information that is above a critical value from among the candidate keywords as recommended keywords. Conversely, when none of the candidate keywords have a match degree with the target information that reaches the critical value, the electronic device 110 can determine that the recommended keyword among the candidate keywords is not searchable. For example, the critical value can be 0.7, but it is not limited to this.

Figure 9 exemplarily illustrates a page displaying recommended keywords that match target information, according to one embodiment of the present invention.

In one embodiment, when it is determined that a recommended keyword among one or more candidate keywords is searchable, the electronic device 110 may provide the recommended keyword matching the target information to the user terminal 120. In other words, when at least one candidate keyword among one or more candidate keywords has a matching degree with the target information exceeding a critical value, the electronic device 110 may provide the user terminal 120 with the candidate keyword whose matching degree with the target information exceeds a critical value as a recommended keyword. The electronic device 110 may provide the user terminal 120 with a page 901 displaying the recommended keyword matching the target information among one or more candidate keywords.

Page 901 may display one or more recommended keywords 911, 921, 931, 941, ... that match the target information. Each of the recommended keywords 911, 921, 931, 941, ... that match the target information may be a candidate keyword whose matching degree with the target information is above the critical value among one or more candidate keywords. For example, referring to Figure 9, page 901 may display information 910 about the first recommended keyword 911, information 920 about the second recommended keyword 921, information 930 about the third recommended keyword 931, and information 940 about the fourth recommended keyword 941.

In one embodiment, electronic device 110 can determine the recommendation values of one or more recommended keywords 911, 921, 931, 941, ... Electronic device 110 can display the recommended keywords 911, 921, 931, 941, ... in descending order of recommendation value. For example, the higher the recommendation value of a recommended keyword, the more likely electronic device 110 will display that recommended keyword in the area closer to the first edge of page 901. Referring to Figure 9, the recommendation value of the first recommended keyword 911 may be higher than that of the second recommended keyword 921, and the recommendation value of the second recommended keyword 921 may be higher than that of the third recommended keyword 931.

In one embodiment, electronic device 110 can calculate a recommendation value for a recommended keyword using the matching degree of a recommended keyword with target information and the credibility corresponding to any recommended keyword. More specifically, electronic device 110 can calculate a recommendation value corresponding to a recommended keyword, which is the sum of a first weighted value applied to the matching degree of the recommended keyword with the target information and a second weighted value applied to the credibility corresponding to the recommended keyword. Here, the first weighted value can be greater than or equal to the second weighted value. Both the first weighted value and the second weighted value can have values greater than 0 and less than 1. For example, the first weighting value could be 0.8, and the second weighting value could be 0.5, but it is not limited to these. For reference, although page 901 of Figure 9 shows an example of displaying the matching degree and credibility of more than one recommended keyword 911, 921, 931, 941, ... with the target information, the information displayed on page 901 is not limited to this, and may also display other information related to more than one recommended keyword 911, 921, 931, 941, ... (e.g., part of the source code, recommended values, etc.).

In one embodiment, electronic device 110 responds to user input of a specific recommended keyword (e.g., the second recommended keyword 921) among one or more recommended keywords 911, 921, 931, 941, ... displayed on selection page 901, and can provide information (e.g., a portion of source code corresponding to the second recommended keyword 921) about the specific recommended keyword (e.g., the second recommended keyword 921) to user terminal 120.

Figure 10 is a diagram illustrating the software of an electronic device according to one embodiment of the present invention for providing a search function for recommended keywords.

In one embodiment, electronic device 110 may use a plurality of software programs to provide a function for searching recommended keywords that match target information. For example, electronic device 110 may use an automation framework 1001, a source code parser 1002, a keyword credibility management program 1003, and a recommended keyword search platform 1004. In one embodiment, at least one of the automation framework 1001, the source code parser 1002, the keyword credibility management program 1003, and the recommended keyword search platform 1004 may be included as part of electronic device 110. The actions performed by each software program will be described below.

First, the automation framework 1001 can generate source code (1011) for test cases associated with a page through an external user. Furthermore, the automation framework 1001 can generate source code for more than one candidate keyword (1012) and source code for test data used in the test cases (1013). In other words, the automation framework 1001 can generate resource files corresponding to a page.

Source code parser 1002 may receive pull requests (e.g., first pull request, second pull request) from automation framework 1011 (1021). Source code parser 1002 may respond to the recipient of the pull request by triggering a keyword parser (1022). The keyword parser of source code parser 1002 may generate attribute information corresponding to each candidate keyword based on parsing the source code of one or more candidate keywords (1023). Source code parser 1002 may pass the attribute information corresponding to each candidate keyword to keyword trust management program 1003.

The keyword confidence management program 1003 can adjust the confidence level of one or more candidate keywords (1031) based on the execution of test cases. The keyword confidence management program 1003 may include a storage location 1030, and can store the confidence level of each candidate keyword in the storage location 1030. The keyword confidence management program 1003 can store attribute information corresponding to each candidate keyword received from the source code parser 1002 in the storage location 1030.

The recommended keyword search platform 1004 can provide users who want to generate test cases with recommended keywords that match the target information through the user terminal 120. Specifically, the recommended keyword search platform 1004 can receive target information from the user terminal 120 (1041). The recommended keyword search platform 1004 can use the attribute information of each candidate keyword stored in the storage location 1030 to search for recommended keywords that match the target information (1042). The recommended keyword search platform 1004 can provide the user terminal 120 with a page displaying the recommended keywords (1043).

The method of this invention can be implemented by a computer. The computer may include, for example, an electronic device capable of processing. In this invention, the steps of the method are shown and described in a prescribed order; however, in addition to being performed sequentially, the steps may also be performed in any combination according to this invention. In one embodiment, at least some steps may be performed in parallel, repeatedly, or heuristically. This invention does not preclude changes or modifications to the method. In one embodiment, at least some steps may be omitted or other steps may be added.

Various embodiments of the present invention can be implemented in the form of recorded software on a machine-readable storage medium. The software can be software used to implement the various embodiments of the present invention described above. Programmers in the art to which the present invention pertains can infer the software based on the various embodiments of the present invention. A device is an apparatus capable of performing actions according to commands called from a recording medium, such as a computer. In one embodiment, the device can be an electronic device of an embodiment of the present invention. In one embodiment, the processor of the device executes the called commands, thereby enabling the components of the device to perform functions corresponding to those commands. In one embodiment, the processor can be a processor of an embodiment of the present invention. Recording medium can refer to all types of recording medium that can be read and stored by a device. Recording medium can include, for example, ROM (Read-only memory), RAM (Random-access memory), CD-ROM (Compact Disc Read-Only Memory), magnetic tape, floppy disk, optical information storage device, etc. In one embodiment, the recording medium can be memory. In one embodiment, the recording medium can be implemented in a form distributed across computer systems connected to a network. Software can be distributed and executed across computer systems. The recording medium can be a non-transitory recording medium. Non-transitory recording media refers to media that actually exist, whether the information is stored semi-permanently or temporarily, and does not include transient signals.

The technical concept of this invention has been described above based on various embodiments. However, the technical concept of this invention includes various substitutions, variations, and modifications that can be implemented within the scope of understanding of a person skilled in the art to which this invention pertains. Furthermore, it should be understood that such substitutions, variations, and modifications may be included within the scope of the appended invention claims. The embodiments of this invention can be combined with each other. The embodiments can be combined in various ways depending on the number of cases, and the combined embodiments also fall within the scope of this invention.

110: Electronic Device 120: User Terminal 200: Electronic Device 210: Processor 220: Memory 230: Communication Interface 401: Resource File Corresponding to a Page 410: Source Code of a Test Case Associated with a Page 420: Source Code of Test Data Used in a Test Case Associated with a Page 430: Source Code of One or More Candidate Keywords Related to the Execution of a Test Case 501: Resource File Corresponding to a Page 530: Source Code of One or More Candidate Keywords 540: First Tag 550: Partial Source Code Corresponding to the First Candidate Keyword 560: Partial source code corresponding to the second candidate keyword 571: Column 1 572: Column 2 573: Column 601: Resource file corresponding to a page 630: Source code of more than one candidate keyword 650: Partial source code corresponding to the third candidate keyword 651: Code 652: Code 653: Code 654: Code 671: Starting column 701: Table 711: Page name 712: Keyword name 713: Keyword description 714: Keyword label 715: Keyword parameters 721: Attribute information 722: Attribute information 730: Credibility 901: Page 910: Information 911: Top Recommended Keyword 920: Information 921: Top Recommended Keyword 930: Information 931: Top Recommended Keyword 940: Information 941: Top Recommended Keyword 1001: Automation Framework 1002: Source Code Analysis Program 1003: Keyword Reliability Management Program 1004: Recommended Keyword Search Platform 1011: Action 1012: Action 1013: Action 1021: Action 1022: Action 1023: Action 1031: Action 1030: Storage Location 1041: Action 1042: Action 1043: Action S310: Action S320: Action S330: Action S340: Action S841: Action S842: Action S843: Action

Figure 1 illustrates the environment of an electronic device to which one embodiment of the present invention can be applied. Figure 2 is a block diagram of the electronic device according to one embodiment of the present invention. Figure 3 is a flowchart illustrating a method for retrieving and recommending keywords by parsing the source code of candidate keywords according to one embodiment of the present invention. Figure 4 is a diagram illustrating the process of obtaining the source code of candidate keywords according to one embodiment of the present invention. Figure 5 is a diagram illustrating an example of identifying the portion of source code corresponding to each candidate keyword from the source code of one or more candidate keywords according to one embodiment of the present invention. Figure 6 is a diagram illustrating an example of parsing the source code of one or more candidate keywords according to one embodiment of the present invention. Figure 7 is a diagram illustrating an example of storing attribute information corresponding to one or more candidate keywords in one embodiment of the present invention. Figure 8 shows a flowchart of the process of retrieving recommended keywords in one embodiment of the present invention. Figure 9 exemplarily shows a page displaying recommended keywords matching the target information in one embodiment of the present invention. Figure 10 is a diagram illustrating the software used by the electronic device in one embodiment of the present invention to provide the function of retrieving recommended keywords.

S310: Action S320: Action S330: Action S340: Action

Claims (18)

A method implemented by an electronic device includes the following steps: Obtaining source code corresponding to one or more candidate keywords related to the execution of one or more test cases; Generating attribute information corresponding to each of the one or more candidate keywords based on parsing the source code; Receiving target information for retrieving recommended keywords; and Retrieving recommended keywords matching the target information from the one or more candidate keywords by comparing the attribute information corresponding to each of the one or more candidate keywords with the target information, The step of generating attribute information corresponding to each of the one or more candidate keywords includes the following steps: Identify the portion of source code corresponding to each of the aforementioned candidate keywords from the aforementioned source code; and Based on analyzing the portion of source code corresponding to each of the aforementioned candidate keywords, generate partial information of each of the aforementioned candidate keyword's keyword attributes. The partial information of each of the aforementioned candidate keyword's keyword attributes constitutes the attribute information corresponding to each of the aforementioned candidate keywords. As in Request 1, where each of the above-mentioned test cases represents a test case associated with a page, the steps to obtain the above-mentioned source code include the following: Identifying the above-mentioned source code from the resource file corresponding to the above-mentioned page. As in Request 2, the step of generating attribute information corresponding to each of the above-mentioned candidate keywords further includes the following steps: In response to receiving the first pull request to merge the above source code into the main branch, trigger the parsing of the above source code. As in the method of claim 1, the step of generating attribute information corresponding to each of the above-mentioned candidate keywords includes the following steps: Identifying one or more columns in the above-mentioned source code that do not begin with a space, and determining each of the above-mentioned columns as the starting column of the portion of source code corresponding to the candidate keywords. As in the method of Request 1, the above-mentioned keyword attributes include at least one of the following: page name, keyword name, keyword description, keyword tag, and keyword argument. As in the method of claim 1, wherein for a specific keyword attribute among the aforementioned one or more keyword attributes, a marker is pre-set to distinguish it from other keyword attributes, the steps for generating partial information of each of the aforementioned candidate keyword's one or more keyword attributes include the following steps: Based on retrieving the aforementioned marker from the portion of source code corresponding to each of the aforementioned candidate keywords, partial information of the aforementioned specific keyword attribute of each of the aforementioned candidate keywords is generated. The method of claim 1 further includes the following steps: Receiving a second fetch request to update the source code based on the changes to the source code; In response to receiving the second fetch request, identifying the changed code portion in the source code; and Based on analyzing the identified code portion, updating the attribute information corresponding to each of the one or more candidate keywords. The method described in Request 1 further includes the following steps: Assigning credibility to each of the above-mentioned candidate keywords. As in the method of claim 8, the step of setting the confidence level for each of the above-mentioned candidate keywords includes the following steps: In the above-mentioned test cases, execute a specific test case and determine whether the execution of at least one candidate keyword related to the execution of the specific test case is successful; and Based on the success of the execution of the at least one candidate keyword, adjust the confidence level corresponding to each of the at least one candidate keyword. The method described in Request 1 includes the following steps for retrieving the recommended keywords: Identifying keyword attributes that map to the target information; Calculating the matching degree between each candidate keyword and the target information by comparing partial information of the identified keyword attributes of each candidate keyword with the target information; Based on the calculated matching degree, retrieving the recommended keywords from the one or more candidate keywords. The method of claim 10, wherein the step of retrieving the recommended keyword from the above-mentioned candidate keywords includes the following steps: From the above-mentioned candidate keywords, the candidate keywords whose matching degree with the target information is above a critical value are identified as the recommended keywords. The method of claim 11 further includes the following steps: When there are multiple recommended keywords as determined above, determine the recommended value of each of the multiple recommended keywords; and display the multiple recommended keywords in descending order of their recommended values. The method of claim 12, wherein the step of determining the recommendation value of each of the plurality of recommended keywords includes the following steps: Calculating the value obtained by applying a first weight to the match degree of the target information corresponding to the recommended keyword and adding a second weight to the credibility corresponding to the recommended keyword, and using this value as the recommendation value. The method of claim 13, wherein the first weighted value is greater than or equal to the second weighted value. The method of claim 10, wherein the step of calculating the matching degree between each candidate keyword and the target information includes the following steps: Calculating the overlap between partial information of the identified keyword attributes of each candidate keyword and the target information; and Based on the calculated overlap, calculating the matching degree between each candidate keyword and the target information. As in the method of claim 15, the step of calculating the repetition between the partial information of the identified keyword attributes and the target information for each candidate keyword is: the repetition is calculated using a ratio, which is the ratio of the number of words that overlap between the partial information of the identified keyword attributes and the target information for each candidate keyword to the total number of words included in the partial information. An electronic device includes: one or more processors; and one or more memories storing commands to be executed by the one or more processors; the electronic device is configured such that, upon executing the commands, the one or more processors perform the method described in any one of claims 1 to 16. A non-temporary computer-readable recording medium that records commands that, when executed by one or more processors, cause the one or more processors to perform actions, wherein the commands are configured to cause the one or more processors to perform any of the methods described in claims 1 to 16.