TWI912821B - Apparatus, method, and recording medium for generating test case - Google Patents

Abstract

This invention proposes an electronic device for generating test cases. The electronic device of this invention includes one or more processors; and one or more memories storing commands executed by the one or more processors; and the one or more processors are configured such that, when executing the commands, they generate one or more keywords in association with test steps and verification steps that may occur during the process of testing one or more pages, generate one or more tags to be assigned to each of the one or more generated keywords, and generate a script for test cases including at least one step based on the mapping between the one or more generated tags and page elements belonging to the one or more pages.

Description

Devices, methods, and recording media for generating test cases

This invention relates to a technique for generating test cases. More specifically, this invention relates to a technique for generating test case scripts by mapping keywords generated in association with test steps and verification steps.

Software testing refers to the process of verifying whether software functions correctly as intended by the developer. In recent years, automated testing has become increasingly important in the software development process. Software automated testing can include techniques for automatically generating test cases. Automated testing can perform repeatable testing tasks without human intervention, thereby significantly improving testing efficiency. Furthermore, automated testing not only improves the accuracy and reliability of tests but also plays a significant role in shortening testing cycles and reducing related costs. Current test case writing methods primarily involve test engineers manually writing test case scripts. However, this manual process is not only time-consuming but may also result in insufficient test coverage and inconsistent test case quality.

[Problem to be Solved by the Invention] This invention relates to a technique for generating test cases. [Technical Means for Solving the Problem]

This invention provides a method for generating test cases. One embodiment of the invention may include the following steps: generating one or more keywords in association with test steps and verification steps that may occur during the process of testing one or more pages; generating one or more tags to be assigned to each of the generated one or more keywords; and generating a script for test cases including at least one check step based on the mapping between the generated one or more tags and page elements belonging to the one or more pages.

In one embodiment, the steps of generating one or more of the above keywords may include the following steps: generating atomic keywords corresponding to a single test step or a single verification step; and generating scenario keywords corresponding to a single scenario that includes a plurality of check steps for verifying the functionality of the page; the scenario keywords are composed of a plurality of atomic keywords.

In one embodiment, a test step may correspond to a page element belonging to one or more of the aforementioned pages, and the step of generating one or more of the aforementioned keywords may include the following steps: generating atomic keywords in a manner that includes information representing the aforementioned page element corresponding to the aforementioned test step.

In one embodiment, a page element belonging to one or more of the aforementioned pages may represent a single component constituting the user interface displayed by each of the aforementioned pages.

In one embodiment, the steps of generating one or more tags may include the following steps: grouping the generated one or more keywords based on page elements belonging to one or more pages; and assigning the same tag to the keywords belonging to each group of the group generated based on the grouping results.

In one embodiment, the step of generating one or more of the above-mentioned tags may include the following steps: when a test step is accompanied by one or more verification steps, assigning the same tag to a plurality of keywords generated in association with the test step and the one or more verification steps.

In one embodiment, the steps of generating one or more of the above-mentioned tags may include the following steps: parsing one of the above-mentioned keywords word by word, and using at least a portion of the parsed words to generate a tag to be assigned to the above-mentioned keyword.

In one embodiment, the steps of generating the script for the test cases may include the following steps: mapping each of the generated tags to one of the page elements belonging to the page; receiving at least one user input for generating the test cases; and identifying at least one page element corresponding to the at least one user input, and identifying at least one tag mapped to the identified at least one page element, thereby generating the script for the test cases.

In one embodiment, the step of receiving the at least one user input may include the following steps: connecting the user's user terminal to a device farm, which is the environment in which the electronic device operates; transmitting the one or more pages to the user's device; and rendering the one or more pages on the user terminal, thereby receiving the at least one user input from the user terminal.

In one embodiment, the steps for generating the script for the test cases may include the following steps: for each of the at least one tag, identifying at least one keyword assigned to each of the at least one tag, and combining the code corresponding to the at least one keyword to generate a temporary script; and combining the temporary script generated for each of the at least one tag to generate the script for the test cases.

In one embodiment, the steps for generating the aforementioned temporary script may include the following steps: when there are multiple keywords assigned to the aforementioned tags, by combining the code corresponding to each of the multiple keywords assigned to the aforementioned tags in the execution order of the tests corresponding to each of the multiple keywords, a temporary script corresponding to the aforementioned tags is generated.

