CN115065510A

CN115065510A - Login method, device, system, electronic equipment and readable storage medium

Info

Publication number: CN115065510A
Application number: CN202210603560.0A
Authority: CN
Inventors: 陆祎; 王倩
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2022-05-30
Filing date: 2022-05-30
Publication date: 2022-09-16
Anticipated expiration: 2042-05-30
Also published as: CN115065510B

Abstract

The embodiment of the invention provides a login method, a login device, a login system, electronic equipment and a readable storage medium, and relates to the technical field of testing. In the method, a creation request is sent to a preset platform; the creating instruction is used for indicating the preset platform to create the target monitoring task for the testing end and return first response information under the condition that the target monitoring task does not exist at present, wherein the target monitoring task is a monitoring task bound with an account number used by the testing end and a system identifier of the tested system. And under the condition of receiving the first response information, triggering the tested system to send the verification code to the target terminal. Sending a query request to a preset platform, and logging in based on a verification code when the verification code returned by the preset platform in response to the query request is received; the verification code returned by the preset platform is monitored based on a target monitoring task, and the target monitoring task is used for monitoring the verification code submitted by the target terminal. Therefore, the test end can be ensured to successfully log in the tested system.

Description

Login method, device, system, electronic equipment and readable storage medium

Technical Field

The invention belongs to the technical field of testing, and particularly relates to a login method, a login device, a login system, electronic equipment and a readable storage medium.

Background

At present, in order to improve the testing efficiency, a mode that a plurality of testing ends carry out automatic testing on the same tested system in parallel is widely applied. When testing a system under test, the system under test often needs to be logged in first to perform subsequent testing operations. When logging in a tested system by using an account, sometimes the tested system needs to be triggered to issue a verification code to a communication number bound to the account, and logging in is completed based on the verification code.

However, sometimes, multiple test terminals perform parallel tests by using the same account, and the same account is often bound with the same communication number. Therefore, how to ensure that the testing end can successfully log in the tested system becomes an urgent problem to be solved.

Disclosure of Invention

The invention provides a login method, a login device, a login system, electronic equipment and a readable storage medium, and aims to solve the problem of how to ensure that a test end can successfully log in a tested system.

In a first aspect, the present invention provides a login method applied to a test end, where the method includes:

sending a creation request to a preset platform; the creating request carries an account of the testing terminal and a system identifier of a tested system to be tested, the creating instruction is used for indicating the preset platform to create a target monitoring task for the testing terminal and return first response information under the condition that the target monitoring task does not exist at present, and the target monitoring task is a monitoring task bound with the account and the system identifier;

under the condition of receiving the first response information, triggering the tested system to send a verification code to a target terminal; the target terminal is configured with a communication number bound by the account;

sending a query request to the preset platform, and logging in based on a verification code when the verification code returned by the preset platform in response to the query request is received; the verification code returned by the preset platform is monitored based on the target monitoring task, and the target monitoring task is used for monitoring the verification code submitted by the target terminal.

In a second aspect, the present invention provides another login method applied to a preset platform, where the method includes:

receiving a creation request sent by a test end; the creating request carries the account of the testing terminal and the system identification of the tested system;

responding to the creation request, if a target monitoring task does not exist, creating the target monitoring task for the test terminal, and returning first response information; the target monitoring task is a monitoring task bound with the account and the system identifier, the first response information is used for indicating the test terminal to trigger the tested system to issue a verification code to a target terminal, and the target terminal is configured with a communication number bound with the account;

responding to a query request sent by the test end, returning the verification code to the test end under the condition that the verification code submitted by the target terminal is monitored based on the target monitoring task,

in a third aspect, the present invention provides a login device applied to a test end, where the login device includes:

the first sending module is used for sending a creation request to a preset platform; the creating request carries an account of the testing terminal and a system identifier of a tested system to be tested, the creating instruction is used for indicating the preset platform to create a target monitoring task for the testing terminal and return first response information under the condition that the target monitoring task does not exist at present, and the target monitoring task is a monitoring task bound with the account and the system identifier;

the trigger module is used for triggering the tested system to send a verification code to a target terminal under the condition of receiving the first response information; the target terminal is configured with a communication number bound by the account;

the login module is used for sending a query request to the preset platform and logging in based on a verification code when the verification code returned by the preset platform in response to the query request is received; the verification code returned by the preset platform is monitored based on the target monitoring task, and the target monitoring task is used for monitoring the verification code submitted by the target terminal.

In a fourth aspect, the present invention provides another login apparatus, which is applied to a preset platform, and the apparatus includes:

the first receiving module is used for receiving a creation request sent by a testing end; the creating request carries the account of the testing terminal and the system identification of the tested system;

the creating module is used for responding to the creating request, creating the target monitoring task for the testing terminal if the target monitoring task does not exist, and returning first response information; the target monitoring task is a monitoring task bound with the account and the system identifier, the first response information is used for indicating the test terminal to trigger the tested system to issue a verification code to a target terminal, and the target terminal is configured with a communication number bound with the account;

and the returning module is used for responding to the query request sent by the testing end and returning the verification code to the testing end under the condition that the verification code submitted by the target terminal is monitored based on the target monitoring task.

In a fifth aspect, the present invention provides a login system, where the login system includes a test terminal, a preset platform, and a target terminal, and the target terminal is configured with a communication number bound to an account of the test terminal;

the test end is used for sending a creation request to the preset platform; the creating request carries the account of the testing terminal and the system identification of the tested system;

the preset platform is used for responding to the received establishment request, establishing a target monitoring task for the test terminal if the target monitoring task does not exist, and returning first response information; the target monitoring task is a monitoring task bound with the account and the system identifier;

the test end is further used for triggering the tested system to issue a verification code to the target terminal under the condition that the first response information is received;

the target terminal is used for submitting the received verification code to the preset platform;

the test end is also used for sending a query request to the preset platform;

the preset platform is further configured to respond to the received query request, and return the verification code to the test end under the condition that the verification code submitted by the target terminal is monitored based on the target monitoring task;

the test end is further used for logging in based on the verification code when the verification code returned by the preset platform in response to the query request is received.

In a sixth aspect, the present invention provides an electronic device comprising: processor, memory and computer program stored on the memory and executable on the processor, characterized in that the processor implements the above-mentioned logging method when executing the program.

In a seventh aspect, the present invention provides a readable storage medium, wherein instructions of the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the above login method.

In the embodiment of the invention, a creation request is sent to a preset platform; the creating request carries an account of the testing terminal and a system identifier of the tested system, and the creating instruction is used for indicating the preset platform to create a target monitoring task for the testing terminal and return first response information under the condition that the target monitoring task does not exist currently, wherein the target monitoring task is a monitoring task bound with the account used by the testing terminal and the system identifier of the tested system. Under the condition of receiving the first response information, triggering the tested system to send a verification code to the target terminal; and the target terminal is configured with a communication number bound by the account number. Sending a query request to a preset platform, and logging in based on a verification code when the verification code returned by the preset platform in response to the query request is received; the verification code returned by the preset platform is monitored based on a target monitoring task, and the target monitoring task is used for monitoring the verification code submitted by the target terminal. In the embodiment of the invention, after the preset platform successfully creates the monitoring task for the test end, the test end can trigger the tested system to issue the verification code. And the preset platform creates a target monitoring task for the test end only when the target monitoring task bound with the account used by the test end and the system identifier of the tested system tested by the test end does not exist at present. Therefore, when a plurality of test terminals use the same account number to perform parallel test, the situation that the target monitoring task is successfully established for the plurality of test terminals by a preset platform at the same time can be avoided, the plurality of test terminals all apply for the target monitoring task, and then the situation that the plurality of test terminals trigger the tested system to send the verification codes in parallel at the same time is avoided, so that the communication account number receives the plurality of verification codes at the same time, the verification codes corresponding to each test terminal cannot be correctly distinguished, and finally the problem that the tested system cannot be successfully logged in is solved, and the test terminals can be ensured to be successfully logged in the tested system.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.

