Method of processing information on plurality of test cases which are previously executed before and electronic apparatus thereof

Abstract

According to one embodiment, a method for an electronic device to process information of a plurality of previously executed test cases is provided. The method includes the steps of: obtaining execution count information, priority information, and automation information for each of the plurality of test cases; determining at least one first test case based on the execution count information; determining at least one second test case based on the priority information and automation information of each of the at least one first test case; and providing at least one of the priority information and automation information of the at least one second test case to a user terminal. According to another embodiment, an apparatus for implementing the method and a computer-readable recording medium for recording a computer program used to implement the method are provided.

Description

Technical Field

[0001] This invention relates to a method and electronic device for processing information from a plurality of previously executed test cases. Prior Technology

[0002] In the software development process, various testing procedures must be used to verify the stability and functionality of the system to ensure quality. In particular, test cases are a crucial element in verifying whether the software operates as expected, defining input conditions, execution procedures, and expected results for specific functions or modules. As the complexity of software systems increases, the number of test cases continues to rise, and the importance of testing efficiency and management also increases accordingly. In the e-commerce field, the development of applications that provide consumers with online product purchasing services developed through software is also very active, thus generating and executing a large number of test cases.

[0003] In current software testing environments, most testing is performed manually by developers. However, with the development of test automation tools, methods for automatically generating and executing test cases are becoming increasingly common. Automated test cases are particularly useful for repetitive testing such as regression testing, and can also verify whether existing functions are working correctly after adding new features or changing code.

[0004] However, existing systems suffer from difficulties in efficiently managing information from multiple test cases. In particular, analyzing the results of past test cases and using this information to comprehensively assess the software's status can become complex. This is because the amount of information increases as test cases accumulate, making it difficult to extract the necessary data in a timely manner. Furthermore, the lack of tools for managing and analyzing the change history of test results makes it difficult for developers to track bugs or evaluate software quality.

[0005] Therefore, in order to improve the problems of the existing system, a method is needed that can efficiently process information from multiple test cases executed in the past and systematically manage test results. Summary of the Invention

[0006] [The problem the invention aims to solve] The disclosed embodiments aim to provide a technique for processing statistical information for providing users with information on test cases, which is what users expect from managing and correcting information on previously executed test cases.

[0007] The technical problem to be solved in this embodiment is not limited to the technical problem described above. Other technical problems can be deduced from the following embodiments. [Technical means to solve the problem]

[0008] According to one embodiment, a method for an electronic device to process information of a plurality of test cases executed in the past is provided. The method includes the following steps: obtaining execution count information, priority information, and automation information of each of the plurality of test cases; determining at least one first test case based on the execution count information; determining at least one second test case based on the priority information and automation information of each of the at least one first test case; and providing at least one of the priority information and automation information of the at least one second test case to a user terminal.

[0009] The method of one embodiment includes the step of determining at least one first test case, which may include the following steps: determining at least one first test case whose execution count information of each of the plurality of test cases is above the critical execution count. Here, the critical execution count may be the absolute execution count predetermined by an electronic device, or the execution count of the test case of the percentile predetermined by an electronic device among the plurality of test cases.

[0010] The method of one embodiment includes the step of determining at least one second test case, which may include the following steps: determining at least one second test case based on whether at least one first test case has a priority above a predetermined critical priority and whether it is a non-automated test case.

[0011] One embodiment of the method may further include the following steps: receiving a correction request from a user terminal that has received information on at least one second test case for at least one of the following: priority information and automation information of at least one portion of at least one second test case; in response to the correction request, correcting at least one of the following: priority information and automation information of at least one portion of at least one second test case according to the correction request; and providing the corrected information to the user terminal.

[0012] The method of one embodiment includes the step of obtaining execution count information, priority information, and automation information of a plurality of test cases, which may include the following steps: obtaining execution count information, priority information, and automation information of a plurality of test cases executed within a predetermined period via an electronic device.

[0013] The method of one embodiment includes the step of determining at least one first test case, which may include the following steps: determining a test case that is repeatedly executed among a plurality of test cases; determining the execution count information of at least one first test case based on the cumulative statistics of the execution count of each of the repeatedly executed test cases; and determining at least one first test case based on the determined execution count information.

[0014] One embodiment of the method includes the step of determining test cases to be executed repeatedly, which may include the following steps: based on the case identification code assigned to each of the plurality of test cases, determining the test cases with the same case identification code among the plurality of test cases as test cases to be executed repeatedly.

[0015] In one embodiment of the method, a plurality of test cases may be included in at least one test suite, at least one test suite may be included in at least one test plan, and at least one test plan may be included in at least one test project.

[0016] One embodiment of the method may further include the steps of: setting at least one non-automated test case in the second test case to be automated; and assigning an automation label to the test cases set to be automated.

[0017] According to another embodiment, an electronic device for processing information of a plurality of previously executed test cases can be provided. The electronic device includes: a transceiver; memory; and a processor. The electronic device is configured such that: the processor controls at least one of the transceiver and the memory, thereby obtaining execution count information, priority information, and automation information for each of the plurality of test cases; based on the execution count information, at least one first test case is determined; based on the priority information and automation information of each of the at least one first test case, at least one second test case is determined; and at least one of the priority information and automation information of the at least one second test case is provided to a user terminal.

[0018] An electronic device in one embodiment can be configured such that: the processor included in the electronic device determines that the execution count information of each of the plurality of test cases is at least one first test case that is above the critical execution count; and the critical execution count can be an absolute execution count predetermined by the electronic device, or the execution count of a percentile test case among the plurality of test cases predetermined by the electronic device.

