Disclosure of Invention
The embodiment of the invention provides a test-based enterprise user distribution method and test-based enterprise user distribution equipment, which are used for increasing the distribution sample quantity of a platform during testing and improving the testing efficiency and the testing effect.
In a first aspect, an embodiment of the present application provides a test-based enterprise user offloading method, including:
acquiring an access request of an enterprise user; selecting an access page of a target version from the access pages of the multiple versions according to the generation time of the access request and the user information of the enterprise user; and shunting the access request to the access page of the target version.
It can be known that, in the method provided by the present embodiment, the offloading policy for each access request initiated by the enterprise user is not only related to the user information of the enterprise user, but also related to the generation time corresponding to the access request. Through such a mode, the number of shunting samples in the testing process can be greatly expanded, so that the testing efficiency of the TO B platform is not limited by the number of enterprise users, and the testing effect is improved.
Optionally, selecting a target version of the access page from the multiple versions of the access page according to the generation time of the access request and the user information of the enterprise user, where the selecting includes: determining a shunting identifier of the access request according to the generation time of the access request and the user information of the enterprise user; and performing Hash modular operation on the split stream identifier, and determining the target version and the page address of the access page corresponding to the target version according to the operation result of the Hash modular operation.
Optionally, determining a split identifier of the access request according to the access request generation time and the user information of the enterprise user includes: determining a time period to which the generation time of the access request belongs, and determining a time identifier of the access request according to the time period; determining an identity corresponding to user information of an enterprise user; and combining the time identification and the identity identification to obtain the shunting identification.
It can be known that the distribution identifier of each access request can be determined through the generation time of each access request and the user information of the enterprise user, so that the distribution processing of the access requests can be performed according to the distribution identifier, and the distribution uniformity and fairness are further ensured.
Optionally, the method further includes: laying access pages of a plurality of versions; the access pages of different versions adopt the same page layout, and the page contents in the access pages of different versions are generated based on different algorithms.
It can be known that, in the embodiment of the present application, pages of different versions of a platform are generated based on a page variable that cannot be perceived by a user, which will enable an access request initiated by the same enterprise user at different access times, and although the access request is distributed to access pages of different versions of the platform, the enterprise user does not perceive the distributed condition, which is beneficial to independence and fairness of distribution tests.
Optionally, the method further includes: further comprising: acquiring access data of access pages of various versions; and determining a shunting test result according to the access data.
In a second aspect, an embodiment of the present application provides a test-based enterprise user offloading device, including:
the access module is used for acquiring an access request of an enterprise user;
the shunting module is used for selecting an access page of a target version from the access pages of the multiple versions according to the generation time of the access request and the user information of the enterprise user; and shunting the access request to the access page of the target version.
Optionally, the shunting module is specifically configured to:
determining a shunting identifier of the access request according to the generation time of the access request and the user information of the enterprise user; and carrying out Hash modular operation on the shunting identification, and determining a target version and a page address of an access page corresponding to the target version according to an operation result of the Hash modular operation.
In a third aspect, an embodiment of the present application provides an electronic device, including: a memory, a processor; at least one processor; and
a memory;
the memory stores computer-executable instructions;
the at least one processor executing the computer-executable instructions stored by the memory causes the at least one processor to perform the method of the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when a processor executes the computer-executable instructions, the method according to the first aspect is implemented.
In a fifth aspect, the present application provides a computer program product comprising a computer program that, when executed by a processor, implements the method according to the first aspect.
The embodiment of the application provides an enterprise user distribution method and equipment based on testing, and in the process of testing a platform, a distribution strategy for each access request is not only related to user information of an enterprise user, but also related to generation time corresponding to the access request. Through such a mode, the number of shunting samples in the testing process can be greatly expanded, so that the testing efficiency of the TO B platform is not limited by the number of enterprise users, and the testing effect is improved.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Existing platforms are generally classified into a TO B platform and a TO C platform, wherein the TO C platform is a platform for providing platform services for individual users, such as a search service platform. The TO B platform is a platform for providing platform services for enterprise users, such as a service platform of an internal system of an enterprise and the like.
In order to better improve the product quality and the user experience, a plurality of platforms adopt a sub-test technology including a gray test or an AB test to test the current platforms of each version before the platforms are released formally, so as to determine the released platform version according to the test result.
In the existing test, the access users of the platform are generally distributed according to the principle of random distribution, so as to count behavior data of each user after distribution, and further obtain a test result. This type of testing requires a large number of test samples, which requires a certain number of user visits by the platform.
Specifically, taking the TO C platform as an example, fig. 1 is a schematic diagram of a scenario for testing the TO C platform.
The tested diversion policy is associated with the user identification of the individual user. As shown in fig. 1, when each of the individual users 1 to 6 initiates an access request to the platform, the platform allocates a fixed user identifier to the user, and the identifier serves as a split basis, that is, after the individual user 1 initiates an access request, the platform returns an access page of version 1 to the individual user 1 according to the user identifier of the individual user 1.
By the aid of the shunting and testing method, behavior data of each individual user in the access page of the version 1 and behavior data of each individual user in the access page of the version 2 can be obtained, and different versions of the access page can be evaluated according to different behavior data. This also makes it possible TO test TO C platforms using testing techniques, since TO C platforms have a sufficient amount of user access.
However, it can be known that, for the TO B platform, because it is oriented TO enterprise users, and the number of general enterprise users is small, when the TO B platform tests the platform by using the shunting manner described above, problems such as a small number of samples per version, low testing efficiency, etc. occur, and these problems will severely limit platform development.
In the face of the above problems, the present application analyzes and finds out the sample units of the shunting samples that can be used by the current TO B platform:
in the prior art, the split samples after the splitting of the user generally take each user as a sample unit, and for the same user, the page of the version that can be accessed by the platform each time the same user accesses is the same.
In order to increase the number of split samples obtained from each version, the present application contemplates changing the sample unit, i.e., instead of using each user as a sample unit, the method changes to using the visit of each user in each time period as a sample unit. That is, in the process of conducting the offloading test on the TO B platform, the offloading policy for each access request is related not only TO the user information of the enterprise user, but also TO the generation time corresponding TO the access request.
By the mode, the number of the shunt samples in the testing process can be greatly increased, so that the testing efficiency of the TO B platform is not limited by the number of enterprise users, and the testing effect is improved.
Referring to fig. 2, fig. 2 is a schematic diagram of a network architecture based on the present application, and the network architecture shown in fig. 2 may specifically include a server 1 and a terminal 2.
The server 1 may be a server cluster disposed in a cloud. The server 1 may specifically carry a platform providing functions such as page access and page operation processing for enterprise users, the platform stores, processes, and receives and transmits page related data, and the platform provides access related services for the enterprise users through communication with the terminal 2.
The terminal 2 may be a hardware device with a network communication function, which includes but is not limited to a smart phone, a tablet computer, a desktop computer, an internet of things device, and the like. The enterprise user sends a plurality of access requests for the platform to the server 1 through the terminal 2 to access the service platform erected in the server 1, so as to obtain related services.
When the version of the platform is updated or upgraded, the enterprise user distribution method based on the test provided by the application can be used for distributing and testing pages of different versions, wherein the specific test mode includes but is not limited to an AB test, a gray test and the like. Specifically, the shunting device is additionally arranged in the server to shunt the access requests received by the platform, so that the access requests of the enterprise users can be shunted to the access pages of the corresponding versions, and the platform in the server can be tested.
The test-based enterprise user offloading method according to the embodiment of the present application is described in detail below with reference to specific embodiments. The following embodiments may be combined with each other and may not be described in detail in some embodiments for the same or similar concepts or processes.
It should be noted that the main execution body of the test-based enterprise user offloading method provided in this embodiment is a test-based enterprise user offloading device, which is carried in the aforementioned server, and the offloading method according TO the present application is performed for a TO B platform, and the platform is also disposed in the aforementioned server. For the TO B platform, the user attributes of the enterprise users it serves are enterprise attributes.
For example, for a sales platform, enterprise a, enterprise B, and enterprise C are platform users of the platform. Enterprise a, enterprise B, and enterprise C may each utilize the sales related functions provided by the sales platform to implement operations such as management, inventory, and statistics of sales data within the enterprise, and enterprise a, enterprise B, and enterprise C may all be used as enterprise users in the present application.
Fig. 3 is a flowchart illustrating an enterprise user offloading method based on testing according to an embodiment of the present disclosure. As shown in fig. 3, the test-based enterprise user offloading method may include the following steps:
step 301, obtaining an access request of an enterprise user.
And step 302, selecting a target version of the access page from the multiple versions of the access page according to the generation time of the access request and the user information of the enterprise user.
And step 303, shunting the access request to an access page of a target version.
It should be noted that, in the process of testing the access pages of different versions of the platform, the enterprise user is unaware of the shunting situation of the enterprise user. For each enterprise user, the platform can be continuously accessed and used according to actual requirements, and during the processing of the access request of the enterprise user, the shunting device is started and triggered to execute the corresponding shunting method.
Specifically, when an enterprise user initiates an access request to the platform, the platform receives the access request, and at this time, the offloading device disposed in the same server as the platform captures the request and performs corresponding offloading processing.
Unlike the conventional splitting of access requests based on user identification, the splitting in the embodiment of the present application is determined based on the generation time of the access request and the user information of the enterprise user at the same time. That is, the flow splitting device may determine the flow splitting identifier of the access request according to the generation time of the access request and the user information of the enterprise user, then perform hash modulo operation on the flow splitting identifier, and determine the target version and the page address of the access page corresponding to the target version according to the operation result of the hash modulo operation.
Fig. 4 is a schematic data interaction diagram of a test-based enterprise user offloading method, as shown in fig. 4, after an enterprise user sends an access request TO a server through a terminal, the access request is sent TO a TO B platform, and a test-based enterprise user offloading device continuously monitors the platform in real time TO capture and acquire the access request when the platform receives the access request.
After the shunting device obtains the access request, the shunting identification of the access request is determined and obtained by utilizing the generation time of the access request and the user information of the enterprise user, and therefore the target version is determined based on the shunting identification.
In the process of determining the target version, in order to ensure the uniformity of the distribution, the distribution device determines the target version targeted by the current access by adopting a hash modulo operation mode. And performing operation processing on each identification bit in the split stream identification by adopting a preset modulo operation rule to obtain a corresponding operation result, wherein the operation result determines a target version corresponding to the access request.
Of course, in order to ensure the uniformity of the shunting, the correspondence between the operation result and the versions should be related to the number of versions. For example, if the operation result is in the range of 0-9 and the number of versions is 2, then the access requests with operation results of 0-4 may be split into version 1 and the access requests with operation results of 5-9 may be split into version 2 to ensure the average split. The correspondence between the shunting identifications and the versions is only an example, and a person skilled in the art can set the correspondence between the shunting identifications and the versions according to actual situations.
For the split flow identifier in the present embodiment, the specific form may be represented in a character string form, and the relationship between the split flow identifier and the generation time of the access request may be associated in various ways. In an alternative example, the split flag may be obtained as follows: determining a time period to which the generation time of the access request belongs, and determining a time identifier of the access request according to the time period; determining an identity corresponding to user information of an enterprise user; and combining the time identification and the identity identification to obtain the shunting identification.
Wherein the time identification of the access request will be related to the time period to which the generation time belongs, and the period unit of the time period may be generally a natural day, a week, or a month or even a year, etc.
Fig. 5 is a schematic shunting diagram of a test-based enterprise user shunting method. As shown in fig. 5, assuming that the generation time of a certain access request is 10 o' clock 00 min 00 s on 2/22/2022, the time stamp of the access request can be represented as 20220222 when the cycle unit is natural day, and the time stamps of other enterprise users who initiate access requests on the day of 2/22/2022 will also be represented as 20220222. When the period unit is one month, the time stamp of the access request can be represented as 202202.
It can be known that, for the period unit of the time period, a person skilled in the art can select it according to the actual situation, and the embodiment of the present application does not limit it.
In other alternative embodiments, the time identification for the access request may also be generated based on mathematical characteristics of the generation time. For example, the time identification of the access request may be determined according to the parity of a certain time bit in the generation time.
For example, when the natural day bit in the generation time is an odd number of days, the time stamp of the access request may be represented as 01, and when the natural day bit in the generation time is an even number of days, the time stamp of the access request may be represented as 02. Taking the generation time of a certain access request as 2022 years, 2 months and 22 days as an example, the time identifier of the access request can be represented as 02 since the natural day in the generation time is 22 days. Of course, the time positions can also be month positions, year positions and the like.
The above-mentioned manner only provides a possible determination manner of the time identifier, and those skilled in the art may also adopt other possible implementation manners according to the idea to determine the time identifier according to the generation time of the access request, which is not limited too much in this application.
Meanwhile, the shunting detection device also needs to determine an identity corresponding to the user information of the enterprise user, and generally, the identity is a fixed identity, that is, each enterprise user is assigned an identity when completing platform registration so as to indicate the identity of the enterprise user. In the embodiment of the present application, the identity identifier and the aforementioned time identifier together form a split flow identifier.
For example, if the time identifier of a certain access request is 20220222 and the identity identifier of an enterprise user is 12345, the split stream identifier can be obtained directly through the listed combination, such as 2022022212345; some mathematical operations may also be performed to obtain the split flag, such as adding 20220222+12345 to 20232567, where 20232567 may be the split flag.
By the method, the shunting identification can be effectively generated, the tested shunting samples are effectively multiplied, and more test results can be provided for the test.
It is of course known that for the same enterprise user, the same enterprise user may access different versions of the access page due to the inconsistency of access times each time the platform is accessed. In order to ensure the independence between test split samples, when the access pages of different versions are laid, the following characteristics exist among the pages of the access versions in the embodiment: the same page layout is adopted by different versions of the access pages, and the page contents in the different versions of the access pages are generated based on different algorithms.
Fig. 6 is an interface diagram of a test-based enterprise user offloading method, and as shown in fig. 6, this example shows a process of generating an access page by an offloading device, where the access page displays a plurality of selectable items such as a data list, data monitoring and data management, and in this option, detailed data contents of data a, data B, data C and data D are displayed.
For the access page of the version 1, the data in the data list are distributed by adopting an algorithm A, namely the data A, the data B, the data C and the data D are sequentially displayed; for the access page of version 2, each data in the data list is distributed by using the algorithm B, that is, the data content of the data a, the data C, the data D and the data B is displayed in sequence.
It can be seen that the page layout in the version 1 access page and the page layout in the version 2 access page are completely consistent, as are the layouts of the selectable options operable as data lists, data monitoring and data management.
The page contents are different between different versions, for example, the display order of the list contents of the data list is different, and the determination of the display order of each data in the list contents is realized based on different algorithms. For the enterprise user, the different display sequences of the data will not affect the operation and use of the data by the enterprise user, i.e. the data list adopting the different data display sequences will not bring more user perception to the operation service of the enterprise user.
Based on this, two access requests initiated by the same enterprise user at different times may be respectively split to access pages of different versions. Where only the differences in page content will not be perceived by the enterprise user since the page layouts of the different versions are the same. Through the setting mode of the access pages with different versions, the mode of determining the shunting version according to the generation time of the access request and the user information of the enterprise user becomes possible.
Of course, in an alternative embodiment, different access requests may be distributed to access pages of different versions through the above steps, and meanwhile, the server may further obtain access data of the access pages of each version; and determining the shunting test result of the platform according to the access data.
Specifically, the access data may be obtained by performing a buried point on each version of the access page. By calculating various test indexes of the access data, the shunting test result of each platform can be analyzed and determined. The test indexes include but are not limited to: click rate, number of clicks, dwell time, etc.
The embodiment of the application provides a test-based enterprise user distribution method, and in the process of testing a platform, a distribution strategy for each access request is not only related to user information of an enterprise user, but also related to generation time corresponding to the access request. Through such a mode, the number of shunting samples in the testing process can be greatly expanded, so that the testing efficiency of the TO B platform is not limited by the number of enterprise users, and the testing effect is improved.
Fig. 7 is a block diagram of a test-based enterprise user offloading device according to an embodiment of the present application, which corresponds to the test-based enterprise user offloading method provided in the foregoing embodiment. For convenience of explanation, only portions related to the embodiments of the present application are shown. Referring to fig. 7, the test-based enterprise user offloading device is provided in a server, and the test-based enterprise user offloading device includes: an access module 710 and a shunting module 720.
The access module 710 is used for acquiring an access request of an enterprise user;
the splitting module 720 is used for selecting an access page of a target version from the access pages of the multiple versions according to the generation time of the access request and the user information of the enterprise user; and shunting the access request to the access page of the target version.
In an optional embodiment, the shunting module 720 is specifically configured to:
determining a shunting identifier of the access request according to the generation time of the access request and the user information of the enterprise user; and performing Hash modular operation on the split stream identifier, and determining the target version and the page address of the access page corresponding to the target version according to the operation result of the Hash modular operation.
In an optional embodiment, the shunting module 720 is specifically configured to:
determining a time period to which the generation time of the access request belongs, and determining a time identifier of the access request according to the time period; determining an identity corresponding to user information of an enterprise user; and combining the time identification and the identity identification to obtain the shunting identification.
In an optional embodiment, the shunt detection device further comprises: an access page generation module;
the access page generation module is used for laying access pages of a plurality of versions;
the access pages of different versions adopt the same page layout, and the page contents in the access pages of different versions are generated based on different algorithms.
In an alternative embodiment, the method further comprises: an analysis module;
the analysis module is used for acquiring access data of the access pages of all versions; and determining a shunting test result according to the access data.
The embodiment of the application provides a test-based enterprise user shunting device, and in the process of testing a platform, a shunting strategy for each access request is not only related to user information of an enterprise user, but also related to generation time corresponding to the access request. Through such a mode, the number of shunting samples in the testing process can be greatly expanded, so that the testing efficiency of the TO B platform is not limited by the number of enterprise users, and the testing effect is improved.
Fig. 8 is a schematic diagram of a hardware structure of an electronic device provided in the present application, and as shown in fig. 8, an embodiment of the present application provides an electronic device, a memory of the electronic device may be configured to store at least one program instruction, and a processor is configured to execute the at least one program instruction, so as to implement the technical solution of the above method embodiment. The implementation principle and technical effect are similar to those of the embodiments related to the method, and are not described herein again.
The embodiment of the application provides a chip. The chip comprises a processor for calling a computer program in a memory to execute the technical solution in the above embodiments. The principle and technical effects are similar to those of the related embodiments, and are not described herein again.
The embodiment of the present application provides a computer program product, which, when running on an electronic device, enables the electronic device to execute the technical solutions in the above embodiments. The principle and technical effects are similar to those of the related embodiments, and are not described herein again.
The embodiment of the present application provides a computer-readable storage medium, on which program instructions are stored, and when the program instructions are executed by an electronic device, the electronic device is enabled to execute the technical solutions of the above embodiments. The principle and technical effects are similar to those of the related embodiments, and are not described herein again.
The above embodiments are only for illustrating the embodiments of the present invention and are not to be construed as limiting the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the embodiments of the present invention shall be included in the scope of the present invention.