In one embodiment, the steps for generating the script for the above test case may include the following steps: determining the action order of the at least one page element based on the input order of the at least one user input; and generating the script for the above test case by combining the temporary scripts generated corresponding to each of the at least one tag according to the action order of the corresponding page elements.

In one embodiment, the steps to generate one or more of the above keywords may include the following steps: obtaining the checking steps for each of the above multiple test cases by performing a pre-stored plurality of test cases on the one or more of the above pages.

The present invention provides an apparatus for generating test cases. The electronic apparatus of the present invention may include: one or more processors; and one or more memories storing commands executed by the one or more processors. The one or more processors are configured to: generate one or more keywords in association with test steps and verification steps that may occur during the execution of the commands, and generate one or more tags to be assigned to each of the generated keywords; and generate a script for test cases including at least one check step based on the mapping between the generated tags and page elements belonging to the one or more pages.

The present invention provides a non-transitory computer-readable recording medium that records commands for managing and executing test data related to test cases. The commands recorded in the recording medium of one embodiment of the present invention can be commands that can be executed by one or more processors or implemented on a computer. These commands, when executed by one or more processors, can generate one or more keywords in association with test and verification steps that may occur during the process of testing one or more pages, and generate one or more tags to be assigned to each of the generated keywords. Based on the mapping between the generated tags and page elements belonging to the one or more pages, scripts for test cases including at least one check step are generated. [Effects of the Invention]

According to this invention, since the script can receive user input to select page elements belonging to the page to generate test cases, the time required to generate test cases can be greatly reduced.

According to the present invention, one or more keywords can be grouped based on page elements, and the same tags can be assigned to the keywords included in the same group, thereby generating tags that can correspond one-to-one with page elements as parameters.

According to this invention, by mapping page elements and tags belonging to more than one page, the test steps or verification steps included in the test case can be identified using tags mapped to the page elements selected by the user.

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 present invention and are not intended to limit them to any particular embodiment. The technical concept of the present 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 technical concept of the present 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 herein may include the meaning of the plural forms 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 not 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 phrase “based on” as used in this document is used to describe one or more factors that influence the determination or judgment made in the statement or text, but does not exclude additional factors that influence the determination or judgment made.

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 various embodiments described in this invention 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 that embodiment.

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

Test cases may include or represent a series of operations, actions, conditions and/or variables designed to verify whether the software conforms to specific design specifications.

An embodiment of the electronic device 110 may be a device for generating and storing one or more test cases. The electronic device 110 may be implemented using one or more computing devices. For example, all functions of the electronic device 110 may be implemented using a single computing device. As another example, a first function of the electronic device 110 may be implemented using a first computing device, and a second function may be implemented using a second computing device. As another example, a plurality of computing devices may be used to implement all or specific functions of the electronic device 110. The aforementioned computing devices may 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 may be computing devices.

In one embodiment, user terminal 120 may be connected to a device farm, which is the environment in which electronic device 110 operates. Test cases for testing applications using electronic device 110 may be generated. User terminal 120 may receive pages provided by the application from electronic device 110. User terminal 120 may render the received pages. User terminal 120 may receive user input from an input unit and transmit the received user input to electronic device 110. Electronic device 110 may identify page elements corresponding to the user input received from user terminal 120 and may use the identified page elements to generate test cases.

In one embodiment, electronic device 110 and user terminal 120 can perform actions using a single device. User terminal 120 may be included in electronic device 110 as all or part of its constituent elements. In this case, for example, various information exchanged between electronic device 110 and user terminal 120 via a network may be various information exchanged between the constituent elements of a single device.

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 that allows the user to input or output information, and can communicate 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 a user, and can receive input from the user and transmit it to electronic device 110. Specifically, user terminal 120 can obtain input from the user representing various page calls, and generate commands corresponding to the obtained input representing various page calls. User terminal 120 can transmit commands representing various page calls to electronic device 110. Input obtained from the user may include various forms of input such as mouse clicks, touch controls using a touch panel 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 serves to connect 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).

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 of Figure 1) can generate and store more than one test case. 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, some constituent elements may be additionally or alternatively integrated, 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 expressly stated herein, 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 expressly stated herein, 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.).

In one embodiment, processor 210 can control at least one component of electronic device 200 connected to processor 210 via driver software (e.g., commands, programs, etc.). Furthermore, processor 210 can perform various actions related to the present invention, such as calculation, processing, data generation, and manipulation. Processor 210 can load data from memory 220 or store data in memory 220. In one embodiment, processor 210 can control 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.

In one embodiment, memory 220 may store various information (data). The information stored in memory 220 is information acquired, processed, or used by at least one component of electronic device 200, and may include 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.

In one embodiment, the communication interface 230 enables wireless or wired communication between the electronic device 200 and a database or other external electronic device. 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, NFC (Near Field Communication), and GPS (Global System for Mobile Communications). Wireless communication can be implemented using methods such as Positioning System (GPS) or GNSS (Global Navigation Satellite System). For example, communication interface 230 can implement wired communication via methods such as USB (Universal Serial Bus), HDMI (High Definition Multimedia Interface), RS-232 (Recommended Standard-232), or POTS (Plain Old Telephone Service). In one embodiment, electronic device 200 can also be integrated with other devices. In this case, communication interface 230 can function as a connection circuit or interface connecting electronic device 200 to corresponding other devices.

The actions described below in Figures 3 to 9 as being performed by an electronic device can be understood as being performed by the processor 210 of the electronic device 200 described in Figure 2.

Figure 3 is a flowchart illustrating the process of generating test cases by an electronic device according to one embodiment of the present invention.

In action S310, electronic device 110 may generate one or more keywords in association with the test steps and verification steps that may occur during the process of testing one or more pages.

In one embodiment, electronic device 110 can perform software testing on an application. Electronic device 110 can test (or inspect) actions provided on more than one page of the application, each page potentially requiring testing of various actions. To test the actions provided on each page of the application, test steps or verification steps can be performed using test cases. In other words, a test case can consist of more than one inspection step (e.g., a test step, a verification step). Executing a test case can mean executing more than one inspection step that constitutes the test case.

In this specification, "test steps" refer to the steps taken to verify whether interactions with page elements belonging to an application's page are performed correctly. A page element represents a single component that constitutes the user interface displayed on a specific page. For example, a page element may represent a specific part of a webpage, such as a button or icon. Test steps simulate interactions with page elements, such as clicking buttons, clicking icons, clicking links, and entering text, to verify whether the action is performed as expected. In other words, the purpose of test steps is to verify whether a specific page element responds correctly to user interactions. Furthermore, a "verification step" can represent a step to confirm whether the result of an interaction with a page element belonging to the application page matches the predicted result. For example, by clicking a specific button displayed on the page in the test step, it can be confirmed whether specific information is displayed on that page, or whether the specific information is displayed when moving to another page. In the verification step, the reliability of the result can be evaluated by comparing the predicted output with the actual output.

In one embodiment, electronic device 110 can obtain inspection steps for each of the multiple test cases by executing a pre-stored plurality of test cases for one or more pages of an application. For example, electronic device 110 can receive and store a plurality of test cases for one or more pages from an external device (e.g., user terminal 120). Alternatively, electronic device 110 can generate and store a single inspection step itself. Electronic device 110 can identify page elements belonging to one or more pages of an application and generate an inspection step corresponding to each identified page element.

In one embodiment, the electronic device 110 can generate atomic keywords corresponding to a single check step (e.g., a testing step, a verification step) and scenario keywords corresponding to a scenario including multiple check steps. In other words, a keyword (e.g., an atomic keyword, a scenario keyword) can represent more than one check step.

In action S320, electronic device 110 can generate more than one tag to be assigned to each of the generated keywords. In one embodiment, electronic device 110 can assign one tag to one keyword. Furthermore, electronic device 110 can assign the same tag to a plurality of keywords. Specifically, electronic device 110 can group more than one keyword generated in association with more than one page based on page elements, and can assign the same tag to keywords included in the same group. For example, electronic device 110 can group check steps associated with the same page element into one group, but is not limited to this.

In action S330, electronic device 110 can automatically generate a script containing at least one step of test cases based on the mapping between one or more generated tags and page elements belonging to one or more pages. In other words, electronic device 110 can map each of the one or more generated tags to a page element.

In one embodiment, electronic device 110 may receive user input from user terminal 120 for generating specific test cases. The user input may represent a page element belonging to one or more pages of an application. Electronic device 110 may analyze the page element represented by the received user input and identify tags mapped to the analyzed page element. Electronic device 110 may then generate scripts for specific test cases using keywords assigned to the identified tags. For example, electronic device 110 may automatically generate scripts for specific test cases by combining the codes of the keywords assigned to the identified tags.

Figure 4 is a diagram illustrating the process by which an electronic device of one embodiment of the present invention generates one or more keywords in conjunction with testing and verification steps.

In one embodiment, electronic device 110 may generate one or more keywords in association with test steps and verification steps that may occur during the process of testing one or more pages. However, it is not limited to this; electronic device 110 may generate keywords based on information received from user terminal 120, and may also receive and store keywords generated by user terminal 120. The following description mainly describes embodiments of keyword generation by electronic device 110.

In one embodiment, electronic device 110 may generate an atomic keyword 420 corresponding to a single test step or a single verification step. In other words, electronic device 110 may generate an atomic keyword 420 corresponding to a check step. The atomic keyword 420 may represent a check step (e.g., a test step, a verification step). Electronic device 110 may generate an atomic keyword 420 corresponding to a single test step or a single verification step that may occur during the actions provided on a page of a testing application. For example, referring to Figure 4, electronic device 110 may generate an atomic keyword 420 corresponding to a test step confirming the action of clicking the alert icon 421 on page 410. In this case, the test step may be represented as corresponding to the alert icon 421, i.e., a page element of page 410. As another example, electronic device 110 may generate each atomic keyword 420 corresponding to a test step confirming the action of clicking the search icon 422 or the supermarket icon 423 on page 410.

In one embodiment, electronic device 110 may correspond to a single scenario including a plurality of check steps for verifying the functionality of a page used to apply an application, and generate scenario keywords 430. Scenario keywords 430 may consist of a plurality of atomic keywords 420, each atomic keyword 420 corresponding to a check step constituting the scenario. In other words, scenario keywords 430 may represent two or more check steps.

A scenario can represent a specific function provided by one or more pages in an application. For example, there might be a scenario representing a login function. A scenario representing a login function might include test steps for clicking a login box, test steps for entering a username and password in the login box, and verification steps for confirming whether to output a page showing login using the entered username and password. In this case, the pages associated with each of the multiple check steps constituting the scenario do not need to be all the same. That is, the pages associated with the first check step and the pages associated with the second check step may be different among the multiple steps constituting the scenario. In this specification, the pages associated with check steps may represent the pages that provide the actions to be tested in the check steps.

For example, referring to Figure 4, electronic device 110 can generate first-scene keywords corresponding to a first scenario representing the function of moving from page 410 to the homepage of the application. The first scenario may include a test step of clicking the homepage button 431 displayed on page 410 and a verification step of confirming whether the page loaded by clicking the homepage button 431 is the homepage. That is, the first-scene keywords generated corresponding to the first scenario can represent a test step and a verification step. As another example, electronic device 110 can generate second-scene keywords corresponding to a second scenario representing the function of moving from page 410 to the search page of the application. The second scenario may include a test step of clicking the search button 432, and a verification step of confirming whether the page loaded by clicking the search button 432 is the search page.

Figure 5 is an illustration of the keywords related to the generation, testing and verification steps of an electronic device according to one embodiment of the present invention.

In one embodiment, test steps that may occur during the process of testing actions provided on more than one page of an application can correspond to a page element belonging to more than one page. For example, referring to Figure 5, confirming that the first test step of clicking the search icon 511 on the gate page 510 of the application can correspond to the search icon 511, which is a page element belonging to the gate page 510.

In one embodiment, electronic device 110 can generate atomic keywords corresponding to a corresponding test step, including information representing the page associated with the test step. Furthermore, electronic device 110 can generate atomic keywords corresponding to a corresponding test step, including information representing the page element associated with the test step. Information representing page numbers and page numbers may represent words describing each page and words describing page elements, but is not necessarily limited to this. However, for ease of explanation, the following description primarily focuses on an embodiment where the information representing pages and page elements is in the form of words.

For example, referring to Figure 5, electronic device 110 may generate an atomic keyword 420 corresponding to a first test step, which verifies the action of clicking the search icon 511 on the application's gateway page 510. Information indicating the gateway page 510 associated with the first test step may include words such as "gateway" and "page". Similarly, information indicating the search icon 511, i.e., the page element corresponding to the first test step, may include words such as "search" and "icon". In this case, the atomic keyword 420 corresponding to the first test step may include, but is not limited to, all of the above-mentioned words such as "click search icon in gateway page".

