KR20240038364A - Electronic apparatus for managing information of ab test code and method therefor - Google Patents

Abstract

An electronic device and method for managing AB test code information are disclosed. The AB test code information management method according to an embodiment includes obtaining history information of a pull request (PR) for the AB test code based on a reference point, and obtaining history information for the AB test code based on the history information of the PR. It includes obtaining status information, checking whether notification conditions related to the AB test code are met based on the status information, and transmitting notification information related to the AB test code when the notification conditions are met.

Description

Electronic device and method for managing AB test code information {ELECTRONIC APPARATUS FOR MANAGING INFORMATION OF AB TEST CODE AND METHOD THEREFOR}

This disclosure relates to an electronic device and method for tracking and managing information related to AB test code.

AB testing is a method of comparing two pieces of content between a control group and an experimental group in a digital environment to identify content that better demonstrates the intended effect. It is widely used in product design, development, marketing, etc. by applying proven options. there is. For example, AB testing can be used during the development process to determine whether to update the code to add specific features or maintain the existing code.

However, if it is decided to maintain only the existing functions as a result of AB testing, the updated code must be cleaned up again. During this process, the AB test manager must find function definitions, wiki pages, related personnel, pull requests (PRs), etc. related to the updated code, and through this, clarify the scope of the code to be organized. Although this work is not directly related to the implementation of the target function, it takes a considerable amount of time and is one of the factors that hinders rapid and efficient development.

In this regard, prior documents such as US2015-0012852A1 and US2015-0058077A1 may be referred to.

The present disclosure is proposed to solve the above-mentioned problems, and its purpose is to provide an electronic device and method that can automatically search, track, and manage information about code that needs to be organized in the AB testing process.

The technical problems to be achieved by the present disclosure are not limited to the technical problems described above, and other technical problems can be inferred from the following embodiments.

An AB test code information management method according to an embodiment disclosed includes the steps of obtaining history information of a pull request (PR) for an AB test code based on a reference point in time; Obtaining status information about the AB test code based on the history information of the PR; checking whether notification conditions related to the AB test code are met based on the status information; and transmitting notification information related to the AB test code when the notification condition is met.

According to one embodiment, the history information of the PR may include an AB test key capable of identifying the AB test code and checklist information set in relation to the AB test. In this regard, the checklist information may include identification information that can confirm whether the PR is a PR requesting a code cleanup task for the AB test code.

According to one embodiment, the step of acquiring the history information of the PR may be characterized by acquiring the history information of the PR based on content entered by the developer in the PR template defined separately from the PR code. .

According to one embodiment, the step of obtaining the history information of the PR may be characterized by extracting the history information of the PR based on a value assigned to a specific variable in the code of the PR written by the developer.

According to one embodiment, the state information includes first state information corresponding to a state before execution of the AB test code, second state information corresponding to a state during execution of the AB test code, and completion of execution of the AB test code. Third state information corresponding to the state and fourth state information corresponding to the state in which code cleanup for the AB test code has been performed may optionally be included.

According to one embodiment, the step of obtaining the status information may be characterized by acquiring status information about the AB test code corresponding to the AB test key included in the history information of the PR.

According to one embodiment, the step of checking whether the notification condition is met includes checking whether an unorganized code that is not the target of code cleaning work exists among AB test codes corresponding to each PR; And when the unresolved code exists, it may include checking whether the notification condition is satisfied based on status information about the unresolved code. In this regard, the step of confirming whether the notification condition is met based on the status information about the unresolved code includes, if the unorganized code exists, checking whether the unorganized code is in an execution complete state; When the unorganized code is in an execution-finished state, checking whether a set period of time has elapsed from the point of execution of the unorganized code; And when the set period has elapsed from the end of execution of the unorganized code, it may include determining that the notification condition is satisfied.

According to one embodiment, the state information may optionally additionally include fifth state information corresponding to a state in which execution of the AB test code is completed and code cleanup is possible, and checking whether the notification condition is met. may be characterized in that, when the status information corresponds to the fifth status information, it is determined that the notification condition is satisfied.