Fig. 1 is a flowchart illustrating steps of a login method according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of a scenario architecture according to an embodiment of the present invention;

FIG. 3 is a flowchart illustrating steps of another exemplary method for logging in;

FIG. 4 is a schematic overall flow chart provided by the embodiment of the present invention;

FIG. 5 is a schematic diagram of a service flow provided by an embodiment of the present invention;

FIG. 6 is a schematic diagram of another service flow provided by an embodiment of the present invention;

fig. 7 is a structural diagram of a login device according to an embodiment of the present invention;

FIG. 8 is a block diagram of another exemplary logging device provided in accordance with embodiments of the present invention;

FIG. 9 is a block diagram of a login system provided by embodiments of the present invention;

fig. 10 is a block diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

First, an application scenario related to an embodiment of the present invention is exemplarily described. In the process of automatic testing, the first step is often the step of logging in the tested system, and in order to improve the security of logging in, many tested systems are additionally provided with some special authentication means besides inputting an account number and a login password. For example, a verification code is used for further authentication checks. Specifically, the short message containing the verification code is issued in the form of a short message to the communication number bound during account registration. And inputting the verification code, the account and the login password within a certain time to complete the login of the tested system, thereby carrying out subsequent test operation. The account may be registered in the system under test in advance, and may be a login account for logging in the system under test.

Under the scene that a plurality of testing terminals use the same account number to perform parallel testing on the same tested system, because the communication numbers bound by the same account number are consistent, when the plurality of testing terminals use the same account number to log in the tested system in parallel, the communication numbers bound by the account number can receive a plurality of verification codes at the same time. Since it is impossible to distinguish which test end the verification code belongs to, a problem of unsuccessful login is caused.

Therefore, the embodiment of the invention provides a login method, which can complete login of a system to be tested in a scene that a plurality of test terminals use the same account to perform parallel test on the same system to be tested, so that the test terminals can execute subsequent test operations. Of course, it should be noted that the login method provided in the embodiment of the present invention may also be used in other scenarios, for example, a scenario in which a single test end performs a test, a scenario in which multiple test ends use different accounts, a scenario in which multiple test ends use the same account to perform asynchronous login, and the like, which is not limited in this embodiment of the present invention.

The registration method will be described in detail below.

Fig. 1 is a flowchart illustrating steps of a login method according to an embodiment of the present invention, where the method may be applied to any testing end. As shown in fig. 1, the method may include:

step 101, sending a creation request to a preset platform; the creating request carries the account of the testing terminal and the system identification of the tested system, the creating instruction is used for indicating the preset platform to create the target monitoring task for the testing terminal and return first response information under the condition that the target monitoring task does not exist at present, and the target monitoring task is a monitoring task bound with the account and the system identification.

In the embodiment of the invention, the system to be tested can be a website system, and the system to be tested can represent the tested website. The test end can be an automatic execution end, and the test end can automatically access the tested system based on the pre-deployed automation script. When a webpage provided by a tested system is accessed, an account used at this time and a login password of the account are automatically input. The account and the login password of the account used at this time can be predefined in the automation script. In the existing scheme, after an input account and a login password are input, a tested system is triggered to send a verification code to a communication number bound to the account. Therefore, in a scene that a plurality of test terminals use the same account number to test the same tested system, in the process that the plurality of test terminals execute login operation in parallel, the plurality of test terminals trigger the tested system to issue verification codes to the communication numbers bound by the account number in parallel, so that the communication numbers receive the plurality of verification codes at the same time, the verification codes corresponding to the test terminals cannot be correctly distinguished, and the problem that login cannot be successfully performed is caused.

In the embodiment of the invention, the test terminal sends a creation request to the preset platform before triggering the tested system to issue the verification code to the communication number bound to the account. The preset platform may be a preset automation platform, and the preset platform may be a server or a server cluster. The test end can send a creation request to the preset platform before triggering the tested system to issue the verification code so as to control the preset platform to create the target monitoring task. The target monitoring task is a monitoring task corresponding to the account used this time and the system identifier of the system to be tested, and the monitoring task can be understood as a monitoring service. The preset platform may be configured to create an interception task for the test end, and if the creation is successful, the test end may be considered to apply for the interception task. Otherwise, if the creation is not successful, the test end is considered to have not applied for the listening task. When a plurality of test terminals use the same account number to test the same tested system, the account number bound to the monitoring task and the system identification created for each test terminal are the same. When the monitoring task is created, if a monitoring task corresponding to the account and the system identifier of the system under test currently exists, that is, a target monitoring task created for other test terminals that use the same account to test the same system under test currently exists. In this case, a target snoop task is not created for the test end. On the contrary, if the target monitoring tasks created for other test ends do not exist currently, the target monitoring tasks can be created for the test ends, so that the number of the monitoring tasks corresponding to the same account and the same system identifier in the same time is controlled to be not more than 1. That is, when a plurality of test terminals log in the same tested system by using the same account, only one test terminal can apply for a target monitoring task at the same time.

102, under the condition of receiving the first response information, triggering the tested system to send a verification code to a target terminal; and the target terminal is configured with the communication number bound by the account.

In the embodiment of the invention, the terminal configured with the communication number bound by the account is the target terminal. For example, if the communication number of a Subscriber Identity Module (SIM) card of the terminal is the communication number bound to the account used this time, the terminal may be regarded as the target terminal. The page of the tested system can provide a verification code acquisition button, and after the testing end inputs the account and the login password, the verification code acquisition button can be triggered, so that the tested system is triggered to issue the verification code to the communication number bound by the account. Specifically, the test end may generate a click event for the verification code obtaining button, for example, the executed automation script generates a click event to click the verification code obtaining button, so as to trigger the verification code obtaining button. The tested system can directly send the verification code to the communication number, or send the verification code to the communication number through the communication server. After triggering the tested system to issue the verification code to the communication number bound to the account, the target terminal configured with the communication number can receive the short message containing the verification code.

For any test end, the test end triggers the tested system to issue the verification code to the communication number under the condition that the test end successfully applies for the target monitoring task, namely, the preset platform creates the target monitoring task for the test end. And the number of the monitoring tasks corresponding to the same account and the same system identification in the preset platform is not more than 1 at the same time, that is, only 1 target monitoring task exists at the same time. For other testing ends which use the same account number to test the same tested system in parallel, a target monitoring task cannot be applied currently, and then other testing ends cannot trigger the tested system to issue verification codes currently. Therefore, in the embodiment of the invention, under the scene that a plurality of test terminals of the same tested system are logged in by using the same account number, only one test terminal in the plurality of test terminals can be controlled to trigger the tested system to issue the verification code each time, and the plurality of test terminals can sequentially trigger the tested system to issue the verification code according to the sequence of applying for the target monitoring task, so that the problem that the plurality of test terminals trigger the tested system to issue the verification code simultaneously, the same communication account number receives a plurality of verification codes simultaneously, and the verification code corresponding to each test terminal cannot be correctly distinguished, so that successful logging cannot be realized is solved.

103, sending a query request to the preset platform, and logging in based on a verification code when the verification code returned by the preset platform in response to the query request is received; the verification code returned by the preset platform is monitored based on the target monitoring task, and the target monitoring task is used for monitoring the verification code submitted by the target terminal.

In the embodiment of the invention, the target terminal can process the received short message to identify the verification code in the short message and submit the verification code to the preset platform, and as the target terminal can receive other types of verification codes, for example, the verification code issued when logging in other websites. Therefore, the preset platform may monitor the verification code submitted by the target terminal based on the target monitoring task to determine whether the verification code submitted by the target terminal is sent to the target terminal when logging in the system under test by using the account, that is, to monitor whether the verification code is issued by triggering the system under test in step 102. If yes, the verification code triggered when the testing end logs in the tested system by using the account can be considered to be monitored. The test end can send a query request to a preset platform after triggering the tested system to send the verification code to the communication number. Accordingly, the preset platform can respond to the query request and return the verification code to the test end under the condition of monitoring, so that the test end can log in the tested system and execute subsequent test operation on the tested system.

