Method for managing test information and electronic apparatus supporting thereof

The electronic device generates mock data to manage test information, creating independent testing environments that enhance testing efficiency and reduce service disruptions.

TWI932099BActive Publication Date: 2026-07-11COUPANG CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
TW114108943
Authority / Receiving Office
TW · TW
Patent Type
Patents
Current Assignee / Owner
Priority Date
2022-11-29
Filing Date
2023-11-07
Publication Date
2026-07-11
Estimated Expiration
2043-11-06

AI Technical Summary

Technical Problem

Existing application testing methods rely on actual service data, which can be unstable and require generating data for various scenarios, leading to inefficiencies and potential service disruptions.

Method used

An electronic device manages test information by generating mock data based on service responses and executing code to obtain baseline data, allowing for independent testing environments and minimizing service load.

Benefits of technology

This approach enables stable and efficient testing by reducing dependence on the system environment, providing independent testing and minimizing service disruptions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure IMG-2_DRAW_114108943-A0304-14-0001-1
    Figure IMG-2_DRAW_114108943-A0304-14-0001-1
  • Figure IMG-2_DRAW_114108943-A0304-14-0002-2
    Figure IMG-2_DRAW_114108943-A0304-14-0002-2
  • Figure IMG-2_DRAW_114108943-A0304-14-0003-3
    Figure IMG-2_DRAW_114108943-A0304-14-0003-3
Patent Text Reader

Abstract

This invention discloses a test information management method, which is a method for managing test information via an electronic device, comprising the following steps: sending request information based on first test case information to a service server related to a service provided based on an application; generating first simulation data information corresponding to the first test case information based on a first response information received from the service server in response to the request information; and obtaining first baseline data information based on first output information, wherein the first output information is output as a result of executing first code information based on the first test case information and the first simulation data information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to an electronic device and method for managing test information, and more specifically to an electronic device and method for performing unit tests on applications based on mock data information. Prior Technology

[0002] With the development of electronic technology, consumers of e-commerce services can use applications installed on their own devices to search for and purchase items, and each service provider manages its own application. Consumers can use the applications provided by various service providers to purchase items online, and as mentioned above, the online purchase rate is showing a gradual increasing trend.

[0003] During the development process of updating the baseline functionality of such applications or adding new features, various data used in the actual service can be used to test whether the updated or added features are properly driven. However, when using data based on the actual service, the ideal testing conditions may vary depending on the current state of the service, and during the testing process, the data used to provide the actual service may change, or the service delivery may become unstable, such as affecting the actual service traffic. Furthermore, when data is intentionally generated, it is necessary to generate data suitable for various test scenarios one by one, resulting in lower testing efficiency.

[0004] Therefore, there is a need for a technology that improves the ease of development and management for application developers and minimizes the impact of testing on services. Summary of the Invention

[0005] [The problem the invention aims to solve] According to the method of the present invention, the electronic device can manage test information.

[0006] The technical issues to be addressed by this invention are not limited to those mentioned above. Those with common knowledge in the field of this invention can clearly understand other technical issues not mentioned based on the following description. [Technical means to solve the problem]

[0007] Various embodiments can provide methods for managing test information for electronic devices and electronic devices that support such management.

[0008] The method for managing test information of an electronic device according to various embodiments described in this specification may include the following steps: sending request information based on first test case information to a service server related to a service provided based on an application; generating first mock data information corresponding to the first test case information based on a first response information received from the service server in response to the request information; and obtaining first baseline data information based on first output information, wherein the first output information is output as a result of executing first code information based on the first test case information and the first mock data information.

[0009] In an embodiment, the method for managing test information may include the following steps: obtaining the first benchmark data information based on information related to whether the first output information has been verified.

[0010] In an embodiment, the above-mentioned test information management method may further include the following steps: confirming the first simulation data information based on the first test case information; and confirming the second output information, which is output as a result of executing the second code information based on the first test case information and the first simulation data information.

[0011] In the embodiments, the second code information may include code information obtained by modifying at least a portion of the first code information.

[0012] In an embodiment, the above-mentioned test information management method may further include the following steps: confirming the comparison information obtained based on the above-mentioned first benchmark data information and the above-mentioned second output information.

[0013] In this embodiment, the comparison information may include information about the difference between the first reference data information and the second output information.

[0014] In an embodiment, the above-mentioned test information management method may further include the following steps: obtaining second benchmark data corresponding to the above-mentioned second output information based on information related to whether the above-mentioned second output information has been verified.

[0015] In this embodiment, information related to whether the second output information has been verified can be confirmed based on comparison information corresponding to the first reference data information and the second output information.

[0016] In an embodiment, the test information management method may further include the following steps: confirming the modified first test case information and the modified first output information, wherein the first test case information is obtained by modifying at least a part of the first test case information, and the first output information is output as a result of executing the first code information based on the first simulation data information; and confirming the modified first baseline data information based on a comparison of the modified first output information and the modified first output information.