According to one embodiment, the step of transmitting the notification information may be characterized by sending an email with a tracking result file for the AB test code attached to the set AB test-related account as the recipient. In this regard, the step of transmitting the notification information may be characterized by inserting and transmitting a link to a website that provides tracking results for the AB test code in the body of the email.

According to one embodiment, the AB test code information management method refers to a database in which at least part of the history information of the PR and status information about the AB test code is stored, and records at least part of the tracking results of the AB test code. A step of generating a report or dashboard may be further included.

An electronic device for managing information about an AB test code according to an embodiment of the disclosure includes a transceiver, a memory for storing instructions, and a processor, and the processor is connected to the transceiver and the memory, and is based on a reference point. Obtain history information of the Pull Request (PR) for the AB test code, obtain status information for the AB test code based on the history information of the PR, and perform the AB test based on the status information. It is checked whether the notification conditions related to the code are met, and if the notification conditions are met, notification information related to the AB test code is transmitted.

Specific details of other embodiments are included in the detailed description and drawings.

According to the present disclosure, by tracking the status of AB test code and automatically notifying when code cleanup is necessary, developers and other related personnel can easily identify the scope of code to be cleaned up and efficiently maintain or update the AB test code. there is.

The effect of the invention is not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description of the claims.

1 is a schematic configuration diagram showing an environment in which an electronic device operates, according to an embodiment.
Figure 2 is a flowchart illustrating a method for managing AB test code information according to an embodiment.
3 to 5 are flowcharts to explain an AB test code information management method according to an additional embodiment.
Figure 6 is an exemplary diagram illustrating a process for managing information about AB test code according to an embodiment.
Figures 7a and 7b are example diagrams to explain history information of pull requests for AB test code.
Figure 8 is an example diagram for explaining notification information related to AB test code.
FIG. 9 is a block diagram illustrating an electronic device that manages information about AB test codes, according to an embodiment.

The terms used in the embodiments are general terms that are currently widely used as much as possible while considering the functions in the present disclosure, but this may vary depending on the intention or precedent of a person working in the art, the emergence of new technology, etc. In addition, in certain cases, there are terms arbitrarily selected by the applicant, and in this case, the meaning will be described in detail in the relevant description. Therefore, the terms used in this disclosure should be defined based on the meaning of the term and the overall content of this disclosure, rather than simply the name of the term.

When it is said that a part "includes" a certain element throughout the specification, this means that, unless specifically stated to the contrary, it does not exclude other elements but may further include other elements. In addition, terms such as "...unit" and "...module" used in the specification refer to a unit that processes at least one function or operation, which is implemented as hardware or software, or as a combination of hardware and software. It may be possible, and unlike the example shown, specific operations may not be clearly distinguished.

The expression “at least one of a, b, and c” used throughout the specification means ‘a alone’, ‘b alone’, ‘c alone’, ‘a and b’, ‘a and c’, ‘b and c ', or 'all of a, b, and c'.

The “terminal” or “user terminal” mentioned below may be implemented as a computer or portable terminal that can connect to a server or other terminal through a network. Here, the computer includes, for example, a laptop, desktop, laptop, etc. equipped with a web browser, and the portable terminal is, for example, a wireless communication device that guarantees portability and mobility. , all types of communication-based terminals such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), and LTE (Long Term Evolution), smartphones, tablet PCs, etc. It may include a handheld-based wireless communication device.

In the following description, “transmission,” “communication,” “transmission,” “reception,” “transmission,” “transmission,” “reception,” or similar terms of a signal, message, or information refer to the direct transmission of information, message, or information from one component to another. It includes not only what is done, but also what is transmitted through other components.

In particular, “transmitting” or “transmitting” a signal, message or information as a component indicates the final destination of the signal, message or information and does not mean the direct destination. The same applies to “receiving” signals, messages or information. Additionally, in the present disclosure, “related” to two or more data or information means that if one data (or information) is acquired, at least part of other data (or information) can be obtained based on it.

Additionally, terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The above terms may be used for the purpose of distinguishing one component from another component.

For example, a first component may be referred to as a second component, and similarly, the second component may also be referred to as the first component without departing from the scope of the present disclosure.