In summary, the login method provided in the embodiment of the present invention sends a creation request to a preset platform; the creating request carries an account of the testing terminal and a system identifier of the tested system, and the creating instruction is used for indicating the preset platform to create a target monitoring task for the testing terminal and return first response information under the condition that the target monitoring task does not exist currently, wherein the target monitoring task is a monitoring task bound with the account used by the testing terminal and the system identifier of the tested system. Under the condition of receiving the first response information, triggering the tested system to send a verification code to the target terminal; and the target terminal is configured with a communication number bound by the account number. Sending a query request to a preset platform, and logging in based on a verification code when the verification code returned by the preset platform in response to the query request is received; the verification code returned by the preset platform is monitored based on a target monitoring task, and the target monitoring task is used for monitoring the verification code submitted by the target terminal. In the embodiment of the invention, after the preset platform successfully creates the monitoring task for the test end, the test end can trigger the tested system to issue the verification code. And the preset platform creates a target monitoring task for the test end only when the target monitoring task bound with the account used by the test end and the system identifier of the tested system tested by the test end does not exist at present. Therefore, when a plurality of test terminals use the same account number to perform parallel test, the situation that the target monitoring task is successfully established for the plurality of test terminals by a preset platform at the same time can be avoided, the plurality of test terminals all apply for the target monitoring task, and then the situation that the plurality of test terminals trigger the tested system to send the verification codes in parallel at the same time is avoided, so that the communication account number receives the plurality of verification codes at the same time, the verification codes corresponding to each test terminal cannot be correctly distinguished, and finally the problem that the tested system cannot be successfully logged in is solved, and the test terminals can be ensured to be successfully logged in the tested system.

Fig. 2 is a schematic view of a scenario architecture according to an embodiment of the present invention. As shown in fig. 2, the test end may be any one of the plurality of test ends, the test end may first send a creation request to the preset platform, and the preset platform creates a target monitoring task for the test end and returns the first response information when the target monitoring task does not exist currently. Correspondingly, the test end can trigger the tested system to issue the verification code under the condition of receiving the first response information. The target terminal can submit the received verification code to a preset platform. The preset platform returns the verification code monitored based on the target monitoring task to the testing end based on the query request sent by the testing end, so that the testing end can complete login.

Optionally, the test end may be any one of at least two test ends that perform parallel testing on the same system under test using the same account, so as to ensure that a scheme in which multiple test ends perform parallel testing on the test ends using the same account can be performed smoothly. Specifically, the same account used by at least two test terminals may be bound to the same communication number. The bound communication number may be specifically a bound communication number for receiving the verification code.

Optionally, after sending the creation request to the preset platform, the following operations may be further performed in the embodiment of the present invention:

step S21, under the condition that second response information returned by the preset platform is received, the creating instruction is sent to the preset platform again according to the first interval duration until the target monitoring task is successfully created for the test end; and the second response information is returned by the preset platform under the condition that the target monitoring task is not created for the test end.

In this embodiment of the present invention, the second response information may be returned when the preset platform currently has the target monitoring task, that is, when the target monitoring task successfully created for the other test end currently exists. In this case, in order to avoid that multiple test terminals simultaneously trigger the tested system to issue the verification code to the communication number bound to the account, a target monitoring task may not be created for the test terminal, and accordingly, second response information may be returned to represent that the creation fails. The test end may send the creation instruction to the preset platform again after waiting for the first interval duration under the condition that the second response information is received. If the first response information is received, the transmission may be stopped. Otherwise, if the second response message is received, the first detection duration is waited again, and the creation instruction is sent to the preset platform again. And so on until the first response information is received.

The successful creation of the target monitoring task for the test end can be understood as that the preset platform responds to a creation request sent by the test end, creates the target monitoring task for the test end, and returns first response information. The target listening task unsuccessfully created for the test end may be understood as that the preset platform responds to the creation request sent by the test end, does not create the target listening task for the test end, and returns the second response information. Further, the first interval duration may be preset according to actual requirements, for example, the first interval duration may be 10 seconds, 15 seconds, 30 seconds, and the like. The first response information and the second response information returned by the preset platform may include different type identifiers, and the test end may identify whether the response information is the first response information/the second response information according to the type identifier of the received response information. For example, the type identifier of the first response information may be 1, and the type identifier of the second response information may be 0. The test end may determine that the first response information is received in a case where the type identifier of the received response information is 1. In a case where the type identification of the received response information is 0, it is determined that the second response information is received.

In the embodiment of the invention, under the condition of receiving the second response information representing that the target monitoring task is not successfully created, the creating instruction is continuously sent to the preset platform according to the first interval duration until the target monitoring task is successfully created for the test terminal. Therefore, the testing end can apply for the target monitoring task and obtain the authority of obtaining the verification code, and the testing end can complete login.

Optionally, the embodiment of the present invention may further include the steps of:

step S31, under the condition that the first response information is received, obtaining the task identifier of the target listening task carried in the first response information, and obtaining a target task identifier.

In the embodiment of the invention, the preset platform can allocate a task Identifier (ID) to the target monitoring task under the condition of creating the target monitoring task for the test end, the task identifier of the target monitoring task can be used as the target task identifier, and the task identifiers of different monitoring tasks in the same moment can be different.

Step S32, sending a task clearing instruction to the preset platform under the condition of receiving the verification code returned by the preset platform in response to the query request; the task clearing instruction carries the target task identifier, and the task clearing instruction is used for instructing the preset platform to clear the target monitoring task indicated by the target task identifier.

Clearing a snoop task may refer to ending the snoop task, e.g., setting the snoop task to ended. Further, the completed snoop task may also be deleted. After the listening task is finished, the preset platform can determine that the listening task does not exist. That is to say, the preset platform does not currently have a target monitoring task, which may specifically mean that the preset platform does not currently have an unfinished target monitoring task.

Further, after receiving the task clearing instruction, the preset platform may extract a target task identifier therein, and clear the target listening task corresponding to the target task identifier. The target monitoring tasks created for the test terminals are removed, so that subsequent creation requests sent to other test terminals tested by the same tested system by using the same account can be successfully responded by the preset platform, that is, the subsequent preset platform can create the target monitoring tasks for the other test terminals.

In the embodiment of the invention, under the condition of receiving the verification code returned by the preset platform in response to the query request, a task clearing instruction is sent to the preset platform; the task clearing instruction carries a target task identifier, and the task clearing instruction is used for indicating a preset platform to clear the target monitoring task indicated by the target task identifier. The target monitoring task created for the test terminal can be cleared as soon as possible by the preset platform, and the problem that other test terminals tested by the same tested system by using the same account number cannot apply for the target monitoring task and further login delay is increased due to the fact that the target monitoring task created for the test terminal still exists under the condition that the test terminal acquires the verification code is solved. By timely clearing, other testing terminals which do not apply for the target monitoring task can apply for the target monitoring task as soon as possible, and therefore monitoring efficiency is improved to a certain extent.

Optionally, the step of sending the query request to the preset platform may specifically include:

step S41, sending a query request carrying the target task identifier to the preset platform according to a second time interval until third response information returned by the preset platform in response to the query request is received; the third response information comprises a verification code which is stored in the preset platform corresponding to the target task identifier, and the verification code which is monitored based on different monitoring tasks in the preset platform is stored in the preset platform corresponding to the task identifier of the monitoring task.

For the verification code monitored based on the target monitor task, the verification code may be stored in correspondence with the target task identifier of the target monitor task. Correspondingly, first response information carrying the target task identifier can be returned to the test end, and the target task identifier can be carried when the test end sends a query request to the preset platform, so that the preset platform can return the verification code stored corresponding to the target task identifier to the test end.