[0019] An electronic device in one embodiment may be configured such that a processor included in the electronic device determines at least one second test case based on whether at least one first test case has a priority above a predetermined critical priority and whether it is a non-automated test case.

[0020] An electronic device in one embodiment may be configured such that the processor in the electronic device receives, from a user terminal that has received information of at least one second test case, a correction request for at least one of the following: priority information and automation information of at least one portion of the at least one second test case; in response to the correction request, corrects at least one of the following: priority information and automation information of at least one portion of the at least one second test case; and provides the corrected information to the user terminal.

[0021] An electronic device in one embodiment may be configured such that a processor included in the electronic device obtains execution count information, priority information, and automation information for each of a plurality of test cases executed within a predetermined period by means of the electronic device.

[0022] An electronic device according to one embodiment may be configured such that the processor included in the electronic device is configured to: determine test cases that are repeatedly executed among a plurality of test cases; determine execution count information of at least one first test case based on the cumulative statistical result of the execution count of each of the repeatedly executed test cases; and determine at least one first test case based on the determined execution count information.

[0023] An electronic device in one embodiment can be configured such that a processor in the electronic device determines test cases with the same case identification code among the plurality of test cases as test cases to be executed repeatedly, based on a case identification code assigned to each of the plurality of test cases.

[0024] In one embodiment of the electronic device, a plurality of test cases may be included in at least one test kit, at least one test kit may be included in at least one test plan, and at least one test plan may be included in at least one test project.

[0025] An electronic device in one embodiment may be configured such that the processor in the electronic device is configured to automate at least one non-automated test case in the second test case; and to assign an automation label to the test cases configured to automate.

[0026] According to another embodiment, a non-transitory computer-readable recording medium is provided, which records a computer program for implementing a method for an electronic device to process information of a plurality of test cases executed in the past. The method includes the following steps: obtaining execution count information, priority information, and automation information of each of the plurality of test cases; determining at least one first test case based on the execution count information; determining at least one second test case based on the priority information and automation information of each of the at least one first test case; and providing at least one of the priority information and automation information of the at least one second test case to a user terminal. [Effects of the Invention]

[0027] According to the proposed embodiments, one or more of the following effects can be expected.

[0028] Information provided based on embodiments of the present invention can reduce the workload of QA (Quality Assurance Engineer) in filtering a large number of test cases based on the number of times the test cases are executed, their priority, and whether they are automated, and in revising the sorted test cases.

[0029] Furthermore, according to embodiments of the present invention, by providing users with a screen that can filter and process information on regression test cases, important test cases can be easily selected when implementing test case improvement work, thereby further improving the efficiency of processing and correction work.

[0030] The effects of the invention are not limited to those mentioned above. Those skilled in the art can clearly understand other effects not mentioned based on the description in the patent application. Simple Explanation of the Diagram

[0031] Figure 1 shows a system according to one embodiment. Figure 2 illustrates a method of one embodiment. Figure 3 shows a block diagram differentiated based on the characteristics of the functions implemented in one embodiment. Figure 4 is a diagram illustrating the process by which an electronic device in one embodiment acquires, modifies, and stores information about test cases. Figure 5 is a diagram illustrating the process by which an electronic device in one embodiment obtains, modifies, and stores test case information using a test case tool. Figure 6 illustrates a user interface that can be displayed by a user terminal based on information received from an electronic device, according to one embodiment. Figure 7 is a flowchart illustrating the process of processing and transmitting test case information in an electronic device and user terminal according to an embodiment. Figure 8 is a diagram illustrating the process of automatically tagging information of automated test cases according to an embodiment. Figure 9 shows a block diagram of an electronic device according to an embodiment. Implementation

[0032] The terminology used in the embodiments is selected as widely used and common terms as possible to consider the functions of this invention, but may vary depending on the intentions or precedents of those skilled in the art, the emergence of new technologies, etc. Furthermore, in certain situations, there may be terms arbitrarily chosen by the applicant; in such cases, their meanings will be described in detail in the corresponding explanatory section. Therefore, the terminology used in this invention should be defined based on the meaning of the term and the entire content of this invention, and not simply based on the name of the term.

[0033] Throughout this specification, when a part is described as "including" a certain constituent element, it means that other constituent elements may be included, rather than excluded, unless otherwise specified.

[0034] The expression "at least one of a, b and c" as used throughout the specification may include "a alone", "b alone", "c alone", "a and b", "a and c", "b and c" or "all three of a, b and c".

[0035] The term "terminal" as used below can refer to a computer or a portable terminal that can connect to a server or other terminal via a network. Here, a computer includes, for example, a laptop, desktop, or tablet computer equipped with a web browser. A portable terminal, as a wireless communication device ensuring portability and mobility, can include, for example, IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution) communication terminals, as well as all types of handheld wireless communication devices such as smartphones and tablets.

[0036] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings, so that those skilled in the art can easily implement the invention. However, the present invention can be implemented in various different forms and is not limited to the embodiments described herein.

[0037] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0038] Figure 1 shows a system according to one embodiment.

[0039] Referring to FIG1, the system may include an electronic device 110 and a user terminal 120. On the other hand, the system shown in FIG1 illustrates that the electronic device 110 can be connected to the user terminal 120 in various embodiments of the present invention. Those skilled in the art related to the various embodiments of the present invention will understand that the electronic device 110 or the user terminal 120 may include common components.

[0040] According to one embodiment, electronic device 110 is a device that configures and provides various information. Electronic device 110 can display the configured information through a user interface, web page, or application screen, or provide the configured information to user terminal 120 so that user terminal 120 can receive the information and display it through a user interface, web page, or application screen.