Below, with reference to the attached drawings, embodiments of the present disclosure will be described in detail so that those skilled in the art can easily practice them. However, the present disclosure may be implemented in many different forms and is not limited to the embodiments described herein.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.

In describing the embodiments, description of technical content that is well known in the technical field to which the present invention belongs and that is not directly related to the present invention will be omitted. This is to convey the gist of the present invention more clearly without obscuring it by omitting unnecessary explanation.

For the same reason, some components are exaggerated, omitted, or schematically shown in the accompanying drawings. Additionally, the size of each component does not entirely reflect its actual size. In each drawing, identical or corresponding components are assigned the same reference numbers.

The advantages and features of the present invention and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various different forms. The present embodiments are merely provided to ensure that the disclosure of the present invention is complete and to provide common knowledge in the technical field to which the present invention pertains. It is provided to fully inform those who have the scope of the invention, and the present invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

It will be understood that each block of the processing flow diagrams and combinations of the flow diagram diagrams may be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory It is also possible to produce manufactured items containing instruction means that perform the functions described in the flowchart block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially at the same time, or it is possible for the blocks to be performed in reverse order depending on the corresponding function.

FIG. 1 is a schematic configuration diagram 100 illustrating an environment in which an electronic device operates according to an embodiment. Referring to FIG. 1, the electronic device 110, the history information storage 120, the AB test management server 130, and the database 140 communicate with each other or with other external devices through the connected network 150. You can. The network 150 includes a local area network (LAN), a wide area network (WAN), a value added network (VAN), a mobile radio communication network, a satellite communication network, and their respective networks. It is a comprehensive data communication network that includes a combination and allows each component shown in Figure 1 to communicate smoothly with each other, and may include wired Internet, wireless Internet, and mobile wireless communication network. Wireless communications include, for example, wireless LAN (Wi-Fi), Bluetooth, Bluetooth low energy, ZigBee, WFD (Wi-Fi Direct), UWB (ultra wideband), and infrared communication (IrDA, infrared Data Association). ), NFC (Near Field Communication), etc., but are not limited thereto.

The electronic device 110 collects information about the AB test code, verifies at least some of the information that satisfies specific conditions, generates notification information related to the confirmed information, and then transmits the notification information to an external entity. do. In this process, the electronic device 110 may communicate with the history information storage 120, the AB test management server 130, or the database 140 to collect information about the AB test code. In addition, the electronic device 110 may be a server that collects information about the AB test code, checks whether certain conditions are met, and performs operations related to generating and transmitting notification information, but depending on the embodiment, It may include a plurality of servers, and may be configured so that one or more servers and an external cloud server can communicate electronically.

The history information repository 120 contains detailed information (in the present disclosure, at the time each request is reflected) related to a series of requests (e.g., Pull Request, PR, etc.) for reflecting changes to the AB test code. Since changes in the AB test code occur, each request causes changes in the AB test code over time, so detailed information related to the request (referred to as 'history information') is stored. The history information storage 120 may be a medium that has a storage space physically separate from the electronic device 110, but depending on the embodiment, it may be a conceptual name for a storage space included in the electronic device 110.

The AB test management server 130 stores status information that can identify the status of the AB test code. In the present disclosure, the AB test management server 130 can automatically check status information and AB test key values input by relevant personnel (eg, project managers) of the AB test code. In addition, in the present disclosure, the AB test management server 130 provides the electronic device 110 with an API (Application Programming Interface) that can check status information about the AB test code, or provides the status information itself about the AB test code. It may be a device provided to the electronic device 110. In other words, the AB test management server 130 is an entity that provides a service that outputs status information about the AB test code in a form that can be confirmed by the electronic device 110, so depending on the embodiment, it may consist of one server or multiple servers. It may also include a set of servers. Additionally, the electronic device 110 may obtain status information for each AB test code for each corresponding AB test key through the API provided by the AB test management server 130.

The database 140 is physically or electronically separated from the history information storage 120 and the AB test management server 130, and stores at least some of the information collected from the history information storage 120 or the AB test management server 130. Refers to the space where is stored. However, the form (format) of information stored in the database 140 follows the schema set for the database 140, and the database 140 stores the history information storage 120 at the request of the electronic device 110. Information collected from the AB test management server 130 may be stored, or pre-stored information may be provided to the electronic device 110.