The second duration interval may be set according to actual requirements, and the second preset interval may be the same as or different from the first duration interval, and exemplarily, the second preset interval may be 30 seconds. The test end can extract the verification code from the third response information and log in the tested system based on the extracted verification code. Specifically, the test end may input the verification code into a corresponding control of a login page of the system under test based on a preset automation script, for example, fill the verification code into a specified object position of the automation script, for example, fill the specified object position into an automation task window of the test end, and complete login by running the automation script.

It should be noted that, in the embodiment of the present invention, specifically, after the verification code is extracted from the third response message and login is completed based on the verification code, the task clear instruction may be sent.

Since there may be a monitoring task created for other accounts and/or other systems under test in the preset platform, that is, the preset platform has a verification code monitored based on other monitoring tasks. In the embodiment of the invention, the test end sends the query request carrying the target task identifier to the preset platform, so that the preset platform can return the verification code which is stored corresponding to the target task identifier based on the target task identifier, and the problem of subsequent login failure caused by the fact that the preset platform returns the verification code which is monitored based on other monitoring tasks can be avoided to a certain extent.

Optionally, in the case of receiving first response information indicating that the target listening task is successfully created, the embodiment of the present invention may further include:

and step S51, timing after receiving the first response information, and obtaining a timing duration.

Step S52, when the timing duration reaches a preset duration threshold and the third response information is not received yet, stopping the operation of sending the query request carrying the target task identifier to the preset platform, and outputting error information.

The timing duration may represent a total waiting duration of the test terminal. The preset duration threshold may be set according to actual requirements, for example, the preset duration threshold may be set according to valid duration of the verification code of the system under test, and the preset duration threshold may be positively correlated with the valid duration of the verification code of the system under test, for example, the preset duration threshold may be equal to the valid duration of the verification code, so that validity of the preset duration threshold may be ensured to a certain extent.

In the embodiment of the invention, the test terminal can wait for the second interval duration after receiving the first response message, and send the query request after finishing the waiting. If third response information is received in response to the query request, the transmission may be stopped. If not, the second interval duration can be waited again, the query request is sent again after the waiting is finished, and the like until the third response message is received. Of course, if the third response message is not received when the timing duration reaches the preset duration threshold, it may be indicated that an error occurs, and the verification code cannot be correctly obtained currently, or even if the verification code is obtained, the verification code is invalid and cannot be successfully logged in. Therefore, the operation of sending the query request carrying the target task identifier to the preset platform can be stopped, so that unnecessary operation is avoided from being executed, processing resources are wasted, and meanwhile, the problem that the subsequent other testing ends cannot acquire the verification code due to unnecessary occupation of too much time by the testing end is avoided. Further, the error information can be used to prompt the user that the verification code cannot be successfully obtained currently, so that the user can check the fault in time. The outputting of the error information may be sending the error information to a pre-bound user terminal, or directly displaying the error information.

Fig. 3 is a flowchart of steps of another login method provided in an embodiment of the present invention, where the method may be applied to a default platform, and as shown in fig. 3, the method may include:

step 201, receiving a creation request sent by a test end; the creating request carries the account of the testing terminal and the system identification of the tested system.

Step 202, responding to the creation request, if a target monitoring task does not exist, creating the target monitoring task for the test terminal, and returning first response information; the target monitoring task is a monitoring task bound with the account and the system identifier, the first response information is used for indicating the test terminal to trigger the tested system to issue a verification code to a target terminal, and the target terminal is configured with a communication number bound with the account.

In the embodiment of the invention, if a target monitoring task exists, namely, a monitoring task bound with the account number used at this time and the system identifier of the system under test exists currently, a target monitoring task created for other test terminals which use the same account number to test the same system under test exists currently, or a target monitoring task which is not yet finished and is applied by the test terminal before exists. The monitoring task is bound with the account and the system identifier, and the monitoring task can be understood to have a corresponding relationship with the account and the system identifier.

Step 203, responding to the query request sent by the test end, and returning the verification code to the test end under the condition that the verification code submitted by the target terminal is monitored based on the target monitoring task.

The implementation manner of each step may refer to the foregoing related description, and is not described herein again.

In summary, the login method provided in the embodiment of the present invention receives a creation request sent by a test end. Responding to the creation request, if the target monitoring task does not exist, creating the target monitoring task for the test terminal, and returning first response information; the target monitoring task is a monitoring task bound with an account of the testing terminal and a system identifier of the tested system, the first response information is used for indicating the testing terminal to trigger the tested system to send a verification code to the target terminal, and the target terminal is configured with a communication number bound with the account. And responding to a query request sent by the test end, and returning the verification code to the test end under the condition that the verification code submitted by the target terminal is monitored based on the target monitoring task. In the embodiment of the invention, after the preset platform successfully creates the monitoring task for the test end, the test end can trigger the tested system to issue the verification code. And the preset platform creates a target monitoring task for the test end only when the target monitoring task bound with the account number used by the test end and the system identification of the tested system tested by the test end does not exist at present. Therefore, when a plurality of test terminals use the same account number to perform parallel test, the situation that the target monitoring task is successfully established for the plurality of test terminals by a preset platform at the same time can be avoided, the plurality of test terminals all apply for the target monitoring task, and then the situation that the plurality of test terminals trigger the tested system to send the verification codes in parallel at the same time is avoided, so that the communication account number receives the plurality of verification codes at the same time, the verification codes corresponding to each test terminal cannot be correctly distinguished, and finally the problem that the tested system cannot be successfully logged in is solved, and the test terminals can be ensured to be successfully logged in the tested system.

Optionally, in the embodiment of the present invention, the creation request sent by the test end may carry the account used by the test end and the system identifier of the system under test to be tested. Wherein the system identifiers of different systems under test are different. The embodiment of the invention also comprises the following steps:

step S61, determining the account and the system identifier carried in the creation request as first comparison information, and determining the account and the system identifier bound to the currently existing monitoring task as second comparison information.

In the embodiment of the invention, the received creation request can be analyzed, and then the carried account and the system identifier of the tested system are extracted from the received creation request to be used as the first comparison information. Further, the account and the system identifier corresponding to each currently existing monitoring task may be acquired, and the second comparison information may be obtained. It should be noted that if there is no listening task currently, the second comparison information may be null. If there are currently a plurality of listening tasks, the second comparison information may be plural.

Further, the first comparison information and each second comparison information may be compared separately, and if the two comparison information are consistent, it may be determined that the first comparison information matches with the second comparison information. If the two are not consistent, it may be determined that the first comparison information does not match the second comparison information. Further, if there is second comparison information that matches the first comparison information, it may be determined that the matching is successful. On the contrary, if there is no second comparison information matching the first comparison information, it may be determined that the matching fails.

And step S62, if second comparison information matched with the first comparison information exists, determining that the target monitoring task does not exist currently.

Step S63, if there is no second comparison information matching with the first comparison information, determining that the target monitoring task exists currently, and returning second response information to the test terminal; and the second response information is used for indicating the test end to send the creating instruction to the preset platform again according to the first interval duration.

In the embodiment of the present invention, the preset platform may represent whether to respond to the creation request sent by the test end this time by returning the first response information or the second response information to the test end, and execute an operation of creating the target monitoring task for the test end. Specifically, when it is determined that the target monitoring task does not exist currently and the target monitoring task is created for the test end execution this time, first response information is returned to indicate the test end to trigger the tested system to issue the verification code. And returning second response information to indicate the test end to resend the creation request after waiting for the first interval duration under the condition that the target monitoring task exists currently and the creation target monitoring task is not executed for the test end at this time. In the waiting period, other testing ends acquire the verification codes from the preset platform, and the existing target monitoring task may be cleared, so that the second response information is returned to indicate the testing end to resend the creation request after waiting for the first interval duration, and the problem that the testing end sends the request too frequently can be avoided while ensuring that the testing end can subsequently apply for the target monitoring task to a certain extent.