[0041] According to one embodiment, the electronic device 110 may modify information executed, processed and / or managed in the electronic device 110 based on information received through the interface displayed in the user terminal 120, and provide the modified information to the user terminal 120.

[0042] In this invention, the plurality of test cases processed by electronic device 110 includes previously executed test cases. According to one embodiment, information on the plurality of test cases can be obtained from database 130. According to another embodiment, by batch storing, statistically analyzing, and managing information on previously executed test cases through electronic device 110, all test cases (e.g., regression test cases) can be stored in a central storage such as database 130, and accessible to electronic device 110 and / or user terminal 120. This allows testers, developers, or managers (hereinafter referred to as "users") to quickly retrieve relevant test cases and easily understand their scope and focus. Furthermore, the electronic device 110 of this invention can easily identify missing or duplicate test cases within the scope of the test cases through batch statistical analysis, thereby confirming whether the test cases adequately cover important functions.

[0043] According to one embodiment, user terminal 120 is a terminal used by each user, and users can use their respective user terminal 120 to access services provided through network 140. In this invention, the user using user terminal 120 can be a QA engineer.

[0044] According to one embodiment, database 130 is a data structure implemented in a specified storage space, which may include relational databases such as MySQL, Oracle, and MSSQL, non-relational databases such as Redis, MongoDB, and CouchDB, open source search engines such as Elasticsearch, and combinations thereof.

[0045] According to one embodiment, the database 130 may store various information about test cases. For example, the database 130 may store detailed information about test cases executed by the electronic device 110 (e.g., test case identification code, test case external identification code, test case link, section information to which the test case belongs, test case title, test case pre-condition, steps included in the test case, expected results corresponding to the execution of the test case, test case priority information, test case automation information, test case execution count information, etc.).

[0046] User terminal 120, database 130, and electronic device 110 can communicate with each other in network 140. Network 140 includes Local Area Network (LAN), Wide Area Network (WAN), Value Added Network (VAN), mobile radio communication network, satellite communication network, and combinations thereof. This network is a comprehensive data communication network that enables the main components of the networks 140 shown in FIG1 to communicate smoothly with each other. It may include wired Internet, wireless Internet, and mobile wireless communication network. Wireless communication may include, for example, Wi-Fi, Bluetooth, Bluetooth Low Energy, Wi-Fi Direct (WFD), UWB (ultra-wideband), IrDA (infrared data association), NFC (near field communication), etc., but is not limited to these.

[0047] The following describes a specific embodiment in which the electronic device 110 collects information on a plurality of test cases executed in the past, determines test cases that meet the prescribed conditions based on this information, and then provides them to the user terminal 120.

[0048] Figure 2 illustrates a method of one embodiment.

[0049] In step S210, according to one embodiment, the electronic device 110 can obtain execution count information, priority information, and automation information for each of the plurality of test cases.

[0050] According to one embodiment, the electronic device 110 can count the number of times multiple test cases are executed. The counted execution count information can be determined by the electronic device 110 and / or the user terminal 120 by counting the number of times test cases are executed within a specified period.

[0051] According to one embodiment, priority information can be assigned to each of a plurality of test cases. According to one embodiment, the priority information assigned to each of the plurality of test cases can be priority information manually or automatically specified by the electronic device 110 and / or the user terminal 120. For example, the plurality of test cases can be specified in descending order of priority, such as P0, P1, or P2.

[0052] Electronic device 110 compiles test case information based on test case priority, thereby improving test case management efficiency and enabling efficient verification of important functions within a limited timeframe. Specifically, by prioritizing each test case after all test cases have been compiled, and observing the compiled information accordingly, users can easily identify test cases for important technical or commercial functions. Furthermore, when code changes or new functions are added to applications managed by electronic device 110, the compiled test case information can be used to filter out test cases related to the changes and review, modify, or execute them. This allows for efficient test case implementation and quick confirmation that the changed code functions as expected.

[0053] According to one embodiment, the automation information for each of the plurality of test cases may be information indicating whether the plurality of test cases have been automated in terms of API or UI.

[0054] Electronic device 110 can identify automatable test cases from a plurality of test cases. Electronic device 110 can analyze the statistical information of the test cases and identify repetitive and frequently executed test cases, or test cases that are less frequently changed or more stable, resulting in fewer executions. Users can strategically select test cases to be automated from those not yet automated, considering the technical significance of this execution frequency information. Since test case automation needs to consider the workload required for initial development, maintenance costs, etc., electronic device 110 can determine whether automation is appropriate based on the statistical information of the test cases.

[0055] By centrally managing test case information through electronic device 110, the relationship between automated and manual test cases can be clearly distinguished. Therefore, when maintaining and updating the automated scripts for test cases, the correlation with related manual test cases can be considered, thereby building a more complete automation system.

[0056] In step S220, according to one embodiment, the electronic device 110 can determine at least one test case among a plurality of test cases based on the execution count information obtained in step S210. According to one embodiment, the electronic device 110 can determine that the execution count information of each of the plurality of test cases is at least one first test case above the critical execution count.

[0057] According to one embodiment, the critical execution count may be an absolute execution count predetermined by the electronic device 110 (e.g., A times (A is 1 or more), or B*N (where N is the number of unit time units (e.g., days, weeks, months, or years) for a predetermined period for statistical execution count information, and B and N are 1 or more), or the execution count of test cases at the percentile predetermined by the electronic device 110 among a plurality of test cases (e.g., the execution count belonging to the top 90% based on the execution count of test cases statistically analyzed within a predetermined period).

[0058] In step S230, according to one embodiment, the electronic device 110 may determine at least one second test case based on priority information and automation information of at least one first test case determined in step S220.

[0059] According to one embodiment, the electronic device 110 can determine at least one second test case based on priority information of at least one first test case. According to another embodiment, the electronic device 110 can determine at least one second test case based on whether each of the at least one first test case has a priority higher than a predetermined critical priority. For example, each of the at least one first test case may have priorities P0, P1, or P2 in descending order of priority. The electronic device 110 can determine at least one second test case by filtering out only the test cases with a priority of P0 among the at least one first test case.

[0060] According to one embodiment, electronic device 110 can determine at least one second test case based on automation information of at least one first test case. According to another embodiment, electronic device 110 can determine at least one second test case that is not automated among at least one first test case.

[0061] In step S240, according to one embodiment, the electronic device 110 may provide the user terminal 120 with at least one of priority information and automation information of at least one second test case determined in step S230.

[0062] According to one embodiment, the user terminal 120 may display detailed information of at least one of priority information and automation information as at least one second test case based on the information received from the electronic device 110 in step S240.

[0063] Figure 3 shows a block diagram differentiated based on the characteristics of the functions implemented in one embodiment. The functions implemented by the case tool 310, case scanner 320 and high-frequency case management unit 330 shown in Figure 3 can be understood as being implemented by the hardware (e.g., processor 920) included in the electronic device 110 as described below.

[0064] According to one embodiment, the electronic device 110 can be configured using various test case management tools. These tools are used to generate test projects, formulate plans for implementing the test cases included in the test projects, and generate result reports. For example, the electronic device 110 can use test case tool 310 to generate test projects and generate and manage at least one test plan, at least one test suite, and at least one test case constituting a test project. According to one embodiment, the concept is that at least one test case is included in each test suite, at least one test suite is included in each test plan, and at least one test plan is included in each test project.

[0065] According to one embodiment, the electronic device 110 may utilize the following tools as test case tools 310: TestLink, which supports test planning, test case management, test execution, and result reporting as an open source test case management tool, or Testrail, which provides functions such as test case management, test execution and tracking, and report generation as a commercial test management tool.

[0066] According to one embodiment, information about test cases executed by the test case tool 310 of the electronic device 110 can be obtained from the test case scanner 320. The test case scanner 320 can obtain all information related to the plurality of test cases executed by the test case tool 310, including execution count information, automation information, and / or priority information of the plurality of test cases executed in any period. Based on the obtained information, the test case scanner 320 can determine at least one first test case that satisfies the conditions related to the execution count of the plurality of test cases. The test case scanner 320 can filter out at least one first test case that satisfies the conditions related to the priority information and automation information, thereby determining at least one second test case. Detailed information related to the at least one second test case determined by the test case scanner 320 can be stored in the database 130 by the high-frequency test case management unit 330.

[0067] Figure 4 is a diagram illustrating the process by which an electronic device 110 acquires, modifies, and stores test case information according to an embodiment. Referring to Figure 4, the operation of the test case tool 310, test case scanner 320, and high-frequency test case management unit 330 illustrated in Figure 3 can be understood more accurately. The test case tool 410, test case scanner 420, and high-frequency test case management unit 430 in Figure 4 correspond to the test case tool 310, test case scanner 320, and high-frequency test case management unit 330 in Figure 3. According to one embodiment, the functions described below related to the test case tool 410, test case scanner 420, and high-frequency test case management unit 430, as well as other blocks and objects shown in Figure 4, can be functions implemented by the processor 920 of the electronic device 110.

[0068] According to one embodiment, the test case tool 410 is configured to execute test cases. The electronic device 110 can obtain information on previously executed test plans 440, which may be stored in the database 130. According to one embodiment, the information on executed test plans 440 may include information on at least one test suite included in each test plan, and information on at least one test case included in each test suite. According to one embodiment, at least one test plan may be included in each test project. According to one embodiment, the test case tool 410 can obtain information on test plans 440 executed within a specified period. According to one embodiment, the electronic device 110 can determine information on test cases to be executed within a specified period (e.g., N days, N weeks, N months, or N years (N>0)) based on the information on executed test plans 440 obtained from the database 130.

[0069] According to one embodiment, the test case scanner 420 can fetch from the test case tool 410 at least one test plan included in each test project executed within a predetermined period. According to one embodiment, the test case scanner 420 can obtain information on all executed test cases 450 within the predetermined period based on the information obtained from the test case tool 410. According to one embodiment, the test case scanner 420 can calculate the execution count of each test case, i.e., the number of times it was executed within the predetermined period, based on the obtained test case information.

[0070] According to one embodiment, the test case scanner 420 can determine the number of times each test case is executed and sort the test cases based on this number of executions.

[0071] According to one embodiment, the test case scanner 420 can analyze the information of the obtained test cases based on the information collected by the test case tool 410. Through this analysis, the test case scanner 420 can determine whether each test case has been automated. According to one embodiment, the test case scanner 420 can process the information of each test case based on whether it is automated.

[0072] For example, the case scanner 420 can determine at least one first test case whose execution count information, representing the number of times the test case has been executed within a predetermined period, is above the critical execution count. According to one embodiment, the critical execution count can be an absolute number of executions predetermined by the electronic device 110 (e.g., X times (X>0)). According to another embodiment, the critical execution count can be the number of executions of test cases at a predetermined percentile, determined by the electronic device 110 among a plurality of test cases (e.g., the number of executions of test cases belonging to the top 90% based on the number of executions among a plurality of test cases executed within a predetermined period).

[0073] According to one embodiment, the case scanner 420 can determine whether there is a test case with a predetermined critical priority or higher among at least one first test case whose execution count information, representing the number of times the test case has been executed within a predetermined period, is above the critical execution count. For example, each test case can be set to have one of P0, P1, and P2 priorities. The case scanner 420 can determine at least one first test case with a priority of P0 or higher (i.e., a test case with a priority of P0), or determine a test case with a priority of P1 or higher (i.e., a test case with a priority of P0 or P1).

[0074] According to one embodiment, the test case scanner 420 can identify at least one non-automated test case among the first test cases whose execution count information, representing the number of times the test case has been executed within a predetermined period, is above the critical execution count. According to another embodiment, information on whether each test case is automated can be set for each test case and stored in the database 130.

[0075] According to one embodiment, the case scanner 420 can identify at least one second test case as a first test case that has a predetermined critical priority or higher and is set to non-automation, among at least one first test case whose execution count information, representing the number of times it is executed within a predetermined period, is above the critical execution count.

[0076] According to one embodiment, the case scanner 420 can store information of at least one second test case in the database 130 via the high-frequency case management unit 430. According to another embodiment, the high-frequency case management unit 430 can provide detailed information of at least one second test case to the user terminal 120, which can then display the information of at least one second test case on a results display page. Based on the displayed information, the user can easily identify which test cases, executed more frequently and with higher priority but not automated, were executed within a predetermined period.

[0077] Figure 5 is a diagram illustrating the process by which an electronic device 110, according to an embodiment, obtains, modifies, and stores test case information using a test case tool 550. As described above, the test case tool 550 is a conceptually defined configuration used to illustrate the functions performed by the processor 920 of the electronic device 110.

[0078] In step S510, according to one embodiment, electronic device 110 obtains information on all test projects through case tool 550.

[0079] In step S512, according to one embodiment, the electronic device 110 may specify the period for collecting information on previously executed test cases.

[0080] In step S514, according to one embodiment, electronic device 110 can obtain information on all test plans to be executed within a predetermined period by means of case tool 550.

[0081] In step S516, according to one embodiment, the electronic device 110 may perform a process of filtering completed test plans. According to one embodiment, the electronic device 110 may perform filtering to collect information on test cases included in the completed test plans from test cases executed within a predetermined period. Thereby, the electronic device 110 can improve the accuracy of the information provided to the user for at least one second test case based on the collected information on the number of times the test cases were executed, priority information, and automation information.

[0082] In step S518, electronic device 110 can obtain information on all test cases collected in step S516. The information obtained in this way can be obtained from test case tool 550.

[0083] In step S520, the electronic device 110 can remove duplicate test cases based on the case identification codes assigned to each test case. According to one embodiment, when generating test cases, the electronic device 110 can assign the case identification code of the test case to the corresponding test case, and generate and store it together with the test case. According to one embodiment, since test cases can be included in various test plans, the same test case can be included separately in multiple test plans. Therefore, in the information obtained by the test case tool 550 (e.g., the information of all test plans obtained in step S514), test cases assigned the same case identification code can be executed separately in different test plans. Therefore, the information obtained from the test case tool 550 can repeatedly include information on test cases that are executed separately in different test plans but have the same case identification code.

[0084] In step S522, according to one embodiment, the electronic device 110 can identify repeatedly executed test cases among a plurality of test cases, and determine the execution count information of at least one first test case based on the cumulative statistical result of the execution count of each repeatedly executed test case. That is, the electronic device 110 can determine at least one first test case based on the combined result of the execution count information of test cases with the same case identification code executed in multiple test plans within a predetermined period.

[0085] In step S524, according to one embodiment, the electronic device 110 can obtain detailed information about at least one second test case determined based on the number of times the test case was executed calculated in step S522. According to one embodiment, the detailed information about at least one second test case may include at least one of the following: test case identifier, test case link, external test case identifier, information about the section name associated with the test case, test case title, test case prerequisites, information about the steps included in the test case, information about the expected result of the test case, test case priority information, test case automation information, and information about the number of times the test case was executed.

[0086] In step S526, according to one embodiment, the electronic device 110 may store the detailed information of at least one first test case obtained in step S524 in the database 130. According to one embodiment, the electronic device 110 may perform a predetermined process before storing the detailed information of at least one first test case in the database 130, thereby determining the information of at least one second test case. Since the process of determining the information of at least one second test case has been described above, it is omitted here.

[0087] In step S528, the electronic device 110 may be configured to display at least a portion of the detailed information of at least one second test case. For example, a display connected to the electronic device 110 may display at least a portion of the detailed information of at least one second test case. As another example, the user terminal 120 may be configured to receive and display at least a portion of the detailed information of at least one second test case stored in the database 130.

[0088] Figure 6 illustrates a user interface that can be displayed by a user terminal 120 based on information received from an electronic device 110, according to an embodiment.

[0089] According to one embodiment, user terminal 120 can receive information about at least one first test case stored in database 130 and display it on a user interface. According to one embodiment, the information displayed through the user interface of user terminal 120 may include a case identification code 610, priority information 620, automation information 630, and execution count information 640. Referring to the case identification code 610 displayed in user terminal 120, since the at least one first test case displayed in the user interface has merged test cases that were repeatedly executed in each test plan, duplicate identification codes are not displayed in the case identification code 610 displayed in the user interface. This reduces confusion for the user of user terminal 120 during the process of confirming and correcting test cases, and reduces unnecessary processing time required according to the confirmation procedure.

[0090] According to one embodiment, the user interface displays priority information 620, automation information 630, and execution count information 640 in the detailed information of at least one first test case determined by the electronic device 110. This improves the time and effort required for the user terminal 120 to understand which test case among the at least one first test case has been executed more times and has a higher priority but has not been automated, and reduces the possibility of human error.

[0091] According to one embodiment, a user can modify the detailed information of the second test case through a user interface. For example, the user can modify the priority information 620 and / or automation information 630 of the second test case through the user interface. This allows the user to modify the priority and / or automation status of the second test case, thereby modifying the detailed information of the second test case to be stored. The modified detailed information of the second test case, as described above, can be stored in the database 130, and when executing test cases based on the stored test case information, the execution can be based on the modified information.

[0092] Figure 7 is a flowchart illustrating the process of processing and transmitting test case information in an electronic device and user terminal according to an embodiment.

[0093] The case tool 700, case scanner 720, and high-frequency case management unit 720 in Figure 7 are conceptually distinguished to illustrate the functions of the electronic device 110. The user terminal 730 in Figure 7 corresponds to the user terminal 120 in Figure 1.

[0094] According to one embodiment, the test case tool 700 can execute multiple test cases according to the test plan included in the test project (S710). According to one embodiment, information on all test cases executed in step S710 can be provided to the test case scanner 710 (S712).

[0095] According to one embodiment, the case scanner 710, which has obtained information on all test cases (S714), can perform filtering to determine information on at least one first test case executed within a specific period among all test cases (S716).

[0096] According to one embodiment, the case scanner 720 can determine, based on the filtering results and information from at least one first test case executed within a specific period, at least one first test case with a pre-specified percentile number of executions (e.g., the number of executions in the top 90% of at least one first test case executed within a specific period, based on the order of execution counts from high to low) (S718).

[0097] According to one embodiment, the test case scanner 710 can identify non-automated test cases among the first test cases that have been executed a number of times above a pre-specified percentile. According to one embodiment, since non-automated test cases among the first test cases that have been executed a number of times above a pre-specified percentile are equivalent to test cases that have been executed a large number of times but are not automated, users can improve the efficiency of test plan implementation by automating these test cases.

[0098] According to one embodiment, the test case scanner 710 can perform filtering to identify test cases of a predetermined level or higher among the test cases identified in step S720. According to one embodiment, test cases that are not automated and have a predetermined priority or higher among the first set of test cases with a number of executions above a predetermined percentile can be identified. This allows the user to further improve the efficiency of test plan implementation by automating test cases with a high number of executions and high priority that are not automated.

[0099] According to one embodiment, the case scanner 710 can provide information on at least one second test case to the high-frequency case management unit 720. The at least one second test case is a first test case that has not been automated and has a priority of at least a predetermined priority among the first test cases that have been executed more than a predetermined percentile (S724). The high-frequency case management unit 720 can store the received information in the database 130.

[0100] According to one embodiment, the user terminal 730 may request detailed information about at least one second test case from the high-frequency test case management unit 730 to retrieve, analyze, or correct the detailed information of the test case. The at least one second test case is a test case executed within a specific period that has been executed at a predetermined percentile or higher, is not automated, and has a predetermined priority or higher (S728). The user terminal 730 may display the detailed information received as a response to the request in step S728 via a user interface. The displayed detailed information may include execution count information, priority information, and automation information for the at least one second test case.

[0101] Figure 8 is a diagram illustrating the process of automatically tagging information of automated test cases according to an embodiment.

[0102] According to one embodiment, electronic device 110 can execute all test cases (810) and store them in database 130.

[0103] The electronic device 110 can perform a scan (820) based on detailed information of test cases accumulated and stored over a specific period.

[0104] The electronic device 110 can collect information on at least one first test case executed within a specific period through a scanning process, and thereby obtain information on the number of times at least one first test case was executed (830).

[0105] The electronic device 110 can determine at least one second test case (840) by filtering based on execution count information, priority information and automation information based on detailed information of at least one first test case.

[0106] The user can identify at least one non-automated test case in the second test case and adjust whether it should be automated (850). For example, the user can command the electronic device 110 to automate the non-automated second test case via the user interface.

[0107] Information regarding whether modified second test cases have been automated can be uploaded to Github (860). QA engineers can automate non-automated second test cases by modifying whether at least one specific second test case is automated, thus allowing users to verify software behavior without direct testing. The code used for this automation can be written within an automation framework. According to one embodiment, the automation framework may include various programs that provide functionality to facilitate the writing of automated tests in a consistent format and structure.

[0108] According to one embodiment, GitHub is a platform for code management and collaboration, enabling multiple users to write and manage test cases. Electronic device 110 can generate pull requests (PRs), which are procedures for requesting code changes to submit information about automated second test cases to GitHub. This allows other users, i.e., QA engineers, to confirm and review the modified code for these second test case changes.

[0109] According to one embodiment, a hook mechanism can be activated if a pull request is generated. According to one embodiment, the hook mechanism is configured to automatically perform a specific task when a specific condition or event occurs. According to one embodiment, if a pull request is generated, the electronic device 110 can add an automation tag to the test case tool (870). By adding such a tag, it can be shown that the test case is an automated test case.

[0110] According to one embodiment, the electronic device 110 can implement a "closed loop," which involves repeatedly automating the second test case by generating pull requests and running hook mechanisms. That is, the electronic device 110 can repeatedly perform the following cyclical process: if at least one unautomated second test case is identified, it is then automated, and an automation tag is added to the unautomated second test case by executing a pull request to resubmit to GitHub and using the hook mechanism. In this way, users can gradually expand the scope of test case automation based on information such as the number of times test cases are executed, their priority, and whether they are automated within a specific period, thereby continuously improving software quality.

[0111] Figure 9 shows a block diagram of an electronic device 900 according to one embodiment.

[0112] According to one embodiment, the electronic device 900 may include a transceiver 910, a processor 920, and memory 930. FIG9 shows only the components relevant to this embodiment. Therefore, those skilled in the art will understand that other common components may be included in addition to those shown in FIG9. In this embodiment, the transceiver 910 may be included in a communication device. Furthermore, in this embodiment, the processor 920 may be included in a controller.

[0113] Transceiver 910, as a device for wired / wireless communication, can communicate with external electronic devices. These external electronic devices can be user terminals 950 or servers. Furthermore, the communication technologies utilized by transceiver 910 may include GSM (Global System for Mobile communication), CDMA (Code Division Multi Access), LTE (Long Term Evolution), 5G, WLAN (wireless LAN), Wi-Fi (Wireless-Fidelity), Bluetooth™, RFID (Radio Frequency Identification), Infrared Data Association (IrDA), ZigBee, and NFC (Near Field Communication).

[0114] The processor 920 can control at least one of the transceiver 910 and memory 930 and process data and signals to perform the overall operation of the electronic device 900. The processor 920 may include at least one hardware unit. Furthermore, the processor 920 can operate by executing one or more software modules generated from the program code stored in memory 930. The processor 920 may include memory, and the processor 920 can execute the program code stored in memory to control the overall operation of the electronic device 900 and process data and signals.

[0115] The electronic device described in the above embodiments may include a processor, memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with external devices, and a user interface device such as a touch panel, keys, or buttons. Methods implemented using software modules or algorithms can store computer-readable code or program commands executable in the processor in a computer-readable recording medium. Here, computer-readable recording media include magnetic storage media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disks, hard disks, etc.) and optical reading media (e.g., CD-ROM, DVD, etc.). The computer-readable recording medium is distributed across a networked computer system, enabling distributed storage and execution of computer-readable code. The medium can be read by a computer, stored in memory, and executed in a processor.