For example, a search page 520 can be output by clicking the search icon 511 on the application's gateway page 510. The electronic device 110 can generate an atomic keyword 420 corresponding to a second test step, which confirms the action of entering a search keyword into the search box 521 in the search page 520. Information indicating the search page 520 associated with the second test step may include words such as "search" and "page". Similarly, information indicating the search box 521, the page element corresponding to the second test step, may include words such as "search" and "box". In this case, the atomic keyword 420 corresponding to the second test step may include, but is not limited to, all of the aforementioned words such as "input search keyword into search box in search page". Similarly, the electronic device 110 may generate an atomic keyword 420 such as "click search icon in search page" in the third test step, which confirms the action of clicking search icon 522 on search page 520.

In one embodiment, validation steps that may occur during the process of testing an action provided on one or more pages of an application can correspond to one or more page elements belonging to one or more pages. A validation step can correspond to the page element finally selected during the testing of a specific action, but is not limited to this. For example, when a validation step interacts with multiple page elements during the testing of a specific action, it can also correspond to multiple page elements. Referring to Figure 5, it is confirmed that the first validation step of the keyword results page 530 output after clicking the search icon 522 on the application's search page 520 corresponds to the search icon 522, i.e., the page element finally selected on the search page 520.

In one embodiment, electronic device 110 can generate atomic keywords corresponding to verification steps, including information representing the page related to the verification steps. Furthermore, electronic device 110 can generate atomic keywords corresponding to verification steps, including information representing the page elements corresponding to the verification steps. For example, after a specific search keyword is entered into the search box 521 of the search page 520, electronic device 110 can generate atomic keyword 420 corresponding to confirming whether the keyword results page 530 output by clicking the search icon 522 meets the first verification step for the specific search keyword. Information indicating the search page 520 related to the first verification step may include words such as "search" and "page". Information indicating the search icon 522, i.e., the page element corresponding to the first verification step, may include words such as "search" and "icon". In this case, the atomic keyword 420 corresponding to the first verification step may be generated by all of the above-mentioned words such as "check search result by clicking search icon in search page".

In another embodiment, the electronic device 110 does not include a page associated with the verification step, nor information indicating the page elements corresponding to the verification step. Instead, it may only include information indicating the verification step to generate the atomic keyword 420 corresponding to the verification step. In this case, the atomic keyword 420 corresponding to the first verification step can be simplified to "check the search result".

Figure 6 is a diagram illustrating the process by which an electronic device of one embodiment of the present invention generates tags to be assigned to keywords.

In one embodiment, electronic device 110 can group one or more generated keywords based on page elements belonging to one or more pages of an application. Electronic device 110 can generate one or more groups by grouping the generated keywords, and can assign the same tag to all keywords included in each group.

In one embodiment, the electronic device 110 can identify one or more check steps corresponding to one or more page elements belonging to one or more pages, and can group the atomic keywords representing each of the identified check steps into a group. Furthermore, scene keywords associated with a page element can also be grouped into the same group. Here, when two or more check steps represented by a scene keyword both correspond to a page element, the scene keyword can represent association with a page element. For example, referring to Figure 5, the electronic device 110 can group the atomic keywords of the third test step, which respectively confirms the action of clicking the search icon belonging to the search page 520, and the first verification step, which confirms whether the keyword result page 530 output based on clicking the search icon 522 meets the specific search keywords, into the same group. In another embodiment, the electronic device 110 can also group the atomic keywords represented by the check steps corresponding to each of two or more page elements, and the scenario keywords associated with the two or more page elements into the same group. Grouping the keywords associated with two or more page elements into the same group indicates that the two or more page elements are related to each other. For example, referring to Figure 5, when search icon 511 is selected, search box 521 is automatically activated, so keywords related to search icon 511 and search box 521 can be grouped into the same group. However, even if two or more page elements are related to each other, keywords related to each page element can be generated in independent groups, as in existing embodiments.

In one embodiment, when a check step is accompanied by other check steps, the electronic device 110 may group the check step and the other check steps into the same group. A check step accompanied by other check steps may mean that when performing one check step, other check steps must also be performed. For example, the other check steps may be more than one check step. For example, the electronic device 110 may receive information about the check step accompanied by other check steps from an external device (or a test engineer).

In one embodiment, a test step may be accompanied by more than one verification step. For example, a first test step that verifies the action of clicking the search icon 511 on the gate page 510 may be accompanied by a verification step that verifies whether the search page 520 output corresponding to clicking the search icon 511 matches the predicted output page. When a test step is accompanied by more than one verification step, the electronic device 110 may assign the same label to a plurality of keywords generated in association with the test step and more than one verification step.

