TWI900887B - Electronic device and method for providing a report on a page, and non-transitory computer-readable recording medium for performing the method - Google Patents

Abstract

The present invention discloses a method for providing a page report, which is performed by an electronic device. Specifically, the method for providing a page report may include the following steps: identifying a target page; identifying a base environment and a test environment; based on configuration information for comparing the pages, identifying a first page corresponding to the target page in the base environment and a second page corresponding to the target page in the test environment; performing a test to detect at least one of a difference between the first page and the second page and errors in the first page and the second page; and providing a report including information on the results of the test.

Description

Electronic device and method for providing page report, and non-transitory computer-readable recording medium for executing the method

Embodiments of this specification relate to a method and apparatus for providing a page report. Embodiments of this specification relate to a method and apparatus for performing a test to determine the differences between pages in a base environment and a test environment, as well as errors contained in each page, and providing a report including test result information.

Before releasing a test service, it's necessary to compare the live and test pages in an online environment, such as online marketing. However, manually verifying the differences between the live and test pages, as well as errors that arise during page execution, can take time, leading to concerns that the test release process will take an excessive amount of time. Therefore, a method and device are needed to address this issue.

To solve the above-mentioned problem, the present invention provides a method and device for providing page reports.

More specifically, the present invention provides a method and apparatus for performing a test on the differences between pages in a base environment and a test environment, as well as on errors contained in each page, and providing a report including result information, such as image or text differences between pages or errors generated during the execution of the pages.

The technical issues to be implemented by this embodiment are not limited to the technical issues described above; other technical issues can be derived based on the following embodiments.

As a technical means for achieving the above-mentioned problem, the first aspect of the present invention, a method for providing a page report using an electronic device, may include the following steps: identifying a target page; identifying a base environment and a test environment; identifying a first page corresponding to the target page in the base environment and a second page corresponding to the target page in the test environment based on configuration information for comparison between the pages; performing a test to detect at least one of a difference between the first and second pages and errors contained in the first and second pages; and providing a report including information on the results of the test.

According to one embodiment, the steps of confirming the basic environment and the test environment may include the following steps: confirming the basic environment based on traffic data of the basic environment collected in batches; and confirming the test environment based on traffic data of the test environment collected online.

According to one embodiment, the step of confirming the basic environment may include the following steps: based on the number of visits corresponding to the collected traffic data of the basic environment, determining a basic environment whose number of visits is above a set threshold value.

According to one embodiment, the setting information may include at least one of information regarding excluding a first element among the elements included in the page from the inter-page comparison and information regarding including a second element among the elements included in the page in the inter-page comparison.

According to one embodiment, the first page and the second page may be pages that do not include the first element but include the second element.

According to one embodiment, the step of implementing the test may include the following steps: implementing an A/B test on page 1 and page 2 based on the test setting information of the test.

According to one embodiment, the step of confirming the first page and the second page may include the following step: using the first thread and the second thread to confirm the first page and the second page in parallel, and the step of performing a test may include the following step: using the main thread to perform a test on the difference between the first page and the second page.

According to one embodiment, the step of providing a report may include the following step: providing a report including a comparison image showing the difference between the first page and the second page by sliding an icon.

According to one embodiment, the step of providing a report may include the following steps: based on the difference between the first page and the second page, identifying a first element that is different from an element included in the second page that corresponds to an element on the first page; and providing a report including the second page displaying the first element.

According to one embodiment, the step of providing a report may include the following steps: identifying, in the second source code corresponding to the second page, a source code that is different from the first source code corresponding to the first page, namely a third source code; and providing a report including the second source code displayed with the third source code.

According to one embodiment, the error may include at least one of a first console error corresponding to the first page, a second console error corresponding to the second page, and a loading error of a resource included in the page.

According to one embodiment, the difference between the first page and the second page may include at least one of a difference in images, text, and resources between the pages.

The electronic device for providing a page report according to the second aspect of the present invention may include: a transceiver; a memory storing one or more commands; and a processor; the processor being configured to: identify a target page, identify a base environment and a test environment, and based on configuration information comparing the pages, identify a first page corresponding to the target page in the base environment and a second page corresponding to the target page in the test environment; perform a test to detect at least one of a difference between the first and second pages and errors in the first and second pages; and provide a report including information on the results of the test.

The recording medium of the third aspect of the present invention may be a non-transitory computer-readable recording medium used to execute programs on a computer.

According to an embodiment of this specification, an electronic device can identify a first page corresponding to a target page in a base environment and a second page corresponding to a target page in a test environment, and then perform a test to detect at least one of the differences between the first and second pages and errors detected during the execution of the first and second pages. The electronic device 100 can provide a report including test result information. By detecting the differences between the first and second pages and errors detected during the execution of the first and second pages, the electronic device 100 can automatically provide a report containing test result information. This allows users to quickly confirm test results and, based on the test results, quickly determine whether to publish the test.

The effects of the invention are not limited to those mentioned above. A person with common sense in the relevant technical field can clearly understand other effects not mentioned based on the description of the invention patent application.

10: System

100: Electronic devices

110: Server

300: User interface difference architecture

301: Object Operation Library

302: Browser Operation Program Library

303: Error handling

304: Console Monitor

305: Comparison Core

306: Differential Regular Phase

307: Step Phase

308: URL loading monitor

310: User interface differences

311: Selenium

312:Configuration Phaser

313: Excel Phaser

320: Distributed Execution

330: Backend

340: Front-end

350: Data storage

400: System

410: User Interface Difference Tool

420: Page Different Frame

423: Page 1

424: Page 2

600: Page

610: URL

620:pc shopping cart page EN

630:En

640:Y

650: Area of page 600

660: Icon

700: Page

710:pc shopping cart page EN

720: Exclusion rules

730: Only compare rules

800: Page

810: Column label

820: Icon

830: Icon

840: Icon

850: Number 1

860: Number 2

870: Number 3

900: Page

910: Test A configuration

920: Test B configuration

930: Icon

1000: Page

1010: Test B configuration

1020:Account

1030: Check text only

1040: Baseline Configuration

1041: Production

1050: Test configuration

1060:Host Mapping

1100: Page

1110: Icon

1120: Icon

1130: Icon

1140: Icon

1200: Page

1205: Icon

1210: URL version

1211: URL version

1220:Frequency

1300: Page

1310: Test 1

1320: Test 2

1321: Icon

1330: Test 3

1400: Page

1410: Entry Point 1

1420: Second Entry Point

1430: Entry Point 3

1500: Page

1510: Compare images

1520: Area 1

1530: Area 2

1540: Slide icon

1610: Page 1

1620: Page 2

1630: 2nd element

1640:The third element

1700: Difference results

1800: Difference results

1810: Text comparison error

1820: Source code 1

1830: Second source code

1831: Source code

1832: Source code

1833: Source code

1834: Source code

1835: Source code

1836: Source code

1900: HTML report

1910: Information

1920: Steps

1930: Information

2000: Electronic devices

2010: Transceiver

2020: Processor

2030: Storage

S210: Step

S220: Step

S230: Step

S240: Step

S250: Step

S411: Step

S412: Step

S413: Step

S414: Step

S415: Step

S421: Step

S422: Step

S425: Step

S430: Step

S510: Step

S520: Step

S530: Step

S540: Step

FIG1 is a diagram illustrating a system for implementing a method for providing a page report by an electronic device according to various embodiments.

Figure 2 is a flow chart showing a method for an electronic device to provide a page.

FIG3 is a diagram illustrating an embodiment of an electronic device providing a page report in the device.

Figure 4 is a diagram illustrating a system for providing page reports.

Figure 5 illustrates the process of processing traffic data.

Figure 6 illustrates the page for setting the URL for the test environment.

Figure 7 illustrates the page for editing setting information compared between pages.

Figure 8 illustrates the page for setting up and storing the URL for the test environment.

Figure 9 is a diagram following Figure 8, illustrating the page for managing test execution.

Figure 10 illustrates the detailed page for setting up a test.

Figure 11 is a diagram illustrating the flow data page.

Figure 12 is a diagram following Figure 11, illustrating the page displaying traffic data.

Figure 13 is a diagram of a page used to illustrate the results of the test.

Figure 14 is a diagram illustrating a page including information on the results of a test run.

Figure 15 is a diagram illustrating a comparison image for comparing the differences between Page 1 and Page 2.

Figure 16 is a diagram used to illustrate the first and second images.

Figure 17 is a graph used to illustrate the results of the test, namely the difference results.

Figure 18 is a graph used to illustrate the results of the test, namely the difference results.

Figure 19 is an HTML report used to illustrate the implementation of the test.

Figure 20 is a block diagram illustrating an electronic device for providing page reports according to one embodiment.

The terms used in the embodiments are selected to the greatest extent possible from commonly used terms, taking into account the functions of the present invention. However, they may vary depending on the intentions of those skilled in the art, precedents, the emergence of new technologies, and so on. Furthermore, in certain cases, the applicant may arbitrarily select terms. In such cases, their meanings will be described in detail in the corresponding explanatory sections. Therefore, the terms used in this invention should be defined based on their meanings and the overall content of the invention, not simply based on their names.

Throughout this specification, when a section is described as "including" a certain component, this implies that other components may be included, and does not exclude other components, unless otherwise specified. Furthermore, terms such as "unit" and "module" used in this specification refer to a unit that processes at least one function or action, which may be implemented by hardware or software, or a combination of hardware and software.

The phrase "at least one of a, b, and c" throughout this specification may include "a alone," "b alone," "c alone," "a and b," "a and c," "b and c," or "all three of a, b, and c."

The "terminal" mentioned below can be implemented as a computer or portable terminal connected to a server or other terminal via a network. Computers include, for example, laptops, desktops, and notebooks equipped with web browsers. Portable terminals are wireless communication devices that ensure portability and mobility, and include, for example, IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution), and all types of handheld wireless communication devices, including smartphones and tablets.

The following describes an embodiment of the present invention in detail with reference to the accompanying drawings so that those skilled in the art can easily implement the present invention. However, the present invention can be implemented in many different forms and is not limited to the embodiment described here.

Below, the embodiments of the present invention are described in detail with reference to the accompanying drawings.

When describing the embodiments, descriptions of technical contents that are well-known in the art and not directly related to the present invention are omitted. This is done to clearly convey the main points of the present invention by omitting redundant descriptions and to avoid confusion.

For similar reasons, some components may be exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the dimensions of each component do not necessarily reflect the actual dimensions. In the drawings, identical or corresponding components are designated by the same reference symbols.

The advantages and features of the present invention, as well as methods for achieving such advantages and features, will become apparent by referring to the accompanying drawings and the embodiments described in detail below. However, the present invention is not limited to the embodiments disclosed below and can be implemented in a variety of different forms. These embodiments are provided solely to fully disclose the present invention and enable those skilled in the art to fully understand the scope of the invention. The present invention is defined solely by the scope of the patent applications. Throughout this specification, identical reference numerals denote identical components.

At this point, it should be understood that each block of the process flow chart and the combination of the flow charts can be implemented by computer program instructions. These computer program instructions can be loaded into a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that these instructions, when executed by the processor of the computer or other programmable data processing device, will produce a method for implementing the functions described in the blocks of the flow chart. In order to implement the functions in a specific manner, these computer program instructions can be stored in a computer-usable or computer-readable memory that is readable by the computer or other programmable data processing device, so that the instructions stored in the computer-usable or computer-readable memory can also produce an article of manufacture that includes the following instruction method, which implements the functions described in the blocks of the flow chart. Computer program instructions may also be loaded onto a computer or other programmable data processing device, thereby causing the computer or other programmable data processing device to execute a series of action steps, thereby generating a process executed by the computer. The instructions executed by the computer or other programmable data processing device may also provide steps for performing the functions described in the blocks of the flowchart.

Furthermore, each block may represent a module, segment, or portion of code that includes one or more executable instructions for performing a specific logical function. Furthermore, it should be noted that in some alternative embodiments, the functions described in the blocks may not occur in the order in which they are described. For example, two blocks shown in succession may be executed simultaneously, or may occasionally be executed in the reverse order depending on the corresponding functions.

FIG1 is a diagram illustrating a system for implementing a method for providing a page report by an electronic device according to various embodiments.

Referring to FIG. 1 , system 10 of various embodiments can be implemented using various types of devices. For example, system 10 may include an electronic device 100 and a server 110 . The system 10 shown in FIG. 1 only illustrates components relevant to this embodiment. Therefore, those skilled in the art will appreciate that, in addition to the components shown in FIG. 1 , other commonly used components may be included.

Each of the electronic device 100 and the server 110 may include a transceiver, storage, and a processor. Furthermore, each of the electronic device 100 and the server 110 refers to a unit that processes at least one function or action, which may be implemented by hardware or software, or a combination of hardware and software. Furthermore, throughout the embodiments, the electronic device 100 and the server 110 are referred to as separate devices or servers, but they may be logically separate structures, at least a portion of which may be implemented by functions separated from a single device or server.

According to one embodiment, electronic device 100 and server 110 may include multiple computer systems or computer software implemented via a network server. For example, at least a portion of electronic device 100 and server 110 may refer to computer systems and computer software that are connected to downstream devices capable of communicating with other network servers via a computer network, such as an intranet or the Internet, to receive requests to perform tasks, perform those tasks, and provide results. Furthermore, electronic device 100 and at least a portion of server 110 may also be understood as a broad concept encompassing a range of applications that can operate on the network server, as well as various databases built within the server or on other connected nodes. For example, at least a portion of the electronic device 100 and the server 110 may be implemented using a network server program provided in various forms based on an operating system such as DOS (Disk Operating System), Windows, Linux, UNIX, or MacOS.

Electronic device 100 and server 110 can communicate with each other via a network (not shown). Networks include local area networks (LANs), wide area networks (WANs), value-added networks (VANs), mobile radio communication networks, satellite communication networks, and combinations thereof. This network is a comprehensive data communication network that enables the various network components shown in FIG. 1 to communicate smoothly with each other. It can include wired internet, wireless internet, and mobile wireless communication networks. Wireless communication may include, but is not limited to, Wi-Fi, Bluetooth, Bluetooth low energy, Zigbee, Wi-Fi Direct (WFD), UWB (ultra wideband), infrared data association (IrDA), and NFC (near field communication).

According to one embodiment, the electronic device 100 can identify a target page, a base environment, and a test environment. Based on the configuration information obtained by comparing the pages, the electronic device 100 can identify a first page corresponding to the target page in the base environment and a second page corresponding to the target page in the test environment. The electronic device 100 can then test at least one of the differences between the first and second pages and any errors contained in the first and second pages, and provide a report containing information on the test results. The server 110 can provide the electronic device 100 with information used to implement the above-described embodiment, as well as traffic data for the base and test environments.

Page 1, which corresponds to the target page in the current service environment, and Page 2, which corresponds to the target page in the test environment, may have some differences in text, images, and resources. In this case, since electronic device 100 provides the differences in user interface styles between Page 1 and Page 2, as well as errors in the execution of Page 1 and Page 2, users can quickly identify the differences and errors in the execution of Page 1 and Page 2. Furthermore, electronic device 100 provides a platform for setting up a basic environment and a test environment, and can easily perform tests to detect differences between pages or errors in page execution. This allows users to easily conduct tests on the platform. By reviewing the report containing test results, users can easily compare the performance of Page 1 (corresponding to the base environment) and Page 2 (corresponding to the test environment). The following details specific implementation examples related to this.

Figure 2 is a flow chart showing a method for an electronic device to provide a page report.

Referring to Figure 2, it can be understood that the various actions of the electronic device in providing information can be modified, with some of the actions or some of the sequence between the actions being replaced within the scope clearly understood by those with common sense in the technical field to which the present invention belongs.

In step S210, the electronic device 100 may confirm the target page.

According to one embodiment, the electronic device 100 can confirm the target page corresponding to the user's request. More specifically, as the user enters URL (Uniform Resource Locator) information through the user interface, the electronic device 100 can confirm that the entered URL information becomes the URL information of the target page of the test object. Here, the target page can be, but is not limited to, a GW or SDP page.

In step S220, the electronic device 100 may confirm the basic environment and the test environment.

According to one embodiment, the electronic device 100 can confirm a basic environment and a test environment. A user can select a basic environment serving as a test baseline and a test environment serving as a test target. The electronic device 100 can then confirm a basic environment for a target page and a test environment for the target page. In this application, the basic environment can be the environment serving as a test baseline, and the test environment can be the environment serving as a test target. More specifically, the basic environment can be a production environment currently in service, and the test environment can be an environment developed by a QA (quality assurance) team and currently undergoing testing, but the present invention is not limited thereto.

According to one embodiment, the electronic device 100 can verify the basic environment based on batch-collected traffic data for the basic environment, and verify the test environment based on online traffic data for the test environment. More specifically, based on the number of accesses corresponding to the traffic data for the basic environment, the electronic device 100 can determine that the basic environment has a number of accesses exceeding a predetermined threshold. The specific operations for verifying the basic environment and the test environment will be discussed in detail below.

In step S230 , the electronic device 100 can identify the first page corresponding to the target page in the basic environment and the second page corresponding to the target page in the test environment based on the configuration information of the page comparison.

According to one embodiment, the electronic device 100 can concurrently verify multiple pages using multiple threads. For example, the electronic device 100 can utilize a first thread to verify a first page corresponding to a target page in a base environment, and a second thread to verify a second page corresponding to a target page in a test environment. Verifying the page may include parsing the page source based on the URL of the target page in each environment. Furthermore, based on configuration information, the page verification may select only a portion of the page verified by parsing the page source as the reference or target page for comparison.

Here, the configuration information may include at least one of information for excluding a portion of the elements included on a page (or, referred to as the first element) from the inter-page comparison, and information for including another portion of the elements included on the page (or, referred to as the second element) in the inter-page comparison. Here, the configuration information may be referred to as a difference rule (DIFF RULE), information for excluding a portion of the elements included on a page from the inter-page comparison may be referred to as an exclusion rule (EXCLUDE RULE), and information for including another portion of the elements included on a page in the inter-page comparison may be referred to as an ONLY COMPARE RULE, but are not limited thereto. Thus, the page including the first and second pages may be a page that does not include the first element but includes the second element. The following will examine in detail the specific actions on Page 1 and Page 2.

In step S240 , the electronic device 100 may perform a test on at least one of the difference between the first page and the second page, and errors included in the first page and the second page.

According to one embodiment, electronic device 100 may perform a test for differences between page 1 and page 2. For example, after verifying page 1 and page 2 via thread 1 and thread 2, electronic device 100 may verify the differences between page 1 and page 2 via the main thread. The differences between page 1 and page 2 may be differences in the user interface appearance of elements included in the pages. For example, the differences between page 1 and page 2 may include differences in text, images, resource URLs, etc.

According to one embodiment, electronic device 100 may test errors included in page 1 and page 2. Here, errors may be errors generated during the execution of page 1 and page 2. Errors may include at least one of a first console error corresponding to page 1, a second console error corresponding to page 2, and errors loading resources included in page 1 and page 2. Furthermore, errors may include JS (Java Script) errors, CSS (Cascading Style Sheets) errors, and the like.