It should be noted that, in the embodiment of the present invention, each test end that uses the same account to test the same system under test does not apply for the target monitoring task at the same time, and therefore, task identifiers of the target monitoring tasks of each test end that uses the same account to test the same system under test may be the same or different.

Optionally, the verification codes monitored based on different monitoring tasks in the preset platform are stored corresponding to the task identifiers of the monitoring tasks. The embodiment of the invention can also comprise the following steps:

and step S71, receiving the related information of the verification code submitted by the target terminal.

The verification code related information can be submitted by the target terminal after receiving the verification code short message. In the embodiment of the invention, the target terminal can detect whether the short message is the verification code short message or not after receiving the short message, and if so, the verification code, the account number requesting the verification code and the system identification can be extracted from the verification code short message and submitted to a preset platform as the related information of the verification code. Specifically, the target terminal can extract the relevant information of the verification code in a keyword matching mode. For example, the content of the verification code short message often includes: you are logging in the XX website by the XX account, and the login verification code is XXXXX. Therefore, the related information of the verification code can be extracted by matching keywords with the content of the short message. Or, the numbers of the verification codes senders used by different systems are often different, so that the verification codes and the accounts can be extracted from the content of the short messages, and the system identifiers of the systems can be searched based on the numbers of the senders.

It should be noted that, in the embodiment of the present invention, a preset application program may also be installed in the target terminal, and an account number, a system identifier, and a sender number corresponding to the system under test that are required to be used in the current parallel test scenario are set in the preset application program. Correspondingly, when the target terminal receives the short message from the set sender number needing monitoring, the content is analyzed, and the short message verification code, the login account and the system identification of the logged-in system are identified and extracted. Wherein the system identification can be the name, number, etc. of the system. And under the condition that the login account and the related information of the logged-in system are matched with the preset system identification and account number, extracting the verification code. And the system identification and the account are sent to a preset platform. Or only the short message verification code is identified and extracted, and then the extracted verification code, the set system identification and the set account number are sent to the preset platform. Therefore, even if the short message does not contain the system identification and/or the account number, the related information of the verification code can be successfully acquired. Correspondingly, the verification code related information submitted under the condition is the related information of the verification code triggered by the test end applying for the target monitoring task at present.

Step S72, if the system identifier and the account number in the verification code related information match the account number and the system identifier corresponding to the target monitoring task, storing the verification code in the verification code related information and the task identifier of the target monitoring task correspondingly.

Specifically, the system identifier and the account corresponding to the monitoring task may be compared with the system identifier and the account carried in the information related to the verification code, and if the system identifier and the account are consistent with the system identifier and the account carried in the information related to the verification code, it is indicated that the monitoring task corresponding to the system identifier and the account carried in the information related to the verification code exists. The verification code and the task identifier of the task are stored correspondingly, which may be written into the listening task, for example, into a storage area to be corresponding to the listening task.

If the system identifier and the account number in the related information of the verification code are matched with the account number and the system identifier bound to the target monitoring task, the verification code in the related information of the verification code and the task identifier of the target monitoring task can be correspondingly stored.

In the embodiment of the invention, the related information of the verification code submitted by the target terminal is received, and if the system identification and the account number in the related information of the verification code are matched with the account number and the system identification bound with the target monitoring task, the verification code in the related information of the verification code and the task identification of the target monitoring task are correspondingly stored. Therefore, the verification code can be monitored accurately based on the monitoring task to a certain extent, and the login operation can be ensured to be carried out normally.

The embodiment of the invention can also comprise the following steps:

step S81, for any one of the monitoring tasks, detecting whether the interval duration between the receiving time of the target verification code and the current time is greater than a preset interval threshold value; the target verification code corresponds to a task identifier of the monitoring task, and the receiving time is sent to the preset platform by a terminal submitting the target verification code, or is determined by the preset platform according to the time for receiving the target verification code.

In the embodiment of the invention, the receiving time of the verification code monitored by each monitoring task can be calculated regularly, and the interval duration between the receiving time and the current time can be calculated. And judging whether the interval duration is greater than a preset interval threshold.

For any monitoring task, the related information of the verification code submitted by the terminal can carry the receiving time of the verification code received by the characterization terminal. Correspondingly, the preset platform can correspondingly store the receiving time in the verification code related information and the verification code and the task identifier of the monitoring task. Or, because the difference between the time when the preset platform receives the verification code related information and the time when the terminal receives the verification code is small, the preset platform can record the time when the preset platform receives the verification code related information as the receiving time, and correspondingly store the receiving time and the verification code in the verification code related information and the task identifier of the monitoring task. And when determining whether the interval duration is greater than a preset interval threshold, acquiring the receiving time corresponding to the task identifier of the monitoring task.

And step S82, if the interval duration is greater than the preset interval threshold, clearing the monitoring task.

In the embodiment of the invention, the preset interval threshold can be set according to actual requirements, and the preset interval threshold can be the same as the validity duration of the verification code. Assuming that the preset interval threshold is 5 minutes, the preset platform may perform batch processing every 5 minutes, and perform batch end processing on the listening task whose receiving time is 5 minutes before the current time. In particular, these listening tasks may be ended. The preset platform can execute the step based on the expiration processing timing process.

In the embodiment of the invention, the problem that the monitoring task cannot be applied by other testing ends due to the fact that the testing end does not send the task clearing instruction in time and the unnecessary monitoring task exists in the preset platform can be avoided.

Optionally, in the embodiment of the present invention, after the target monitoring task is created for the test end, a task identifier may be set for the target monitoring task and returned to the test end; the task identities of different listening tasks are different. The responding to the query request sent by the test end, returning the verification code to the test end under the condition that the verification code submitted by the target terminal is monitored based on the target monitoring task, which may specifically include: extracting a target task identifier carried in the query request; the target task identifier is a task identifier of the target monitoring task; and returning the verification code to the test end under the condition that the verification code corresponding to the target task identifier is stored. Specifically, the target task identifier may be matched with a task identifier of the listening task having the corresponding stored identifying code, and if the matching is successful, it is determined that the identifying code corresponding to the target task identifier exists.

In the embodiment of the invention, after the target monitoring task is created for the test end, the task identifier is set for the target monitoring task and returned to the test end, so that the test end can send the query request carrying the target task identifier, the preset platform can return the verification code stored corresponding to the target task identifier to the test end, and the problem of subsequent login failure caused by the fact that the preset platform returns the verification code monitored based on other monitoring tasks can be avoided to a certain extent.

Optionally, the following operations may also be performed in the embodiment of the present invention: receiving a task clearing instruction sent by the testing end; the task clearing instruction carries the target task identifier; and clearing the target listening task indicated by the target task identification in response to the task clearing instruction. Therefore, the preset platform can clear the target monitoring task created for the test terminal as soon as possible, and the problem that the target monitoring task cannot be applied to other test terminals tested by the same tested system by using the same account number due to the fact that the target monitoring task created for the test terminal still exists under the condition that the test terminal acquires the verification code, and further login delay is increased is solved. By timely clearing, other testing terminals which do not apply for the target monitoring task can apply for the target monitoring task as soon as possible, and therefore monitoring efficiency is improved to a certain extent.

It should be noted that, in the embodiment of the present invention, the communication number of the target terminal is used as the first communication number, the communication number used when the tested system sends the verification code short message is used as the second communication number, the verification code related information may further include the first communication number and/or the second communication number, and the preset platform may further store the first communication number and/or the second communication number in correspondence with the task identifier of the monitoring task. Accordingly, when the verification code is returned to the test terminal, the first communication number and/or the second communication number can be returned at the same time. The test terminal can use the verification code to log in under the condition that the first communication number and/or the second communication number carried in the third response message is consistent with the preset first communication number and/or the preset second communication number, so that the problem of error of the verification code is avoided as much as possible.