In one embodiment, electronic device 110 can generate tags to be assigned to a keyword. Electronic device 110 can parse a keyword word by word and use at least a portion of the parsed words to generate tags to be assigned to the keyword. Electronic device 110 may generate tags to be assigned to a keyword in a manner that includes information indicating an action to test or verify a check step represented by the keyword, or a function to test or verify a scenario represented by the keyword. For example, referring to Figure 6, the electronic device 110 can enter search keywords in the search box of the application's address page to generate a label 621 corresponding to the atomicity keyword 611 to be assigned to the fourth test step for appending the address. The action to be tested in the fourth test step is the action of appending the address, which can include the word "Address" to represent "address," generating the label 621 to be assigned to the atomicity keyword 611. As another example, the electronic device 110 can enter search keywords in the search box of the address page to generate a label 621 corresponding to the atomicity keyword 612 to be assigned to the second verification step for verifying whether the output result matches the search keywords. At this point, the second verification step accompanies the fourth testing step, so the same label 621, which is assigned to the atomic keyword 611 corresponding to the fourth testing step, can be assigned to the atomic keyword 612 corresponding to the second verification step. Similarly, the electronic device 110 can generate a label 622, which will be assigned to the scenario keyword 613 corresponding to the third scenario of closing the login bottom sheet on the application's login page. At this point, the function to be tested in the third scene is to disable the function of logging into the bottom form. This can include words such as "login", "bottom", and "sheet" to represent "login to the bottom form", generating a label 622 to be assigned to scene keyword 613.

In one embodiment, electronic device 110 can delete specific keywords within each group after grouping more than one keyword. Specifically, a specific group includes both scenario keywords and atomic keywords, where the scenario keywords represent multiple check steps, and the atomic keywords represent check steps. In this case, electronic device 110 can delete atomic type keywords representing duplicate scenario keywords and duplicate check steps within a specific group.

Figure 7 is an illustrative diagram of a mapping obtained by an electronic device according to an embodiment of the present invention by mapping one or more labels to page elements belonging to one or more pages.

In one embodiment, electronic device 110 can generate one or more keywords in association with various check steps generated during the process of testing one or more pages, and can generate one or more tags to be assigned to each of the one or more keywords. Electronic device 110 can map each of the one or more generated tags to one of the page elements belonging to one or more pages. More specifically, electronic device 110 can group the keywords corresponding to a specific page element and related to one or more check steps into a group, and can map the tags assigned to the keywords belonging to that group to a page element. For example, referring to Table 700 of FIG7, the first tag can be mapped to the first page element, and the second tag can be mapped to the second page element. This means that a tag can be mapped one-to-one to a page element.

In another embodiment, a tag can be mapped to two or more page elements. As illustrated in Figure 6, the electronic device 110 can also group keywords associated with one or more check steps corresponding to two or more page elements into a group. In this case, the tag assigned to the keyword belonging to that group can be mapped to two or more page elements.

Figure 8 is a flowchart illustrating the process by which an electronic device of one embodiment of the present invention generates scripts for test cases based on user input. In one embodiment, electronic device 110 can generate scripts for specific test cases by means of user input received from user terminal 120.

In action S810, electronic device 110 can connect user terminal 120 to the environment running electronic device 110, i.e., device farm, to transmit one or more pages of the application. Device farm can represent a test infrastructure provided for testing software applications.

In action S820, electronic device 110 may receive at least one user input from user terminal 120 for generating test cases. In one embodiment, electronic device 110 may receive at least one user input from user terminal 120 based on rendering more than one page in user terminal 120. In user terminal 120, a specific page of the application may be displayed on a display, and the user may interact with the specific page to generate a specific test case. During this process, user terminal 120 may receive at least one user input that interacts with more than one page element belonging to the specific page. User terminal 120 may transmit the received at least one user input to electronic device 110. For example, referring to Figure 5, the gate page 510 can be rendered on the user terminal 120, and the user terminal 120 can receive the action of clicking the search icon 511 and transmit it to the electronic device 110.

In action S830, electronic device 110 can identify and map one or more tags corresponding to at least one page element of at least one user input.

