TWI904045B - Operating method for electronic apparatus for providing information and electronic apparatus supporting thereof - Google Patents

Abstract

According to the present invention, a method for providing information by an electronic device is disclosed, comprising the following steps: based on the processing of request information obtained from a plurality of users on a service related to the electronic device, setting up a code overlay tool for analyzing code overlay of the service, and a simulation testing tool for simulating the code overlay analysis of the service; obtaining code overlay analysis result information and The test result information includes the code coverage analysis result information obtained by analyzing the pages on the aforementioned service based on the aforementioned code coverage tool, and the test result information obtained by testing the code coverage analysis of the pages on the aforementioned service based on the aforementioned simulation testing tool; and provides comparison information obtained by comparing the aforementioned code coverage analysis result information with the aforementioned test result information.

Description

Operating methods of electronic devices that provide information and electronic devices that support them.

This invention relates to a method and apparatus for providing information, and more specifically, to a method and electronic apparatus thereof for providing comparative information obtained by comparing code overlay analysis results generated by a code overlay tool with test results generated by a simulation testing tool.

With the development of electronic technology, e-commerce has become a field of shopping. Customers can buy items online without going to a shopping mall or market, and the items purchased online will be delivered to the customer's requested delivery location.

In the context of e-commerce, providing detailed and accurate information about products has a significant impact on service satisfaction, and therefore various solutions for providing more detailed and accurate information are being discussed.

For related information, see previous references such as KR101756594B1 or KR101500849B1.

[Problem to be solved by the invention] According to the method of the present invention, an electronic device can provide comparative information by comparing the code overlay analysis results generated by a code overlay tool with the test results generated by a simulation test tool.

The technical problem to be solved by this invention is not limited to the technical problems mentioned above. Those skilled in the art to which this invention pertains can clearly understand other technical problems not mentioned based on the following description. [Technical Means for Solving the Problem]

Various embodiments may provide a method of operation for an electronic device that provides information and an electronic device that supports it.

Various embodiments of the electronic device providing information may include the following steps: based on the processing of request information obtained from multiple users on services related to the aforementioned electronic device, setting up a code coverage tool to analyze the code coverage of the aforementioned services. The tool), and a simulation testing tool for performing code coverage analysis on the above-mentioned services; obtaining code coverage analysis result information and test result information, wherein the code coverage analysis result information is obtained by analyzing the pages on the above-mentioned services based on the code coverage tool, and the test result information is obtained by testing the code coverage analysis on the pages on the above-mentioned services based on the simulation testing tool; and providing comparison information obtained by comparing the code coverage analysis result information and the test result information.

In an exemplary embodiment, the code overlay analysis result information may include information in the original code of the page implementing the above service that the user's usage history is confirmed in the first code area, and information in the original code that the user's usage history is not confirmed in the second code area.

In an exemplary embodiment, the code overlay analysis result information may include the first identification information of the first code area and the second identification information of the second code area, wherein the first identification information and the second identification information are identified based on different hues.

In an exemplary embodiment, the code coverage analysis result information may include information on the ratio of the first code region to the original code.

In an exemplary embodiment, the steps for obtaining the code coverage analysis results information may include the following steps: identifying each API domain included in the plurality of API (Application Programming Interface) domains used to perform the above-mentioned service; and obtaining the code coverage analysis results information corresponding to each API domain based on the code coverage tool that executes one or more pages of the above-mentioned service corresponding to each of the above-mentioned API domains.

In an exemplary embodiment, the above information provision method may further include the following steps: obtaining input to select a first API domain from the plurality of API domains; and providing first code coverage analysis result information corresponding to the first API domain in response to the input; and the first code coverage analysis result information includes a single code coverage analysis result for a single page on the service corresponding to the first API domain.

In an exemplary embodiment, the above-described code overlay tool can be executed at a fixed interval.

In an exemplary embodiment, the above-mentioned simulation testing tool may correspond to the first simulation testing tool, which performs simulation testing on the code coverage analysis of the code of the method in the original code.

In an exemplary embodiment, the above-mentioned simulation testing tool may correspond to a second simulation testing tool, which performs simulation testing on the code coverage analysis of the code that implements the input of request information and the output of response information for the API domain.

In an exemplary embodiment, the above-mentioned simulation testing tool may correspond to a third simulation testing tool, which performs simulation testing on the code coverage analysis of the code that performs information processing for the UI (User Interface).

In an exemplary embodiment, the comparison information may include information obtained by comparing a first ratio and a second ratio, wherein the first ratio is the ratio of the code area that has been identified as the user's usage history, which is analyzed in the original code of the page implementing the above service based on the code overlay analysis results, and the second ratio is the ratio of the code area that has been identified as the user's usage history, which is determined in the original code based on the test results.

In an exemplary embodiment, the comparison information may include information about a portion of the code area that is identified in the original code of the page implementing the above-mentioned service as differing from the code overlay analysis results generated by the code overlay tool and the test results generated by the simulation testing tool.

In an exemplary embodiment, the aforementioned portion of the code area may include the following code area: which is identified as having the user's usage history based on the aforementioned code overlay tool, and which is determined as not having the user's usage history based on the aforementioned simulation testing tool.