[0017] In the embodiments, the first test case information may include one or more request parameters related to the above request, and the first simulation data information may include one or more response parameters corresponding to the above one or more requests.

[0018] In this embodiment, the first simulated data information may include simulated data identification information corresponding to the first test case information.

[0019] In this embodiment, the first benchmark information may include benchmark identification information corresponding to the first test case information.

[0020] In the embodiments, the first code information may include at least a portion of code information related to one or more functions provided by the application.

[0021] The electronic device described in the various embodiments herein may include: a transceiver; a memory; and a processor; the processor is configured to: send request information based on first test case information to a service server related to a service provided based on an application; generate first mock data information corresponding to the first test case information based on a first response information received from the service server in response to the request information; and obtain first baseline data information based on first output information, the first output information being output as a result of executing first code information based on the first test case information and the first mock data information. [Effects of the Invention]

[0022] According to the method of the present invention, electronic devices can minimize the load on the services being provided in order to test the developed functions.

[0023] According to the method of the present invention, electronic devices can minimize the dependence of the service being provided on the system environment in order to perform stability testing.

[0024] According to the method of the present invention, the electronic device can provide an independent testing environment according to each developed function.

[0025] According to the method of the present invention, electronic devices can provide plug-ins that support various testing methods depending on the development environment.

[0026] The effects that can be obtained by the present invention are not limited to those mentioned above. Those with common knowledge in the art to which this invention pertains can clearly understand other effects not mentioned based on the following description. Simple Explanation of the Diagram

[0027] Figure 1 is a diagram illustrating a test information management system that enables the management of test information for electronic devices according to various embodiments. Figure 2 is a diagram illustrating the configuration of electronic devices, operator equipment, and service servers in various embodiments. Figure 3 is a flowchart illustrating the operation of electronic devices acquiring reference data information in various embodiments. Figure 4 is a flowchart illustrating the operation of electronic devices acquiring comparative information in various embodiments. Figure 5 is a flowchart illustrating the process of verifying the baseline data information after changes to the electronic device in various embodiments. Figure 6 is a diagram illustrating the process of managing test information for an electronic device in one embodiment. Figure 7 is a diagram illustrating the functional configuration of an electronic device according to an embodiment. Implementation

[0028] The following embodiments combine the constituent elements and features of various embodiments into a prescribed form. Unless otherwise expressly 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, various embodiments can be constructed by combining a portion of constituent elements and features. The order of actions described in the various embodiments may be changed. A portion of a constituent element or feature of one embodiment may be included in other embodiments, or may be interchanged with corresponding constituent elements or features of other embodiments.

[0029] In the illustrations, no procedures or steps are described that would obscure the main points of the various embodiments, nor are any procedures or steps described to the extent that would be understandable to a person of common knowledge in the art.

[0030] Throughout this specification, when a part is described as "comprising" or "including" a certain constituent element, it means that, unless specifically stated to the contrary, other constituent elements are not excluded, but may also be included. Furthermore, the terms "...part," "...device," and "module" used in the 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 (especially in the following claims), unless otherwise indicated in the invention or explicitly refuted in the text, the terms "a" or "an," "one," "the," and similar related terms may be used to mean both singular and plural.

[0031] Hereinafter, preferred embodiments of various embodiments will be described in detail with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is illustrative of various embodiments and is not intended to represent the only embodiments.

[0032] Furthermore, the specific terms used in the various embodiments are provided to aid in understanding the various embodiments, and the use of such specific terms may be changed to other forms without departing from the technical concept of the various embodiments.

[0033] At this point, it should be understood that the blocks and combinations of flowcharts can be executed by computer program instructions. These computer program instructions can be loaded onto the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment. Therefore, these instructions, executed by the processor of the computer or other programmable data processing equipment, produce methods for performing the functions described in the blocks of the flowchart. To implement functions in a specific manner, these computer program instructions can be stored in computer-usable or computer-readable memory that is accessible to a computer or other programmable data processing equipment. Therefore, the instructions stored in such computer-usable or computer-readable memory can also produce manufactured items containing instruction methods that perform the functions described in the blocks of the flowchart. The computer program instructions can also be loaded onto a computer or other programmable data processing equipment. Therefore, a series of action steps are performed on the computer or other programmable data processing equipment to produce a flow executed by the computer. Thus, the instructions executed by the computer or other programmable data processing equipment can also provide steps for performing the functions described in the blocks of the flowchart.

[0034] Furthermore, each block can represent a module, segment, or portion of code comprising one or more executable instructions used to perform a specific logical function. It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may be executed out of order. For example, two blocks represented successively may actually be executed simultaneously, or occasionally in reverse order depending on their corresponding functions.

[0035] Figure 1 is a diagram illustrating a test information management system 100 that enables the management of test information for electronic devices according to various embodiments.

[0036] Referring to FIG1, the test information management system 100 of various embodiments can be implemented in various devices. For example, the test information management system 100 can be implemented in electronic device 101, operator device 102, and server 103. In other words, electronic device 101, operator device 102, and server 103 can implement the operations of various embodiments of the present invention based on the test information management system 100 implemented in each device. On the other hand, the test information management system 100 of various embodiments is not limited to that shown in FIG1 above, and can also be implemented in more electronic devices and servers.

[0037] The electronic device 101 in various embodiments may be a device that enables wireless and wired communication with one or more operator devices 102 and a server 103, and includes a storage device with a large storage capacity. For example, the electronic device 101 may be a cloud device connected to one or more operator devices 102.

[0038] The worker device 102 in various embodiments can be used by personal users such as desktop computers, tablets, and mobile terminals. In addition, other electronic devices that perform similar functions can be used as worker device 102.

[0039] The test information management system 100 in various embodiments may include various modules for performing actions. The modules included in the test information management system 100 may be computer code or one or more instructions implemented in such a way that they cause the physical device (e.g., electronic device 101) implementing the test information management system 100 (or included in the physical device) to perform specified actions. In other words, the physical device implementing the test information management system 100 may store multiple modules in memory in the form of computer code. When executing the multiple modules stored in memory, the multiple modules cause the physical device to perform specified actions corresponding to the multiple modules.

[0040] The electronic device 101, operator device 102, and server 103 of the test information management system 100 may respectively include a transceiver, memory (storage), and processor. Furthermore, each of the electronic device 101, operator device 102, and server 103 can refer to a unit that processes at least one function or action, which can be implemented by hardware or software, or by a combination of hardware and software.

[0041] On the other hand, throughout this embodiment, electronic device 101, operator device 102, and server 103 are referred to as separate devices or servers, but they can be logically separate structures, implemented through separate functions within a single device or server. For example, at least a portion of operator device 102 and server 103 may be included in or integrated with electronic device 101. However, in such cases, a series of test information management methods can be similarly implemented through data transmission and reception between electronic device 101, operator device 102, and server 103. In the case of a device included in or integrated with electronic device 101, communication with electronic device 101 can be understood as the process of data transmission and reception between internal components of the device (e.g., with the processor of electronic device 101).

[0042] For ease of explanation, the following description will be given of an embodiment in which the operator device 102 and the service server 103 exist as devices or servers independent of the electronic device 101. The following description is also applicable when at least a part of the operator device 102 and the service server 103 are included in the electronic device 101 or are integrally formed with the electronic device 101.

[0043] According to one embodiment, electronic device 101, operator device 102, and server 103 may include multiple computer systems or computer software implemented by a network server. For example, at least a portion of electronic device 101, operator device 102, and server 103 may refer to computer systems and computer software that are connected to a computer network, such as an intranet or the Internet, and can communicate with other network servers to accept job execution requests, execute the job, and provide execution results. Furthermore, at least a portion of electronic device 101, operator device 102, and server 103 can be understood as a broad concept including a series of applications that can operate on the network server and various databases built internally. For example, at least a portion of electronic device 101, operator device 102, and server 103 may be implemented using network server programs provided by various operating systems such as DOS (Disk Operating System), Windows, Linux, Unix, or MacOS.

[0044] Figure 2 is a diagram illustrating the configuration of electronic devices, operator equipment, and service servers in various embodiments.

[0045] Referring to Figure 2, the electronic device 101, the operator device 102, and the service server 103 may include an input / output unit 210, a communication unit 220, a storage unit 230, and a processor 240.

[0046] 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. User input can be implemented in various forms, including keypad input, touch input, and voice input. Examples of input modules that can receive such user input include, in addition to conventional keypads or keyboards and mice, touch sensors for sensing the user, microphones for receiving voice signals, cameras for recognizing gestures through image recognition, proximity sensors including at least one of illumination sensors or infrared sensors for sensing the user's proximity, motion sensors for recognizing user movements through accelerometers or gyroscopes, and various other input mechanisms for sensing or receiving various forms of 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 by attaching a touch panel or touch film to the display panel, or an optical touch sensor that senses touch by means of optics. In addition, the input module can also replace the device itself that senses user input by taking the form of an input interface (USB (Universal Serial Bus) port, PS / 2 (Personal System 2) port, etc.) for connecting to an external input device that receives user input. Furthermore, the output module can output various types of information. The output module may include at least one of the following: a display that outputs images, a speaker that outputs sound, a haptic device that generates vibration, and various other types of output mechanisms. Furthermore, the output module can also be implemented as a port-type output interface that connects to the aforementioned individual output mechanisms.

[0047] As an example, an output module in the form of a display can display text, still images, and video. The display may include at least one of the following: Liquid Crystal Display (LCD), Light Emitting Diode (LED), Organic Light Emitting Diode (OLED), Flat Panel Display (FPD), Transparent Display, Curved Display, Flexible Display, 3D Display, Holographic Display, Projector, and other devices capable of image output. Such a display may also be a touch display integrated with the touch sensor of an input module.

[0048] The communication unit 220 can communicate with other devices. Therefore, the electronic device 101, the operator device 102, and the service server 103 can send and receive information with other devices through the communication unit. For example, the electronic device 101, the operator device 102, and the service server 103 can use the communication unit to communicate with each other or with other devices.

[0049] Here, communication, i.e., the transmission and reception of data, can be achieved in wired or wireless form. Therefore, the communication unit may include wired communication modules that connect to the Internet via LAN (Local Area Network), mobile communication modules that connect to mobile communication networks via mobile communication base stations to transmit and receive data, short-range communication modules that utilize communication methods such as Wi-Fi (Wireless Local Area Network) or Bluetooth (Zigbee) (WPAN) communication methods, satellite communication modules that utilize GPS (Global Positioning System) or GNSS (Global Navigation Satellite System), or combinations thereof.

[0050] Storage 230 can store various types of information. Storage can store data temporarily or semi-permanently. For example, the storage of server 100 can store the operating system (OS) used to drive server 100, data used to manage the website, or data from programs and applications (e.g., website applications) used to generate Braille. Furthermore, storage can also store modules in the form of computer code, as described above.

[0051] 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 type of storage device can be provided in an internal or removable type.

[0052] The processor 240 controls the overall operation of the electronic device 101, the operator device 102, and the server 103. To this end, the processor 240 can perform various information calculations and processing, and control the operation of the constituent elements of the electronic device 101. For example, the processor 240 can execute programs and applications for managing test information. The processor 240 can be implemented as a computer or a similar device, depending on hardware, software, or a combination thereof. In terms of hardware, the 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, unless specifically mentioned in the following description, it can be interpreted that the operation of the electronic device 101, the operator device 102, and the server 103 is performed under the control of the processor 240. That is, when the module implemented in the above-mentioned test information management system 100 is executed, the module can be interpreted as the processor 240 controlling the electronic device 101, the operator device 102 and the service server 103 to perform the following actions.

[0053] In summary, various embodiments can be implemented by various methods. For example, various embodiments can be implemented by hardware, firmware, software, or a combination thereof.

[0054] In the case of implementation via hardware, the methods of various embodiments can be implemented by 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.

[0055] When implemented using firmware or software, the methods of various embodiments can be implemented in the form of modules, programs, 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 via various known mechanisms.

[0056] The following describes various embodiments in more detail based on the technical concepts 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 described based on the content described above.

[0057] The following describes various embodiments based on the premise that the electronic device 101 performs test information management operations. According to the various embodiments, the electronic device 101 can send and receive information related to test information management operations with the operator device 102 and the service server 103.

[0058] Figure 3 is a flowchart illustrating the operation of electronic devices acquiring reference data information in various embodiments.

[0059] According to various embodiments, electronic device 101 can send request information to service server 103 (S301). Request information may include information confirming one or more requests based on test case information. Test case information may include information on one or more user actions of an application providing services according to various embodiments of the present invention. Test cases may include information on user actions of functions that are subject to testing. Functions that are subject to testing may include a portion of the functionality provided by the application and can be understood to correspond to at least a portion of one or more code information included in the application. Functions that are subject to testing may be functions corresponding to first code information. For example, a function that is subject to testing may be a function that provides a detailed information page for a product, and the first code information may include one or more logical information, computational information, or algorithms that cause service server 103 to perform the action of providing a detailed information page for a product. For a function that is subject to testing, there may be one or more test cases. Each test case may change one or more parameters corresponding to the first code information to describe a specific user action. For example, the first test case and the second test case could be cases that provide different product price information based on the different membership statuses of users requesting detailed product information pages. Test case information may include one or more request messages corresponding to the function being tested. Test case information may correspond to one or more request messages that request data to be sent back to the service server 103 in accordance with the test case. For example, the electronic device 101 may request information on the user's membership status and product information from the service server 103 in accordance with the test case information. In this case, the request information may include one or more parameters and request action information. For example, the request information may include user identification information and product identification information as request parameters, and may include information on actions such as requesting confirmation of one or more response parameters based on the request parameters. Request information may include API (application programming interface) data. According to one embodiment, the request information may include one or more request parameters corresponding to the test case information and address information (e.g., URL (Uniform Resource Locator) information). Address information can correspond to specific request action information. In one embodiment, request information may include one or more API data related to the functionality of the test case. For example, test case information may include information about a user with a specific membership status requesting a detailed information page for a specific product. Since different response parameters can be requested from the service server 103 based on the same request parameters, the response parameters can be determined based on the information of the request action. In this case, the request information corresponding to the test case information may include API data containing user identification information as a parameter.Electronic device 101 can receive response information corresponding to the request information from server 103 based on the request information, such as information about the user's membership status. Furthermore, the request information corresponding to the test case information may include API data containing product identification information as a parameter. Electronic device 101 can also receive response information corresponding to the request information from server 103 based on the request information, namely, information about specific data included in the product details page, such as the product's price and the discount rate for each membership status.