[0116] This embodiment can be represented by functional blocks and various processing steps. These functional blocks can be implemented by different numbers of hardware and / or software components performing specific functions. For example, the embodiment can employ integrated circuits capable of performing various functions via the control of one or more microprocessors or other control devices, such as memory, processing, logic, lookup tables, etc. The components can be executed by software programs or software elements. Similarly, this embodiment includes various algorithms implemented by combinations of data structures, programs, conventions, or other programs, and therefore can be implemented using programming or scripting languages ​​such as C, C++, Java, and assemblers. Functionally, it can be implemented by algorithms executed in one or more processors. Furthermore, this embodiment can employ prior art for electronic environment setup, signal processing, and / or data processing. Terms such as "mechanism," "component," "mechanism," and "structure" are used broadly and are not limited to mechanical and physical structures. The above terms may be associated with processors and include the meaning of a series of software processes.

[0117] The above embodiments can be implemented as artificial intelligence (AI) using the processor and memory of an electronic device. The processor may include one or more processors, which can be general-purpose processors such as CPUs, APs, and DSPs (digital signal processors), graphics-specific processors such as GPUs and VPUs (vision processing units), or AI-specific processors such as NPUs. One or more processors can be controlled to process input data according to predefined action rules or AI models stored in memory. Alternatively, when one or more processors are AI-specific processors, the AI-specific processors can be designed with hardware structures specifically for processing specific AI models.