In relation to the above, it will be described in more detail through the drawings below. The methods shown in FIGS. 2 to 5 may be performed, for example, by the electronic device 110 described above.

Figure 2 is a flowchart illustrating a method for managing AB test code information according to an embodiment.

In step S210, the electronic device 110 obtains pull request (PR) history information for the AB test code based on the reference point.

As described above with reference to FIG. 1, in the present disclosure, 'history information' refers to detailed information related to a series of requests for reflecting changes in AB test code. In addition, in this disclosure, 'PR' includes a pull request requesting to merge a branch reflecting control commands for the AB test code into the main branch where the existing AB test code is executed.

According to one embodiment, the history information of the PR may include 1) an AB test key that can identify the AB test code, and 2) checklist information set in relation to the AB test. Specifically, the checklist information set in relation to AB testing may include identification information that can confirm whether the PR is a PR requesting a code cleanup operation for the AB test code.

According to one embodiment, the process of the electronic device 110 acquiring PR history information may be performed by collecting PR history information input in advance or extracting PR history information from other information. For example, the electronic device 110 may obtain PR history information based on content input by the developer into a PR template defined separately from the PR code. As another example, the electronic device 110 may extract PR history information based on the value assigned to a specific variable in the PR code written by the developer.

According to one embodiment, the electronic device 110 may periodically acquire PR history information at a set period from a reference point in time. For example, the electronic device 110 may transmit a request to collect PR history information to the history information storage 120 at a set period.

In step S220, the electronic device 110 obtains status information about the AB test code based on the history information of the PR. In the present disclosure, 'status information' includes information that can identify the working status of the AB test code, and the status information can be obtained from the AB test management server 130. However, the AB test management server 130 is one of the sources for obtaining status information, and depending on the embodiment, the electronic device 110 may obtain status information from another entity.

According to one embodiment, status information about the AB test code may correspond to one of the following plural options. The standard for changing the value from the second state information to the third state information can be set in various ways, but a typical example is when the preset AB test period expires or the number of users set as the goal of the AB test is achieved. It can be set to be.

1) First state information corresponding to the state before execution of the AB test code

2)Second state information corresponding to the running state of the AB test code

3) Third state information corresponding to the execution end state of the AB test code

4) Fourth state information corresponding to the state in which code cleanup has been performed for the AB test code

Additionally, according to another embodiment, the state information for the AB test code may optionally additionally include fifth state information corresponding to a state in which the AB test code has finished execution and the code can be cleaned up, and the above-mentioned first to second state information may optionally be included. It may correspond to one of 5 status information.

Meanwhile, according to one embodiment, the electronic device 110 may obtain status information about the AB test code corresponding to the AB test key included in the history information of the PR in step S220.

Meanwhile, according to one embodiment, even for an AB test code for which status information was previously obtained, the electronic device 110 determines that the notification condition related to the AB test code is not met as a result of checking the status information through step S230, which will be described later. If it is determined that this is not the case, status information about the AB test code can be newly obtained at each set cycle. That is, the electronic device 110 can periodically check whether there are PRs that have not been sorted out, and thus automatically search for whether there are PRs that need to be sorted out among previously submitted PRs in addition to new PRs.

In step S230, the electronic device 110 determines whether notification conditions related to the AB test code are met based on status information about the AB test code.

According to one embodiment, following step S220, the electronic device 110 may check whether the above-described notification conditions are met when it is necessary to proceed with code organizing work. Specifically, the electronic device 110 checks whether an unresolved code that is not subject to code cleanup exists among the AB test codes corresponding to each PR, and if an unresolved code exists, based on the status information about the unorganized code. You can check whether the notification conditions are met. This will be described later with reference to FIG. 3 below.

According to another embodiment, following step S220, the electronic device 110 may check whether the notification condition is met based on whether the AB test code is in a cleanable state. This will be described later with reference to FIG. 4 below.

In step S240, the electronic device 110 transmits notification information related to the AB test code when the notification condition related to the AB test code is met.