In step S250 , the electronic device 100 may provide a report including information on the results of the test.

According to one embodiment, electronic device 100 can provide a report including the differences between Page 1 and Page 2 of the test execution, as well as errors included in Page 1 and Page 2. This allows users to easily identify the differences and errors between Page 1 and Page 2, and to easily compare the performance of Page 1 corresponding to the base environment and Page 2 corresponding to the test environment.

According to one embodiment, the electronic device 100 can provide a report including a comparison image showing the difference between the first page and the second page using a sliding icon. This allows the user to easily confirm the difference between corresponding elements on the first and second pages by sliding the icon.

According to one embodiment, based on the difference between the first and second pages, the electronic device 100 can identify a first element included on the second page that is different from an element on the first page, and can provide a report including the second page displaying the first element. By confirming the second page displaying the first element, the user can easily identify the element that differs between the first and second pages.

According to one embodiment, electronic device 100 can confirm the first and second source codes corresponding to the first and second pages. Then, electronic device 100 can confirm a third source code within the second source code that is different from the first source code. Thus, electronic device 100 can provide a report by displaying the third source code within the second source code.

Figure 3 is a diagram illustrating an electronic device for providing page reports.

Referring to FIG. 3 , UI Diff Architecture 300 may be a system architecture for identifying differences between pages and errors within pages. UI Diff Architecture 300 may include UI Diff 310 , Distributed Execution 320 , Backend 330 , Frontend 340 , and Data Storage 350 .

User Interface Difference 310 may include libraries that can be used to test differences between pages. Libraries may also be displayed as "Lib" in the accompanying diagram. 1) Object Operation Library 301 may include functions for exposing elements included in a new page when a page provides a new page form through an entry point, etc. 2) Browser Operation Library 302 may be a library for implementing functions for performing operations through a browser. 3) Error Handling 303 may be a library for resolving errors generated when performing operations through a browser. 4) Console Monitor 304 can be a library for providing console errors generated during page execution. More specifically, if a console error occurs while Console Monitor 304 is executing a page corresponding to the test environment, electronic device 100 can display and provide the console error. 5) Compare Core 305 can be a library for identifying differences between a first page in a base environment and a second page in a test environment. More specifically, Compare Core 305 can identify differences between the first and second pages based on configuration information for comparing the pages. Furthermore, the comparison core 305 can identify elements that differ between pages based on an automatic noise reduction process. These elements can be stored as cached data. 6) The Diff Rule Phase 306 can be a library for configuring and modifying configuration information for page comparisons. 7) The Step Phase 307 can be a library for analyzing functions implemented by the Object Operation Library 301e. 8) The URL Load Monitor 308 can be a library for monitoring JS and CSS in response to URL loading.

Furthermore, user interface differences 310 may include Selenium 311, Appium, Pytest, a configuration phaser 312, and an Excel phaser 313. 1) Selenium 311 can generate test result information. More specifically, Selenium 311 can utilize elements that display a comparison image or a difference between the second image. 2) Configuration phaser 312 provides a page for entering information required for test execution. 3) Excel phaser 313 provides a page for storing and analyzing test data.

Distributed Execution 320 can provide the libraries included in User Interface Difference 310 to the backend through AutoRunner.

The backend 330 may include an open source web framework built using Python, such as Django, Rest-framework, JWT, SDK (software development kit), and traffic data collection.

Front-end 340 may include components including web/H5 differences, Android differences, and iOS differences, as well as runtime configuration and project scripts. Furthermore, front-end 340 may include VUE, Element-UI, JS/CSS (Scss), VUEX, Axios, and an img-comparision-slider. The img-comparision-slider provides image comparisons between pages.

Data storage 350 may include MySQL, MongoDB, Redis, and a file system. MySQL can store target page URL information. More specifically, MySQL can confirm target page URL information within the test environment. Redis can temporarily store test execution status information and real-time reports. Furthermore, the file system can store image files and HTML reports generated based on test execution.

Figure 4 is a diagram illustrating a system for providing page reports.

Referring to FIG. 4 , system 400 , which is used to implement an embodiment of the present application, may include a user interface difference tool (UI DIFF TOOL) 410 and a web diff framework (Web Diff Framework) 420.

In step S411, the user can set a diff URL and a diff function. Here, the diff URL can correspond to the target page. Furthermore, the diff function can correspond to the library function included in the diff 310 in the user interface in Figure 3 . In other words, the user can determine the target page and the library function settings that can be used for testing before executing the test.

In step S412, the user can configure Perm flow data and product flow data. The electronic device 100 can verify the basic environment based on the flow data collected in the basic environment during batches. Here, the flow data in the basic environment, as product flow data, can be flow data collected during the batch configuration period. Furthermore, the electronic device 100 can verify the test environment based on flow data collected online in the test environment. Here, the flow data in the test environment can be flow data used for testing by users such as the QA team.

In step S413, the user can set difference rules. In this application, when performing a test for comparing pages, the difference rules may correspond to setting information for specifying elements on the pages to be compared or elements to be excluded from the comparison.

In step S414, the user can set information for testing at least one of differences or errors between pages. For example, the user can set a basic environment or a test environment as a benchmark for testing using a page provided by the electronic device 100 (herein, the page may be referred to as a user interface).

In step S415 , the electronic device 100 may provide a report including result information, including the difference between the first and second pages, and information about errors generated during the execution of the first and second pages. More specifically, the electronic device 100 may use a webpage difference framework 420 to provide a report including the result information, including the difference between the first and second pages, and information about errors generated during the execution of the first and second pages. FIG. 4 illustrates webpage user interface differences, but is not limited thereto. The embodiments of this application may also be similarly applied to user interface differences in devices such as mobile devices.

In steps S421 and S422, the electronic device 100 can use separate threads to identify the page corresponding to the target page in each environment. For example, the electronic device 100 can use thread 1 to identify page 1 corresponding to the target page in the production environment, and thread 2 to identify page 2 corresponding to the target page in the test environment. Furthermore, identifying the page may include: parsing the page source based on the target page's URL information, IP information of the environment corresponding to the target page, etc.; and, based on configuration information (or difference rules), identifying a portion of the page corresponding to the parsed page source using page 1 423 or page 2 424.

In step S425, the electronic device 100 can compare the resources of page 1 423 and page 2 424 via the main thread. The resources of each page being compared may include not only text, images, and videos, but also all elements that can be included in a page. Furthermore, the electronic device 100 can store the differences between page 1 423 and page 2 424 resulting from the resource comparison, as well as any errors found in the comparison. For example, the electronic device 100 can store the differences between page 423 and page 2 424 as an image, store the differences and errors in Redis, and save a report containing the result information as an HTML file.

In step S430 , the electronic device 100 may generate a report that includes the differences between the first page 423 and the second page 424 , as well as the errors corresponding to the first page 423 and the second page 424 . Furthermore, the generated report may be uploaded or stored in a cached form on the electronic device 100 or the proxy server.

Figure 5 illustrates the process of processing traffic data.

Figure 5 illustrates the process of processing webpage-related traffic data when testing differences between pages in a webpage environment and errors during page execution. However, the traffic data in this application is not limited to webpage-related traffic data.

In step S510, the electronic device 100 may filter a portion of the test environment traffic data collected online based on whether the response is HTML. For example, the electronic device 100 may filter webpage-related traffic data within the test environment traffic data collected online based on whether the response is HTML. This allows the electronic device 100 to filter a portion of the traffic data to implement webpage user interface differentiation. Here, the test environment traffic data collected online may be referred to as Perm traffic data.

In step S520 , the electronic device 100 may filter a portion of the production environment traffic data collected by batch based on whether a user agent match occurs. In this way, the electronic device 100 may filter webpage-related traffic data within the production environment traffic data.

In step S530, the electronic device 100 can filter traffic data with access counts exceeding a set threshold based on the access counts of each filtered traffic data item. This allows the electronic device 100 to filter and provide only web page traffic with access counts exceeding the set threshold within the bulk traffic data. Specifically, the electronic device 100 can identify the basic environment with access counts exceeding the set threshold based on the access counts corresponding to the traffic data in the basic environment. Furthermore, the electronic device 100 can identify the test environment with access counts exceeding the set threshold based on the access counts corresponding to the traffic data in the test environment.

In step S540 , the electronic device 100 may confirm the traffic data corresponding to the base environment and the test environment used in the current test and then add them to a blacklist. For example, to utilize traffic data from various environments, the electronic device 100 may configure the blacklist to include traffic data from the environment used in the test, thereby filtering it out of the traffic data in subsequent tests.

Figure 6 illustrates the page for setting the URL for the test environment.

Referring to Figure 6 , electronic device 100 may provide a user with a page 600 for configuring a test environment URL. The user may use page 600 to enter information about the test environment URL. The user may manually configure a new test environment URL by entering information about the URL to be tested in area 650 of page 600. Page 600 may be provided by Excel Analyzer 313.

The electronic device 100 can provide the page 600 using the URL of a stored test environment. For example, the URL of the test environment corresponding to index number 5 can be "http://cart.coupang.com/cartView.pang" 610, and the page name of the test environment with the URL "http://cart.coupang.com/cartView.pang" 610 can be "pc shopping cart page EN" 620. Furthermore, the language of the test environment with the URL "http://cart.coupang.com/cartView.pang" 610 can be "EN" 630, and the login information can be "Y" 640. Furthermore, as the user receives input for the operation through icon 660, the electronic device 100 may provide a page for editing the setting information compared between the pages.

Figure 7 illustrates the page for editing setting information compared between pages.

Referring to FIG. 7 , as the user receives input regarding an operation via icon 660 , electronic device 100 may provide a page 700 for editing the configuration information for comparing pages. Page 700 may be a page for configuring the configuration information for "pc shopping cart page EN" 710 . More specifically, page 700 may be a page for editing the configuration information for comparing pages of the target page, whose URL is "http://cart.coupang.com/cartView.pang" 610 in the test environment of FIG. 6 . The setting information of page 700 can be referred to as a difference rule. The setting information may include: 1) information for excluding a first element among the elements included in the page from the inter-page comparison, and 2) information for including a second element among the elements included in the page in the inter-page comparison.

1) Information that excludes the first element of the elements included in a page from the inter-page comparison is referred to as exclusion rule 720. Exclusion rule 720 may be a setting that excludes elements from the comparison between the first page corresponding to the target page in the base environment and the second page corresponding to the target page in the test environment. For example, exclusion rule 720 may be a setting that excludes areas with IDs corresponding to "header" and "widget" from the comparison.

2) Information that includes the second element among the elements included in the page in the inter-page comparison may be referred to as comparison-only rule 730. Comparison-only rule 730 may refer to setting the elements to be included in the comparison between the first page corresponding to the target page in the base environment and the second page corresponding to the target page in the test environment. However, as in the embodiment depicted in FIG7 , when comparison-only rule 730 is not specifically configured, elements not included in exclusion rule 720 may be included in the comparison.

Thus, Page 1 and Page 2 may not include elements corresponding to Exclusion Rule 720, but may include elements corresponding to Comparison Rule 730.

Figure 8 illustrates the page for setting up and storing the URL for the test environment.

Referring to Figure 8 , page 800 represents a page storing the URL for the test environment. The page layout may vary depending on the device type and operating system. For example, the page layout may differ depending on whether it is a web page for a computing device or a page for a mobile device, and the page layout may also differ depending on whether the mobile device's operating system is Android or iOS. Therefore, electronic device 100 may provide a field 810 on page 800 to allow selection between web page, Android, or iOS. Furthermore, by checking and saving icon 820 on page 800, electronic device 100 may store test data in MySQL in data storage 350.

Furthermore, "https://cart.coupang.com/subscribe-cart" with index number 1 in FIG8 may include a post-action step, which may include the following actions: 1) a first action of clicking the bottom expand link numbered 1 (850), 2) a second action of rolling the mouse to the question mark icon numbered 2 (860), and 3) a third action of providing additional verification information after the second action numbered 3 (870). In other words, the comparison object of the test may include a user interface that is additionally exposed based on the user's actions.

If icon 820 of page 800 is checked and the user's execution input is executed through icon 830, electronic device 100 can perform a test on at least one of differences between pages and errors generated during the execution of the page based on the checked test data.

If user input is received via icon 840 on page 800, electronic device 100 may provide a page for managing the execution of the test.

Figure 9 is a diagram following Figure 8, illustrating the page for managing test execution.

Referring to Figure 9 , page 900 may be used to manage the execution of tests for the selected test data. Page 900 allows users to view the directory of tests for the selected test environment URL (the test environment URL may be a target page within the test environment). For example, the tests configured for the test environment target page may be indexed 1 through 4, for a total of four tests, including Test A Configuration 910 and Test B Configuration 920.