The following description is made in connection with a specific application scenario. Aiming at the field of software automatic testing of information systems, in the process of automatic testing of a Personal Computer (PC) side webpage, because website login accounts used by a plurality of testing ends are the same and the plurality of testing ends execute testing in parallel, a plurality of different short message verification codes can be received on the same mobile phone, and at the moment, which short message verification code corresponds to a testing task running on which testing end cannot be distinguished. In this case, even if the verification code is manually input manually or the system under test is modified to automatically query the verification code from the system under test to complete automatic login, or the terminal is connected with the test terminal through the data line to acquire the verification code, the verification code cannot be accurately distinguished. Therefore, only different test terminals can use different account numbers to bind different mobile phone numbers for login. Therefore, when large-scale automatic testing is carried out, more account numbers, mobile phone numbers and mobile phone terminals need to be invested, and the resource overhead is high. In one implementation, a universal validation code is set, and each test end uses the universal validation code to log in. However, this method may cause a great potential safety hazard, and requires modification of the system to be tested, which also results in a great implementation cost.

Taking as an example that the target terminal is a mobile phone terminal, the preset platform is an automation platform, the test terminal is an automation execution machine, an application program for monitoring the short message is installed in the mobile phone terminal, a short message verification code management module is deployed in the automation platform, and an automation script is deployed in the automation execution machine.

The short message verification code management module can be provided with the following interfaces: short message monitoring task application interface: the method is used for calling the automation script, creating the monitoring task and managing and controlling so as to avoid generating 2 on-the-way monitoring tasks for the same system identification and the same login account. A short message verification code entering interface: the system is used for calling the mobile phone terminal, inquiring the on-the-way monitoring task according to the system identification and the login account, and writing the short message verification code and the receiving time. The short message verification code inquiry function interface: and the short message verification code is used for calling the automatic script and inquiring the short message verification code according to the task identifier. A short message monitoring task ending interface: the method is used for calling the automation script and ending the on-the-way monitoring task according to the task identifier.

Fig. 4 is a schematic overall flow chart provided in an embodiment of the present invention, and as shown in fig. 4, the mobile phone terminal may monitor the specified short message number based on the application program, and perform parsing and judgment when a short message sent by the specified short message number is monitored, so as to judge whether a correct short message verification code is obtained. And returning to the step of monitoring the appointed short message number when the correct short message verification code is not acquired. And when the correct short message verification code is acquired, the correct short message verification code is sent to the automation platform. The specified short message number can be a communication number used when the verification code is issued by the system to be tested. The correct short message verification code may be: and the verification code corresponding to the preset system identification of the tested system and the account used by the testing end, namely, the short message verification code is issued when the testing end logs in the tested system by using the account. The automation platform may execute a verification code warehousing service flow. Fig. 5 is a schematic view of a service flow provided by an embodiment of the present invention, and as shown in fig. 5, an automation platform may receive verification code warehousing information, that is, the verification code related information. The verification code storage information can carry parameters: the system comprises a system identification, a login account, a verification code and a mobile phone number. And then, judging whether the same system identification + on-the-way monitoring task of the login account exists or not. In this case, an in-transit listening task may be understood as a task that is not completed in operation. If yes, the verification code, the mobile phone number and the current time are written into a record table of the monitoring task, and the processing is returned to be completed. Wherein the current time is the receiving time. The verification code, the mobile phone number and the current time are correspondingly stored with the task identifier of the monitoring task when the verification code, the mobile phone number and the current time are written into the record table of the monitoring task. If not, no processing is done and processing is returned to completion.

The automatic execution machine can input a login account number and a login password based on an automatic script and then apply for short message verification code monitoring to the automatic platform. Correspondingly, the automation platform can execute the preprocessing service flow of the short message monitoring application based on the short message verification code management module. Fig. 6 is another schematic service flow diagram provided in an embodiment of the present invention, and as shown in fig. 6, an automation platform may receive an authentication code monitoring request, where parameters of the authentication code monitoring request may include a system identifier and a login account. The verification code monitoring request is the aforementioned creation request. And then, judging whether the on-the-way monitoring task of the same system identification + login account exists or not. That is, it is determined whether a target listening task currently exists. If so, executing error throwing return: the same listening task already exists. That is, the second response information is returned to the automated execution machine. If not, the monitoring task warehousing operation can be executed, and the monitoring task identifier is returned. Namely, a target monitoring task is created for the automatic execution machine, and the first response information and the task identifier of the target monitoring task are returned to the automatic execution machine.

Further, the automation script may determine whether the application was successful. Specifically, whether the application is successful may be determined according to whether the first response message is received. If the monitoring task is not successfully applied, the step of applying for short message verification code monitoring by the automatic script can be carried out again after 30 seconds, so that the verification code can be obtained through cyclic application. If the short message verification code is successful, the automatic script can click a short message sending button, wait for 30 seconds and update the total waiting time, and then use the task identifier of the monitoring task to inquire the short message verification code for the automatic platform. The automation platform may perform a captcha query operation based on the task identification. That is, if found, it may be returned to the automated execution machine, and otherwise, it may not be returned. Accordingly, the automated execution machine may determine whether the verification code is queried. Specifically, it may be determined whether a verification code returned by the automation platform is received. If the verification code is not inquired, whether the current total waiting time exceeds a preset time threshold or not can be judged, and if the current total waiting time exceeds the preset time threshold, the automatic script is wrongly thrown: and if the verification code is not acquired, outputting error reporting information, and ending the processing flow. And if not, re-entering the step of waiting for 30 seconds and updating the total waiting time to circularly call the short message reading interface, namely the short message verification code inquiry function interface to acquire the verification code.

If the verification code is inquired, the verification code can be filled into the position of the specified object of the automatic script, namely, the verification code is input into the corresponding control, and the website login is completed. Then, the subsequent automation test steps are completed, i.e., the subsequent other operations of the automation script are continued to be executed. The subsequent automated testing steps may be preset according to actual requirements, and may include, for example, specific information query, business handling, and the like.

Meanwhile, after the website login is completed, a task clearing instruction can be sent to the automation platform, namely, the short message verification code management module is informed that the monitoring task is finished, and the automation platform can update the state of the monitoring task to be finished. The automation platform may also perform batch processing of in-transit snoop tasks and clear the snoop tasks in time.

In the embodiment of the invention, under the scene that a plurality of test terminals use the same account number to perform parallel test on the same system to be tested, even if the plurality of test terminals log in parallel, the automatic platform controls the number of monitoring tasks corresponding to the same account number and system identification, so that the plurality of test terminals can obtain the verification codes in sequence, and the problem that the verification codes cannot be correctly distinguished due to the concurrence of the verification codes is avoided.

Aiming at the function of automatically acquiring the short message verification code, when a website system with verification code authentication is subjected to automatic testing by using the same account number in parallel, when a plurality of same automatic logins are concurrent, the successful logins can be ensured by the verification code authentication, so that the subsequent testing operation is successfully executed. In the embodiment of the invention, in the automatic script execution process, manual intervention is not needed, verification codes are not needed to be input manually, and full automation can be realized. And the system of the tested network station is not required to be modified, and the mobile phone which is not required to receive the verification code is connected with the automatic execution machine through a data line, so that the implementation cost can be reduced to a certain extent, and the limitation of the scheme is reduced.

It should be noted that, in the embodiment of the present invention, the parallel test may be performed in a regression test link, or the parallel test may be performed periodically and automatically at a preset specific time, and the like.

In the embodiment of the invention, the test terminal can be deployed in a cloud server, and a plurality of test terminals can be operated on one server, or only one test terminal is operated. Alternatively, the test end may also be understood as a local physical machine, which is not limited in this embodiment of the present invention. One test end may run one test task. In an actual application scenario, the system under test may include multiple application systems, and different test terminals may perform subsequent test operations on some of the application systems, or may perform subsequent test operations on each application system. For a plurality of application systems, login authentication needs to be performed through the unified authentication portal, and after entering the unified authentication portal, each application system can enter to execute corresponding test operation. When a plurality of application systems are tested by using a plurality of testing terminals, the same account bound with the same mobile phone number is used when the unified authentication portal is logged in.