According to one embodiment, before transmitting notification information, the electronic device 110 refers to the history information of the PR collected from the history information storage 120 or status information collected from the AB test management server 120. Information on the account to which notification information is to be transmitted can be obtained by referring to the database 140 where PR history information or status information is stored.

According to one embodiment, the electronic device 110 may transmit an email with a tracking result file for the AB test code attached to a set AB test-related account as a recipient as a method of transmitting notification information. In addition, the electronic device 110 may insert and transmit a link to a website that provides tracking results for AB test codes in the body of the email.

3 to 5 are flowcharts to explain an AB test code information management method according to an additional embodiment. Specifically, Figures 3 and 4 relate to an embodiment specifying notification conditions related to the AB test code, and Figure 5 relates to an embodiment in which additional information related to the AB test code is generated in addition to notification information.

First, referring to FIG. 3, the electronic device 110 acquires PR history information for the AB test code based on a reference point (step S310), and obtains status information for the AB test code based on the PR history information. It can be obtained (step S320). Next, the electronic device 110 may check whether there is an unorganized code that is not subject to code cleaning work among the AB test codes corresponding to each PR (step S330). Subsequently, if there is an unorganized code, the electronic device 110 checks whether the unorganized code is in a finished execution state (step S340), and if the unorganized code is in a finished execution state, whether a set period of time has elapsed from the end of execution of the unorganized code. By confirming (step S350), if a set period of time has elapsed from the end of execution of the unresolved code, it is determined that the notification conditions related to the AB test code are met, and notification information related to the AB test code can be transmitted (step S360).

Meanwhile, referring to FIG. 4, the electronic device 110 acquires PR history information for the AB test code based on a reference point (step S410), and obtains status information for the AB test code based on the PR history information. It can be obtained (step S420). Next, the electronic device 110 checks whether the status information about the AB test code corresponds to the fifth state information (state information corresponding to a state in which the AB test code has finished execution and the code can be cleaned up) (step S430), and confirms. If the status information about the resulting AB test code corresponds to the fifth status information, it is determined that the notification conditions related to the AB test code are satisfied, and notification information related to the AB test code can be transmitted (step S440). In this case, notifications can be sent immediately about AB test code that can be cleaned up right away without having to wait for a certain period of time to pass, helping relevant personnel perform code cleaning work more quickly.

Meanwhile, referring to FIG. 5, the electronic device 110 acquires PR history information for the AB test code based on a reference point (step S510), and obtains status information for the AB test code based on the PR history information. It can be obtained (step S520). Subsequently, the electronic device 110 determines whether the notification condition related to the AB test code is satisfied based on the status information about the AB test code (step S530), and if the notification condition related to the AB test code is satisfied, the AB test code Notification information related to can be transmitted (step S540). Next, the electronic device 110 refers to the database 140 in which at least part of the history information of the PR and the status information about the AB test code is stored, and creates a report or dashboard ( dashboard) can be created (step S550).

According to one embodiment, the report or dashboard generated by the electronic device 110 may display AB test codes that require code cleanup work and AB test codes that do not require code cleanup work.

According to one embodiment, the report or dashboard generated by the electronic device 110 is stored in the database 140, and a request from the electronic device 110 or an external entity (e.g., an individual terminal used by relevant personnel) is stored in the database 140. If there is one, the original or a copy may be provided to the terminal that transmitted the request.

In the flow chart above, the method is divided into a plurality of steps, but at least some of the steps are performed in a different order, combined with other steps, omitted, divided into detailed steps, or not shown. One or more steps may be added and performed.

Figure 6 is an exemplary diagram illustrating a process for managing information about AB test code according to an embodiment. In Figure 6, each step of the process is shown as a shape such as a square, a square with rounded corners, a cylinder, and a diamond. The cylindrical shape represents the storage medium, the rounded square represents the start/end of execution, and the square represents each step of the process. It was used to indicate processing.