[0118] The characteristic of predefined action rules or artificial intelligence models is that they are created through learning. Here, "created through learning" refers to creating predefined action rules or artificial intelligence models set to perform desired characteristics (or purposes) by learning algorithms and utilizing multiple learning materials to learn a basic artificial intelligence model. This learning can be implemented within the electronic device implementing artificial intelligence of this invention, or it can be implemented by a separate server and / or system. Examples of learning algorithms include supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but are not limited to the examples mentioned above.

[0119] Artificial intelligence models can consist of multiple neural network layers. Each of these layers has multiple weight values, and neural network operations are performed by combining the results of previous layers with these multiple weight values. The multiple weight values ​​of the multiple neural network layers can be optimized using the learning results of the artificial intelligence model. For example, during the learning process, the multiple weight values ​​can be updated by reducing or minimizing the loss or cost values ​​obtained by the artificial intelligence model. Artificial neural networks may include deep neural networks (DNN), convolutional neural networks (CNN), recurrent neural networks (RNN), restricted Boltzmann machines (RBM), deep belief networks (DBN), bidirectional recurrent deep neural networks (BRDNN), or deep Q-networks, but are not limited to the examples mentioned above.

[0120] The above embodiment is only an example, and other embodiments can be implemented within the scope of the technical solutions described below.

