CN108400902B - A method, device and equipment for grayscale testing - Google Patents
A method, device and equipment for grayscale testing Download PDFInfo
- Publication number
- CN108400902B CN108400902B CN201810035879.1A CN201810035879A CN108400902B CN 108400902 B CN108400902 B CN 108400902B CN 201810035879 A CN201810035879 A CN 201810035879A CN 108400902 B CN108400902 B CN 108400902B
- Authority
- CN
- China
- Prior art keywords
- client
- test
- identification information
- evaluation
- tested
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Power Engineering (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Information Transfer Between Computers (AREA)
Abstract
本说明书公开一种灰度测试的方法、装置及设备，该方法中可以接收测试服务器推送的测试邀请消息，并当监测到该测试邀请消息被触发时，获取权限标识信息，而后，可以通过评测客户端对该权限标识信息进行验证，并在确定验证通过后，通过该评测客户端对该测试服务器提供的待测试客户端进行灰度测试。
This specification discloses a method, device and device for grayscale testing. In the method, a test invitation message pushed by a test server can be received, and when it is detected that the test invitation message is triggered, the authority identification information can be obtained, and then the evaluation can be performed through the evaluation process. The client verifies the authority identification information, and after determining that the verification is passed, the evaluation client performs a grayscale test on the client to be tested provided by the test server.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, and a device for gray scale testing.
Background
At present, various online services bring great changes to the lives of people, and people can quickly and efficiently complete various service processing through the online services, so that the efficiency of service processing is greatly improved.
In practical applications, a user needs to have a certain right to execute processing of some services. For example, in the process of performing a gray scale test on a client to be tested, a user generally needs to acquire information such as an invitation code, a recommendation code, and the like that have permission to download the client to be tested, and then needs to download the client to be tested through the acquired information, so that the client to be tested can be downloaded and the gray scale test can be performed on the client to be tested. In practical applications, the invitation code, the recommendation code, etc. are typically sent to the user's mailbox.
Based on the prior art, a more efficient gray scale test approach is needed.
Disclosure of Invention
The present specification provides a method for gray scale testing, which is used to solve the problem that a user cannot effectively participate in gray scale testing in the prior art.
The present specification provides a method of gray scale testing, comprising:
receiving a test invitation message pushed by a test server;
when it is monitored that the test invitation message is triggered, authority identification information is obtained;
verifying the authority identification information through an evaluation client;
and after the verification is determined to pass, carrying out gray level test on the client to be tested provided by the test server through the evaluation client.
The present specification provides a device for gray scale testing, which is used to solve the problem that a user cannot effectively participate in gray scale testing in the prior art.
The present specification provides an apparatus for gray scale testing, comprising:
the receiving module is used for receiving the test invitation message pushed by the test server;
the acquisition module acquires authority identification information when the test invitation message is monitored to be triggered;
the verification module verifies the authority identification information through an evaluation client;
and the test module is used for carrying out gray level test on the client to be tested provided by the test server through the evaluation client after the verification is determined to be passed.
The present specification provides a gray scale testing device to solve the problem in the prior art that a user cannot effectively participate in gray scale testing.
The present specification provides a device for gray scale testing comprising one or more memories and a processor, the memories storing a program and configured to perform the following steps by the one or more processors:
receiving a test invitation message pushed by a test server;
when it is monitored that the test invitation message is triggered, authority identification information is obtained;
verifying the authority identification information through an evaluation client;
and after the verification is determined to pass, carrying out gray level test on the client to be tested provided by the test server through the evaluation client.
The present specification provides a method for gray scale testing, which is used to solve the problem that a user cannot effectively participate in gray scale testing in the prior art.
The present specification provides a method of gray scale testing, comprising:
pushing a test invitation message;
when a download request sent by a terminal through an evaluation client is received, a data packet of a client to be tested is provided for the terminal, so that the terminal performs gray level test on the client to be tested through the evaluation client, the download request is sent after the terminal permission identification information passes verification of the evaluation client, and the permission identification information is acquired by the terminal through the test invitation message.
The present specification provides a device for gray scale testing, which is used to solve the problem that a user cannot effectively participate in gray scale testing in the prior art.
The present specification provides an apparatus for gray scale testing, comprising:
the pushing module is used for pushing the test invitation message;
the sending module is used for providing a data packet of a client to be tested to the terminal when receiving a downloading request sent by the terminal through an evaluating client, so that the terminal can perform gray level test on the client to be tested through the evaluating client, the downloading request is sent after the terminal permission identification information passes verification of the evaluating client, and the permission identification information is acquired by the terminal through the test invitation message.
The present specification provides a gray scale testing device to solve the problem in the prior art that a user cannot effectively participate in gray scale testing.
The present specification provides a device for gray scale testing comprising one or more memories and a processor, the memories storing a program and configured to perform the following steps by the one or more processors:
pushing a test invitation message;
when a download request sent by a terminal through an evaluation client is received, a data packet of a client to be tested is provided for the terminal, so that the terminal performs gray level test on the client to be tested through the evaluation client, the download request is sent after the terminal permission identification information passes verification of the evaluation client, and the permission identification information is acquired by the terminal through the test invitation message.
The technical scheme adopted by the specification can achieve the following beneficial effects:
in one or more embodiments of the present disclosure, because the test invitation message sent by the test server can be more effectively obtained and checked by the user through the message pushing manner, and then the client to be tested is obtained from the test server through the test invitation message, and the gray level test is performed on the client to be tested through the evaluation client, compared with the manner of sending the test invitation message to the user through the email, the user participation degree of the gray level test is effectively improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the specification and are incorporated in and constitute a part of this specification, illustrate embodiments of the specification and together with the description serve to explain the specification and not to limit the specification in a non-limiting sense. In the drawings:
FIG. 1 is a schematic diagram of a gray scale test process provided herein;
fig. 2 is a schematic diagram of a gray scale test performed on a test invitation page acquired by a user through a terminal according to the present specification;
FIG. 3 is a schematic diagram of a gray scale testing apparatus provided in the present specification;
FIG. 4 is a schematic diagram of a gray scale testing apparatus provided in the present specification;
FIG. 5 is a schematic diagram of a gray scale testing apparatus provided herein;
fig. 6 is a schematic diagram of a gray scale testing apparatus provided in this specification.
Detailed Description
In the prior art, a user is generally invited to participate in the gray scale test of a client to be tested by sending an email to the user. Specifically, in the whole process of performing the gray scale test on the to-be-tested client running in the iOS system, the test server may apply for the authority identification information such as the invitation code, the recommendation code, and the like to the information management server corresponding to the evaluation client through the pre-collected account information of each user, where the evaluation client mentioned here runs in the iOS system and is used for performing the gray scale test on the to-be-tested client. The information management server can send the determined authority identification information to the mailbox bound by the account information of each user. After the user checks the authority identification information sent by the information management server through the mailbox, the user can start an evaluation client installed in the terminal and input the authority identification information to a specified position in the evaluation client so that the evaluation client can verify the authority identification information. After the evaluation client determines that the authority identification information passes the verification, the download link of the client to be tested can be displayed to the user, so that the user can download and install the client to be tested, and the gray level test is performed on the client to be tested through the evaluation client when the client to be tested is used.
However, in practical applications, since the user may not frequently check the mails in the mailbox, even if the authority identification information is sent to the user, the user may not see the authority identification information, and thus the user may not effectively participate in the gray scale test of the client to be tested.
Therefore, in this specification, a test invitation message pushed by a test server may be received, when it is monitored that the test invitation message is triggered, authority identification information is acquired, then, the authority identification information may be verified by an evaluation client, and after it is determined that the authority identification information passes the verification, a gray level test may be performed on a client to be tested provided by the test server by the evaluation client.
Due to the fact that the message pushing mode is adopted, a user can more effectively obtain and check the test invitation message sent by the test server, the client to be tested is obtained from the test server through the test invitation message, and the gray level test is conducted on the client to be tested through the evaluation client, so that the user participation degree of the gray level test is effectively improved compared with the mode that the test invitation message is sent to the user through a mail.
In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.
Fig. 1 is a schematic diagram of a gray scale testing process provided in this specification, specifically including the following steps:
s100: and receiving a test invitation message pushed by the test server.
In this specification, the terminal may receive a test invitation message pushed by the test server and present the test invitation message to the user. The terminal mentioned here may refer to a terminal device such as a smart phone, a tablet computer, and a desktop computer. Of course, the terminal may also receive the test invitation message pushed by the test server through a designated client installed in the terminal.
S102: and acquiring authority identification information when the test invitation message is monitored to be triggered.
After the test invitation message sent by the test server is acquired, the test invitation message can be monitored, and when the test invitation message is monitored to be triggered, a page acquisition request can be sent to the test server, and the permission identification information carried in the test invitation page is acquired.
For example, when the terminal monitors that the user checks the test invitation message by clicking, it can monitor that the test invitation message is triggered; for another example, when it is detected that the user clicks a link of the test invitation page included in the test invitation message, it may be detected that the test invitation message is triggered. Other ways in which the test invite message is triggered are not necessarily illustrated herein.
When receiving a page acquisition request sent by a terminal, a test server can carry the authority identification information in a test invitation page corresponding to the page acquisition request and return the authority identification information to the terminal. The authority identification information mentioned here may be generated by the test server itself, or may be acquired by the test server from an information management server corresponding to the evaluation client.
The testing server can acquire authority identification information, such as an invitation code, a recommendation code, an activation code and the like, which is used for enabling an evaluation client to carry out authority verification on a user from the information management server through a plurality of account information registered in the information management server in advance, and carry out unified management on the acquired authority identification information. The subsequent test server can push a test invitation message inviting the user to participate in the gray scale test to the user according to actual requirements, so that each user can obtain the authority identification information from the test server through the obtained test invitation message.
It should be noted that the gray scale testing method provided in this specification may be used for performing a gray scale test on a client to be tested running in an iOS system, and may also be used in other systems. For the case that the client to be tested running in the iOS system performs the gray scale test, the above mentioned evaluation client may be an apple official gray scale tool: testflight.
S104: and verifying the authority identification information through an evaluation client.
In this specification, the terminal may obtain the authority identification information from the test invitation page, and verify the authority identification information through an evaluation client installed in the terminal. Specifically, when it is monitored that the user starts the evaluation client through the test invitation page, the terminal can send the authority identification information to the evaluation client so that the evaluation client can verify the authority identification information. In other words, the terminal replaces the user to manually input the authority identification information to the specified position of the evaluation client by directly sending the authority identification information carried in the test invitation page to the evaluation client, thereby bringing great convenience to the user in the process of the gray scale test.
In this specification, there may be many ways for a user to launch an evaluation client through the test invitation page, as shown in fig. 2.
Fig. 2 is a schematic diagram of a user performing a grayscale test through a test invitation page acquired by a terminal according to the present specification.
After monitoring that the test invitation message acquired from the test server is triggered, the terminal may acquire a corresponding test invitation page from the test server and display the test invitation page. The test invitation page can show a user a designated control for directly starting the evaluation client and can also show a link for downloading the evaluation client. When the user determines that the evaluation client is installed in the terminal, the user can click the specified control displayed in the test invitation page, so that the terminal starts the evaluation client after monitoring that the user clicks the specified control.
If the evaluation client is not installed in the current terminal, the user can click the link which is displayed in the test invitation page and used for downloading the evaluation client, so that the terminal jumps to the corresponding download page after monitoring that the user clicks the link, and downloads the evaluation client from the information management server after monitoring that the user executes downloading operation. After the terminal downloads the evaluation client, the terminal can directly start the evaluation client, and then send the authority identification information carried in the test invitation page to the evaluation client for verification, or can start the evaluation client after monitoring that the user executes the operation of starting the evaluation client, and send the authority identification information to the evaluation client for verification.
S106: and after the verification is determined to pass, carrying out gray level test on the client to be tested provided by the test server through the evaluation client.
After the terminal determines that the user passes the verification of the evaluation client, the terminal can download the client to be tested from the test server through the evaluation client, and further perform gray level test on the client to be tested through the evaluation client and various data generated by the client to be tested in the operation process in the process that the user uses the client to be tested.
According to the method, the user can more effectively acquire and check the test invitation message sent by the test server in a message pushing mode, and further acquire the client to be tested from the test server through the test invitation message and perform the gray level test on the client to be tested through the evaluation client, so that the user participation degree of the gray level test is effectively improved compared with the mode of sending the test invitation message to the user through a mail.
Moreover, after the terminal acquires the authority identification information, the authority identification information can be directly sent to the evaluation client, so that the authority identification information is input to a specified position in the evaluation client in a manual input mode instead of the user, and great convenience is brought to the user in the gray level test process.
It should be noted that, in this specification, the test server may monitor the use condition of each authority identification information to improve the utilization rate of the authority identification information, as shown in fig. 2. If the test server monitors that the terminal sends a downloading request for downloading the client to be tested to the test server by receiving the account information based on the test invitation message, it can be determined that the user has checked and participated in the gray scale test of the client to be tested.
And if the test server monitors that the terminal fails to receive the account information based on the test invitation message within the preset time, the test server sends a downloading request for downloading the client to be tested to the test server, so that the test server can determine that the user does not effectively participate in the gray scale test of the client to be tested, and further push the test invitation message to the user or other users.
For the case that the terminal acquires the test invitation page carrying the permission identification information through the test invitation message, but still does not download the client to be tested from the test server through the evaluation client after the preset time, the test server may determine that the time that the terminal holds the permission identification information exceeds the preset time, provide the permission identification information to the test invitation message that passes the reception, and acquire the terminal of the test invitation page from the test server.
In other words, in order to improve the utilization rate of the permission identification information, if it is monitored that the user still fails to obtain the permission identification information after a certain time, the to-be-tested client is downloaded from the test server, and the permission identification information can be recovered to be provided for the user who sends the page obtaining request to the test server again.
In practical applications, the client to be tested may allow the user to download at will, but if the user wants to use the functions of the client to be tested, the user needs to pass the verification of the client to be tested. For such a situation, the terminal may send the acquired authority identification information to the client to be tested, so as to verify the authority identification information through the client to be tested. After the permission identification information is confirmed to pass the verification, the gray level test can be carried out on the client to be tested through the pre-installed evaluation client when the user uses the client to be tested.
Based on the same idea, the present specification further provides a corresponding gray scale testing apparatus, as shown in fig. 3 and 4.
Fig. 3 is a schematic diagram of a gray scale testing apparatus provided in this specification, which specifically includes:
a receiving module 301, configured to receive a test invitation message pushed by a test server;
an obtaining module 302, configured to obtain permission identification information when it is monitored that the test invitation message is triggered;
the verification module 303 is used for verifying the authority identification information through an evaluation client;
and the testing module 304 is used for performing gray level testing on the to-be-tested client provided by the testing server through the evaluating client after the verification is determined to be passed.
The obtaining module 302, when it is monitored that the test invitation message is triggered, obtaining a test invitation page; and acquiring the authority identification information carried by the test invitation page.
The verification module 303 sends the authority identification information to the evaluation client, so as to verify the authority identification information through the evaluation client.
The authority identification information is obtained by the test server from an information management server corresponding to the evaluation client in advance.
The testing module 304, after the verification is determined to pass, downloads the client to be tested provided by the testing server through the evaluating client, so as to perform the gray level test on the client to be tested through the evaluating client when the user uses the client to be tested, where the evaluating client includes: testflight.
Fig. 4 is a schematic diagram of a gray scale testing apparatus provided in this specification, which specifically includes:
the pushing module 401 pushes the test invitation message;
the sending module 402 is configured to, when receiving a download request sent by a terminal through an evaluation client, provide a data packet of a client to be tested to the terminal, so that the terminal performs a gray level test on the client to be tested through the evaluation client, where the download request is sent after the terminal permission identification information passes verification of the evaluation client, and the permission identification information is obtained by the terminal through the test invitation message.
The pushing module 401, when it is monitored that the terminal does not download the client to be tested according to the test invitation message within a preset time, re-pushes the test invitation message.
Based on the method for testing gray scale described above, the present specification also correspondingly provides an apparatus for testing gray scale, as shown in fig. 5. The apparatus includes one or more memories and a processor, the memories storing programs and configured to perform the following steps by the one or more processors:
receiving a test invitation message pushed by a test server;
when it is monitored that the test invitation message is triggered, authority identification information is obtained;
verifying the authority identification information through an evaluation client;
and after the verification is determined to pass, carrying out gray level test on the client to be tested provided by the test server through the evaluation client.
Based on the method for testing gray scale described above, the present specification also correspondingly provides an apparatus for testing gray scale, as shown in fig. 6. The apparatus includes one or more memories and a processor, the memories storing programs and configured to perform the following steps by the one or more processors:
pushing a test invitation message;
when a download request sent by a terminal through an evaluation client is received, a data packet of a client to be tested is provided for the terminal, so that the terminal performs gray level test on the client to be tested through the evaluation client, the download request is sent after the terminal permission identification information passes verification of the evaluation client, and the permission identification information is acquired by the terminal through the test invitation message.
In one or more embodiments of the present disclosure, a test invitation message pushed by a test server may be received, and when it is monitored that the test invitation message is triggered, authority identification information is obtained, then, the authority identification information may be verified by an evaluation client, and after it is determined that the authority identification information passes the verification, a gray level test may be performed on a client to be tested provided by the test server by the evaluation client.
Due to the fact that the message pushing mode is adopted, a user can more effectively obtain and check the test invitation message sent by the test server, the client to be tested is obtained from the test server through the test invitation message, and the gray level test is conducted on the client to be tested through the evaluation client, so that the user participation degree of the gray level test is effectively improved compared with the mode that the test invitation message is sent to the user through a mail.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to one or more embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that 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 an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The above description is merely one or more embodiments of the present disclosure and is not intended to limit the present disclosure. Various modifications and alterations to one or more embodiments of the present description will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of one or more embodiments of the present specification should be included in the scope of the claims of the present specification.
Claims (14)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810035879.1A CN108400902B (en) | 2018-01-15 | 2018-01-15 | A method, device and equipment for grayscale testing |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810035879.1A CN108400902B (en) | 2018-01-15 | 2018-01-15 | A method, device and equipment for grayscale testing |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108400902A CN108400902A (en) | 2018-08-14 |
| CN108400902B true CN108400902B (en) | 2021-08-24 |
Family
ID=63094793
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810035879.1A Active CN108400902B (en) | 2018-01-15 | 2018-01-15 | A method, device and equipment for grayscale testing |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108400902B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109756386B (en) * | 2018-09-07 | 2021-09-28 | 启迪云控(北京)科技有限公司 | Communication optimization method and device based on cloud network vehicle cooperation |
| CN109800150B (en) * | 2018-12-13 | 2022-03-15 | 深圳壹账通智能科技有限公司 | Gray scale testing method, server and computer readable storage medium |
| CN110399288A (en) * | 2019-01-07 | 2019-11-01 | 腾讯科技（深圳）有限公司 | Applied testing method and device, storage medium and electronic device |
| CN111858312B (en) * | 2020-06-24 | 2024-07-12 | 亚美智联数据科技有限公司 | Page display method and device for application program, computer equipment and storage medium |
| CN114528199A (en) * | 2020-11-23 | 2022-05-24 | 腾讯科技（深圳）有限公司 | Software anomaly detection method and device and storage medium |
| CN113138888A (en) * | 2021-04-30 | 2021-07-20 | 北京市商汤科技开发有限公司 | Function detection method and device, electronic equipment and storage medium |
| CN116033007B (en) * | 2022-11-16 | 2025-07-01 | 金钱猫科技股份有限公司 | A message push management method and system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101247251A (en) * | 2008-03-13 | 2008-08-20 | 腾讯科技（深圳）有限公司 | System and method for internet service resource popularization |
| CN102148849A (en) * | 2010-06-30 | 2011-08-10 | 华为技术有限公司 | Data processing method, device and system for audience measurement |
| CN104519377A (en) * | 2014-12-30 | 2015-04-15 | 康佳集团股份有限公司 | Method and system for television software storage release verification |
| CN104579854A (en) * | 2015-02-12 | 2015-04-29 | 北京航空航天大学 | Crowdsourcing test method |
| CN105373402A (en) * | 2015-10-29 | 2016-03-02 | 努比亚技术有限公司 | Device and method for software upgrading gated launch |
| CN105653440A (en) * | 2014-11-13 | 2016-06-08 | 阿里巴巴集团控股有限公司 | Gray release method and device |
| CN106155751A (en) * | 2016-08-02 | 2016-11-23 | 传线网络科技（上海）有限公司 | Application packing and issuing method and device |
| CN107145438A (en) * | 2016-03-01 | 2017-09-08 | 阿里巴巴集团控股有限公司 | Code test method, code tester device and code tester system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080235746A1 (en) * | 2007-03-20 | 2008-09-25 | Michael James Peters | Methods and apparatus for content delivery and replacement in a network |
| CA2815569C (en) * | 2010-10-25 | 2016-03-01 | Research In Motion Limited | System and method for enabling applications to communicate using a peer-to-peer (p2p) system |
| US20150347970A1 (en) * | 2014-05-30 | 2015-12-03 | Apple Inc. | Beta testing distribution |
| CN106656959B (en) * | 2016-09-28 | 2020-07-28 | 腾讯科技（深圳）有限公司 | Access request regulation and control method and device |
| CN107483534B (en) * | 2017-06-28 | 2020-07-28 | 阿里巴巴集团控股有限公司 | Service processing method and device |
-
2018
- 2018-01-15 CN CN201810035879.1A patent/CN108400902B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101247251A (en) * | 2008-03-13 | 2008-08-20 | 腾讯科技（深圳）有限公司 | System and method for internet service resource popularization |
| CN102148849A (en) * | 2010-06-30 | 2011-08-10 | 华为技术有限公司 | Data processing method, device and system for audience measurement |
| CN105653440A (en) * | 2014-11-13 | 2016-06-08 | 阿里巴巴集团控股有限公司 | Gray release method and device |
| CN104519377A (en) * | 2014-12-30 | 2015-04-15 | 康佳集团股份有限公司 | Method and system for television software storage release verification |
| CN104579854A (en) * | 2015-02-12 | 2015-04-29 | 北京航空航天大学 | Crowdsourcing test method |
| CN105373402A (en) * | 2015-10-29 | 2016-03-02 | 努比亚技术有限公司 | Device and method for software upgrading gated launch |
| CN107145438A (en) * | 2016-03-01 | 2017-09-08 | 阿里巴巴集团控股有限公司 | Code test method, code tester device and code tester system |
| CN106155751A (en) * | 2016-08-02 | 2016-11-23 | 传线网络科技（上海）有限公司 | Application packing and issuing method and device |
Non-Patent Citations (1)
| Title |
|---|
| "TestFlight Beta Testing (翻译)";DOC_XHUAN;《https://www.jianshu.com/p/0480b4be4d0c》;20160706;第1-6页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108400902A (en) | 2018-08-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108400902B (en) | A method, device and equipment for grayscale testing | |
| CN106970873B (en) | Online mock testing method, device and system | |
| US9307342B2 (en) | Dynamic rendering for software applications | |
| CN106201850B (en) | A kind of compatibility test method and device | |
| CN111475142A (en) | A method, device and device for generating a small program file package | |
| CN107357726A (en) | A kind of application compatibility method of testing and device | |
| CN107479868B (en) | Interface loading method, device and device | |
| CN110955887B (en) | Abnormal behavior detection method and device | |
| CN108334340B (en) | Cross-environment data communication method, device and system | |
| CN107360265B (en) | A kind of equipment exclusive identification code acquisition methods, device and mobile terminal | |
| CN110502591A (en) | A kind of data extraction method, device and equipment | |
| CN114548744B (en) | A business risk management method, device and equipment | |
| CN111611558B (en) | A method and device for identity verification | |
| CN109471799A (en) | A deployment method, device, storage medium and terminal for a demand environment | |
| CN111753270A (en) | Application login verification method, device, device and storage medium | |
| CN107368293B (en) | Page structure generation method, page screenshot reporting method, device and system | |
| CN108345536A (en) | A kind of dispositions method, device and the equipment of continuous integrating environment | |
| CN107733866A (en) | RPC requests, RPC request processing methods, device and equipment | |
| CN108037914B (en) | Method and device for developing android native system by combining js | |
| CN110602163A (en) | File uploading method and device | |
| HK1258552B (en) | Gray scale test method, device and equipment | |
| HK1258552A1 (en) | Gray scale test method, device and equipment | |
| CN109542775B (en) | A method and device for generating and executing a test script | |
| CN110471828B (en) | An operating system testing method, device and equipment thereof | |
| CN107483534B (en) | Service processing method and device |
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 | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1258552 Country of ref document: HK |
|
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201020 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20201020 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240307 Address after: 128 Meizhi Road, Guohao Times City # 20-01, Singapore 189773 Patentee after: Advanced Nova Technology (Singapore) Holdings Ltd. Country or region after: Singapore Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Innovative advanced technology Co.,Ltd. Country or region before: Cayman Islands |