Figure 6 shows, as an example, a tracking process for AB test code performed every week. 'AB Code Tracking' in the center refers to the AB test code tracking process performed internally in the electronic device 110, and 'Code Repos' at the top refers to the AB test code tracking process performed internally by the electronic device 110 and the history information storage 120. The test code tracking process, 'XPC' at the bottom, shows the AB test code tracking process performed by communication between the electronic device 110 and the AB test management server 130 (in the 'AB Code Tracking' area in the center). An AB Store corresponding to the database 140 is shown, but this does not limit the database 140 to one component included in the electronic device 110 and is for convenience of explanation).

According to one embodiment, before acquiring status information about the AB test code, the electronic device 110 may select the AB test code for which to obtain status information. To this end, the electronic device 110 may obtain PR history information for the AB test code from the history information storage 120 (All Merged PRs).

According to one embodiment, the electronic device 110 refers to the AB test key included in the history information of the acquired PR and communicates with the AB test management server 130 to determine the status of the AB test code corresponding to the AB test key. Information can be obtained (Reading Code Status).

In relation to the above embodiment, a form of PR history information acquired by the electronic device 110 will be described with reference to FIGS. 7A and 7B. First, Figure 7a illustrates a template of PR history information for AB test code.

According to one embodiment, the AB test key included in the history information of the PR consists of an array of letters, numbers, or a mixture of letters and numbers. It may be composed of a single array, but depending on the embodiment, it may be composed of a plurality of arrays. It may also be included. For example, if the AB test key includes a plurality of arrangements (AB-key-0 and AB-key-1), the electronic device 110 will state for both AB test keys and the corresponding AB test code. Information can be obtained. Through this, the electronic device 110 can prevent the AB test key from being arranged in an overly complicated arrangement and reduce the computational load in the process of checking the mapping between the AB test key and the AB test code (AB-key-0 By first using some AB test keys represented by, AB test codes that do not map to these are excluded from the selection target in advance, and the mapping to AB-key-1 is checked for the remaining AB test codes, thereby reducing the computational load. alleviate).

According to one embodiment, the PR's history information may include label information that can identify the type of work requested by the PR for the AB test code. Specifically, the label information options include the first label option (New Feature), which indicates that the PR is requesting work to add a new feature to the AB test code, or the PR is a work to fix bugs in the AB test code. A second label option (BugFix) indicating that the PR is requesting a code cleanup operation for the AB test code may be included, or a third label option (CodeCleanup) indicating that the PR is requesting a code cleanup operation for the AB test code may be included.

Meanwhile, according to one embodiment, the history information of the PR may separately include identification information that can confirm that the PR is requesting code cleanup work for the AB test code. For example, the identification information may be in the form of a checklist, and depending on whether it is checked, it may indicate whether the PR is requesting code cleanup work for the AB test code (Is Clean AB Code). This feature can be especially useful when label information preset by the developer does not exist in the PR history information.

FIG. 7B shows a sample reflecting the embodiments related to FIG. 7A. According to the history information of the PR shown in Figure 7b, the history information corresponds to an AB test code with an AB test key of '18722', and the 'Is Clean AB Code' item on the checklist is checked, so the PR You can recognize that this is for code cleanup work on AB test code.

Referring again to FIG. 6, the tracking process after the electronic device 110 obtains status information for the AB test code will be described.

According to one embodiment, the electronic device 110 terminates the tracking process for the AB test code when it is unnecessary to clean up the AB test code (i.e., if there is no unorganized code), and the electronic device 110 terminates the tracking process for the AB test code. If there is unorganized code, it is checked whether a set period (e.g., 2 weeks) has passed since the execution of the unorganized code ended, and if the period has elapsed, code cleaning work is still done in the preset AB test-related account. An email can be sent notifying the existence of AB test code that has not been performed. If the corresponding unresolved code is still executing, or if a set period of time has not yet elapsed from the point at which execution ends, the electronic device 110 may similarly end the tracking process for the corresponding AB test code.

According to one embodiment, the electronic device 110 may generate a report or dashboard containing at least some of the tracking results of the AB test code after sending notification information (e.g., email) related to the AB test code. . Furthermore, the electronic device 110 may post the generated report or dashboard on its own hosting page, transmit it to the AB test management server 130, or store it in the database 140.