[0121] 110: Electronic devices 120: User Terminal 130: Database 140: Internet 310: Case Study Tools 320: Case Scanner 330: High-Frequency Case Management Department 410: Case Study Tools 420: Case Scanner 430: High-Frequency Case Management Department 440: Test Plan 450: Test Cases 550: Case Study Tools 610: Case Identifier 620: Priority Information 630: Automation News 640: Execution Count Information 700: Case Tools 710: Case Scanner 720: High-Frequency Case Management Department 730: User Terminal 810: Execute all test cases 820: Scanning is performed based on detailed information about test cases accumulated and stored within a specific period. 830: By means of a scanning process, information on at least one first test case executed within a specific period is collected, and information on the number of times at least one first test case was executed is obtained. 840: Based on detailed information of at least one first test case, perform filtering based on execution count information, priority information, and automation information to determine at least one second test case. 850: Identify at least one non-automated test case in the second test case and correct whether it should be automated. 860: Upload information on whether the modified second test case has been automated to Github. 870: Add the automation tag to the case tool 900: Electronic Devices 910: Transceiver 920: Processor 930: Memory 950: User Terminal S210: Steps S220: Steps S230: Steps S240: Steps S510: Steps S512: Steps S514: Steps S516: Steps S518: Steps S520: Steps S522: Steps S524: Steps S526: Steps S528: Steps S710: Steps S712: Steps S714: Steps S716: Steps S718: Steps S720: Steps S722: Steps S724: Steps S726: Steps S728: Steps S730: Steps S732: Steps