In the embodiment of the invention, the mobile phone can monitor the verification code issued by the short message number corresponding to the tested system based on the pre-installed application program, and return the verification code, the preset system identification and the preset account number to the preset platform. Through interaction among the preset platform, the testing end and the mobile phone end, when multiple testing tasks use the same account number to test the website in parallel, the verification codes during login can be correctly distinguished, and the verification codes are automatically and correctly filled, so that the login success rate can be greatly improved.

It is assumed that there are two testing terminals, and the two testing terminals use the same account number to test the system under test at the same time, that is, perform parallel testing. After the preset platform successfully creates the monitoring task for the test end, the test end triggers the tested system to issue the verification code. And the preset platform creates the target monitoring task for the test end only when the target monitoring task does not exist currently. Therefore, when a plurality of test terminals use the same account number to perform parallel test, the situation that the target monitoring task is successfully established for the plurality of test terminals by a preset platform at the same time can be avoided, the plurality of test terminals all apply for the target monitoring task, and then the situation that the plurality of test terminals trigger the tested system to send the verification codes in parallel at the same time is avoided, so that the communication account number receives the plurality of verification codes at the same time, the verification codes corresponding to each test terminal cannot be correctly distinguished, and finally the problem that the tested system cannot be successfully logged in is solved, and the test terminals can be ensured to be successfully logged in the tested system.

Further, assume that there are two testing terminals, which use the same account number to test the system under test at different time periods. Therefore, even after the preset platform successfully creates the monitoring task for the test end, the test end can trigger the tested system to issue the verification code. And the preset platform can ensure that each test terminal can acquire the verification code only under the condition that the target monitoring task is established for the test terminal when the target monitoring task does not exist at present, so that login is completed.

Fig. 7 is a structural diagram of a login apparatus according to an embodiment of the present invention, where the apparatus may be applied to a test end, and the apparatus may include:

a first sending module 301, configured to send a creation request to a preset platform; the creation request carries an account number of the testing terminal and a system identification of a tested system to be tested, the creation instruction is used for indicating the preset platform to create a target monitoring task for the testing terminal and return first response information under the condition that the target monitoring task does not exist at present, and the target monitoring task is a monitoring task bound with the account number and the system identification;

the triggering module 302 is configured to trigger the system under test to issue a verification code to a target terminal when the first response information is received; the target terminal is configured with a communication number bound by the account;

the login module 303 is configured to send an inquiry request to the preset platform, and perform login based on a verification code returned by the preset platform in response to the inquiry request when the verification code is received; the verification code returned by the preset platform is monitored based on the target monitoring task, and the target monitoring task is used for monitoring the verification code submitted by the target terminal.

In summary, the login apparatus provided in the embodiment of the present invention sends a creation request to a preset platform; the creating request carries an account of the testing terminal and a system identifier of the tested system, and the creating instruction is used for indicating the preset platform to create a target monitoring task for the testing terminal and return first response information under the condition that the target monitoring task does not exist currently, wherein the target monitoring task is a monitoring task bound with the account used by the testing terminal and the system identifier of the tested system. Under the condition of receiving the first response information, triggering the tested system to send a verification code to the target terminal; and the target terminal is configured with a communication number bound by the account number. Sending a query request to a preset platform, and logging in based on a verification code when the verification code returned by the preset platform in response to the query request is received; the verification code returned by the preset platform is monitored based on a target monitoring task, and the target monitoring task is used for monitoring the verification code submitted by the target terminal. In the embodiment of the invention, after the preset platform successfully creates the monitoring task for the test end, the test end can trigger the tested system to issue the verification code. And the preset platform creates a target monitoring task for the test end only when the target monitoring task bound with the account used by the test end and the system identifier of the tested system tested by the test end does not exist at present. Therefore, when a plurality of test terminals use the same account number to perform parallel test, the situation that the target monitoring tasks are successfully established for the plurality of test terminals by a preset platform at the same time can be avoided, the plurality of test terminals all apply for the target monitoring tasks, and then the situation that the plurality of test terminals trigger the tested system to send the verification codes in parallel at the same time is avoided, so that the communication account number can receive the plurality of verification codes at the same time, the verification codes corresponding to each test terminal can not be correctly distinguished, and finally the problem that the tested system can not be successfully logged in is solved, and the test terminals can be ensured to be successfully logged in the tested system.

Optionally, the apparatus further comprises:

the acquisition module is used for acquiring the task identifier of the target monitoring task carried in the first response information under the condition of receiving the first response information to obtain a target task identifier;

the second sending module is used for sending a task clearing instruction to the preset platform under the condition of receiving the verification code returned by the preset platform in response to the query request; the task clearing instruction carries the target task identifier, and the task clearing instruction is used for instructing the preset platform to clear the target monitoring task indicated by the target task identifier.

Optionally, the apparatus further comprises:

a third sending module, configured to, in a case that second response information returned by the preset platform is received, send the creation instruction to the preset platform again according to the first interval duration until the target monitoring task is successfully created for the test end;

and the second response information is returned by the preset platform under the condition that the target monitoring task is not created for the test end.

Optionally, the login module 303 is specifically configured to:

sending a query request carrying the target task identifier to the preset platform according to a second time interval until third response information returned by the preset platform in response to the query request is received;

the third response information comprises a verification code which is stored in the preset platform corresponding to the target task identifier, and the verification code which is monitored based on different monitoring tasks in the preset platform is stored in the preset platform corresponding to the task identifier of the monitoring task.

Optionally, the apparatus further comprises:

the timing module is used for timing after receiving the first response information to obtain timing duration;

and the output module is used for stopping the operation of sending the query request carrying the target task identifier to the preset platform and outputting error reporting information under the condition that the timing duration reaches a preset duration threshold and the third response information is not received.

Optionally, the test end is any one of at least two test ends that use the same account to test the same tested system in parallel.

Fig. 8 is a block diagram of another login apparatus according to an embodiment of the present invention, where the apparatus may be applied to a default platform, and the apparatus may include:

a first receiving module 401, configured to receive a creation request sent by a test end; the creating request carries the account of the testing terminal and the system identification of the tested system;

a creating module 402, configured to respond to the creating request, create a target listening task for the test end if the target listening task does not exist, and return first response information; the target monitoring task is a monitoring task bound with the account and the system identifier, the first response information is used for indicating the test terminal to trigger the tested system to issue a verification code to a target terminal, and the target terminal is configured with a communication number bound with the account;

a returning module 403, configured to, in response to the query request sent by the testing end, return the verification code to the testing end when the verification code submitted by the target terminal is monitored based on the target monitoring task.

In summary, the login device provided in the embodiment of the present invention receives a creation request sent by a test end. Responding to the creation request, if the target monitoring task does not exist, creating the target monitoring task for the test terminal, and returning first response information; the target monitoring task is a monitoring task bound with an account of the testing terminal and a system identifier of the tested system, the first response information is used for indicating the testing terminal to trigger the tested system to send a verification code to the target terminal, and the target terminal is configured with a communication number bound with the account. And responding to a query request sent by the test end, and returning the verification code to the test end under the condition that the verification code submitted by the target terminal is monitored based on the target monitoring task. In the embodiment of the invention, after the preset platform successfully creates the monitoring task for the test end, the test end can trigger the tested system to issue the verification code. And the preset platform creates a target monitoring task for the test end only when the target monitoring task bound with the account number used by the test end and the system identification of the tested system tested by the test end does not exist at present. Therefore, when a plurality of test terminals use the same account number to perform parallel test, the situation that the target monitoring task is successfully established for the plurality of test terminals by a preset platform at the same time can be avoided, the plurality of test terminals all apply for the target monitoring task, and then the situation that the plurality of test terminals trigger the tested system to send the verification codes in parallel at the same time is avoided, so that the communication account number receives the plurality of verification codes at the same time, the verification codes corresponding to each test terminal cannot be correctly distinguished, and finally the problem that the tested system cannot be successfully logged in is solved, and the test terminals can be ensured to be successfully logged in the tested system.