Meanwhile, Figure 8 is an example diagram for explaining notification information related to AB test code, and specifically shows a sample of an email, which is a form of notification information, for convenience of explanation.

According to one embodiment, a tracking result file 810 for the corresponding AB test code may be attached to the email transmitted by the electronic device 110. There is no limitation on the format of the attached file, but the electronic device 110 can automatically select and generate a recommended format of the tracking result file depending on the type of data (image, text, etc.) included in the tracking result file. Additionally, if the size of the generated tracking result file 810 exceeds the standard file attachment capacity standard for mail, the electronic device 110 may query the user of the electronic device 110 whether to attach a large file.

According to one embodiment, the electronic device 110 may transmit an email by inserting an email address 820 to receive an inquiry in the body of the email or inserting a link 830 to a website that provides tracking results for AB test code. there is. In this regard, the electronic device 110 inserts an email address ( fff@AAA.com ) previously set in the name of the email sending account (e.g., aaa@AAA.net ) into the body of the email, but the separately set email address is If it does not exist, the sending account for the mail can be inserted into the body of the mail and sent. In addition, the electronic device 110 may include a link ( https://mobile.AAA.net/dist-dev/abcodetracking ) to a website previously set in the name of the mail transmission account (e.g., aaa@AAA.net ) in the mail. Insert it into the body of the email, but if a link to a separately set website does not exist, a link to the Github page registered under the name of the account sending the email can also be inserted into the body of the email.

According to one embodiment, the electronic device 110 may insert and transmit a table 840 summarizing tracking results for AB test codes in the body of the email. In this regard, the format and content of the table 840 can be freely configured, but illustratively the components of the table 840 include a name (tf_name) by which the AB test code can be identified and a summary that exists for each AB test code. The number of PRs being worked on may be included.

FIG. 9 is a block diagram illustrating an electronic device that manages information about AB test codes, according to an embodiment.

According to one embodiment, the electronic device 110 may include a transceiver 111, a processor 113, and a memory 115. In one embodiment, the electronic device 110 may be connected to the history information storage 120, the AB test management server 130, or the database 140 through the transceiver 111 and exchange data.

The processor 113 may perform at least one method described above through FIGS. 1 to 8. The memory 115 may store information for performing at least one method described above with reference to FIGS. 1 to 8 . Memory 115 may be volatile memory or non-volatile memory.

The processor 113 can control the electronic device 110 to execute programs and provide information. The code of the program executed by the processor 113 may be stored in the memory 115.

The processor 113 is connected to the transceiver 111 and the memory 115, obtains history information of the PR for the AB test code based on a reference point, and obtains status information for the AB test code based on the history information of the PR. Obtain and check whether notification conditions related to the AB test code are met based on the status information, and if the notification conditions are met, notification information related to the AB test code can be transmitted.

The electronic device 110 shown in FIG. 9 shows only components related to this embodiment. Accordingly, those skilled in the art can understand that other general-purpose components may be included in addition to the components shown in FIG. 9.

Devices according to the above-described embodiments include a processor, memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with an external device, a touch panel, keys, buttons, etc. It may include a user interface device, etc. Methods implemented as software modules or algorithms may be stored on a computer-readable recording medium as computer-readable codes or program instructions executable on the processor. Here, computer-readable recording media include magnetic storage media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disk, hard disk, etc.) and optical read media (e.g., CD-ROM). ), DVD (Digital Versatile Disc), etc. The computer-readable recording medium is distributed among computer systems connected to a network, so that computer-readable code can be stored and executed in a distributed manner. The media may be readable by a computer, stored in memory, and executed by a processor.

This embodiment can be represented by functional block configurations and various processing steps. These functional blocks may be implemented in various numbers of hardware or/and software configurations that execute specific functions. For example, embodiments include integrated circuit configurations such as memory, processing, logic, look-up tables, etc. that can execute various functions under the control of one or more microprocessors or other control devices. can be hired. Similar to how the components can be implemented as software programming or software elements, this embodiment includes various algorithms implemented as combinations of data structures, processes, routines or other programming constructs, such as C, C++, Java ( It can be implemented in a programming or scripting language such as Java), assembler, etc. Functional aspects may be implemented as algorithms running on one or more processors. Additionally, this embodiment may employ conventional technologies for electronic environment setting, signal processing, message processing, and/or data processing. Terms such as “mechanism,” “element,” “means,” and “composition” can be used broadly and are not limited to mechanical and physical components. The term may include the meaning of a series of software routines in connection with a processor, etc.