[0060] According to various embodiments, electronic device 101 may generate mock data information based on response information (S302). Electronic device 101 may generate mock data information based on response information confirmed by request information. The response information may include one or more pieces of information received from service server 103 corresponding to the request information. In one embodiment, the response information may include one or more pieces of information returned by service server 103 corresponding to API data. Service server 103 may include a database and may confirm one or more pieces of data included in the response information from the database based on one or more actions and request information of the currently provided service. Service server 103 may receive request information from electronic device 101 and return response information corresponding to the request information to electronic device 101. Electronic device 101 may generate mock data information based on the response information. The mock data information may include one or more pieces of data related to the test function. The mock data information may include response information corresponding to the request information. In this embodiment, the simulated data information can be understood as a sample corresponding to the response of the service server 103. The simulated data information may include one or more response parameters included in the response information. The response parameters may include one or more specific service-related data corresponding to the request parameters and request action information, such as product price information, discount rate information, price information for each membership status, user information, user membership status information, and other data related to the provision of one or more specific services. The electronic device 101 may store the simulated data information. The simulated data information may correspond to the identification information of the test case. The simulated data information may include identification information corresponding to the identification information of the test case.

[0061] According to various embodiments, electronic device 101 can obtain first reference data information based on first output information (S303). Electronic device 101 can confirm the first output information. The output information may include data output as a result of executing application code based on test case information and simulation data information. The application code may include one or more code information (first code) related to the function that is being tested, and electronic device 101 can execute the function that is being tested from one or more functions provided by the application based on the first code. For example, corresponding to the product details page output function that is being tested, the first code may include information about specific application actions, which calculate the discount price based on user membership status information and product information, and determine the data to be output on the product details page. At this time, electronic device 101 can execute the first code based on test case information. Test case information may include information about user actions related to the function being tested. For example, when the function being tested is the output of a product details page, the test case information may include information about a user in a specific membership status requesting a detailed page for a specific product. Electronic device 101 can confirm the action result of the first code corresponding to the test case information. At this time, the specific parameter values ​​required for the action of the first code, such as product information and user information, can be obtained based on simulated data information. Electronic device 101 can execute the first code based on the test case information and can read at least a portion of the simulated data information to generate output information, thereby producing the execution result of the first code. The output information may include one or more pieces of data to be provided to the user device. The data to be provided to the user device may include components rendered for providing services, such as data used to output a page. The output information may, for example, include information in HTML (Hypertext Markup Language) format. In this case, during the testing process, the user device can be understood as operator device 102.

[0062] Electronic device 101 can obtain first benchmark information based on first output information corresponding to first test case information. The first benchmark information can be confirmed based on information related to whether the first output information has been verified. For example, if the output conforms to the function to be tested by the first output information, the first output information can be verified as a suitable output, and electronic device 101 can store the first output information as first benchmark information based on information related to whether the first output information has been verified. The first benchmark information can be benchmark information used to confirm whether the output information conforms to the specification benchmark to be developed. This output information is generated as a result of testing the application code corresponding to subsequent test case information. Therefore, electronic device 101 can test the developed application code based on subsequent test case information and can verify the test output information without sending a request to server 103. The electronic device 101 can map the first reference data onto the identification information corresponding to the first test case information, and store the first reference data information including the identification information corresponding to the first test case information.

[0063] Figure 4 is a flowchart illustrating the operation of electronic devices acquiring comparative information in various embodiments.

[0064] According to various embodiments, electronic device 101 can confirm first simulation data information based on first test case information (S401). Electronic device 101 can confirm simulation data information corresponding to the first test case based on the identification information of the first test case. Electronic device 101 can read the stored first simulation data information based on the first test case information.

[0065] According to various embodiments, electronic device 101 can confirm second output information based on second code and first simulation data information (S402). The second code can be understood as application code. The second code may include application code information corresponding to the function being tested. For example, the second code may be generated by changing a portion of the first code information or adding a portion of code information to the first code information. The second code can be understood as code obtained by updating specific action code for the function corresponding to the first code. The second code may include a newly developed version of application code. In this case, the first code may be a baseline version of application code used to verify the functionality of the newly developed application version. Electronic device 101 can execute the second code. At this time, electronic device 101 can execute the second code based on first test case information and first simulation data information. Electronic device 101 can confirm second output information including result data from executing the second code.

[0066] According to various embodiments, the electronic device 101 can obtain comparison information based on first reference data information and second output information (S403). In one embodiment, the comparison information may include information on the result of comparing the first reference data and the second output information with each other. For example, the comparison information may include information about the difference between the first reference data and the second output information. For example, in the case of first code information, it may include information on actions to display discount information for membership status on the product details page; in the case of second code information, if in addition to discount information for membership status, it further includes information on actions to display additional discount information available when changing membership status, then the comparison information may include information for outputting additional discount information.