Based on the test setting information in which the user changes the default value to yes in a plurality of tests, the electronic device 100 can perform a test for at least one of the difference between the first page corresponding to the target page in the basic environment and the second page corresponding to the target page in the test environment, and errors included in the first and second pages.

If the user input regarding the test settings is received via icon 930, the electronic device 100 may provide a detailed page for editing the test setting information.

Figure 10 illustrates the detailed page for setting up a test.

FIG10 shows a detailed page provided by electronic device 100 to the user for editing the configuration information for Test B in FIG9 in response to user input via the icon corresponding to Test B. The user can use page 1000 to configure the test configuration information, such as setting the test server corresponding to "cart.coupang.com."

The name of the test on page 1000 may be Test B Configuration 1010. Furthermore, Account 1020 on page 1000 may be information about the user of the corresponding test, such as "UserA@coupang.com." Check Text Only 1030 on page 1000 may indicate whether to detect differences only in the text included in the pages during the inter-page comparison. 1) For example, as shown in FIG10 , if the check text only option is "No," the electronic device 100 may detect not only differences in the text included in the pages, but also differences in CSS and JS formats. 2) Conversely, if the check text only option is "Yes," the electronic device 100 may detect differences only in the text included in the pages.

According to one embodiment, the electronic device 100 can perform an A/B test on Page 1 and Page 2 based on the test configuration information. More specifically, the electronic device 100 can perform the A/B test based on the configuration information of A, which serves as the basis for comparison, and B, which serves as the object of comparison.

Baseline configuration 1040 for page 1000 may be part of a basic environment that is set as a benchmark for comparison. If the test is used to compare a page currently in service with a page scheduled for release, the comparison benchmark may be the page currently in service. That is, the default value of baseline configuration 1040 may be set to Production 1041. However, baseline configuration 1040 is not limited to Production 1041. For example, if the test is used to compare multiple pages scheduled for release, baseline configuration 1040 may not be limited to Production 1041.

Test configuration 1050 on page 1000 may be part of configuring the test environment used as a comparison target. Specifically, when a user performs a test on "cart.coupang.com," electronic device 100 may select the test server corresponding to "cart.coupang.com" via host mapping 1060 on page 1000. Referring to FIG. 10 , the test environment for the target page "cart.coupang.com" may be set to "PERM_coupang_cart_web_stage5."

Figure 11 is a diagram illustrating the flow data page.

FIG11 is a diagram illustrating a page 1100 displaying flow data for a test environment and flow data for a basic environment. For example, in response to user input via icon 1110, the electronic device 100 may provide flow data for a test environment and flow data for a basic environment via page 1100. For example, when icon 1110 is "Perm" or "Test," the electronic device 100 may provide flow data used by QA for testing. Conversely, when icon 1110 is production, the electronic device 100 may provide flow data for current service provision via page 1100. Here, the flow data for current service provision may be characterized by a large flow rate and being collected in batches. On the other hand, the characteristics of traffic data used by QA during testing can be collected online in real time.

Additionally, electronic device 100 may use page 1100 to provide an icon 1120 for the period during which traffic data is collected, and an icon 1130 for setting information about the domain corresponding to the traffic data. For example, referring to FIG. 11 , electronic device 100 may display on page 1100 traffic data collected from June 18, 2022, to June 20, 2022, for the domain name "Coupang-web" in the traffic data provided by the service.

Furthermore, if the user changes the reply count using the reply count icon 1140 , the electronic device 100 can determine the detailed URL that is arranged below the target URL among the detailed URLs included below the target URL based on the set reply count.

Figure 12 is a diagram following Figure 11, illustrating the page displaying traffic data.

Referring to Figure 12 , page 1200 may display traffic data for the domain name "Coupang-web" from traffic data collected during service provision from June 18, 2022, to June 20, 2022. The response count for page 1200 can be determined as 5 by icon 1205 . Electronic device 100 may display page 1200 by sorting the displayed traffic based on frequency 1220 of total visits, starting with the most visited URLs.

For example, the URL version "vp/products/_num_" has a total of 18,395 visits, making it the most visited URL page. Furthermore, within the detailed URLs included below the URL version "vp/products/_num_" 1210, the URL "vp/products/121816223" 1211 may be the same as the URLs indexed 2 through 5, corresponding to the URL with call number 9. The electronic device 100 may display and provide the URLs indexed 1 through 5, including "vp/products/_num_" 1210, which has a response count of 5.

Based on user settings, electronic device 100 can respond to only a portion of the traffic data and display it on page 1200. More specifically, electronic device 100 can display the most frequently visited URLs in the traffic data corresponding to the user settings above page 1200 or on the homepage. In other words, pages within the same domain may have similar layouts, not just the content included in a portion of the layout. Even by comparing pages corresponding to the most frequently visited URLs, differences in user interfaces can be identified.

According to one embodiment, the electronic device 100 can identify production environment traffic data with a number of accesses exceeding a predetermined threshold based on the number of accesses corresponding to the collected production environment traffic data. For example, referring to FIG12 , the electronic device 100 can use URLs indexed 1 to 5 as production environment traffic data when performing a test comparing product detail pages using Coupang_web.

Figure 13 is a diagram of a page used to illustrate the results of the test.

Page 1300 may be a page showing the results of testing differences between pages and errors contained within them. For example, page 1300 may include the results of multiple tests, including a first test 1310, a second test 1320, and a third test 1330. Page 1300 may include not only tests that have been tested and have been determined to be successful or failed, but also tests that are still being executed.

Furthermore, page 1300 may include an entry point to a page containing information about the results of each test. For example, upon receiving user input via icon 1321 , electronic device 100 may provide a report containing information about the results of the second test 1320 .

Figure 14 is a diagram illustrating a page including information on the results of a test run.

According to one embodiment, the electronic device 100 can perform a test on the difference between the first page and the second page using the main thread and provide a page 1400 including the result information.

For example, page 1400 may include a first entry point 1410 corresponding to a detailed page of difference results, a second entry point 1420 corresponding to a detailed page of difference images, and a third entry point 1430 corresponding to a detailed page of an HTML report. A detailed description of these will be discussed in detail in Figures 15 to 19.

Figure 15 is a diagram illustrating a comparison image for comparing the differences between Page 1 and Page 2.