In an exemplary embodiment, the above information provision method may further include the following steps: obtaining tool update information, which is used to update the above simulation test tool based on the information of the above-mentioned part of the code area; and confirming the simulation test tool updated based on the above-mentioned tool update information.

In an exemplary embodiment, the above information provision method may further include the following steps: providing simulation test update result information, which is obtained from code overlay analysis of the pages on the above service based on the updated simulation test tool.

In an exemplary embodiment, the above information providing method may further include the following steps: providing updated feedback information of the above simulation testing tool based on comparison information obtained by comparing the above code coverage analysis results information with the above simulation test update results information.

Various embodiments of the information-providing electronic device may include: a processor; and one or more memories storing one or more instructions; and when executing the one or more instructions, controlling the processor to perform the following steps: based on the processing of request information obtained from multiple users on services related to the electronic device, setting up a code coverage tool to analyze the code coverage of the services. The tool); and a simulation testing tool for performing code coverage analysis on the above-mentioned services; obtaining code coverage analysis result information and test result information, wherein the code coverage analysis result information is obtained by analyzing the pages on the above-mentioned services based on the code coverage tool, and the test result information is obtained by testing the code coverage analysis on the pages on the above-mentioned services based on the simulation testing tool; and providing comparison information obtained by comparing the code coverage analysis result information and the test result information.

The various embodiments described above are only a part of the preferred embodiments of the present invention. Those skilled in the art can derive and understand multiple embodiments reflecting the technical features of the various embodiments of the present invention based on the following detailed description. [Effects of the Invention]

This invention proposes an electronic device that provides a method for comparing code overlay analysis results generated by a code overlay tool with test results generated by a simulation testing tool, thereby improving the accuracy of simulation testing tools used for code overlay simulation testing.

The effects that can be obtained in this invention are not limited to those mentioned above. Those skilled in the art to which this invention pertains can clearly understand other effects not mentioned based on the following description.

The following embodiments combine the constituent elements and features of various embodiments in a specific form. Unless otherwise explicitly stated, each constituent element or feature may be considered optional. Each constituent element or feature can be implemented without being combined with other constituent elements or features. Furthermore, a portion of the constituent elements and features can be combined to constitute various embodiments. The order of actions described in the various embodiments may be changed. A portion of the constituent elements or features of a certain embodiment may be included in other embodiments, or may be interchangeable with corresponding constituent elements or features of other embodiments.

The description of the diagrams does not describe processes or steps that could confuse the main points of various embodiments, nor does it describe processes or steps that are understandable to a person of common knowledge in the art.

Throughout this specification, when a part is described as "comprising" or "including" a constituent element, unless specifically stated otherwise, it implies that other constituent elements may be included, not excluded. Furthermore, terms such as "...part," "...device," and "module" used in this specification refer to a unit that processes at least one function or action, which may be implemented by hardware, software, or a combination of hardware and software. Also, in the description of various embodiments (particularly within the scope of the invention claim below), unless otherwise indicated in this specification or expressly refuted in the text, "a (or an)," "one," "the," and similar related terms may be used in both singular and plural senses.

The following description, with reference to the accompanying diagrams, details preferred embodiments of various examples. The detailed descriptions disclosed below, together with the accompanying diagrams, are illustrative of various embodiments and are not intended to represent the only embodiments.

Furthermore, the specific terms used in the various embodiments are provided to aid in understanding the various embodiments, and the use of these specific terms can be transformed into other forms without departing from the technical ideas of the various embodiments.

Figure 1 is a diagram illustrating an information providing system for providing information by means of an electronic device that can implement various embodiments.

Referring to Figure 1, the information providing system of various embodiments can be implemented in various electronic devices. For example, the information providing system can be implemented in server device 100 and user device 200. In other words, server device 100 and user device 200 can implement the operations of various embodiments of the present invention based on the information providing system implemented in each device. As an example, in various embodiments of the present invention, server device 100 can provide the user device 200 corresponding to the administrator with comparison information obtained by comparing the code overlay analysis results generated by the code overlay tool with the test results generated by the simulation test tool. On the other hand, the information providing system of various embodiments can also be implemented in more electronic devices and servers, and is not limited to those shown in Figure 1 above.

The server device 100 in various embodiments may be a device that enables wireless and wired communication with a plurality of user devices 200, including storage devices with large unit storage capacity. For example, the server device 100 may be a cloud device connected to a plurality of user devices 200.

The user device 200 in various embodiments can be a desktop computer, tablet computer, mobile terminal, or other device that can be used by a personal user. In addition, other electronic devices that perform similar functions can also be used as user device 200.

The information providing system of various embodiments may include various modules for performing actions. The modules included in the information providing system may be computer code and one or more instructions implemented in such a way that the physical device implementing the information providing system (or included in the physical device) (e.g., server device 100 and user device 200) can perform specified actions. In other words, the physical device implementing the information providing system may store multiple modules in memory in the form of computer code, and when executing the multiple modules stored in memory, the multiple modules cause the physical device to perform specified actions corresponding to the multiple modules.

Figure 2 is a diagram showing the configuration of server device 100 and user device 200 in various embodiments.

Referring to FIG2, the server device 100 and the user device 200 may include an input/output unit 210, a transceiver unit (or, communication unit) 220, a memory 230 and a processor 240.

The input/output unit 210 may be various interfaces or ports for receiving user input or outputting information to the user. The input/output unit 210 may include an input module and an output module, with the input module receiving user input from the user. The user input can be implemented in various forms, including key input, touch input, and audio input. As examples of input modules capable of receiving such user input, in addition to traditional small keyboards or keyboards and mice, they also include touch sensors that sense user touch, microphones that receive audio signals, cameras that recognize gestures by image recognition, proximity sensors that sense user proximity by at least one of an illuminance sensor or an infrared sensor, motion sensors that recognize user movements by an accelerometer or a gyroscope sensor, and other various types of input mechanisms that sense or receive user input. The input module of the embodiments of the present invention may include at least one of the devices listed above. Here, the touch sensor can be implemented as a piezoelectric or electrostatic touch sensor that senses touch via a touch panel or touch film attached to the display panel, or an optical touch sensor that senses touch via optical means. In addition, the input module can also be implemented as an input interface (Universal Serial Bus (USB) port, Personal System 2 (PS/2) port, etc.) that connects to an external input device to receive user input, replacing the input interface of the device that senses user input itself. Furthermore, the output module can output various types of information. The output module may include at least one of the following: a display for outputting images, a speaker for outputting sound, a tactile device for generating vibration, and other types of output mechanisms. In addition, the output module may also be implemented as an output interface of the port type connected to the above-mentioned individual output mechanisms.

As an example, an output module in the form of a display can display text, still images, and video. Displays include at least one of the following: liquid crystal displays (LCDs), light-emitting diode (LED) displays, organic light-emitting diode (OLED) displays, flat panel displays (FPDs), transparent displays, curved displays, flexible displays, three-dimensional (3D) displays, holographic displays, projectors, and various other devices capable of performing image output functions. Such displays can also be in the form of touch displays integrated with the touch sensors of the input module.

The transceiver unit 220 can communicate with other devices. Therefore, the server device 100 and the user device 200 can send and receive information with other devices through the transceiver unit 220. For example, the server device 100 and the user device 200 can use the transceiver unit 220 to perform signal-to-signal communication or to communicate with other devices.

Here, communication, i.e., the transmission and reception of data, can be achieved via wired or wireless means. For this purpose, the transceiver unit 220 may include a wired communication module that connects to the Internet via a LAN (Local Area Network), a mobile communication module that transmits and receives data by connecting to a mobile communication network via a mobile communication base station, a short-range communication module that uses communication methods such as Wi-Fi (WLAN) or Bluetooth (WPAN) (Wireless Personal Area Network), a satellite communication module that uses GPS (Global Positioning System) or GNSS (Global Navigation Satellite System), or a combination thereof.

Memory 230 can store various information. Memory 230 can store data temporarily or semi-permanently. For example, memory 230 of server device 100 can store the operating system (OS) used to drive server device 100, data used to manage the website, programs used to generate Braille, and data related to applications (e.g., website applications). Furthermore, memory 230 can store modules in computer code form as described above.

As an example of storage device 230, it may include hard disk drive (HDD), solid state drive (SSD), flash memory, read-only memory (ROM), random access memory (RAM), etc. This storage device 230 can be provided in a built-in or removable form.

Processor 240 controls the overall operation of server device 100 and user device 200. To this end, processor 240 can perform various information calculations and processing, and control the operation of the components of server device 100. For example, processor 240 can execute programs and applications to provide information. Processor 240 can be implemented as a computer or a similar device, depending on the combination of hardware, software, or the like. In terms of hardware, processor 240 can be implemented as a circuit that processes electrical signals to perform control functions; in terms of software, it can be implemented as a program that drives the hardware processor 240. On the other hand, in cases not specifically mentioned in the following description, the actions of the server device 100 and the user device 200 can be interpreted as being implemented by the control of the processor 240. That is, when the module implemented in the above information providing system is executed, the module can be interpreted as controlling the processor 240 in a manner that causes the server device 100 and the user device 200 to perform the following actions.

In short, various embodiments can be implemented by various mechanisms. For example, various embodiments can be implemented by hardware, firmware, software, or a combination thereof.

In the case of implementation via hardware, various embodiments can be implemented using one or more ASICs (application-specific integrated circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), PLDs (programmable logic devices), FPGAs (field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, etc.

When implemented using firmware or software, the methods of various embodiments can be implemented in the form of modules, processes, or functions that perform the functions or actions described below. For example, software code can be stored in memory and driven by a processor. The memory can be located inside or outside the processor and can send and receive data with the processor through various known mechanisms.

The following describes various embodiments in more detail based on the technical ideas described above. The content described above can be applied to the various embodiments described below. For example, actions, functions, terms, etc., not defined in the various embodiments described below can be implemented and explained based on the content described above.

In the following description, various embodiments are explained based on the premise that the server device 100 provides comparison information obtained by comparing the code coverage analysis results and the test results. According to various embodiments, the user device 200 of the service administrator can output the comparison information received from the server device 100.

Figure 3 is a diagram illustrating the operation of the server device 100 used to provide information in various embodiments.

According to Figure 3, the server device 100 can provide comparison information obtained by comparing code coverage analysis results with test results. Specifically, based on the processing of request information obtained from multiple users on the service, it sets up a code coverage tool for analyzing the code coverage of the service and a simulation test tool for simulating the code coverage analysis of the service. 301), obtain code coverage analysis results information based on code coverage tools to analyze pages on the service, and test results information based on simulation testing tools to test code coverage analysis of pages on the service (303), and provide comparison information obtained by comparing code coverage analysis results information and test results information (305).

According to Figure 3, the comparison information provided by server device 100 can be implemented for services provided by server device 100 or services related to server device 100. These services can be services in which multiple users can order and purchase multiple items sold in the service. The multiple items sold in the service are not limited to the type or category of items, and can include various types or categories of items registered by the seller for the purpose of selling items.

According to various embodiments, in action 301, server device 100 may configure a code overlay tool for analyzing the code overlay of the service and a simulation test tool for simulating the code overlay analysis of the service based on the processing of request information obtained by multiple users on the service.

For example, code coverage analysis can refer to analyzing whether the code of a system or software used to provide services is actually executed. Code coverage tools can refer to software tools or programming tools that can be applied to a system or software to analyze code coverage.

For example, the code overlay tool configured on server device 100 according to action 301 can be configured to run at a fixed interval. At the management service level, server device 100 can be configured to run the code overlay tool at fixed intervals to allow for continuous analysis of code overlay. Specifically, it can be configured to run the code overlay tool at fixed date intervals, avoiding peak user usage times and instead running it during off-peak hours such as early morning. Similarly, the simulation testing tool configured on server device 100 according to 301 can also be configured to run at a fixed interval. At this point, the execution cycle of the code overlay tool and the execution cycle of the simulation test tool can be set separately for each tool.

For example, the simulation test tool configured by server device 100 according to action 301 can be a first simulation test tool for code coverage analysis of code that simulates test method settings in the original code. That is, server device 100 can configure a simulation test tool for code coverage analysis of code written for setting methods in a series of original code. Here, "method" can refer to a set of code in the original code used to perform a specific operation. From a similar perspective, the aforementioned first simulation test tool can be not only the code of the setting method, but also the code of the simulated test class or thread.

For example, the server device 100 can be configured with a second simulation test tool based on the simulation test tool set according to action 301, which performs code coverage analysis on the code that simulates the input of request information and the output of response information in the API domain. That is, the server device 100 can be configured with a simulation test tool that performs code coverage analysis on the code written in a series of original codes to perform the function of inputting request information or outputting response information in the API domain.

For example, the simulation test tool set by the server device 100 according to action 301 can be a third simulation test tool for simulating the code coverage analysis of the code that performs UI (User Interface) information processing. That is, the server device 100 can be configured to perform simulation test code coverage analysis on the code written in a series of original codes to perform information processing functions of the UI on the service.

According to various embodiments, in action 303, server device 100 can obtain code coverage analysis results information and test results information. The code coverage analysis results information is obtained by analyzing the pages on the service based on a code coverage tool, and the test results information is obtained by testing the code coverage analysis of the pages on the service based on a simulation testing tool.

For example, the code overlay analysis result information obtained by server device 100 according to action 303 may include: information confirming the first code area of the user's usage history in the original code of the page implementing the service; and information not confirming the second code area of the user's usage history in the original code. That is, the information on analyzing the code in the original code of the page implementing the service based on whether the user's usage history has been confirmed may be included in the code overlay analysis result information.

At this point, in order to identify and confirm the user's usage history in the first code zone and the user's usage history in the second code zone that has not been confirmed, identification information for each code zone can be set. The code coverage analysis result information can be set to the first identification information for the first code zone that has confirmed the user's usage history and the second identification information for the second code zone that has not been confirmed. As mentioned above, the first and second identification information can be set in a way that identifies based on different hues.

For example, the code coverage analysis results obtained by server device 100 based on action 303 may include information on the ratio of the first code block that identifies the user's usage history in the original code of the page implementing the service. This can be managed in such a way that the ratio of the code block that identifies the user's usage history in the original code analysis can be used to confirm the level of code coverage of the page on the service by providing quantified information.

For example, action 303, which obtains code overlay analysis results information for pages on the analysis service, can be the following action: apply a code overlay tool to the pages of each API (Application Programming Interface) domain included in the service and obtain information including individual code overlay analysis results for individual pages on the service corresponding to each API domain.

Specifically, server device 100 can confirm that each API domain included in the plurality of API domains used to provide services can execute a code coverage tool at the API domain unit to obtain code coverage analysis results corresponding to each API domain. That is, server device 100 confirms that it can execute a code coverage tool on one or more pages of the service corresponding to each API domain to obtain code coverage analysis results information corresponding to each API domain.

Furthermore, when an administrator wishes to confirm the code coverage analysis results of an API domain, if the administrator receives input indicating a specific first API domain among the plurality of API domains included in the selected service, the server device 100 can provide the first code coverage analysis results corresponding to the first API domain in accordance with the aforementioned input. In this case, the first code coverage analysis results corresponding to the first API domain can be information that integrates the code coverage analysis results of a single page on the service corresponding to the first API domain.

For example, the test result information obtained by server device 100 according to action 303 may include information on the results of code coverage analysis simulated using a simulation testing tool configured to perform code coverage analysis in a simulated test manner. As a simulation result of code coverage analysis, the test result information described above may include information such as how many users' usage history has been identified in the source code of the pages implementing the service.

According to various embodiments, in action 305, server device 100 can provide comparison information obtained by comparing code coverage analysis results information with test results information.

For example, the comparison information provided by the server device 100 according to the action 305 may include information obtained by comparing a first ratio and a second ratio. The first ratio is the ratio of the code area that confirms the user's usage history, which is analyzed in the original code of the page implementing the service based on the code overlay analysis results. The second ratio is the ratio of the code area that confirms the user's usage history, which is determined in the original code based on the test results. That is, the information in the original code that is analyzed as the ratio of the code area where the user's usage history is confirmed based on the code coverage analysis results is compared with the information in the original code that is judged as the ratio of the code area where the user's usage history is confirmed based on the test results. In this way, management can be carried out in the following way: confirming that the code coverage ratio included in the test results generated by the simulation test tool is mostly consistent with the code coverage ratio included in the actual code coverage analysis results.

For example, the comparison information provided by server device 100 according to action 305 may include information about the portion of the original code that differs between the code coverage analysis results generated by the code coverage tool and the test results generated by the simulation testing tool in the original code of the page implementing the service. That is, information about the portion of the code that differs between the actual code coverage analysis results performed on the page of the service and the test results of the simulated code coverage analysis may be included in the comparison information provided by server device 100 according to action 305.

Specifically, the server device 100 may identify, based on the comparison information provided by action 305, a portion of the code area where the code coverage analysis results differ from the test results. This may include code areas where the user's usage history is confirmed by the code coverage tool analysis but not by the simulation test tool. In the results of code coverage analysis performed on service pages, if the user's usage history is confirmed but not confirmed in the simulation test results, the code area is determined to be a code area not properly covered by the simulation test tool. Therefore, the code area described above can be identified as a code area that needs to be confirmed in order to improve the simulation test tool.

When the server device 100 confirms, through comparison information, that the code overlay tool has identified the user's usage history, but the simulation test tool determines that a portion of the user's usage history has not been identified, the server device 100 may also perform the following actions as shown in Figure 4: based on the information of the aforementioned portion of the code area, the simulation test tool is updated more appropriately to provide test results generated by the updated simulation test tool.

Figure 4 is a diagram illustrating the action method of providing simulated test update result information by providing the server device 100 with code overlay analysis of pages on the simulated test service based on the updated simulated test tool.

Server device 100 can confirm information (401) in the original code of the page implementing the service that the code coverage analysis results generated by the code coverage tool are different from the test results generated by the simulation test tool. At this time, the code area confirmed according to action 401 may include code areas that, contrary to the analysis by the code coverage tool, confirm the user's usage history, but are determined by the simulation test tool to have no confirmed user usage history.

Subsequently, the server device 100 can obtain tool update information (403) for updating the simulation test tool based on the information of a confirmed portion of the code area, and can confirm the updated simulation test tool based on the tool update information (405). Here, the tool update information may include information on updates where the administrator directly modifies the simulation test tool to better match the actual code coverage analysis results, or information on updates where the server device 100 confirms and determines that the parts of the simulation test tool need improvement and automatically modifies them.

The server device 100 of the confirmed updated simulation test tool can be configured to simulate the code coverage analysis of the page on the test service based on the updated simulation test tool, and can obtain the simulation test update result information of the code coverage analysis of the page on the test service again (407).

For example, according to Figure 4, the server device 100 providing simulation test update result information can also perform the following actions: compare the simulation test update result information with the code coverage analysis result information again to obtain comparison information obtained from the comparison of the simulation test update result information and the code coverage analysis result information, thereby providing feedback information on the updated simulation test tool based on the obtained comparison information. That is, when updating the simulation test tool, the server device 100 compares the simulation test update results generated by the updated simulation test tool with the actual code coverage analysis results, thereby generating feedback on whether improvements have been made to achieve a certain level of accuracy.

For example, according to Figure 4, the tool update information obtained by the server device 100, which provides simulation test update result information, can be information managed in a way that updates are performed on a page-by-page basis for the service. As an example, for the code set corresponding to the code area on the original code of a specific page of the service and the user's usage history confirmed by the code overlay tool, if the test result generated by the first simulation test tool indicates that the above code set has not been used by the user, then the specific page including the above code set can be confirmed by the first simulation test tool as the object that should be improved by updating.

In this case, the tool update information may include instruction information that indicates the API domain corresponding to the specific page and the specific page, and may also include update event information that sets update events in a manner that can improve the test results of the first simulation test tool for the specific page. Based on the instruction information and update event information included in the tool update information, the server device 100 can update the test settings of the first simulation test tool related to the specific page.

For example, when updating a simulation test tool in a way that conforms to the code coverage analysis results generated by a code coverage tool, if there are many test settings in the simulation test tool that need to be updated, and the corresponding tool update information becomes very large, then according to the specifications of the device running the simulation test tool, overload will occur during the update process of the increased tool update information. Therefore, the server device 100 can be configured to set a critical size for the tool update information in a way that the size of the tool update information does not exceed a fixed size. Furthermore, as the critical size is set, if the information of the test settings that are determined to need updating in the simulation test tool is not fully included in the tool update information, the server device 100 assigns an update priority to the page corresponding to the test settings that are being updated through the tool update information. This allows for management in the following way: the information of the test settings of the simulation test tool that are updated and the page with the higher update priority are first included in the tool update information.

As described above, the tool update information can update the test settings of the simulation test tool associated with a specific page corresponding to a specific API domain included in the service. Therefore, the specific API domain and the specific page can be specified. At this time, the server device 100 can set the priority of the API domain and the priority of the page specified by the instruction information as described above.

The priority of API domains configured on server device 100 can be set based on the utilization rate of multiple users of the API domain on the service. Specifically, the higher the user utilization rate of an API domain, the higher its priority can be. As an example, when the simulation test tool related to the test settings of page 1 included in API domain 1 and page 2 included in API domain 2 needs to be updated, if the user utilization rate of API domain 1 is higher than that of API domain 2, the tool update information can be configured so that the update of the simulation test tool related to the test settings of page 1 can be performed before the update of the test settings of page 2.

Furthermore, the priority of the pages configured on the server device 100 can be set based on the utilization rate of multiple users across multiple pages included in the same API domain. Specifically, among the multiple pages included in an API domain, the page with the higher user utilization rate can have a higher priority. As an example, when the simulation test tool related to the test settings of the first page and the third page included in the first API domain needs to be updated, if the user utilization rate of the first page is higher than that of the third page, the tool update information can be configured so that the update of the simulation test tool related to the test settings of the first page can be performed before the update of the test settings of the third page.

Server device 100 can be managed in the following manner: first, the priority of API domains is applied, and then the priority of pages is applied, thereby determining the update priority of the pages included in each API domain on the service, and setting tool update information according to the determined update priority. In the case corresponding to the above example, the information used to update each test setting section in the order of the test setting section related to the first page, the test setting section related to the third page, and the test setting section related to the second page can be included in the tool update information.

Figure 5 is a block diagram showing the comparison information between code coverage analysis results and test results obtained based on code coverage tools and simulation testing tools.

In Figure 5, a "Canary" system is built on a portion of the overall server or a designated server for service, and managed in a manner that can be applied to software tools. A code overlay tool ("Coverage tool") that analyzes code overlay based on the request information of the "Canary" system built as described above can be set by the server device 100 (501). Furthermore, at least a portion of the first simulation test tool (“UT (Unit Test)”) for code coverage analysis of the code simulating the test setup method in the original code, the second simulation test tool (“Automation”) for code coverage analysis of the code simulating the input of request information and output of response information in the API domain, and/or the third simulation test tool (“Manual testing”) for code coverage analysis of the code simulating the information processing of the UI (User Interface) in the test, can be configured by the server device 100 (503).

Obtain code coverage analysis results information, including the results of code coverage analysis based on the configured code coverage tool and targeting the pages on the service; obtain test results information, including the results of code coverage analysis based on the configured simulation testing tool and targeting the pages on the service; thereby, obtain comparison information obtained by comparing the code coverage analysis results information and the test results information (505).

It should be understood that, according to Figures 3 to 5, during the process of implementing the method of providing comparison information obtained by comparing code coverage analysis results and test results in the server device 100, the information can be combined in various forms.

Figures 6 to 9 are diagrams illustrating examples of UI/UX (User Experience) used to provide information in various embodiments. For example, the examples in Figures 6 to 9 can be the UI/UX (user interface/user experience) of user device 200, and the embodiments described in the following figures can be implemented based on the operation of server device 100 described in Figures 6 to 9.

Specifically, the various embodiments of the UI/UX of the user device 200 illustrated in the following figures can be implemented in the following manner: after the server device 100 provides information to the user device 200 based on the actions described in Figures 3 to 5, the user device 200 outputs it. However, the various embodiments of the UI/UX illustrated in the following figures are not limited to the manner described above, and can be implemented in various forms that can implement the various embodiments of the UI/UX.

Figure 6 is an example of the code overlay analysis results information corresponding to the output of user device 200 and a single page on the service in various embodiments.

In Figure 6, the code overlay analysis result information output by the user device 200 may include the code overlay analysis result information including the original code of a certain page on the service.

In Figure 6, the code overlay analysis result information output by the user device 200 can be set as follows: including information 601 of the first code area in the original code where the user's usage history has been confirmed and information 603 of the second code area where the user's usage history has not been confirmed.

At this point, a first identification information for identifying information 601 in the first code area and a second identification information for identifying information 603 in the second code area can be set separately. The first and second identification information can be set in a way that identifies information based on different hues. That is, information 601 in the first code area and information 603 in the second code area can be distinguished in the original code by different hues.