Claims

1. A method for processing information of a plurality of test cases executed in the past via an electronic device, comprising the following steps: obtaining execution count information, priority information, and automation information for each of the plurality of test cases; determining at least one first test case based on the execution count information; determining at least one second test case based on the priority information and automation information for each of the at least one first test case; and providing at least one of the priority information and automation information for the at least one second test case to a user terminal; wherein the step of determining at least one first test case comprises the following steps: determining that the execution count information of each of the plurality of test cases is at least one first test case with a critical execution count or higher; and the critical execution count is an absolute execution count predetermined by the electronic device, or the execution count of a test case of a percentile predetermined by the electronic device among the plurality of test cases.

2. The method of request item 1, wherein the step of determining the at least one second test case includes the following steps: determining the at least one second test case based on whether the at least one first test case has a priority above a predetermined critical priority and whether it is a non-automated test case.

3. The method of claim 2 further includes the following steps: receiving a correction request for at least one of the following from the user terminal that received the information of at least one second test case: priority information and automation information of at least a portion of the at least one second test case; in response to the correction request, correcting at least one of the following: priority information and automation information of at least a portion of the at least one second test case; and providing the corrected information to the user terminal.

4. The method of claim 1, wherein the step of obtaining the execution count information, priority information and automation information of each of the plurality of test cases includes the following steps: obtaining the execution count information, priority information and automation information of each of the plurality of test cases executed within a predetermined period by means of the electronic device.

5. The method of claim 1, wherein the step of determining the at least one first test case comprises the following steps: determining the test case that is repeatedly executed among the plurality of test cases; determining the execution count information of the at least one first test case based on the cumulative statistics of the execution count of each of the repeatedly executed test cases; and determining the at least one first test case based on the determined execution count information.

6. The method of claim 5, wherein the step of determining the test cases to be repeatedly executed includes the following steps: using the case identification code assigned to each of the plurality of test cases as a basis, determining the test cases with the same case identification code among the plurality of test cases as the test cases to be repeatedly executed.

7. The method of Request 1, wherein the plurality of test cases are included in at least one test suite, the at least one test suite is included in at least one test plan, and the at least one test plan is included in at least one test project.

8. The method of request item 1 further includes the following steps: setting the non-automated test cases in at least one of the second test cases to be automated; and assigning automation labels to the test cases set to be automated.

9. An electronic device for processing information from a plurality of previously executed test cases, comprising: transceiver; The electronic device is configured such that: the processor controls at least one of the transceiver and the memory, thereby obtaining execution count information, priority information, and automation information for each of the plurality of test cases; based on the execution count information, at least one first test case is determined; based on the priority information and automation information for each of the at least one first test case, at least one second test case is determined; and at least one of the priority information and automation information for the at least one second test case is provided to a user terminal; the execution count information for each of the plurality of test cases is determined to be at least one first test case with a critical execution count or higher; wherein the critical execution count is an absolute execution count predetermined by the electronic device, or the execution count of a test case of a percentile predetermined by the electronic device among the plurality of test cases.

10. The electronic device of claim 9 is configured such that the processor determines the at least one second test case based on whether the at least one first test case has a priority above a predetermined critical priority and whether it is a non-automated test case.

11. The electronic device of claim 10 is further configured such that the processor receives, from the user terminal that received the information of the at least one second test case, a modification request for at least one of the following: priority information and automation information of at least a portion of the at least one second test case; in response to the modification request, modifying at least one of the following: priority information and automation information of at least a portion of the at least one second test case; and providing the modified information to the user terminal.

12. The electronic device of claim 9 is configured such that the processor obtains execution count information, priority information, and automation information for each of the plurality of test cases executed within a predetermined period by means of the electronic device.

13. The electronic device of claim 9 is configured such that the processor is configured to: determine the test cases that are repeatedly executed among the plurality of test cases; determine the execution count information of the at least one first test case based on the cumulative statistical result of the execution count of each of the repeatedly executed test cases; and determine the at least one first test case based on the determined execution count information.

14. The electronic device of claim 9 is configured such that the processor determines the test cases with the same case identification code among the plurality of test cases as the test cases to be repeatedly executed, based on the case identification code assigned to each of the plurality of test cases.

15. The electronic device of claim 9, wherein the plurality of test cases are included in at least one test kit, the at least one test kit is included in at least one test plan, and the at least one test plan is included in at least one test project.

16. The electronic device of claim 9 is further configured such that the processor is configured to: set at least one of the non-automated test cases in the second test case to be automated; and assign an automation label to the test cases set to be automated.

17. A non-transitory computer-readable recording medium recording a computer program for implementing an electronic device to process information of a plurality of test cases executed in the past, the method comprising the steps of: obtaining execution count information, priority information, and automation information of each of the plurality of test cases; determining at least one first test case based on the execution count information; determining at least one second test case based on the priority information and automation information of each of the at least one first test case; and providing at least one of the priority information and automation information of the at least one second test case to a user terminal; wherein the step of determining at least one first test case comprises the steps of: determining that the execution count information of each of the plurality of test cases is at least one first test case with a critical execution count or higher; and the critical execution count is an absolute execution count predetermined by the electronic device, or the execution count of a test case of a percentile predetermined by the electronic device among the plurality of test cases.

Images