In one embodiment, electronic device 110 can identify at least one page element corresponding to each of at least one user input. For example, user terminal 120 can transmit information related to the page elements represented by each user input to electronic device 110. Electronic device 110 can identify more than one tag obtained by mapping to the identified at least one page element. For example, in the case of a one-to-one mapping between a tag and a page element, there exists a specific tag (e.g., the first tag) obtained by mapping to a specific page element (e.g., the first page element). In this case, electronic device 110 can identify a tag mapped to each page element. As another example, there may be a case where a specific tag is mapped to a plurality of page elements. At this time, the multiple page elements can be related to each other. Therefore, when a specific user input corresponds to one of the multiple page elements, the electronic device 110 can identify the specific tag as the page element corresponding to the specific user input. Furthermore, when subsequent user inputs following the specific user input correspond to one of the multiple page elements, the electronic device 110 can ignore the user input.

In action 840, electronic device 110 can identify the keywords of each of the identified tags, and can combine the codes corresponding to the identified keywords to generate scripts for specific test cases.

In one embodiment, the electronic device 110 can identify at least one keyword assigned to each of the identified more than one tag, and can combine the code corresponding to the identified at least one keyword to generate temporary scripts corresponding to each tag. Here, the code corresponding to the keyword can be code representing one or more check steps for the keyword representation. When there are multiple keywords assigned to each tag, the electronic device 110 can combine the code corresponding to each of the multiple keywords according to the execution order of the check steps representing each of the multiple keywords to generate temporary scripts corresponding to each tag.

In one embodiment, electronic device 110 can generate scripts for specific test cases by combining the generated temporary scripts for each of the identified one or more tags. Electronic device 110 can determine the action sequence of at least one page element based on the input sequence of at least one user input. Electronic device 110 can generate scripts for specific test cases by combining the temporary scripts corresponding to each of the identified one or more tags according to the action sequence of each tag and its mapped page element. This approach improves the efficiency of automatically generating and managing test cases.

The method of this invention can be implemented using a computer. The computer may include, for example, an electronic device capable of processing. In this invention, the steps of the method are described sequentially, but in addition to performing the steps sequentially, they may also be performed in any combination of orders. The descriptions of this invention related to sequence diagrams or flowcharts do not preclude changes or modifications to the method or algorithm, and do not imply that any action is necessary or preferred. In one embodiment, at least some steps may be performed in parallel, repeatedly, or heuristically. 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 software recorded on a machine-readable storage medium. The software can be any software used to implement the various embodiments of the present invention. Programmers in the art to which the present invention pertains can infer the software based on the various embodiments described in the present invention. For example, the software can be a program that includes machine-readable commands (e.g., code or code segments). A machine is a device capable of operating according to commands called from a recording medium, such as a computer. In one embodiment, the machine can be an electronic device of an embodiment of the present invention. In one embodiment, the machine's processor executes the called commands, thereby enabling the machine's components to perform functions corresponding to those commands. In one embodiment, the processor may be the processor of the embodiment of the present invention. The recording medium may refer to all types of recording medium capable of being read and storing data by a machine. Recording media may include, for example, ROM (Read-only memory), RAM (Random-access memory), CD-ROM (Compact Disc Read-Only Memory), magnetic tape, floppy disk, optical data storage device, etc. In one embodiment, the recording medium may 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 within computer systems, etc. Recording media can be non-transitory. Non-transitory recording media refers to media that actually exist without relation to semi-permanent or temporary data storage (Tangible Medium), excluding transiently transmitted signals.

The technical concept of the present invention has been described above based on various embodiments. However, the technical concept of the present invention includes various substitutions, changes, and modifications that can be implemented within the scope of the art to which the present invention pertains and are understandable to a person of ordinary skill. Furthermore, it should be understood that such substitutions, changes, and modifications may be included within the scope of the appended invention claims.

110: Electronic Device 120: User Terminal 200: Electronic Device 210: Processor 220: Memory 230: Communication Interface 410: Page 420: Atomicity Keyword 421: Alert Icon 422: Search Icon 423: Supermarket Icon 430: Scene Keyword 510: Gate Page 511: Search Icon 520: Search Page 5 21: Search Box 522: Search Icon 530: Keyword Results Page 611: Atomic Keywords 612: Atomic Keywords 613: Scene Keywords 621: Tags 622: Tags 700: Table S310: Steps S320: Steps S330: Steps S810: Steps S820: Steps S830: Steps S840: Steps

