CN110990275B - Page display test method and device for mobile banking - Google Patents
Page display test method and device for mobile banking Download PDFInfo
- Publication number
- CN110990275B CN110990275B CN201911198819.2A CN201911198819A CN110990275B CN 110990275 B CN110990275 B CN 110990275B CN 201911198819 A CN201911198819 A CN 201911198819A CN 110990275 B CN110990275 B CN 110990275B
- Authority
- CN
- China
- Prior art keywords
- party merchant
- web page
- page
- merchant web
- mobile banking
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Data Mining & Analysis (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephone Function (AREA)
Abstract
The application provides a page display test method and device for a mobile phone bank, which are applied to a third-party merchant test tool independent of a mobile phone bank server. And after the service call data passes the verification, the service call data is sent to the mobile phone bank server, so that the safety of the information in the mobile phone bank can be ensured.
Description
Technical Field
The application relates to the technical field of mobile banking, in particular to a page display test method and device of a mobile banking.
Background
With the expansion requirement of mobile banking business, more and more third-party merchants (such as telephone charge recharging) pages are displayed on mobile banking living channels, so that users can conveniently use services provided by the third-party merchants.
In order for the third party merchant pages to be reliably displayed, the display of each third party merchant page needs to be tested. At present, in view of internal information security of a bank, a testing process is mainly deployed at one end of a mobile banking server, but the mobile banking server is overloaded due to the mode.
Disclosure of Invention
In order to solve the technical problems, the embodiment of the application provides a method and a device for testing page display of a mobile phone bank, so as to achieve the purpose of reducing the burden of a mobile phone bank server, and the technical scheme is as follows:
the page display testing method of the mobile phone bank is applied to a third party merchant testing tool independent of a mobile phone bank server, and comprises the following steps:
responding to a page selection request input by a user on a test client, and displaying and storing a third-party merchant web page corresponding to the page selection request;
responding to a service call request returned by the third-party merchant web page, acquiring service call data in the third-party merchant web page, analyzing and checking the service call data, and sending the service call data to a mobile banking server after the service call data passes the check;
receiving a processing result returned by the mobile banking server aiming at the service call data;
displaying and storing a third-party merchant web page corresponding to the processing result;
and taking the third-party merchant web page corresponding to the page selection request and the third-party merchant web page corresponding to the processing result as the basis of the page display test.
Preferably, the responding to the page selection request input by the user on the test client, displaying and storing the third party merchant web page corresponding to the page selection request includes:
responding to a page selection request input by a user on a test client, acquiring page configuration information input by the user in advance, and generating a third-party merchant web page corresponding to the page selection request according to the page configuration information;
and displaying and storing the third-party merchant web page corresponding to the page selection request.
Preferably, the sending the service call data to a mobile banking server includes:
assembling the service call data according to the data format recognizable by the mobile banking server, and sending the assembled data to the mobile banking server;
the receiving the processing result returned by the mobile phone banking server aiming at the service calling data comprises the following steps:
and receiving a processing result returned by the mobile banking server aiming at the service call data, and assembling the processing result into data identifiable by the third-party merchant testing tool.
Preferably, the service call request returned by the third-party merchant web page is initiated by the third-party merchant testing tool according to an operation mode program.
Preferably, the service call request returned by the third-party merchant web page is input by the user at the third-party merchant web page.
The utility model provides a mobile banking's page show testing arrangement, is applied to the third party merchant testing tool that is independent of mobile banking server, and the device includes:
the first display and storage module is used for responding to a page selection request input by a user on the test client, and displaying and storing a third-party merchant web page corresponding to the page selection request;
the calling module is used for responding to a service calling request returned by the third-party merchant web page, acquiring service calling data in the third-party merchant web page, analyzing and checking the service calling data, and sending the service calling data to a mobile banking server after the service calling data passes the check;
the receiving module is used for receiving a processing result returned by the mobile banking server aiming at the service call data;
the second display and storage module is used for displaying and storing the third-party merchant web page corresponding to the processing result;
and the determining module is used for taking the third-party merchant web page corresponding to the page selection request and the third-party merchant web page corresponding to the processing result as the basis of the page display test.
Preferably, the first display and save module is specifically configured to:
responding to a page selection request input by a user on a test client, acquiring page configuration information input by the user in advance, and generating a third-party merchant web page corresponding to the page selection request according to the page configuration information;
and displaying and storing the third-party merchant web page corresponding to the page selection request.
Preferably, the calling module is specifically configured to:
assembling the service call data according to the data format recognizable by the mobile banking server, and sending the assembled data to the mobile banking server;
the receiving module is specifically configured to:
and receiving a processing result returned by the mobile banking server aiming at the service call data, and assembling the processing result into data identifiable by the third-party merchant testing tool.
Preferably, the service call request returned by the third-party merchant web page is initiated by the third-party merchant testing tool according to an operation mode program.
Preferably, the service call request returned by the third-party merchant web page is input by the user at the third-party merchant web page.
Compared with the prior art, the application has the beneficial effects that:
according to the application, based on the third-party merchant testing tool independent of the mobile banking server, the display testing flow of the third-party merchant web page of the mobile banking is deployed in the third-party merchant testing tool, so that the mobile banking server only needs to perform data interaction with the third-party merchant testing tool, the resource occupation of the mobile banking server is reduced, and the burden of the mobile banking server can be reduced. And after the service call data passes the verification, the service call data is sent to the mobile phone bank server, so that the safety of the information in the mobile phone bank can be ensured.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.
Fig. 1 is a flowchart of an embodiment 1 of a method for testing page display of a mobile banking machine;
fig. 2 is a flowchart of an embodiment 2 of a method for testing page display of a mobile banking machine according to the present application;
FIG. 3 is a flowchart of an embodiment 3 of a method for testing the page display of a mobile banking machine;
fig. 4 is a schematic diagram of a logic structure of a page display testing device of a mobile banking.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
In the process of exploring how to solve the technical problem of overlarge burden of a mobile phone banking server, the inventor considers that the safety of the internal information of the mobile phone banking needs to be ensured while the burden of the mobile phone banking server is reduced, so that a third party merchant testing tool independent of the mobile phone banking server is provided.
In particular, the third party merchant testing tool may include: the interface display module, the interface interaction module and the simulation operation module.
Wherein, interface show module: the function of configuring the interface main diagram and the web page is provided, and the display effect of the mobile phone bank can be simulated.
Interface interaction module: and providing all callable APIs of the third-party merchant, wherein the interaction with a bank background product is involved, and the analysis and the assembly of the internet message are required.
All callable APIs for third party merchants may include, but are not limited to:
the method comprises the steps of acquiring an API of client information, jumping to a login page, returning to an API of a mobile phone bank home page, calling an API of a payment control, acquiring an API of a login state, an API of a WeChat sharing link, opening an API of a WeChat applet, acquiring an API of current positioning information, acquiring an API of a local image file, generating an API of a two-dimensional code, identifying the two-dimensional code, monitoring acceleration, jumping to an application market, dialing a call or opening APIs of other APPs.
The API calling the payment control has the highest requirement on information security, and the embodiment preferably ensures the information security related to calling the API of the payment control.
And the simulation operation module: and simulating clicking events of basic operation of the client, and saving the screenshot for testing web pages of third-party merchants.
Next, a page display test method of a mobile phone bank applied to a third party merchant test tool independent of a mobile phone bank server is introduced, as shown in fig. 1, and a flowchart of an embodiment 1 of the page display test method of the mobile phone bank provided by the application may include the following steps:
and step S11, responding to a page selection request input by a user on the test client, and displaying and storing a third-party merchant web page corresponding to the page selection request.
And step S12, responding to a service call request returned by the third-party merchant web page, acquiring service call data in the third-party merchant web page, analyzing and checking the service call data, and sending the service call data to a mobile banking server after the service call data passes the check.
Because the interface interaction module of the third-party merchant testing tool provides all callable APIs of the third-party merchant, the third-party merchant testing tool supports service call, and can specifically receive a service call request through the third-party merchant web page, the third-party merchant testing tool responds to the service call request returned by the third-party merchant web page, analyzes and checks the service call data, and sends the service call data to the mobile banking server after the service call data passes the check.
Parsing and checking the service call data can be understood as: analyzing the public key of the third-party merchant from the service call data, forwarding the public key of the third-party merchant to a certificate verification background, and confirming the validity of the third-party merchant configuration by the verification background; and analyzing the authority of the third-party merchant, and checking the legitimacy of calling the simulated interactive interface.
Preferably, the service call request returned by the third-party merchant web page can be initiated by the third-party merchant testing tool according to the operation mode program. The third-party merchant testing tool is initiated according to the operation mode program, so that full automation of the testing process can be realized, manual participation is not needed, and the testing efficiency is improved.
Of course, the service call request returned by the third party merchant web page may also be input by the user at the third party merchant web page.
And step S13, receiving a processing result returned by the mobile phone banking server aiming at the service call data.
And step S14, displaying and storing the third-party merchant web page corresponding to the processing result.
And S15, taking the third-party merchant web page corresponding to the page selection request and the third-party merchant web page corresponding to the processing result as the basis of the page display test.
Of course, the tester can monitor the display effect of the third party merchant web page in the display process of the various third party merchant web pages, specifically monitor whether the UI of the third party merchant web page is deformed, whether the button is invalid or whether the background picture is not fully displayed.
According to the application, based on the third-party merchant testing tool independent of the mobile banking server, the display testing flow of the third-party merchant web page of the mobile banking is deployed in the third-party merchant testing tool, so that the mobile banking server only needs to perform data interaction with the third-party merchant testing tool, the resource occupation of the mobile banking server is reduced, and the burden of the mobile banking server can be reduced. And after the service call data passes the verification, the service call data is sent to the mobile phone bank server, so that the safety of the information in the mobile phone bank can be ensured.
As another alternative embodiment of the present application, referring to fig. 2, a flow chart of an embodiment 2 of a method for testing page display of a mobile phone bank according to the present application is provided, and this embodiment is mainly a refinement of the method for testing page display of a mobile phone bank described in the foregoing embodiment 1, as shown in fig. 2, where the method may include, but is not limited to, the following steps:
and S21, responding to a page selection request input by a user on a test client, acquiring page configuration information input by the user in advance, and generating a third-party merchant web page corresponding to the page selection request according to the page configuration information.
And S22, displaying and storing the third-party merchant web page corresponding to the page selection request.
Step S21 to step S22 are a specific embodiment of step S11 in example 1.
And S23, responding to a service call request returned by the third-party merchant web page, acquiring service call data in the third-party merchant web page, analyzing and checking the service call data, and sending the service call data to a mobile banking server after the service call data passes the check.
And step S24, receiving a processing result returned by the mobile phone banking server aiming at the service call data.
And S25, displaying and storing the third-party merchant web page corresponding to the processing result.
And S26, taking the third-party merchant web page corresponding to the page selection request and the third-party merchant web page corresponding to the processing result as the basis of the page display test.
The detailed procedure of steps S23-S26 can be referred to the relevant description of steps S12-S15 in embodiment 1, and will not be repeated here.
As another alternative embodiment of the present application, referring to fig. 3, a flow chart of an embodiment 3 of a method for testing page display of a mobile phone bank according to the present application is provided, and this embodiment is mainly a refinement of the method for testing page display of a mobile phone bank described in the foregoing embodiment 1, as shown in fig. 3, where the method may include, but is not limited to, the following steps:
and step S31, responding to a page selection request input by a user on the test client, and displaying and storing a third-party merchant web page corresponding to the page selection request.
And step S12, responding to a service call request returned by the web page of the third-party merchant, acquiring service call data in the web page of the third-party merchant, analyzing and checking the service call data, assembling the service call data according to a data format identifiable by the mobile banking server after the service call data passes the check, and transmitting the assembled data to the mobile banking server.
The step of assembling the service call data according to the data format recognizable by the mobile banking server and sending the assembled data to the mobile banking server is a specific implementation mode of sending the service call data to the mobile banking server in embodiment 1.
The process of assembling the service invocation data may include: removing verification information related to service call data; and replacing the message header and the field name in the service call data according to the data format which can be identified by the mobile banking server.
And step S33, receiving a processing result returned by the mobile phone banking server aiming at the service call data, and assembling the processing result into data identifiable by the third-party merchant testing tool.
The process of assembling the processing results into data recognizable by the third party merchant testing tool may include:
changing the message header and the field name in the processing result to enable the processing result to be identified by a third-party merchant testing tool;
verification information is added to the processing results.
Step S33 is a specific embodiment of step S13 in example 1.
And step S34, displaying and storing the third-party merchant web page corresponding to the processing result.
And step 35, taking the third-party merchant web page corresponding to the page selection request and the third-party merchant web page corresponding to the processing result as the basis of the page display test.
The detailed procedure of steps S34-S35 can be referred to in the related description of steps S14-S15 in embodiment 1, and will not be described here.
The application further provides a device for testing the page display of the mobile phone bank, and the device for testing the page display of the mobile phone bank and the method for testing the page display of the mobile phone bank can be correspondingly referred to each other.
Referring to fig. 4, the mobile banking page display testing device is applied to a third party merchant testing tool independent of a mobile banking server, and the mobile banking page display testing device includes: the system comprises a first exhibition saving module 11, a calling module 12, a receiving module 13, a second exhibition saving module 14 and a determining module 15.
The first display and storage module 11 is used for responding to a page selection request input by a user on a test client, and displaying and storing a third-party merchant web page corresponding to the page selection request;
the calling module 12 is configured to respond to a service calling request returned by the third-party merchant web page, obtain service calling data in the third-party merchant web page, analyze and verify the service calling data, and send the service calling data to a mobile banking server after verification is passed;
the receiving module 13 is used for receiving a processing result returned by the mobile banking server aiming at the service call data;
a second display and save module 14, configured to display and save a third party merchant web page corresponding to the processing result;
and the determining module 15 is configured to use the third party merchant web page corresponding to the page selection request and the third party merchant web page corresponding to the processing result as a basis for a page display test.
In this embodiment, the first display and save module 11 may specifically be configured to:
responding to a page selection request input by a user on a test client, acquiring page configuration information input by the user in advance, and generating a third-party merchant web page corresponding to the page selection request according to the page configuration information;
and displaying and storing the third-party merchant web page corresponding to the page selection request.
In this embodiment, the calling module 12 may specifically be configured to:
assembling the service call data according to the data format recognizable by the mobile banking server, and sending the assembled data to the mobile banking server;
the receiving module 13 may specifically be configured to:
and receiving a processing result returned by the mobile banking server aiming at the service call data, and assembling the processing result into data identifiable by the third-party merchant testing tool.
In this embodiment, the service call request returned by the third-party merchant web page may be initiated by the third-party merchant testing tool according to an operation mode program.
Of course, the service call request returned by the third party merchant web page may also be input by the user at the third party merchant web page.
It should be noted that, in each embodiment, the differences from the other embodiments are emphasized, and the same similar parts between the embodiments are referred to each other. For the apparatus class embodiments, the description is relatively simple as it is substantially similar to the method embodiments, and reference is made to the description of the method embodiments for relevant points.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in the same piece or pieces of software and/or hardware when implementing the present application.
From the above description of embodiments, it will be apparent to those skilled in the art that the present application may be implemented in software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the embodiments or some parts of the embodiments of the present application.
The application provides a method and a device for testing page display of a mobile phone bank, which are described in detail, wherein specific examples are applied to explain the principle and the implementation mode of the application, and the description of the examples is only used for helping to understand the method and the core idea of the application; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.
Claims (10)
1. The page display testing method of the mobile banking is characterized by being applied to a third-party merchant testing tool independent of a mobile banking server, and comprises the following steps of:
responding to a page selection request input by a user on a test client, and displaying and storing a third-party merchant web page corresponding to the page selection request;
responding to a service call request returned by the third-party merchant web page, acquiring service call data in the third-party merchant web page, analyzing and checking the service call data, and after the service call data passes the check, sending the service call data to a mobile banking server, wherein the analyzing and checking the service call data comprises the following steps: analyzing the public key of the third-party merchant from the service call data, forwarding the public key of the third-party merchant to a certificate verification background, and confirming the validity of the third-party merchant configuration by the certificate verification background; analyzing the authority of the third-party merchant, and checking the legitimacy of calling the simulated interactive interface;
receiving a processing result returned by the mobile banking server aiming at the service call data;
displaying and storing a third-party merchant web page corresponding to the processing result;
and taking the third-party merchant web page corresponding to the page selection request and the third-party merchant web page corresponding to the processing result as the basis of the page display test.
2. The method of claim 1, wherein the responding to the page selection request input by the user on the test client, and displaying and saving the third party merchant web page corresponding to the page selection request, comprises:
responding to a page selection request input by a user on a test client, acquiring page configuration information input by the user in advance, and generating a third-party merchant web page corresponding to the page selection request according to the page configuration information;
and displaying and storing the third-party merchant web page corresponding to the page selection request.
3. The method of claim 1, wherein the sending the service invocation data to a mobile banking server comprises:
assembling the service call data according to the data format recognizable by the mobile banking server, and sending the assembled data to the mobile banking server;
the receiving the processing result returned by the mobile phone banking server aiming at the service calling data comprises the following steps:
and receiving a processing result returned by the mobile banking server aiming at the service call data, and assembling the processing result into data identifiable by the third-party merchant testing tool.
4. The method of claim 1, wherein the service invocation request returned by the third party merchant web page is initiated by the third party merchant testing tool in accordance with an operation mode program.
5. The method of claim 1, wherein the service invocation request returned by the third party merchant web page is entered by a user at the third party merchant web page.
6. The utility model provides a mobile banking's page show testing arrangement which characterized in that is applied to the third party merchant testing tool independent of mobile banking server, and the device includes:
the first display and storage module is used for responding to a page selection request input by a user on the test client, and displaying and storing a third-party merchant web page corresponding to the page selection request;
the calling module is used for responding to the service calling request returned by the third-party merchant web page, obtaining the service calling data in the third-party merchant web page, analyzing and checking the service calling data, and after the service calling data passes the check, sending the service calling data to the mobile banking server, wherein the analyzing and checking the service calling data comprises the following steps: analyzing the public key of the third-party merchant from the service call data, forwarding the public key of the third-party merchant to a certificate verification background, and confirming the validity of the third-party merchant configuration by the certificate verification background; analyzing the authority of the third-party merchant, and checking the legitimacy of calling the simulated interactive interface;
the receiving module is used for receiving a processing result returned by the mobile banking server aiming at the service call data;
the second display and storage module is used for displaying and storing the third-party merchant web page corresponding to the processing result;
and the determining module is used for taking the third-party merchant web page corresponding to the page selection request and the third-party merchant web page corresponding to the processing result as the basis of the page display test.
7. The apparatus of claim 6, wherein the first display-preservation module is specifically configured to:
responding to a page selection request input by a user on a test client, acquiring page configuration information input by the user in advance, and generating a third-party merchant web page corresponding to the page selection request according to the page configuration information;
and displaying and storing the third-party merchant web page corresponding to the page selection request.
8. The apparatus of claim 6, wherein the calling module is specifically configured to:
assembling the service call data according to the data format recognizable by the mobile banking server, and sending the assembled data to the mobile banking server;
the receiving module is specifically configured to:
and receiving a processing result returned by the mobile banking server aiming at the service call data, and assembling the processing result into data identifiable by the third-party merchant testing tool.
9. The apparatus of claim 6, wherein the service invocation request returned by the third party merchant web page is initiated by the third party merchant testing tool in accordance with an operation mode program.
10. The apparatus of claim 6, wherein the service invocation request returned by the third party merchant web page is entered by a user at the third party merchant web page.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911198819.2A CN110990275B (en) | 2019-11-25 | 2019-11-25 | Page display test method and device for mobile banking |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911198819.2A CN110990275B (en) | 2019-11-25 | 2019-11-25 | Page display test method and device for mobile banking |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110990275A CN110990275A (en) | 2020-04-10 |
| CN110990275B true CN110990275B (en) | 2023-09-22 |
Family
ID=70088266
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911198819.2A Active CN110990275B (en) | 2019-11-25 | 2019-11-25 | Page display test method and device for mobile banking |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110990275B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112511510B (en) * | 2020-11-18 | 2022-09-30 | 中国建设银行股份有限公司 | Authorization authentication method, system, electronic equipment and readable storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016178068A1 (en) * | 2015-05-06 | 2016-11-10 | Yandex Europe Ag | System and method for testing web pages |
| CN110245069A (en) * | 2019-04-28 | 2019-09-17 | 阿里巴巴集团控股有限公司 | The methods of exhibiting and device of the test method and device of page versions, the page |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9882959B2 (en) * | 2014-09-30 | 2018-01-30 | International Business Machines Corporation | Managing requests to a high utilization website |
-
2019
- 2019-11-25 CN CN201911198819.2A patent/CN110990275B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016178068A1 (en) * | 2015-05-06 | 2016-11-10 | Yandex Europe Ag | System and method for testing web pages |
| CN110245069A (en) * | 2019-04-28 | 2019-09-17 | 阿里巴巴集团控股有限公司 | The methods of exhibiting and device of the test method and device of page versions, the page |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110990275A (en) | 2020-04-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110378749B (en) | Client similarity evaluation method and device, terminal equipment and storage medium | |
| CN109308266A (en) | Construction method, test method, device, equipment and the medium of test case | |
| CN102932332B (en) | Data verification system and data verification method | |
| CN107436844B (en) | Method and device for generating interface use case aggregate | |
| CN111143207B (en) | Method for checking model training notice and training log at mobile terminal | |
| CN110659206B (en) | Simulation architecture establishment method and device based on micro-service, medium and electronic equipment | |
| CN110392054A (en) | Log in method of calibration, device, system, equipment and readable storage medium storing program for executing | |
| CN109543405B (en) | Privacy calling behavior identification method and electronic equipment | |
| CN112653670A (en) | Service logic vulnerability detection method, device, storage medium and terminal | |
| CN106603571A (en) | Safety authentication method and safety authentication device | |
| CN109729303A (en) | Meeting provides the connection terminal variation in device and described device | |
| WO2023284505A1 (en) | Method and apparatus for code-scanning payment | |
| CN110990275B (en) | Page display test method and device for mobile banking | |
| CN103164324A (en) | Microblog test method and device | |
| CN109214189B (en) | Method, device, storage medium and electronic equipment for identifying program bugs | |
| CN108345508A (en) | Interface calls test method and device | |
| CN112241544A (en) | Business system, access method, device, computer equipment and storage medium | |
| CN106910055A (en) | A kind of payment data treating method and apparatus based on mobile terminal | |
| CN109034643A (en) | Order processing method and device, the method and device of translation on line of translation on line | |
| CN110992166B (en) | Method and device for testing online loan application | |
| CN114428737A (en) | Communication method, device, equipment and storage medium based on micro service system | |
| CN114880018A (en) | Request processing method and device, storage medium and electronic equipment | |
| CN109543398B (en) | Application program account migration method and device and electronic equipment | |
| CN113420133A (en) | Session processing method, device, equipment and storage medium | |
| CN113556430A (en) | Outbound system and outbound method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |