Operating method of electronic device for providing information, and electronic device supporting same
The electronic device method compares code coverage analysis with simulation test results to provide accurate information, addressing the inconsistency issue in e-commerce product details by updating simulation tools to match actual usage, thus enhancing user experience and service satisfaction.
Patent Information
- Application Number
- PCT/KR2023/007071
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-10
- Filing Date
- 2023-05-24
- Publication Date
- 2024-11-14
AI Technical Summary
Existing methods for providing detailed and accurate information about products in e-commerce lack effective comparison tools for code coverage analysis and simulation test results, leading to inconsistencies and inaccuracies in user experience.
An electronic device method that compares code coverage analysis results from a code coverage tool with test results from a simulation test tool, providing comparative information by identifying usage history in source code and updating simulation test tools based on discrepancies, ensuring accurate and detailed information provision.
This method enhances the accuracy of simulation tests by comparing code coverage analysis with actual usage data, improving user experience and service satisfaction by identifying and updating simulation test tools to match actual code coverage results.
Smart Images

Figure KR2023007071_14112024_PF_FP_ABST
Abstract
Description
Method of operation of an electronic device providing information and an electronic device supporting the same
[0001] The present invention relates to a method and device for providing information, and more particularly, to a method and an electronic device thereof for providing comparative information comparing a code coverage analysis result according to a code coverage tool and a test result according to a simulation test tool.
[0002] With the advancement of electronic technology, e-commerce has become a prominent part of the shopping experience. Customers can purchase items online without having to visit a physical shopping mall or market, and items purchased online are delivered to the customer's requested delivery address.
[0003] In the case of e-commerce, providing detailed and accurate product information significantly impacts customer satisfaction, so various methods for providing more detailed and accurate information are being discussed.
[0004] In this regard, reference may be made to prior literature such as KR101756594B1 or KR101500849B1.
[0005] According to the method of the present invention, an electronic device can provide comparative information comparing a code coverage analysis result according to a code coverage tool and a test result according to a simulation test tool.
[0006] The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.
[0007] Various embodiments may provide a method of operating an electronic device for providing information and an electronic device supporting the same.
[0008] A method for an electronic device to provide information according to various embodiments may include: a step of setting a code coverage tool for analyzing code coverage for a service based on processing of request information obtained from a plurality of users on a service related to the electronic device, and a mock test tool for mock testing code coverage analysis for the service; a step of obtaining code coverage analysis result information obtained by analyzing a page on the service based on the code coverage tool and test result information obtained by testing code coverage analysis for a page on the service based on the mock test tool; and a step of providing comparison information obtained by comparing the code coverage analysis result information and the test result information.
[0009] In an exemplary embodiment, the code coverage analysis result information may include information about first lines of code for which a history of use by a user is confirmed in the source code implementing a page on the service, and information about second lines of code for which a history of use by a user is not confirmed in the source code.
[0010] In an exemplary embodiment, the code coverage analysis result information includes first identification information for the first code lines and second identification information for the second code lines, and the first identification information and the second identification information can be identified based on different colors.
[0011] In an exemplary embodiment, the code coverage analysis result information may include information about the proportion of the first code lines among the source code.
[0012] In an exemplary embodiment, the step of obtaining the code coverage analysis result information may include the step of identifying each API domain included in a plurality of API (Application Programming Interface) domains for the service; and the step of obtaining each code coverage analysis result information corresponding to each API domain based on execution of the code coverage tool for one or more pages on the service corresponding to each API domain.
[0013] In an exemplary embodiment, the method for providing information further includes: obtaining an input for selecting a first API domain from among the plurality of API domains; and providing, in response to the input, first code coverage analysis result information corresponding to the first API domain, wherein the first code coverage analysis result information may include individual code coverage analysis results for individual pages on the service corresponding to the first API domain.
[0014] In an exemplary embodiment, the code coverage tool may be run at regular intervals.
[0015] In an exemplary embodiment, the mock test tool may correspond to a first mock test tool that mock tests code coverage analysis for codes that set methods in source code.
[0016] In an exemplary embodiment, the mock test tool may correspond to a second mock test tool that mock tests code coverage analysis for codes that perform input of request information and output of response information for an API domain.
[0017] In an exemplary embodiment, the mock test tool may correspond to a third mock test tool that simulates code coverage analysis for codes that perform information processing for a UI (User Interface).
[0018] In an exemplary embodiment, the comparison information may include information comparing a first ratio of code lines analyzed as having a history of use by a user according to the code coverage analysis result information among source codes implementing a page on the service, and a second ratio of code lines determined as having a history of use by a user according to the test result information among the source codes.
[0019] In an exemplary embodiment, the comparison information may include information about some lines of code that are confirmed to be different between the code coverage analysis result by the code coverage tool and the test result by the mock test tool among the source code implementing the page on the service.
[0020] In an exemplary embodiment, some of the above code lines may include code lines that are analyzed as having a history of use by a user according to the code coverage tool, but are determined as not having a history of use by a user according to the mock test tool.
[0021] In an exemplary embodiment, the method for providing information may further include the steps of: obtaining tool update information for updating the mock test tool based on information about the some lines of code; and confirming the updated mock test tool based on the tool update information.
[0022] In an exemplary embodiment, the method for providing information may further include a step of providing mock test update result information for testing code coverage analysis for a page on the service based on the updated mock test tool.
[0023] In an exemplary embodiment, the method for providing information may further include a step of providing feedback information for the updated mock test tool based on comparison information obtained by comparing the code coverage analysis result information and the mock test update result information.
[0024] In an electronic device providing information according to various embodiments, the electronic device comprises: a processor; and one or more memories storing one or more instructions, wherein the one or more instructions, when executed, cause the processor to perform: a step of setting a code coverage tool for analyzing code coverage for a service and a mock test tool for mock testing code coverage analysis for the service based on processing of request information obtained from a plurality of users on a service related to the electronic device; a step of obtaining code coverage analysis result information obtained by analyzing a page on the service based on the code coverage tool and test result information obtained by testing code coverage analysis for a page on the service based on the mock test tool; and a step of providing comparison information obtained by comparing the code coverage analysis result information and the test result information.
[0025] The various embodiments of the present disclosure described above are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the various embodiments of the present disclosure can be derived and understood by a person having ordinary skill in the art based on the detailed description to be described below.
[0026] The present invention has a technical effect in that it can improve the accuracy of a mock test tool that performs a mock test for code coverage by suggesting a method for an electronic device to provide comparative information comparing the code coverage analysis results according to a code coverage tool and the test results according to a mock test tool.
[0027] The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present invention belongs from the description below.
[0028] FIG. 1 is a drawing for explaining an information providing system in which an operating method of an electronic device for providing information according to various embodiments can be implemented.
[0029] FIG. 2 is a diagram illustrating the configuration of a server device (100) and a user device (200) according to various embodiments.
[0030] FIG. 3 is a diagram illustrating an operation method of a server device (100) for providing information according to various embodiments.
[0031] FIG. 4 is a diagram illustrating an operation method of providing mock test update result information by mock testing code coverage analysis for a page on a service based on an updated mock test tool of a server device (100).
[0032] FIG. 5 is a block diagram illustrating a process for obtaining comparative information on code coverage analysis results and test results based on a code coverage tool and a simulation test tool.
[0033] FIG. 6 is a diagram illustrating an example of a user device (200) outputting code coverage analysis result information corresponding to an individual page on a service according to various embodiments.
[0034] FIG. 7 is a diagram illustrating an example of a user device (200) outputting code coverage analysis result information corresponding to an API domain according to various embodiments.
[0035] FIGS. 8 and 9 are diagrams illustrating an example of a user device (200) outputting comparison information comparing code coverage analysis result information and test result information according to various embodiments.
[0036] The following embodiments combine components and features of various embodiments in a predetermined form. Each component or feature may be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, various embodiments may be formed by combining some components and features. The order of operations described in various embodiments may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment.
[0037] In the description of the drawings, procedures or steps that may obscure the gist of various embodiments are not described, and procedures or steps that can be understood by a person with ordinary skill in the art are also not described.
[0038] Throughout the specification, when a part is said to "comprising" (or including) a certain component, this does not mean that other components are excluded, but rather that other components can be included, unless specifically stated otherwise. In addition, terms such as "...part," "...unit," and "module" described in the specification mean a unit that processes at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software. In addition, the words "a" or "an," "one," "the," and similar related words may be used in the singular and plural sense in the context of describing various embodiments (especially in the context of the claims below) unless otherwise indicated herein or clearly contradicted by context.
[0039] Hereinafter, preferred embodiments according to various embodiments will be described in detail with reference to the attached drawings. The detailed description set forth below, together with the attached drawings, is intended to explain exemplary embodiments of various embodiments and is not intended to represent the only embodiments.
[0040] Additionally, specific terms used in various embodiments are provided to aid understanding of the various embodiments, and the use of such specific terms may be changed in other forms without departing from the technical spirit of the various embodiments.
[0041] FIG. 1 is a drawing for explaining an information providing system in which an operating method of an electronic device for providing information according to various embodiments can be implemented.
[0042] Referring to FIG. 1, the information providing system according to various embodiments may be implemented in various types of electronic devices. For example, the information providing system may be implemented in a server device (100) and a user device (200). In other words, the server device (100) and the user device (200) may perform operations according to various embodiments of the present disclosure based on the information providing system implemented in each device. For example, in various embodiments according to the present disclosure, the server device (100) may provide comparison information comparing the code coverage analysis results according to a code coverage tool and the test results according to a simulation test tool to the user device (200) corresponding to the administrator. Meanwhile, the information providing system according to various embodiments is not limited to that illustrated in FIG. 1, and may be implemented in a wider variety of electronic devices and servers.
[0043] According to various embodiments, a server device (100) may be a device that performs wireless and wired communication with a plurality of user devices (200) and includes storage with a large storage capacity. For example, the server device (100) may be a cloud device that is linked with a plurality of user devices (200).
[0044] The user device (200) according to various embodiments may be a device that can be used by individual users, such as a desktop PC, tablet PC, or mobile terminal. In addition, other electronic devices that perform similar functions may be used as the user device (200).
[0045] An information providing system according to various embodiments may include various modules for operation. The modules included in the information providing system may be computer codes or one or more instructions implemented so that a physical device (e.g., a server device (100) and a user device (200)) in which the information providing system is implemented (or included in a physical device) can perform a specified operation. In other words, a physical device in which the information providing system is implemented stores a plurality of modules in a memory in the form of computer codes, and when the plurality of modules stored in the memory are executed, the plurality of modules can cause the physical device to perform specified operations corresponding to the plurality of modules.
[0046] FIG. 2 is a diagram illustrating the configuration of a server device (100) and a user device (200) according to various embodiments.
[0047] Referring to FIG. 2, the server device (100) and the user device (200) may include an input / output unit (210), a transceiver (or communication unit) (220), storage (230), and a processor (240).
[0048] The input / output unit (210) may be various interfaces or connection ports that receive user input or output information to the user. The input / output unit (210) may include an input module and an output module, and the input module receives user input from the user. The user input may be in various forms, including key input, touch input, and voice input. Examples of input modules that can receive such user input include not only a traditional keypad, keyboard, or mouse, but also a touch sensor that detects the user's touch, a microphone that receives a voice signal, a camera that recognizes gestures through image recognition, a proximity sensor including at least one of an illuminance sensor or an infrared sensor that detects the user's approach, a motion sensor that recognizes the user's movement through an acceleration sensor or a gyro sensor, and various other forms of input means that detect or receive various forms of user input, and the input module according to an embodiment of the present disclosure 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 detects touch through a touch panel or touch film attached to the display panel, an optical touch sensor that detects touch by an optical method, etc. In addition, the input module can be implemented in the form of an input interface (USB port, PS / 2 port, etc.) that connects an external input device that receives user input instead of a device that detects user input on its own. In addition, the output module can output various types of information. The output module can include at least one of a display that outputs an image, a speaker that outputs a sound, a haptic device that generates vibration, and various other forms of output means. In addition, the output module can be implemented in the form of a port-type output interface that connects the individual output means described above.
[0049] For example, an output module in the form of a display can display text, still images, and moving images. The display can include at least one of a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, a flat panel display (FPD), a transparent display, a curved display, a flexible display, a 3D display, a holographic display, a projector, and various other devices capable of performing an image output function. Such a display can also be in the form of a touch display that is integrated with a touch sensor of the input module.
[0050] The transceiver (220) can communicate with other devices. Accordingly, the server device (100) and the user device (200) can transmit and receive information with other devices via the transceiver (220). For example, the server device (100) and the user device (200) can communicate with each other or with other devices using the transceiver (220).
[0051] Here, communication, i.e., transmission and reception of data, can be performed wired or wirelessly. To this end, the transceiver (220) may include a wired communication module that connects to the Internet, etc., via a LAN (Local Area Network), a mobile communication module that connects to a mobile communication network via a mobile communication base station and transmits and receives data, a short-range communication module that uses a WLAN (Wireless Local Area Network) series communication method such as Wi-Fi or a WPAN (Wireless Personal Area Network) series communication method such as Bluetooth or Zigbee, a satellite communication module that uses a GNSS (Global Navigation Satellite System) such as a GPS (Global Positioning System), or a combination thereof.
[0052] Storage (230) can store various types of information. Storage (230) can store data temporarily or semi-permanently. For example, the storage (230) of the server device (100) can store an operating program (OS: Operating System) for operating the server device (100), data for hosting a website, a program for generating Braille, or data related to an application (e.g., a web application). In addition, the storage (230) can store modules in the form of computer code, as described above.
[0053] Examples of storage (230) may include a hard disk drive (HDD), a solid state drive (SSD), flash memory, read-only memory (ROM), random access memory (RAM), etc. This storage (230) may be provided as a built-in type or a detachable type.
[0054] The processor (240) controls the overall operation of the server device (100) and the user device (200). To this end, the processor (240) may perform calculations and processing of various types of information and control the operation of components of the server device (100). For example, the processor (240) may execute a program or application for providing information. The processor (240) may be implemented as a computer or a similar device according to hardware, software, or a combination thereof. In terms of hardware, the processor (240) may be implemented in the form of an electronic circuit that processes electrical signals to perform control functions, and in terms of software, it may be implemented in the form of a program that drives the hardware processor (240). Meanwhile, unless otherwise specified in the following description, the operations of the server device (100) and the user device (200) may be interpreted as being performed under the control of the processor (240). That is, when the modules implemented in the above-described information provision system are executed, the modules can be interpreted as controlling the processor (240) to perform the following operations on the server device (100) and the user device (200).
[0055] In summary, the various embodiments may be implemented through various means. For example, the various embodiments may be implemented through hardware, firmware, software, or a combination thereof.
[0056] In the case of hardware implementation, the methods according to various embodiments may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.
[0057] When implemented via firmware or software, the methods according to various embodiments may be implemented in the form of modules, procedures, or functions that perform the functions or operations described below. For example, software code may be stored in memory and executed by a processor. The memory may be located within or external to the processor and may exchange data with the processor via various known means.
[0058] Below, various embodiments are described in more detail based on the above technical concepts. The previously described concepts may be applied to the various embodiments described below. For example, operations, functions, terms, etc. not defined in the various embodiments described below may be performed and explained based on the previously described concepts.
[0059] The following description describes various embodiments based on the assumption that the server device (100) performs an operation of providing comparison information by comparing the code coverage analysis results with the test results, and according to various embodiments, the user device (200) for the manager of the service can output and provide the comparison information received from the server device (100).
[0060] FIG. 3 is a diagram illustrating an operation method of a server device (100) for providing information according to various embodiments.
[0061] According to FIG. 3, the server device (100) provides comparative information comparing the code coverage analysis result and the test result, and specifically, sets a code coverage tool that analyzes the code coverage for the service based on processing of request information obtained from multiple users on the service and a mock test tool that simulates the code coverage analysis for the service (301), obtains code coverage analysis result information that analyzes a page on the service based on the code coverage tool and test result information that tests the code coverage analysis for a page on the service based on the mock test tool (303), and provides comparative information that compares the code coverage analysis result information and the test result information (305).
[0062] According to FIG. 3, the operation of providing comparison information by the server device (100) may be performed for a service provided by the server device (100) or a service related to the server device (100), and the service may correspond to a service in which multiple users using the service can order and purchase multiple items sold in the service. The multiple items sold in the service are not limited to the type or type of the items, and may include various types or types of items registered by sellers to sell the items.
[0063] According to various embodiments, in operation 301, the server device (100) may set a code coverage tool that analyzes code coverage for the service based on processing of request information obtained from multiple users on the service, and a mock test tool that simulates the code coverage analysis for the service.
[0064] For example, code coverage analysis may refer to the act of analyzing whether the code that builds a system or software for a service has actually been executed, and a code coverage tool may refer to a software tool or programming tool that can be applied to a system or software to analyze code coverage.
[0065] For example, the code coverage tool set by the server device (100) according to operation 301 may be set to run at a regular cycle. In order to enable continuous analysis of code coverage in terms of service management, the server device (100) may set the code coverage tool to run at a regular cycle. Specifically, the code coverage tool may be set to run at a regular daily interval, such as during the early morning hours when user usage is low, avoiding times when users frequently use the service. Similarly, the mock test tool set by the server device (100) according to operation 301 may also be set to run at a regular cycle. In this case, the cycle at which the code coverage tool is run and the cycle at which the mock test tool is run may be individually set for each tool.
[0066] For example, the mock test tool set by the server device (100) according to operation 301 may correspond to a first mock test tool that mock tests code coverage analysis for codes that set methods in source codes. That is, the server device (100) may set a mock test tool that mock tests code coverage analysis for codes written to set methods among a series of source codes. Here, a method may mean a set of codes for performing a specific task within the source code, and from a similar perspective, the first mock test tool may correspond to a mock test tool that mock tests code coverage analysis for codes that set classes or threads as well as codes that set methods.
[0067] For example, the mock test tool set by the server device (100) according to operation 301 may correspond to a second mock test tool that simulates code coverage analysis for codes that input request information and output response information for the API domain. That is, the server device (100) may set a mock test tool that simulates code coverage analysis for codes written to perform a function in which request information is input or response information is output in the API domain among a series of source codes.
[0068] For example, the mock test tool set by the server device (100) according to operation 301 may correspond to a third mock test tool that simulates code coverage analysis for codes that perform information processing for a UI (User Interface). That is, the server device (100) may set a mock test tool that simulates code coverage analysis for codes written to perform information processing functions for a UI on a service among a series of source codes.
[0069] According to various embodiments, in operation 303, the server device (100) may obtain code coverage analysis result information obtained by analyzing a page on a service based on a code coverage tool and test result information obtained by testing code coverage analysis on a page on a service based on a mock test tool.
[0070] For example, the code coverage analysis result information acquired by the server device (100) according to operation 303 may include information on first lines of code for which a history of use by a user is confirmed in the source code implementing a page on the service and information on second lines of code for which a history of use by a user is not confirmed in the source code. That is, information analyzing codes within the source code implementing a page on the service based on whether a history of use by a user is confirmed may be included in the code coverage analysis result information.
[0071] At this time, identification information may be set for each code line to identify the first code lines for which the user's usage history is confirmed and the second code lines for which the user's usage history is not confirmed. The code coverage analysis result information may set first identification information for the first code lines for which the user's usage history is confirmed and second identification information for the second code lines for which the user's usage history is not confirmed, and the first identification information and the second identification information may be set to be identified based on different colors.
[0072] For example, the code coverage analysis result information acquired by the server device (100) according to operation 303 may include information on the ratio of first code lines for which a history of use by users is confirmed among the source codes implementing the pages on the service. By providing numerical information on the ratio of code lines analyzed as having a history of use by users among the source codes, the level of code coverage for pages on the service can be managed so as to be confirmed.
[0073] For example, operation 303 of obtaining information on the results of code coverage analysis that analyzed pages on a service may correspond to an operation of applying a code coverage tool to pages for each API (Application Programming Interface) domain included in the service and obtaining information including individual code coverage analysis results for individual pages on the service corresponding to each API domain.
[0074] Specifically, the server device (100) can verify each API domain included in multiple API domains for a service, execute a code coverage tool on an API domain basis, and obtain each code coverage analysis result corresponding to each API domain. That is, the server device (100) that has verified each API domain can execute a code coverage tool on one or more pages on a service corresponding to each API domain, and obtain each code coverage analysis result information corresponding to each API domain.
[0075] In addition, if an administrator wants to check the code coverage analysis result information for an API domain, and an input for selecting a specific first API domain among multiple API domains included in the service is obtained from the administrator, the server device (100) can provide first code coverage analysis result information corresponding to the first API domain in response to the input. In this case, the first code coverage analysis result information corresponding to the first API domain may correspond to information that includes a synthesis of individual code coverage analysis results for individual pages on the service corresponding to the first API domain.
[0076] For example, the test result information acquired by the server device (100) according to operation 303 may include information on the results of a simulated code coverage analysis according to a simulated test tool configured to simulate code coverage analysis. Such test result information may include information on how much of the user's usage history is confirmed for codes in the source code that implements the page on the service as a simulation result for the code coverage analysis.
[0077] According to various embodiments, in operation 305, the server device (100) may provide comparison information comparing code coverage analysis result information and test result information.
[0078] For example, the comparison information provided by the server device (100) according to operation 305 may include information comparing a first ratio of code lines analyzed as having a history of use by users according to code coverage analysis result information among source codes implementing a page on the service with a second ratio of code lines determined as having a history of use by users according to test result information among source codes. That is, by comparing information quantifying the ratio of code lines analyzed as having a history of use by users according to code coverage analysis result information among source codes with information quantifying the ratio of code lines determined as having a history of use by users according to test result information among source codes, it is possible to manage the comparison so as to check how much the code coverage ratio included in the test result by the mock test tool matches the code coverage ratio included in the actual code coverage analysis result.
[0079] For example, the comparison information provided by the server device (100) according to operation 305 may include information about some lines of code that are confirmed to be different between the code coverage analysis result by the code coverage tool and the test result by the mock test tool among the source codes implementing the pages on the service. That is, information about lines of code corresponding to the parts where the results of actually performing code coverage analysis on the pages on the service and the test result of testing the code coverage analysis with a mock test are different may be included in the comparison information provided by the server device (100) according to operation 305.
[0080] Specifically, some of the code lines that are confirmed to be different between the code coverage analysis result and the test result in the comparison information provided by the server device (100) according to operation 305 may include code lines that are analyzed as having a history of use by users according to the code coverage tool, but are determined as not having a history of use by users according to the mock test tool. Code lines that are confirmed as having a history of use by users according to the results of an actual code coverage analysis performed on a page on the service, but are not confirmed as having a history of use by users according to the mock test results, correspond to code lines that are determined to not be properly covered by the mock test tool, and therefore, such code lines may be code lines that are determined to require confirmation in order to supplement the mock test tool.
[0081] In the case where the server device (100) confirms information about some lines of code through comparison information, which are determined to have been used by the user in some code coverage tools but not in some mock test tools, the server device (100) may perform an operation of providing test results according to the updated mock test tool by more appropriately updating the mock test tool based on the information about some of the lines of code as shown in FIG. 4.
[0082] FIG. 4 is a diagram illustrating an operation method of providing mock test update result information by mock testing code coverage analysis for a page on a service based on an updated mock test tool of a server device (100).
[0083] The server device (100) can check information about some code lines that are confirmed to have different results in code coverage analysis by a code coverage tool and test results by a mock test tool among the source codes implementing pages on the service (401). At this time, some code lines confirmed according to operation 401 may include code lines that are analyzed as having a confirmed user usage history according to the code coverage tool, but are determined as not having a confirmed user usage history according to the mock test tool.
[0084] Thereafter, the server device (100) can obtain tool update information for updating the mock test tool based on information about some of the confirmed code lines (403), and can confirm the updated mock test tool based on the tool update information (405). Here, the tool update information may correspond to information including update details directly modified by the administrator to better match the actual code coverage analysis results, or may correspond to information including update details automatically modified by the server device (100) after identifying a part in the mock test tool that is deemed to require supplementation.
[0085] The server device (100) that has verified the updated mock test tool can be set to simulate code coverage analysis for pages on the service according to the updated mock test tool, and can obtain and provide mock test update result information that retests code coverage analysis for pages on the service (407).
[0086] For example, the server device (100) that provides the mock test update result information according to FIG. 4 may perform an operation of comparing the mock test update result information and the code coverage analysis result information again, obtaining comparison information by comparing the mock test update result information and the code coverage analysis result information, and providing feedback information on the updated mock test tool according to the obtained comparison information. That is, the server device (100) may generate and provide feedback on whether the mock test update result according to the updated mock test tool has been supplemented to a certain degree of accuracy compared to the actual code coverage analysis result when the mock test tool is updated.
[0087] For example, the tool update information acquired by the server device (100) providing the mock test update result information according to FIG. 4 may be information for managing updates to be performed in units of service pages. For example, if a test result by the first mock test tool shows that a code set including code lines corresponding to a method whose user usage history has been confirmed by a code coverage tool on the source code for a specific page of the service has not been used by the user, the specific page including the code set may be confirmed by the first mock test tool as a target to be supplemented through an update.
[0088] In this case, the tool update information may include an API domain corresponding to the specific page and instruction information capable of indicating the specific page, and may also include update information regarding update items set so that the first mock test tool can supplement the test results for the specific page. Based on the instruction information and update information included in the tool update information, the server device (100) may update the test setting portion of the first mock test tool related to the specific page.
[0089] For example, when updating a mock test tool to match the code coverage analysis results by a code coverage tool, if there are many test setting parts of the mock test tool that require updating, and the tool update information correspondingly becomes very large, an overload may occur during the update process due to the large tool update information, depending on the specifications of the device executing the mock test tool. Therefore, the server device (100) may set a threshold size at which the tool update information can be set so that the size of the tool update information does not exceed a certain size. In addition, if the information for updating the test setting parts determined to require updating in the mock test tool is not all included in the tool update information due to the setting of the threshold size, the server device (100) may give an update priority to a page corresponding to the test setting part that is the target of update through the tool update information, so that information for updating the test setting parts of the mock test tool related to a page with a high update priority is preferentially included in the tool update information.
[0090] As described above, tool update information can update the test settings of a mock test tool related to a specific page corresponding to a specific API domain included in the service, and for this purpose, can indicate the specific API domain and the specific page. In this case, the server device (100) can set the priority of the API domain and the priority of the page indicated through the instruction information.
[0091] The priority of the API domain set by the server device (100) can be set based on the usage rate of multiple users for the API domain on the service, and specifically, the API domain with a higher user usage rate can have a higher priority. For example, when an update of a mock test tool is required for test setting portions related to a first page included in a first API domain and a second page included in a second API domain, if the user usage rate of the first API domain is higher than the user usage rate of the second API domain, tool update information can be set so that the update of the mock test tool for the test setting portion related to the first page can be performed with priority over the test setting portion related to the second page.
[0092] In addition, the priority of the page set by the server device (100) can be set based on the usage rate of multiple users for multiple pages included in the same API domain, and specifically, a page with a higher user usage rate among multiple pages included in one API domain can have a higher priority. For example, when an update of a mock test tool is required for test setting portions related to a first page included in a first API domain and a third page included in the first API domain, if the user usage rate of the first page is higher than the user usage rate of the third page, tool update information can be set so that the update of the mock test tool for the test setting portion related to the first page can be performed with priority over the test setting portion related to the third page.
[0093] The server device (100) can determine the update priority for pages included in each API domain in the service by first applying the priority of the API domain and then applying the priority of the page, and can manage tool update information to be set according to the determined update priority. According to the examples described above, information for updating each test setting portion in the order of the test setting portion related to the first page, the test setting portion related to the third page, and the test setting portion related to the second page can be included in the tool update information.
[0094] FIG. 5 is a block diagram illustrating a process for obtaining comparative information on code coverage analysis results and test results based on a code coverage tool and a simulation test tool.
[0095] In FIG. 5, a "Canary" system is constructed to manage the application of software tools to some or designated servers among all servers for a service, and a code coverage tool ("Coverage tool") that analyzes code coverage based on the processing of request information according to the "Canary" system constructed in this way can be set by the server device (100) (501). In addition, at least some of a first mock test tool ("UT") that simulates code coverage analysis for codes that set methods in source codes, a second mock test tool ("Automation") that simulates code coverage analysis for codes that input request information and output response information for an API domain, and / or a third mock test tool ("Manual testing") that simulates code coverage analysis for codes that process information for a UI (User Interface) can be set by the server device (100) (503).
[0096] Based on a set code coverage tool, code coverage analysis result information including the result of code coverage analysis for a page on a service is obtained, and test result information including the result of performing a mock test of code coverage analysis for a page on a service based on a set mock test tool is obtained, and through this, comparison information comparing the code coverage analysis result information and the test result information can be obtained (505).
[0097] It is obvious that each piece of information can be combined in various forms in the process of performing the operation method in which the server device (100) provides comparison information comparing the code coverage analysis results and the test results according to FIGS. 3 to 5.
[0098] FIGS. 6 to 9 are diagrams illustrating examples of UI / UX for providing information according to various embodiments. For example, the examples of FIGS. 6 to 9 may be UI / UX (user interface / user experience) for a user device (200), and each of the embodiments described in the drawings below may be performed based on the operation of the server device (100) described above in FIGS. 6 to 9.
[0099] Specifically, each embodiment of UI / UX for a user device (200) described in the drawings below can be performed in a form in which a server device (100) provides information to the user device (200) based on the operations described above in FIGS. 3 to 5, and then the user device (200) outputs the information. However, each embodiment of UI / UX described in the drawings below is not limited to this form, and can be performed in various forms that can implement each embodiment of UI / UX.
[0100] FIG. 6 is a diagram illustrating an example of a user device (200) outputting code coverage analysis result information corresponding to an individual page on a service according to various embodiments.
[0101] The code coverage analysis result information output by the user device (200) in FIG. 6 may be information including the code coverage analysis result for the source code that implements a page on the service.
[0102] In FIG. 6, the code coverage analysis result information output by the user device (200) may be set to include information (601) about first code lines for which a history of use by the user is confirmed within the source code and information (603) about second code lines for which a history of use by the user is not confirmed.
[0103] At this time, first identification information for identifying information (601) on first code lines within the source code and second identification information for identifying information (603) on second code lines within the source code may be set, respectively, and the first identification information and the second identification information may be set to be identified based on different colors. That is, the information (601) on the first code lines and the information (603) on the second code lines may be distinguished within the source code by different colors.
[0104] FIG. 7 is a diagram illustrating an example of a user device (200) outputting code coverage analysis result information corresponding to an API domain according to various embodiments.
[0105] In Fig. 7, the code coverage analysis result information output by the user device (200) can be set to include code coverage analysis results for various pages corresponding to the API domain.
[0106] In FIG. 7, the code coverage analysis result information output by the user device (200) may be information identified in response to a specific API domain ("modular_search") included in the service, and pages on the service included in the API domain for which code coverage analysis was performed may be displayed (701). If there is an input for selecting one of the displayed pages, a code coverage analysis result, such as that shown in FIG. 6, may be output for the selected page.
[0107] In addition, the code coverage analysis result information output by the user device (200) in FIG. 7 may include information on a numerical value indicating the proportion of first code lines for which a history of use by users is confirmed among the source codes implementing each page for each page included in the API domain (703).
[0108] Through the code coverage analysis result information for the API domain output as in Fig. 7, the results of the code coverage analysis can be set to be managed for each unit of the API domain included in the service.
[0109] FIGS. 8 and 9 are diagrams illustrating an example of a user device (200) outputting comparison information comparing code coverage analysis result information and test result information according to various embodiments.
[0110] Figures 8 and 9 may include graph information comparing the ratio of actual code coverage according to a code coverage analysis tool and the ratio of code coverage in a mock test according to a mock test tool among various pieces of information included in the comparison information.
[0111] FIG. 8 may include graph information comparing the actual code coverage ratio according to a code coverage analysis tool with the code coverage ratio in a mock test according to a first mock test tool (“UT Coverage”) that simulates code coverage analysis for codes that set methods in source code (“active_line_cov”-83%) (800). In addition, FIG. 9 may include graph information comparing the actual code coverage ratio according to a coverage analysis tool with the code coverage ratio in a mock test according to a second mock test tool (“Automation Code Coverage”) that simulates code coverage analysis for codes that input request information and output response information for an API domain (“active_line_cov”-71%) (900).
[0112] In FIGS. 8 and 9, if the ratio of code coverage in the mock test according to the mock test tool is lower than the ratio of actual code coverage, it may be that there are some code lines that are determined to have a history of use by the user according to the code coverage tool, but are determined to have no history of use by the user according to the mock test tool. Accordingly, for some of the above-described code lines, the mock test tool can be updated according to the various embodiments described above so that it can match the results of the actual code coverage analysis.
[0113] The UI / UX for the user device (200) of FIGS. 6 to 9 and the operation of the user device (200) can be performed in connection with the operation of the server device (100) described above in FIGS. 3 to 5, and the UI / UX examples of FIGS. 6 to 9 are one example for the disclosure of the present invention, and various embodiments of the present invention are not limited to the UI / UX form of FIGS. 6 to 9 and can be performed according to all forms of UI / UX that can implement various embodiments of the present invention.
[0114] The embodiments of the present invention disclosed in this specification and drawings are merely specific examples to easily explain the technical content of the present invention and to facilitate understanding of the present invention, and are not intended to limit the scope of the present invention. In other words, it will be apparent to those skilled in the art that other modifications based on the technical concept of the present invention are possible. Furthermore, the above-described embodiments can be combined and operated as needed. For example, all embodiments of the present invention can be implemented as a system by combining parts with each other.
[0115] In addition, the method according to the system or the like according to the present invention may be implemented in the form of program commands that can be executed through various computer means and recorded on a computer-readable medium.
[0116] As such, various embodiments of the present invention can be implemented as computer-readable code on a computer-readable recording medium in certain aspects. 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 can include read-only memories (ROMs), random access memories (RAMs), compact disk-read-only memories (CD-ROMs), magnetic tapes, floppy disks, optical data storage devices, and carrier waves (such as data transmission over the Internet). A computer-readable recording medium can also be distributed across network-connected computer systems, so that the computer-readable code is stored and executed in a distributed manner. Additionally, functional programs, codes, and code segments for achieving various embodiments of the present invention can be easily interpreted by programmers skilled in the field to which the present invention is applied.
[0117] It will also be appreciated that devices and methods according to various embodiments of the present invention can be implemented in the form of hardware, software, or a combination of hardware and software. Such software may be stored in a volatile or non-volatile storage device, such as a ROM, for example, regardless of whether it is erasable or rewritable, or in a memory, such as a RAM, a memory chip, a device, or an integrated circuit, or in a storage medium that is optically or magnetically recordable and machine-readable (e.g., a computer), such as a compact disk (CD), a DVD, a magnetic disk, or a magnetic tape. It will be appreciated that methods according to various embodiments of the present invention can be implemented by a computer including a control unit and a memory, or a vehicle including such a memory or a computer, and such a memory is an example of a machine-readable storage medium suitable for storing a program or programs including commands for implementing embodiments of the present invention.
[0118] Accordingly, the present invention encompasses a program containing code for implementing the devices or methods described in the claims of this specification, and a machine-readable storage medium (e.g., a computer) storing such a program. Furthermore, such a program may be transmitted electronically via any medium, such as a communication signal transmitted via a wired or wireless connection, and the present invention appropriately encompasses equivalents thereof.
[0119] Although the present invention has been described above with reference to embodiments, the embodiments of the present invention disclosed in this specification and drawings are merely specific examples to easily explain the technical content of the present invention and assist in understanding the present invention, and are not intended to limit the scope of the present invention. Furthermore, the embodiments of the present invention described above are merely exemplary, and those skilled in the art will understand that various modifications and equivalent embodiments are possible. Therefore, the true technical protection scope of the present invention should be defined by the following claims.
Claims
1. In the method of providing information by an electronic device, A step of setting up a code coverage tool for analyzing code coverage for the service based on processing of request information obtained from multiple users on a service related to the electronic device and a mock test tool for mock testing the code coverage analysis for the service; A step of obtaining code coverage analysis result information obtained by analyzing a page on the service based on the code coverage tool and test result information obtained by testing code coverage analysis on a page on the service based on the mock test tool; and A step of providing comparison information by comparing the code coverage analysis result information and the test result information, How to provide information.
2. In paragraph 1, The above code coverage analysis result information is: Information about the first lines of code in which the user's usage history is confirmed in the source code that implements the page on the above service, and Including information about the second code lines in the above source code for which the history of use by the user is not confirmed, How to provide information.
3. In paragraph 2, The above code coverage analysis result information includes first identification information for the first code lines and second identification information for the second code lines, The first identification information and the second identification information are identified based on different colors, How to provide information.
4. In paragraph 2, The above code coverage analysis result information includes information on the ratio of the first code lines among the source code. How to provide information.
5. In paragraph 1, The step of obtaining the above code coverage analysis result information is: A step of verifying each API domain included in multiple API (Application Programming Interface) domains for the above service; and A step of obtaining each code coverage analysis result information corresponding to each API domain based on the execution of the code coverage tool for one or more pages on the service corresponding to each API domain, How to provide information.
6. In paragraph 5, The method of providing the above information is: A step of obtaining an input for selecting a first API domain among the plurality of API domains; and In response to the above input, further comprising a step of providing first code coverage analysis result information corresponding to the first API domain, The above first code coverage analysis result information includes individual code coverage analysis results for individual pages on the service corresponding to the first API domain. How to provide information.
7. In paragraph 1, The above code coverage tool runs at regular intervals. How to provide information.
8. In paragraph 1, The above mock test tool corresponds to the first mock test tool that simulates code coverage analysis for codes that set methods in source code. How to provide information.
9. In paragraph 1, The above mock test tool corresponds to a second mock test tool that mock tests code coverage analysis for codes that perform input of request information and output of response information for the API domain. How to provide information.
10. In paragraph 1, The above mock test tool corresponds to a third mock test tool that simulates code coverage analysis for codes that perform information processing for UI (User Interface). How to provide information.
11. In paragraph 1, The above comparison information is, Information including a comparison of a first ratio of code lines analyzed as having a history of use by users according to the code coverage analysis result information among the source codes implementing the pages on the service and a second ratio of code lines determined as having a history of use by users according to the test result information among the source codes. How to provide information.
12. In paragraph 1, The above comparison information includes information about some code lines that are confirmed to be different between the code coverage analysis result by the code coverage tool and the test result by the mock test tool among the source codes implementing the pages on the service. How to provide information.
13. In paragraph 12, Some of the above code lines are analyzed as having a history of use by a user according to the code coverage tool, and include code lines that are determined as not having a history of use by a user according to the mock test tool. How to provide information.
14. In paragraph 12, The method of providing the above information is: A step of obtaining tool update information for updating the mock test tool based on information about some of the above code lines; and Further comprising a step of checking the updated mock test tool based on the above tool update information. How to provide information.
15. In paragraph 14, The method of providing the above information is: Further comprising a step of providing mock test update result information for testing code coverage analysis for a page on the service based on the updated mock test tool. How to provide information.
16. In paragraph 15, The method of providing the above information is: Further comprising a step of providing feedback information for the updated mock test tool based on comparison information obtained by comparing the code coverage analysis result information and the mock test update result information. How to provide information.
17. In an electronic device that provides information, processor; and Contains one or more memories that store one or more instructions, The one or more instructions, when executed, cause the processor to: A step of setting up a code coverage tool for analyzing code coverage for the service based on processing of request information obtained from multiple users on a service related to the electronic device and a mock test tool for mock testing the code coverage analysis for the service; A step of obtaining code coverage analysis result information obtained by analyzing a page on the service based on the code coverage tool and test result information obtained by testing code coverage analysis on a page on the service based on the mock test tool; and Controlling the processor to perform a step of providing comparison information by comparing the code coverage analysis result information and the test result information. Electronic devices.
Citation Information
Patent Citations
A testing method, apparatus and server
CN106776338B
System and method for web service monitoring
KR1020130126251A
Etching method and plasma processing apparatus
KR1020210056241A
Method and system for determining mapping of test case(s) with code snippets of computer program
US20170371304A1
KR20230057711A