The above-described embodiments are merely examples and other embodiments may be implemented within the scope of the claims described below.

Claims (15)

In a method for managing information about AB test code in an electronic device,
Obtaining history information of pull requests (PR) for AB test code based on a reference point;
Obtaining status information about the AB test code based on the history information of the PR;
checking whether notification conditions related to the AB test code are met based on the status information; and
When the notification condition is met, an AB test code information management method comprising transmitting notification information related to the AB test code. According to paragraph 1,
The history information of the above PR is,
An AB test code information management method, including an AB test key capable of identifying the AB test code and checklist information set in relation to the AB test. According to paragraph 2,
The above checklist information is:
An AB test code information management method including identification information that can confirm whether the PR is a PR requesting a code cleanup operation for the AB test code. According to paragraph 1,
The step of obtaining the history information of the PR is,
An AB test code information management method, characterized in that the history information of the PR is obtained based on the content entered by the developer in the PR template defined separately from the PR code. According to paragraph 1,
The step of obtaining the history information of the PR is,
An AB test code information management method, characterized in that the history information of the PR is extracted based on the value assigned to a specific variable in the code of the PR written by the developer. According to paragraph 1,
The status information is,
First state information corresponding to a state before execution of the AB test code, second state information corresponding to a state during execution of the AB test code, third state information corresponding to an execution end state of the AB test code, and the AB An AB test code information management method, optionally including fourth state information corresponding to a state in which code cleanup for the test code has been performed. According to paragraph 1,
The step of obtaining the status information is,
An AB test code information management method, characterized in that obtaining status information about the AB test code corresponding to the AB test key included in the history information of the PR. According to paragraph 1,
The step of checking whether the above notification conditions are met is,
Checking whether there is an unorganized code that is not subject to code cleaning work among the AB test codes corresponding to the PRs; and
When the unresolved code exists, AB test code information management method comprising the step of checking whether the notification condition is satisfied based on status information about the unresolved code. According to clause 8,
The step of checking whether the notification condition is met based on the status information about the unorganized code is,
If the unorganized code exists, checking whether the unorganized code is in an execution complete state;
When the unorganized code is in an execution-finished state, checking whether a set period of time has elapsed from the point of execution of the unorganized code; and
AB test code information management method comprising determining that the notification condition is met when the set period has elapsed from the end of execution of the unorganized code. According to paragraph 1,
The status information is,
Optionally additionally including fifth state information corresponding to a state in which the AB test code has finished execution and the code can be cleaned up,
The step of checking whether the above notification conditions are met is,
When the status information corresponds to the fifth status information, the AB test code information management method is characterized in that it is determined that the notification condition is satisfied. According to paragraph 1,
The step of transmitting the notification information is,
An AB test code information management method, characterized in that sending an email with a tracking result file for the AB test code attached to the set AB test-related account as the recipient. According to clause 11,
The step of transmitting the notification information is,
An AB test code information management method, characterized in that a link to a website that provides tracking results for the AB test code is inserted into the body of the email and transmitted. According to paragraph 1,
Referring to a database in which at least part of the history information of the PR and status information about the AB test code is stored, generating a report or dashboard containing at least part of the tracking results of the AB test code Including, AB test code information management method. A computer-readable non-transitory recording medium recording a program for executing the method of any one of claims 1 to 13 on a computer. An electronic device for managing information about AB test codes, comprising:
Includes a transceiver, memory for storing instructions, and a processor;
The processor is connected to the transceiver and the memory,
Obtain pull request (PR) history information for AB test code based on the reference point,
Obtain status information about the AB test code based on the history information of the PR,
Based on the status information, determine whether notification conditions related to the AB test code are met,
An electronic device that transmits notification information related to the AB test code when the notification condition is met.

Images