[0067] In this embodiment, electronic device 101 may verify the second code information based on comparison information. For example, electronic device 101 may verify whether the second code information has been properly developed based on comparison information.

[0068] In this embodiment, electronic device 101 may obtain second reference data based on information related to whether the second output information has been verified. For example, if it is confirmed, based on information related to whether the second output information has been verified, that the second code information has been properly developed, electronic device 101 may use the second code information as a reference for subsequently verifying application code corresponding to the same function. In this case, electronic device 101 may replace the first reference data with the second reference data based on the second output information. Electronic device 101 may store the second reference data information corresponding to the first test case information.

[0069] Figure 5 is a flowchart illustrating the process of verifying the baseline data information after changes to the electronic device in various embodiments.

[0070] Referring to Figure 5, a series of actions performed by the electronic device 101 in the following situation can be described, in which the same function is tested, but a part of the test case is changed.

[0071] According to various embodiments, electronic device 101 can confirm modified first output information based on modified first test case information and first simulation data information (S501). Modified first test case information may include information obtained by modifying at least a portion of the first test case information. Electronic device 101 can execute first code information based on modified first test case information and first simulation data information. At this time, since the function to be tested is the same, the first simulation data information can remain unchanged, and electronic device 101 can execute first code information based on the same first simulation data information. Electronic device 101 can confirm modified first output information, which is output as a result of executing first code information based on modified first test case information. Modified first output information may include data in at least a portion that differs from the first output information. In embodiments, electronic device 101 can generate modified first output information and comparison information between the first output information and the modified first output information.

[0072] According to one embodiment, electronic device 101 can confirm the modified first reference data based on whether the modified first output information has been verified (S502). Electronic device 101 can verify the modified first output information. For example, electronic device 101 verifies the modified first output information based on comparison information, which includes information related to the difference between the first output information and the modified first output information. Based on whether the modified first output information has been verified, electronic device 101 can confirm and / or store the modified first output information corresponding to the modified first test case information as modified first reference data information. At this time, the modified first test case information can be stored in place of the first test case information, and the modified first test case information can be mapped to the identification information corresponding to the test case.

[0073] Figure 6 is a diagram illustrating the process of managing test information for an electronic device in one embodiment.

[0074] Referring to Figure 6, an example of the functional configuration of the electronic device 101 connected to the service environment 10 can be identified. The functional configuration of the electronic device 101 may include one or more software components stored in the memory of the electronic device 101 and instructing various actions of the processor.

[0075] According to one embodiment, the service environment 10 may include a service server 103. The service environment 10 may include a network formed between the electronic device 101 and the service server 103. The service environment 10 may include a network between the service server 103 and the user device receiving the service. The service environment 10 may include one or more devices associated with the service actually provided to the user. For example, the service server 103 may include a web application server that receives one or more requests from the electronic device 101 or the user device, manages the requests and sends them to a web server, and / or performs specific service actions based on the requests. The web server is a static request server that can send request information received from the user or electronic device 101 to the web application server, perform request-based service actions in the web application server, receive response information generated by the web application server, and provide the response corresponding to the request to the user or electronic device 101. A web application server can execute actions based on request information received from the web server and the application logic and code information embodying that logic within the web application server, and provide a response as the result to the web server. The web application server can connect to or include databases containing various specific data required for service provision, and process data based on requests, or return the results of necessary calculations as a response.

[0076] In one embodiment, the electronic device 101 may include a simulation data manager 610. The simulation data manager can store and manage the generated simulation data information. For example, it can assign identification information to the simulation data information and store information mapping the simulation data identification information to test case information corresponding to the simulation data identification information.

[0077] In one embodiment, the electronic device 101 may include a simulation data request unit 620. The simulation data request unit 620 may provide the service environment 10 with one or more request messages corresponding to test cases, and generate simulation data based on response information received as a response to the request messages. The simulation data request unit 620 may generate simulation data corresponding to the test cases and send the generated simulation data to a simulation data manager, or send the simulation data to application 640 when executing test cases.

[0078] In this embodiment, the test case manager 630 may store test case information. The test case information may include test case identification information, and the test case manager 630 may store information relating to the mapping between the test case identification information and the baseline data information or simulation data information corresponding to the test case identification information. The test case manager 630 may provide the test case information to the application 640 in relation to the execution of the test cases.

[0079] In this embodiment, application 640 may store application code that serves as a verification object or a verification benchmark. The application code serving as a verification object may refer to at least a portion of the application code corresponding to at least one developed or updated function. The application code serving as a verification benchmark may refer to at least a portion of the application code corresponding to a control group for verifying at least one developed or updated function. Application 640 may store all application code for each release version, or store information on at least a portion of the code specifically corresponding to the function serving as the verification object, according to the version of each function. Application 640 may store index information of the code information stored according to the version of each application or function, and version index information. Application 640 may execute the application code corresponding to a test case and may provide output information corresponding to the execution result to verification manager 650.

[0080] In one embodiment, the verification manager 650 can verify the output information based on the benchmark data information and the output information. The verification manager 650 can receive benchmark data information from the benchmark data manager 660, receive output information from the application 640, and generate comparison information comparing the benchmark data information and the output information. In one embodiment, the verification manager 650 can request benchmark data information corresponding to the output information from the benchmark data manager 660. The verification manager 650 can request benchmark data corresponding to the test case from the benchmark data manager 650 based on the identification information of the test case corresponding to the output information. The verification manager 650 can provide the output information to the benchmark data manager based on the verification result.

[0081] In this embodiment, the benchmark data manager 660 can store benchmark data information. Based on the verification results of the output information, the benchmark data manager 660 can store the output information as benchmark data, or delete existing benchmark data and overwrite new benchmark data. Based on a request from the verification manager 650, the benchmark data manager 660 can provide the verification manager 650 with benchmark data information corresponding to the test cases. The benchmark data manager 660 can store information on the correspondence between test cases and benchmark data information.

[0082] Even without requesting specific service-related data from the service environment 100 for each test, electronic device 101 can still perform tests using the simulation data manager and benchmark data manager. Electronic device 101 transmits a request to the service environment 100 only once for each test case, and generates simulation and benchmark data based on the received response data. Furthermore, it does not need to send the same request to the service environment 100 for subsequent tests. Therefore, using the test information management method of electronic device 101 disclosed in this specification, tests can be performed stably independently of the service environment 100, while utilizing data in the same format as the actual service environment. This ensures the accuracy and stability of the test results and prevents the generation of loads that could affect the service environment 100 due to testing.

[0083] Figure 7 is a diagram illustrating the functional configuration of an electronic device according to an embodiment.

[0084] Referring to Figure 7, which is an example 700 illustrating the functional configuration of the electronic device 101.

[0085] Electronic device 101 can be used as a testing tool to verify the functionality of an application. Electronic device 101 can provide the functionality of an SDK (Software Development Kit). Electronic device 101 may include one or more SDK components. SDK components are functional components, which can be understood as software components stored in memory or implemented in a processor. Electronic device 101 may include one or more SDK components, and can be modularized according to each SDK component to implement testing functions. New testing functions can be added or existing testing functions can be managed or improved according to each SDK component, thus expecting improved management efficiency and development convenience for testing functions. Electronic device 101 can utilize the modular SDK components to perform various tests (AB testing, upstream dependency testing, system time-based testing) and generate the required simulation data. For example, electronic device 101 may include an AB testing simulation (AB Mocking) component to perform AB testing and can generate simulation data for performing AB testing in an environment independent of service environment 10. Furthermore, the electronic device 101 can utilize a verification component based on benchmark data (Golden File Based Verifier, Golden File-based verifier) ​​to perform tests based on various types of data, depending on the type of file used.

[0086] 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. That is, those skilled in the art will understand that other variations based on the technical concept of the present invention can be implemented. Furthermore, the above embodiments can be combined with each other as needed. For example, a portion of all embodiments of the present invention can be combined with each other and implemented by a system.

[0087] Furthermore, the method of the present invention implemented by a system, etc., can be implemented in the form of program commands that can be executed by various computer mechanisms and recorded in a computer-readable medium.

[0088] As described above, from a particular perspective, various embodiments of the present invention can be implemented as computer-readable code in a computer-readable recording medium. A computer-readable recording medium is any data storage device capable of storing data readable 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.). The computer-readable recording medium can also be distributed across a networked computer system, thus storing and executing computer-readable code in a distributed manner. Furthermore, the functional programs, code, and segments used to achieve the various embodiments of the present invention can be readily interpreted by a skilled programmer applying the art of the present invention.

[0089] Furthermore, it is understood that the apparatuses and methods of various embodiments of the present invention can be implemented in the form of hardware, software, or a combination of hardware and software. Such software, for example, regardless of whether it can be deleted or re-recorded, can be stored in volatile or non-volatile storage devices such as ROM, or in memory such as RAM, memory chips, devices, or integrated circuits, or in storage media such as compact disks (CDs), DVDs (Digital Versatile Discs), magnetic disks, or magnetic tapes that can be optically or magnetically recorded and read by a machine (e.g., a computer). 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 described above. Such memory is an example of a program containing commands for implementing embodiments of the present invention or a storage medium readable by a machine suitable for storing programs.

[0090] Therefore, this invention includes a program of code for implementing the apparatus or method described in the claims of this specification, and a machine-readable storage medium for storing such a program (computer, etc.). Furthermore, such a program can be electronically transmitted via any medium that transmits communication signals, such as using a wired or wireless connection, and this invention appropriately includes equivalents thereof.