Optionally, the apparatus further comprises:

a first determining module, configured to determine the account and the system identifier carried in the creation request as first comparison information, and determine the account and the system identifier bound to the currently existing monitoring task as second comparison information;

a second determining module, configured to determine that the target listening task does not exist currently if second comparison information matching the first comparison information exists;

a third determining module, configured to determine that the target monitoring task currently exists if there is no second comparison information that matches the first comparison information, and return a second response information to the testing end; and the second response information is used for indicating the test end to send the creating instruction to the preset platform again according to the first interval duration.

Optionally, the verification code monitored based on different monitoring tasks is stored in correspondence with the task identifier of the monitoring task; the device further comprises:

the second receiving module is used for receiving the related information of the verification code submitted by the target terminal;

and the storage module is used for correspondingly storing the verification code in the verification code related information and the task identifier of the target monitoring task if the system identifier and the account in the verification code related information are matched with the account and the system identifier bound with the target monitoring task.

Optionally, the apparatus further comprises:

the detection module is used for detecting whether the interval duration between the receiving time of the target verification code and the current time is greater than a preset interval threshold value or not for any monitoring task; the target verification code corresponds to a task identifier of the monitoring task, and the receiving time is sent to the preset platform by a terminal submitting the target verification code, or is determined by the preset platform according to the time for receiving the target verification code;

and the clearing module is used for clearing the monitoring task when the interval duration is greater than the preset interval threshold.

Optionally, the apparatus further comprises: the setting module is used for setting a task identifier for the target monitoring task and returning the task identifier to the test end after the target monitoring task is created for the test end; the task identifiers of different monitoring tasks are different;

the return module 403 is specifically configured to:

extracting a target task identifier carried in the query request; the target task identifier is a task identifier of the target monitoring task;

and returning the verification code to the test end under the condition that the verification code corresponding to the target task identifier is stored.

Optionally, the apparatus further comprises:

the third receiving module is used for receiving the task clearing instruction sent by the testing end; the task clearing instruction carries the target task identifier;

and the second clearing responds to the task clearing instruction and clears the target listening task indicated by the target task identification.

Fig. 9 is a block diagram of a login system according to an embodiment of the present invention, and as shown in fig. 9, the login system 50 may include: the system comprises a testing terminal 501, a preset platform 502 and a target terminal 503, wherein the target terminal 503 is configured with a communication number bound with an account of the testing terminal 501; the testing terminal 501 is configured to send a creation request to the preset platform 502; the creation request carries the account of the testing terminal 501 and the system identifier of the tested system; the preset platform 502 is configured to respond to the received creation request, create a target monitoring task for the test terminal 501 if the target monitoring task does not exist, and return first response information; the target monitoring task is a monitoring task bound with the account and the system identifier; the testing terminal 501 is further configured to trigger the system under test to issue a verification code to the target terminal 503 when receiving the first response message; the target terminal 503 is configured to submit the received verification code to the preset platform 502; the test terminal 501 is further configured to send a query request to the preset platform 502; the preset platform 502 is further configured to respond to the received query request, and return the verification code to the test terminal 501 when the verification code submitted by the target terminal 503 is monitored based on the target monitoring task; the testing terminal 501 is further configured to log in based on the verification code when receiving the verification code returned by the preset platform 502 in response to the query request. Wherein, the logging system is a test system.

The present invention also provides an electronic device, see fig. 10, including: a processor 901, a memory 902 and a computer program 9021 stored on and executable on the memory, which when executed by the processor implements the login method of the previous embodiments.

The present invention also provides a readable storage medium, wherein the instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to execute the login method of the aforementioned embodiment.

For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.

It should be noted that various information and data acquired in the embodiment of the present invention are acquired under the authorization of the information/data holder.

The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.

In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the invention and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It will be appreciated by those skilled in the art that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components in a sequencing device according to the present invention. The present invention may also be embodied as an apparatus or device program for carrying out a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents and improvements made within the spirit and principle of the present invention are intended to be included within the scope of the present invention.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A login method is applied to a test end, and the method comprises the following steps:

2. The method of claim 1, further comprising:

under the condition that the first response information is received, acquiring a task identifier of the target monitoring task carried in the first response information to obtain a target task identifier;

under the condition that the verification code returned by the preset platform in response to the query request is received, sending a task clearing instruction to the preset platform; the task clearing instruction carries the target task identifier, and the task clearing instruction is used for instructing the preset platform to clear the target monitoring task indicated by the target task identifier.

3. The method of claim 1, wherein after sending the create request to the pre-defined platform, the method further comprises:

under the condition of receiving second response information returned by the preset platform, sending the creating instruction to the preset platform again according to the first interval duration until the target monitoring task is successfully created for the test end;

4. The method of claim 2, wherein sending the query request to the default platform comprises:

5. The method of claim 4, further comprising:

timing after receiving the first response information to obtain timing duration;

and under the condition that the timing duration reaches a preset duration threshold and the third response information is not received, stopping the operation of sending the query request carrying the target task identifier to the preset platform, and outputting error reporting information.

6. The method according to any one of claims 1 to 5, wherein the test terminal is any one of at least two test terminals that use the same account number to test the same system under test in parallel.

7. A login method is applied to a preset platform, and the method comprises the following steps:

and responding to a query request sent by the test end, and returning the verification code to the test end under the condition that the verification code submitted by the target terminal is monitored based on the target monitoring task.

8. The method of claim 7, further comprising:

determining the account and the system identification carried in the creation request as first comparison information, and determining the account and the system identification bound to the currently existing monitoring task as second comparison information;

if second comparison information matched with the first comparison information exists, determining that the target monitoring task does not exist currently;

if the second comparison information matched with the first comparison information does not exist, determining that the target monitoring task exists currently, and returning second response information to the test end; and the second response information is used for indicating the test end to send the creating instruction to the preset platform again according to the first interval duration.

9. The method according to claim 7, wherein verification codes heard based on different listening tasks are stored corresponding to task identifiers of the listening tasks; the method further comprises the following steps:

receiving related information of a verification code submitted by the target terminal;

and if the system identification and the account number in the verification code related information are matched with the account number and the system identification bound to the target monitoring task, correspondingly storing the verification code in the verification code related information and the task identification of the target monitoring task.

10. The method of claim 9, further comprising:

for any monitoring task, detecting whether the interval duration of the receiving time of the target verification code and the current time is greater than a preset interval threshold value; the target verification code corresponds to a task identifier of the monitoring task, and the receiving time is sent to the preset platform by a terminal submitting the target verification code, or is determined by the preset platform according to the time for receiving the target verification code;

and if the interval duration is greater than the preset interval threshold, clearing the monitoring task.

11. The method of claim 9, further comprising: after the target monitoring task is created for the test end, a task identifier is set for the target monitoring task and returned to the test end; the task identifiers of different monitoring tasks are different;

the returning the verification code to the test terminal in response to the query request sent by the test terminal under the condition that the verification code submitted by the target terminal is monitored based on the target monitoring task includes:

12. The method of claim 11, further comprising:

receiving a task clearing instruction sent by the testing end; the task clearing instruction carries the target task identifier;

and clearing the target listening task indicated by the target task identification in response to the task clearing instruction.

13. A login system is characterized by comprising a testing end, a preset platform and a target terminal, wherein the target terminal is provided with a communication number bound with an account number of the testing end;

the test end is also used for sending a query request to the preset platform;

14. A login device, which is applied to a test end, the device comprising:

15. A login device is applied to a preset platform, and comprises:

16. An electronic device, comprising:

processor, memory and computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1-12 when executing the program.

17. A readable storage medium, wherein instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the method of any of claims 1-12.