Figure 7 is an example of the code overlay analysis results information corresponding to the user device 200 output and API domain in various embodiments.

As shown in Figure 7, the code overlay analysis results output by the user device 200 can be configured to include code overlay analysis results for various pages corresponding to the API domain.

In Figure 7, the code coverage analysis result information output by the user device 200 can be information that corresponds to a specific API domain (“modular_search”) included in the service. Here, the pages (701) on the service included in the aforementioned API domain where the code coverage analysis is performed can be displayed. When there is an input to select one of the displayed pages, the code coverage analysis result as shown in Figure 6 can be output to the selected page.

Furthermore, in Figure 7, the code coverage analysis results output by the user device 200 may include the following information: the percentage of the user's usage history first code area identified in the original code of each page implemented by the API domain (703).

It can be configured as follows: manage the code coverage analysis results according to the unit of the API domains included in the service by using the code coverage analysis results information of the API domains output as shown in Figure 7.

Figures 8 and 9 are examples of comparison information obtained by comparing the code coverage analysis results and test results information of the user device 200 output in various embodiments.

Figures 8 and 9 may include graphical information comparing the ratio of actual code coverage generated by the code coverage analysis tool with the ratio of code coverage on the simulated test generated by the simulation test tool among various information included in the comparison information.

Figure 8 may include graphical information (800) comparing the ratio of actual code coverage generated by the code coverage analysis tool with the ratio of code coverage on the simulated test ("active_line_cov" - 83%) generated by the first simulation test tool ("UT Coverage") which performs code coverage analysis on code using the test configuration method in the original code. Furthermore, Figure 9 may include graphical information (900) comparing the actual code coverage ratio generated by the coverage analysis tool with the code coverage ratio ("active_line_cov" - 71%) generated by the second simulation test tool ("Automation Code Coverage") that simulates test code coverage analysis of the code implementing API domain request information input and response information output.

In Figures 8 and 9, when the code coverage ratio in the simulated test corresponding to the simulation testing tool is lower than the actual code coverage ratio, it may be that there is a portion of the code area that the code coverage tool analyzes as having confirmed the user's usage history but the simulation testing tool determines as not having confirmed the user's usage history. Therefore, for the portion of the code area described above, the simulation testing tool can be updated according to the various embodiments mentioned above so as to conform to the actual code coverage analysis results.

The UI/UX of the user device 200 in Figures 6 to 9 and the actions of the user device 200 can be implemented in conjunction with the operation of the server device 100 described in Figures 3 to 5. The UI/UX examples in Figures 6 to 9 are examples used to illustrate the present invention. Various embodiments of the present invention are not limited to the UI/UX forms in Figures 6 to 9, and can be implemented according to all forms of UI/UX that can implement various embodiments of the present invention.

The embodiments of the invention disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the invention and to aid in understanding it, and are not intended to limit the scope of the invention. That is, those skilled in the art to which this invention pertains will understand that other variations based on the technical concept of the invention can be implemented. Furthermore, the above embodiments can be combined as needed for application. For example, a portion of all embodiments of the invention can be combined to implement it in a system.

Furthermore, the methods corresponding to the system of this invention can be implemented as program commands that can be executed by various computer mechanisms and recorded on computer-readable media.

As described above, from a specific perspective, various embodiments of the present invention can be implemented in a computer-readable recording medium using computer-readable code. A computer-readable recording medium is any data storage device capable of storing data that can be read by a computer system. Examples of computer-readable recording media may include read-only memory (ROM), random access memory (RAM), compact disk-read-only memory (CD-ROM), magnetic tape, floppy disk, optical data storage devices, and carrier waves (data transmission via the Internet, etc.). Computer-readable recording media can also be distributed via network-connected computer systems, thus allowing computer-readable code to be stored and executed in a distributed manner. Furthermore, the functional programs, code, and segments used to achieve the various embodiments of this invention can be easily interpreted by skilled programmers in the field of this invention.

Furthermore, it is understood that the various embodiments of the present invention can be implemented as hardware, software, or a combination of hardware and software. Such software can be stored, for example, in volatile or non-volatile storage devices such as ROM, or in memory such as RAM, memory chips, devices or integrated circuits, or in optically or magnetically recordable and machine-readable (e.g., computer) media such as compact disks (CDs), DVDs (Digital Versatile Discs), magnetic disks, or magnetic tapes, regardless of whether it is deletable or re-recordable. It is understood that the methods of various embodiments of the present invention can be implemented by a computer including a control unit and memory, or by a vehicle including the memory or computer as described above. Such memory includes a program that implements the instructions of the embodiments of the present invention, or a storage medium that can be read by a machine suitable for storing programs.

Therefore, this invention includes a program for implementing the code of the apparatus or method described in the invention claims of this specification, and a storage medium readable by a machine (computer, etc.) storing such a program. Furthermore, such a program can be electrically transmitted via any medium, such as a communication signal transmitted using a wired or wireless connection, and this invention appropriately includes its equivalent.

The foregoing description refers to embodiments of the present invention. However, the embodiments of the present invention disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present invention and to aid in understanding it, and are not intended to limit the scope of the present invention. Furthermore, it is understood that the previously described embodiments of the present invention are merely examples, and those skilled in the art can implement various variations and equivalent embodiments based on them. Therefore, the true scope of protection of the present invention should be defined according to the following patent application.

100: Server Device 200: User Device 210: Input/Output Unit 220: Transceiver Unit 230: Memory 240: Processor 301: Action 303: Action 305: Action 401: Action 403: Action 405: Action 407: Action 501: Action 503: Action 505: Action 601: Information in Code Area 1 603: Information in Code Area 2 701: Page 703: Information 800: Graphic Information 900: Graphic Information

Figure 1 is a diagram illustrating the operation method of an electronic device for providing information, which can implement various embodiments. Figure 2 is a diagram showing the configuration of server device 100 and user device 200 in various embodiments. Figure 3 is a diagram showing the operation method of server device 100 for providing information in various embodiments. Figure 4 is a diagram showing the operation method of providing server device 100 with simulated test update result information based on updated simulation test tools to simulate test service page code coverage analysis. Figure 5 is a block diagram showing the comparison information of code coverage analysis result information and test result information obtained based on code coverage tools and simulation test tools. Figure 6 is an example of code coverage analysis results information corresponding to a single page on the service from the user device 200 output in various embodiments. Figure 7 is an example of code coverage analysis results information corresponding to an API domain from the user device 200 output in various embodiments. Figures 8 and 9 are examples of comparison information obtained by comparing code coverage analysis results information and test results information from the user device 200 output in various embodiments.

301:Action303:Action305:Action

Claims (11)

An information provision method, in which an electronic device provides information, includes the following steps: based on the processing of request information obtained from a plurality of users on a service related to the electronic device, setting up a code overlay tool for analyzing code overlay of the service, and a simulation testing tool for simulating the code overlay analysis of the service; obtaining code overlay analysis result information and test result information, wherein the code overlay analysis result is based on the code overlay tool analyzing pages on the service. The test result information obtained is based on the code coverage analysis of the page on the service tested using the above-mentioned simulation testing tool; and provides comparison information obtained by comparing the above-mentioned code coverage analysis result information with the above-mentioned test result information; wherein the above-mentioned code coverage analysis result information includes: information that the user's usage history first code area was identified in the original code implementing the page on the service; and information that the user's usage history second code area was not identified in the above-mentioned original code. As in the information provision method of Request 1, the aforementioned code overlay analysis result information includes the first identification information of the first code area and the second identification information of the second code area, wherein the first identification information and the second identification information are identified based on different hues. As in the information provision method of Request 1, the aforementioned code coverage analysis result information includes information on the ratio of the aforementioned first code region in the aforementioned original code. As in the information provision method of Request 1, the steps for obtaining the aforementioned code coverage analysis results information include the following steps: identifying each API domain included in the plurality of API domains used to perform the aforementioned service; and obtaining the code coverage analysis results information corresponding to each of the aforementioned API domains based on the aforementioned code coverage tool that executes one or more pages of the aforementioned service corresponding to each of the aforementioned API domains. The information provision method of claim 4 further includes the following steps: obtaining input to select a first API domain from the plurality of API domains; and providing first code coverage analysis result information corresponding to the first API domain in relation to the input; and the first code coverage analysis result information includes a single code coverage analysis result for a single page on the service corresponding to the first API domain. As in the information provision method of Request 1, the aforementioned code overwriting tool is executed at fixed intervals. As in the information provision method of Request 1, the aforementioned simulation testing tool corresponds to the first simulation testing tool, which is a code overlay analysis of the code of the test setting method in the original code. As in the information provision method of request item 1, the aforementioned simulation test tool corresponds to the second simulation test tool, which performs simulation tests on the code coverage analysis of the code that implements the input of request information and the output of response information for the API domain. As in the information provision method of Request 1, the aforementioned simulation testing tool corresponds to the third simulation testing tool, which performs simulation testing on the code coverage analysis of the code used for information processing of the UI. As in the information provision method of Request 1, the aforementioned comparison information includes information obtained by comparing a first ratio and a second ratio, wherein the first ratio is the ratio of code regions that have been identified in the source code of the page implementing the aforementioned service, based on the aforementioned code overlay analysis results, and the second ratio is the ratio of code regions that have been identified in the source code, based on the aforementioned test results. An electronic device, which provides information, includes: a processor; and one or more memories storing one or more instructions; and, when executing the one or more instructions, controlling the processor to perform the following steps: based on the processing of request information obtained from a plurality of users on a service related to the electronic device, setting up a code overlay tool for analyzing code overlay of the service, and a simulation test tool for simulating the code overlay analysis of the service; obtaining code overlay analysis result information and test result information, wherein the code overlay analysis result information... The test results are obtained by analyzing the pages of the aforementioned service using the aforementioned code overlay tool, and the test results are obtained by testing the code overlay analysis of the pages of the aforementioned service using the aforementioned simulation testing tool; and comparative information is provided by comparing the code overlay analysis results with the test results; wherein the code overlay analysis results include: information that the user's usage history in the first code area is confirmed in the original code implementing the pages of the aforementioned service; and information that the user's usage history in the second code area is not confirmed in the original code.