Figure 1 illustrates the environment in which an electronic device of one embodiment of the present invention can be applied. Figure 2 is a block diagram of the electronic device of one embodiment of the present invention. Figure 3 is a flowchart illustrating the process of generating test cases by the electronic device of one embodiment of the present invention. Figure 4 is a diagram illustrating the process of generating one or more keywords in conjunction with the test and verification steps of the electronic device of one embodiment of the present invention. Figure 5 is an illustration illustrating the generation of keywords in conjunction with the test and verification steps of the electronic device of one embodiment of the present invention. Figure 6 is a diagram illustrating the process of generating tags to be assigned to keywords by the electronic device of one embodiment of the present invention. Figure 7 is an illustrative diagram showing the mapping obtained by an electronic device according to an embodiment of the present invention by mapping one or more tags to page elements belonging to one or more pages. Figure 8 is a flowchart illustrating the process by which an electronic device according to an embodiment of the present invention generates test case scripts based on user input.

S310: Steps S320: Steps S330: Steps

Claims (15)

A method for generating test cases, performed by an electronic device, includes the following steps: generating one or more keywords in association with test steps and verification steps that may occur during the process of testing one or more pages; generating one or more tags to be assigned to each of the generated one or more keywords; and generating a script for test cases including at least one check step based on the mapping between the generated one or more tags and page elements belonging to the one or more pages. The method of claim 1, wherein the steps for generating one or more of the above-mentioned keywords include the following steps: generating atomic keywords corresponding to a single test step or a single verification step; and generating scenario keywords corresponding to a single scenario including a plurality of check steps for verifying the functionality of a page; wherein the scenario keywords consist of a plurality of atomic keywords. As in the method of claim 2, one of the test steps corresponds to a page element belonging to one or more of the aforementioned pages, and the step of generating one or more of the aforementioned keywords includes the following steps: generating atomic keywords in a manner that includes information representing the aforementioned page element corresponding to the aforementioned test step. As in the method of Request 1, a page element belonging to one or more of the aforementioned pages represents a single component constituting the user interface displayed by each of the aforementioned pages. The method of claim 1, wherein the step of generating the above-mentioned one or more tags includes the following steps: grouping the above-mentioned one or more keywords based on page elements belonging to the above-mentioned one or more pages; and assigning the same tag to the keywords belonging to each group for the one or more groups generated according to the above-mentioned grouping results. The method of claim 1, wherein the step of generating one or more of the above-mentioned tags includes the following steps: when a test step is accompanied by one or more verification steps, assigning the same tag to a plurality of keywords generated in association with the test step and the one or more of the verification steps. The method of claim 1, wherein the step of generating one or more of the above-mentioned tags includes the following steps: parsing one of the above-mentioned keywords word by word, and using at least a portion of the parsed words to generate a tag to be assigned to the above-mentioned keyword. The method of claim 1, wherein the step of generating the script for the test case includes the following steps: mapping each of the generated tags to one of the page elements belonging to the page; receiving at least one user input for generating the test case; and identifying at least one page element corresponding to the at least one user input, and identifying at least one tag mapped to the identified at least one page element, thereby generating the script for the test case. The method of claim 8, wherein the step of receiving the at least one user input includes the following steps: connecting one of the user's user terminals to a device field, the device field being the environment in which the electronic device operates; transmitting the one or more pages to the user's device; and rendering the one or more pages in the user terminal, thereby receiving the at least one user input from the user terminal. As in the method of claim 8, the steps of generating the script for the test cases include the following steps: for each of the at least one tag, identifying at least one keyword assigned to each of the at least one tag, and combining the code corresponding to the at least one keyword to generate a temporary script; and combining the temporary script generated for each of the at least one tag to generate the script for the test cases. The method of claim 10, wherein the steps for generating the aforementioned temporary scripts include the following steps: when there are multiple keywords assigned to the aforementioned tags, by combining the codes corresponding to each of the multiple keywords assigned to the aforementioned tags in the execution order of the tests corresponding to each of the multiple keywords, a temporary script corresponding to each of the aforementioned tags is generated. The method of claim 10, wherein the steps for generating the script for the above test cases include the following steps: determining the action order of the at least one page element based on the input order of the at least one user input; and generating the script for the above test cases by combining the temporary scripts generated corresponding to each of the at least one tag according to the action order of the corresponding page elements. The method of Request 1, wherein the steps for generating one or more of the above keywords include the following steps: obtaining the inspection steps for each of the above multiple test cases by performing a pre-stored plurality of test cases on the one or more of the above pages. An electronic device includes: one or more processors; and one or more memories storing commands to be executed by the one or more processors; and the one or more processors are configured to perform the method of any one of claims 1 to 13 when executing the commands. 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 13.