[0091] 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 embodiments of the present invention described above 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 claims.

[0092] 10: Service Environment 100: Test Information Management System 101: Electronic Devices 102: Worker Equipment 103: Server 210: Input / Output Section 220: Communications Department 230: Storage 240: Processor 610: Simulated Data Manager 620: Simulated Data Request Unit 630: Test Case Manager 640: Application 650: Verification Manager 660: Baseline Data Manager 700: Example S301: Action S302: Action S303: Action S401: Action S402: Action S403: Action S501: Action S502: Action

Claims

1. A test information management method, which manages test information via an electronic device, comprising the following steps: From a plurality of test cases corresponding to a plurality of membership statuses, identifying first test case information related to a detailed information page of a provided product, wherein at least a portion of the detailed information page is determined based on the plurality of membership statuses that a user may possess; and identifying first output information output by executing first code information based on the first test case information and first simulation data corresponding to the first test case information, wherein... The first simulation data mentioned above is generated based on the response information received from the service server in response to the request information corresponding to the first test case information mentioned above; by verifying the first output information mentioned above, the first benchmark data information corresponding to the first test case information is obtained; the second output information is confirmed, which is output as a result of executing the second code information based on the first test case information and the first simulation data mentioned above; based on the comparison between the first benchmark data information and the second output information mentioned above, it is determined whether the second output information meets the specification benchmarks related to the detailed information page of the membership status corresponding to the first test case information mentioned above.

2. The test information management method as described in Request 1 further includes confirming the baseline data information corresponding to each of the plurality of test cases mentioned above.

3. The test information management method of request item 1, wherein the confirmation of the first output information includes: sending the request information, which includes user identification information and product identification information as request parameters, based on the first test case information related to the detailed information page of the provided product, to the service server related to the product sales service provided through the application; generating first simulation data information corresponding to the first test case information based on the first response information received from the service server in response to the request information, the first simulation data information including user membership status information, product price information, and price information of each membership status as response parameters; and obtaining first baseline data information based on the first output information related to the detailed information page, the detailed information page including the discounted price of the product calculated based on the user membership status information, the product price information, and the price information of each membership status, the first output information being output by executing first code information based on the first test case information and the first simulation data information.

4. The test information management method as described in Request 1, wherein the second code information mentioned above includes code information obtained by changing at least a portion of the first code information mentioned above.

5. As in request item 1, the test information management method, wherein, Determining whether the second output information conforms to the above specifications further includes: determining whether the second output information conforms to the above specifications based on comparison information obtained from the first reference data information and the second output information.

6. The test information management method as described in Request 5, wherein the comparison information includes information about the differences between the first benchmark data information and the second output information.

7. The test information management method as described in Request 1 further includes the following steps: obtaining second benchmark information corresponding to the second output information described above; and replacing the first benchmark information corresponding to the first test case information described above with the second benchmark information described above.

8. The test information management method of request item 1 further includes the following steps: confirming the modified first test case information and the modified first output information, wherein the first test case information is obtained by modifying at least a part of the first test case information, and the first output information is output as a result of executing the first code information based on the first simulation data information; confirming the modified first benchmark data information based on a comparison of the modified first output information and the first output information; and replacing the first benchmark data information corresponding to the first test case information with the modified first benchmark data information.

9. As in request item 1, the test information management method, wherein, The first test case information mentioned above includes at least one request parameter related to the request, and the first simulation data information mentioned above includes at least one response parameter corresponding to the at least one request parameter.

10. The test information management method as described in Request 1, wherein the aforementioned first simulation data information includes simulation data identification information corresponding to the aforementioned first test case information.

11. The test information management method as described in Request 1, wherein the aforementioned first benchmark information includes benchmark identification information corresponding to the aforementioned first test case information.

12. The test information management method as described in Request 1, wherein the first code information includes at least a portion of code information related to one or more functions of the detailed information page of the aforementioned product that is related to the product sales service provided by the application.

13. An electronic device comprising: transceiver; Storage; and processor; The processor is configured to: identify, from a plurality of test cases corresponding to a plurality of membership statuses, a first test case information related to a product detail page, wherein at least a portion of the detail page is determined based on the plurality of membership statuses that a user may have; identify first output information output by executing first code information based on the first test case information and first simulation data corresponding to the first test case information, wherein the first simulation data is generated based on response information received from a server in response to request information corresponding to the first test case information; obtain first baseline data information corresponding to the first test case information by verifying the first output information; identify second output information, which is output as a result of executing second code information based on the first test case information and the first simulation data; Based on the comparison between the first benchmark information and the second output information, it is determined whether the second output information conforms to the specifications and benchmarks related to the detailed information page of the membership status corresponding to the first test case information.

14. A non-transitory computer-readable recording medium recording a program for performing a method for request item 1 on a computer.