Multi-version web page access test method

Abstract

The invention relates to a multi-version web page access test method, which includes the following steps: step ①, after the user accesses the original page, it is judged whether the user has ever visited the page. In step ②, it is determined whether the original page that the user is currently visiting is the original version. Step ③, return to the server side, and parse the page parameters. In step ④, it is judged whether the visit is redirected or not. Step ⑤, continue to load the original content and update the browser cookie value. After step ⑥ and step ③ are completed, match the page parameters with the new address. Step ⑦, return to the new address. Step ⑧, open the new version of the address, and the browser updates the cookie value. Thereby, it is possible to correspond to effective testing of multi-version web pages. And, it can support static and dynamic pages. Furthermore, the present invention supports tracking and comparison of various webpage data indicators of multiple sets of webpages participating in the experiment, which is convenient for subsequent debugging.

Description

technical field [0001] The invention relates to a testing method, in particular to a multi-version web page access testing method. Background technique [0002] There are not many suppliers in the industry that provide multi-version web page A / B testing services, and most of them are foreign, such as Google Analytics, Visual Website Optimizer, etc. [0003] For commonly used testing requirements, the problems existing in existing methods are listed as follows: [0004] 1. Only one set of pages is supported for A / B testing. When the overall style of the website needs to be revised, it is not possible to conduct A / B testing on only one set of pages each time (because the appearance of inconsistent styles at the same time will confuse people). [0005] 2. Static pages are not supported. The original multi-version web page A / B test method needs to import the old version parameters into the new version address when jumping to the new version. There is no problem with some dynami...

AI Technical Summary

Problems solved by technology

[0004] 1. Only support A / B testing of one set of pages. When the overall style of the website needs to be revised, it is not possible to conduct A / B testing on only one set of pages each time (because the appearance of inconsistent styles at the same time will make people very confused)

[0005] 2. Static pages are not supported. The original multi-version web page A / B test method needs to import the old version parameters into the new version address when jumping to the new version. There is no problem with some dynamic pages, but there is no way to use it for pages with static addresses. , because the static page itself does not take any parameters, and the parameters may already be included in the path or file name of the URI (UniformResource Identifier)

[0006] 3. Only the conversion rate of different versions can be judged according to the conversion status of a specified page, and the indicator is single

Images