Multi-version parallel test method for web pages and server

Abstract

The invention discloses a multi-version parallel test method for web pages and a server. A web framework receives a page rendering request which is submitted by a web application for rendering a certain page of the web; before a page rendering engine renders the certain page of the web, a page processing logic is skipped from a page processing module of the web framework and / or a page rendering module of the rendering engine to the same test execution module for executing AB test on the certain page of the web, and a selected reversion scheme of the certain page of the web is returned to the web framework; the web page is rendered according to the selected reversion scheme of the certain page of the web. A high-efficiency and flexible general method for multi-version parallel test of the web page and a system are realized and are suitable for different web frameworks and different rendering engines; the problem of system invasion caused by multi-version parallel test is solved; the multi-version parallel test execution logic can be reused and is convenient to expand; a test strategy can be flexibly adjusted and can dynamically take effect instead of being issued.

Description

technical field [0001] This application relates to the field of website application promotion, in particular to a multi-version parallel testing method and server for website pages. Background technique [0002] Website operators hope that every visitor can stay on their website as much as possible, and it is best to register as a user, and more ideally, to become a paying user or successfully place an order to bring benefits to the website. The realization of these expectations, on the one hand, depends on whether the website itself can provide the core business that users need; on the other hand, it depends on the typesetting layout, color matching, text description, process design and correlation of display data of the website page. These factors will affect the attractiveness of the website to users, and ultimately affect the user's favorability and conversion rate. [0003] In order to achieve the expected purpose, most websites constantly revise and optimize the websi...

AI Technical Summary

Problems solved by technology

[0011] First of all, before AB testing is carried out on the subsystems of each website application, it is necessary to embed an AB split test strategy in a certain page processing sub-module of each website application. In the module, it is very intrusive to the website application, it is difficult to maintain and manage, and it is easy to cause system problems and failures. However, each website framework and rendering engine is usually developed by a third party, and the source code cannot be modified. The commercial license to embed the AB split test strategy in the three-party website framework and rendering engine;

[0012] Secondly, the AB test needs to adjust the test strategy according to the actual situation during the test period. For example, the diversion hit ratio of the revision plan A1 of page A is increased from 5% to 10%. Every time the test strategy is adjusted, it needs to be re-modified. AB test logic in submodules, and re-release, low flexibility;

[0013] Again, a key step in the AB test is to calculate which revision plan the current user client request hits according to the test strategy. This process divides the user clients of the AB test. There are many types of user client distribution methods, for example: random ratio distribution , splitting according to the proportion of user clients, splitting by region and splitting by members and non-members, etc., when the developed AB split test execution logic is applied to other website applications or different sub-modules of the website application to perform AB tests, it is necessary to split AB The test execution logic is rewritten and embedded in the website application or each sub-module of the website application, which is cumbersome and has poor reusability

Images