According to one embodiment, electronic device 100 can provide a report including a comparison image showing the difference between page 1 and page 2 by sliding an icon. Referring to FIG. 15 , the baseline image of page 1500 may correspond to page 1, and the test image of page 1500 may correspond to page 2. Furthermore, a comparison image 1510 showing the difference between page 1 and page 2 by sliding an icon can be generated as shown in FIG. 15 .

For example, comparison image 1510 may feature a first area 1520 corresponding to page 1 and a second area 1530 corresponding to page 2, displayed overlapping each other. Furthermore, comparison image 1510 may feature a slider icon 1540 located in the center of comparison image 1510 that allows the ratio of the displayed first area 1520 to the displayed second area 1530 to be adjusted. This allows the user to easily discern the difference between the first and second images by adjusting the ratio of the displayed first and second areas 1520 and 1530 using slider icon 1540 on comparison image 1510. More specifically, users can compare images to detect differences in text, JS, CSS, and other color differences.

Figure 16 is a diagram used to illustrate the first and second images.

According to one embodiment, based on the difference between the first page and the second page, the electronic device 100 can identify a first element that is different from the element included in the second page and the corresponding element on the first page, and provide a report on the second page that includes the first element.

Referring to FIG. 16 , electronic device 100 may provide a first page 1610 and a second page 1620 . Page 1610 and page 2 1620 are user interfaces corresponding to target pages in different environments, and the second element included in page 1610 and the third element included in page 2 1620 may differ. Here, the third element may be an element corresponding to the second element. For example, the second element 1630 of the category included in page 1610 may differ from the third element 1640 of the category included in page 2 1620 .

According to one embodiment, the electronic device 100 may provide a second page 1620 that emphasizes the third element 1640 of the category included in the second page 1620. More specifically, the electronic device 100 may provide a second page 1620 that emphasizes the third element 1640 of the category using Selenium 311 in FIG. 3 .

Figure 17 is a graph used to illustrate the results of the test, namely the difference results.

According to one embodiment, electronic device 100 may provide test execution result information, namely, difference result 1700. For example, electronic device 100 may provide difference result 1700 including error information from the test execution. Here, difference result 1700 may include errors generated by executing pages in different environments. The errors may include at least one of a first console error corresponding to the first page, a second console error corresponding to the second page, and an error loading a resource included in the page.

For example, difference results 1700 may include 1) Java script and inline form errors, 2) other resource errors, 3) other resource warnings, 4) text comparison errors, 5) resource loading errors, 6) existing console errors, and 7) new console errors. Referring to FIG17 , there may be six Java script and inline form errors, which are errors caused by the different resources used in the test environment and the base environment. There may be one existing console error, which is an error generated in the base environment or the production environment. Furthermore, new console errors may be errors discovered while executing the target page in the test environment. In response to an erroneous user input, the electronic device 100 may provide the user with detailed information about the error received during the input.

Figure 18 is a graph used to illustrate the results of the test, namely the difference results.

According to one embodiment, the electronic device 100 can identify a third source code that is different from the first source code corresponding to the first page in the second source code corresponding to the second page, and provide a report including the second source code and displaying the third source code.

According to one embodiment, the electronic device 100 may provide test result information, namely, a difference result 1800 . In response to user input of the text comparison error 1810 , the electronic device 100 may provide detailed information about the text comparison error 1810 .

18 , text comparison error 1810 may include first source code 1820 corresponding to page 1 and second source code 1830 corresponding to page 2. Electronic device 100 may then identify a third source code in second source code 1820 corresponding to page 2 that is different from first source code 1830 corresponding to page 1. Referring to FIG. 18 , the third source code may include source code 1831, source code 1832, source code 1833, source code 1834, source code 1835, and source code 1836. For example, the first source code 1820 corresponding to source code 1831 may include 20% of the elements, while the second source code 1830 corresponding to source code 1831 may include 21%, which is different from 20%. In this case, electronic device 100 can emphasize the 20% elements included in first source code 1820 and the 21% elements included in second source code 1830 and provide difference results 1800.

Figure 19 is an HTML report used to illustrate the implementation of the test.

According to one embodiment, electronic device 100 may provide an HTML report 1900 including test result information. For example, HTML report 1900 may be a test report of at least one of the difference between page 1 and page 2, and errors in the execution of page 1 and page 2. HTML report 1900 may include information on whether errors exist in the execution of page 1 and page 2.

For example, HTML report 1900 may include information indicating that the URL was loaded without errors, such as "URL loaded successfully, status 200 OK!" 1910. Furthermore, HTML report 1900 may correspond to steps 1920 of "Get console log errors," "Get all image URLs on the page," and "Get all text on the page," and include the message "Returned results successfully" 1930 indicating that there were no errors.

Figure 20 is a block diagram illustrating an electronic device for providing page reports according to one embodiment.

The electronic device 2000 in FIG. 20 may correspond to the electronic device 100 in this application specification.

According to one embodiment, the electronic device 2000 of the present invention may include a transceiver 2010, a processor 2020, and a memory 2030. Since the components shown in FIG. 20 are not essential for implementing the electronic device, those skilled in the art will understand that the electronic device 2000 described herein may include more or fewer components than those listed above. Furthermore, in this embodiment, the processor 2020 may include at least one processor. Furthermore, the electronic device 100 may provide a report including test results information via a display (not shown), but is not limited thereto.

Transceiver 2010 can communicate with an external device using wired or wireless communication technologies, and includes transceiver 2010. The external device can be a terminal or a server. Furthermore, the communication technologies used by transceiver 2010 may include, but are not limited to, GSM (global system for mobile communication), CDMA (code division multiple access), LTE (long term evolution), 5G (5th Generation Mobile Communication Technology), WLAN (wireless LAN), Wi-Fi (wireless fidelity), Bluetooth ^™ , RFID (radio frequency identification), infrared data association (IrDA), ZigBee, and NFC.

According to one embodiment, transceiver 2010 can transmit a report including test result information to an external data storage. Furthermore, transceiver 2010 can receive traffic data of the basic environment and traffic data of the test environment from an external data storage or server 110.

Processor 2020 controls the overall operation of electronic device 2000 and processes data and signals. Processor 2020 can implement the methods described in Figures 1 through 19 . Processor 2020 controls the implementation of electronic device 2000 by interacting with transceiver 2010 and memory 2030 , as well as other components that electronic device 2000 may include. According to one embodiment, the processor 2020 may identify a target page, identify a base environment and a test environment, identify a first page corresponding to the target page in the base environment and a second page corresponding to the target page in the test environment based on configuration information for comparison between the pages, perform a test to detect at least one of differences between the first page and the second page and errors included in the first page and the second page, and provide a report including information on the results of the test.

Memory 2030 can store information used to implement at least one of the methods described above with reference to Figures 1 through 19. Memory 2030 can be referred to as a memory and can be either volatile or non-volatile. Furthermore, memory 2030 can store one or more commands required to execute the actions of processor 1520 and can temporarily store data stored on the platform or in external memory. For example, memory 2030 may correspond to data storage 350 in Figure 3, but is not limited thereto. Data storage 350 is located external to electronic device 2000.

On the other hand, this specification and accompanying drawings disclose preferred embodiments of the present invention. Although specific terms are used, they are used in a general sense only to illustrate the technical content of the present invention and facilitate understanding of the invention, and are not intended to limit the scope of the present invention. Those skilled in the art will readily appreciate that in addition to the embodiments disclosed herein, other variations based on the technical principles of the present invention may be implemented.

The electronic device or terminal of the above-mentioned embodiment may include a processor, a memory for storing and executing program data, a permanent storage such as a disk drive, a communication port for communicating with external devices, and a user interface device such as a touch panel, keys, or buttons. The method implemented by the software module or algorithm may be stored on a computer-readable recording medium as computer-readable code or program commands executable on the above-mentioned processor. Here, computer-readable recording media include magnetic storage media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disks, hard disks, etc.) and optical readable media (e.g., compact disc read-only memory (CD-ROM) and digital versatile disc (DVD)). Computer-readable recording media are distributed across computer systems connected to a network, enabling the storage and execution of computer-readable code in a distributed manner. The media can be read by the computer, stored in memory, and executed by the processor.

This embodiment can be represented by functional blocks and various processing steps. These functional blocks can be implemented using various hardware and/or software components that perform specific functions. For example, an embodiment can be implemented using integrated circuits that can perform various functions, such as memory, processing, logic, and lookup tables, controlled by one or more microprocessors or other control devices. Components can be implemented using software programs or software components. Similarly, this embodiment includes various algorithms implemented using combinations of data structures, programs, routines, or other program components. Therefore, they can be implemented using programming or scripting languages such as C, C++, Java, assemblers, and Python. Functionally, this can be achieved through algorithms executed on one or more processors. Furthermore, this embodiment can utilize existing technologies for electronic environment configuration, signal processing, and/or data processing. Terms such as "mechanism," "element," "mechanism," and "configuration" are used broadly and are not limited to mechanical or physical configurations. These terms can be associated with processors and include software routines.

The above embodiment is merely an example, and other embodiments may be implemented within the scope of the invention application described below.

S210: Step S220: Step S230: Step S240: Step S250: Step

Claims (12)

A method for providing a page report, which is performed by an electronic device, includes the following steps: confirming a target page; confirming a basic environment and a test environment; confirming a first page corresponding to the target page in the basic environment and a second page corresponding to the target page in the test environment based on setting information for comparison between the pages; performing a test on at least one of a difference between the first page and the second page, and an error included in the first page and the second page. ; and providing a report including information on the results of the implementation of the above-mentioned test, wherein the steps of confirming the above-mentioned basic environment and the above-mentioned test environment include the following steps: based on the number of visits corresponding to the traffic data of the above-mentioned basic environment collected through batches, confirming that the above-mentioned number of visits is above the set first critical value for the above-mentioned basic environment; and based on the number of visits corresponding to the traffic data of the above-mentioned test environment collected through online, confirming that the above-mentioned number of visits is above the set second critical value for the above-mentioned test environment. A method for providing a page report as claimed in claim 1, wherein the setting information includes at least one of information of excluding a first element among the elements included in the page from the comparison between the pages, and information of including a second element among the elements included in the page in the comparison between the pages. The method for providing a page report as claimed in claim 2, wherein the first page and the second page are pages that do not include the first element but include the second element. The method for providing a page report as recited in claim 1, wherein the step of performing the test comprises the following steps: performing an A/B test on the first page and the second page based on the test setting information of the test. The method for providing a page report as claimed in claim 1, wherein the step of confirming the first page and the second page comprises the following steps: using the first thread and the second thread to confirm the first page and the second page in parallel; and the step of performing the test comprises the following steps: performing a test on the difference between the first page and the second page by the main thread. A method for providing a page report as claimed in claim 1, wherein the step of providing the above-mentioned report includes the following step: providing the above-mentioned report including a comparison image showing the difference between the above-mentioned first page and the above-mentioned second page by a sliding icon. A method for providing a page report as claimed in claim 1, wherein the step of providing the above-mentioned report includes the following steps: based on the difference between the above-mentioned first page and the above-mentioned second page, confirming that the first element is different from the element included in the above-mentioned second page that corresponds to the element of the above-mentioned first page; and providing the above-mentioned report including the above-mentioned second page displaying the above-mentioned first element. A method for providing a page report as claimed in claim 1, wherein the step of providing the above-mentioned report includes the following steps: confirming, in the second source code corresponding to the above-mentioned second page, a source code that is different from the first source code corresponding to the above-mentioned first page, namely a third source code; and providing the above-mentioned report including the above-mentioned second source code displayed with the above-mentioned third source code. A method for providing a page report as claimed in claim 1, wherein the error comprises at least one of a first console error corresponding to the first page, a second console error corresponding to the second page, and a loading error of a resource included in the page. The method for providing a page report of claim 1, wherein the difference between the first page and the second page includes at least one of a difference in images, text, and resources between the pages. An electronic device for providing a page report includes: a transceiver; a memory storing one or more commands; and a processor for identifying a target page; identifying a basic environment and a test environment; identifying a first page corresponding to the target page in the basic environment and a second page corresponding to the target page in the test environment based on setting information for comparison between the pages; performing a comparison of the difference between the first page and the second page, and the difference between the first page and the second page. and providing a report including result information of the execution of the above-mentioned test, wherein the above-mentioned processor is further configured to: confirm the above-mentioned basic environment with the above-mentioned access number being above a set first critical value based on the access number corresponding to the traffic data of the above-mentioned basic environment collected by batch; and confirm the above-mentioned test environment with the above-mentioned access number being above a set second critical value based on the access number corresponding to the traffic data of the above-mentioned test environment collected by online. A non-transitory computer-readable recording medium records a program for executing the method of claim 1 on a computer.