Test account generation method and device, equipment and medium

Abstract

The embodiment of the invention discloses a test account generation method and device, equipment and a medium. The scheme can comprise the steps that a test platform obtains a test scene determined by a user; determining a test account for testing based on the test scene; determining a plurality of selectable configuration information associated with the test scene; obtaining target configuration information determined by the user based on the plurality of pieces of selectable configuration information; associating the target configuration information with the test account, and generating test configuration information associated with the test account; sending the test configuration information to a business server; and the service server can feed back test service data corresponding to the test account according to the test configuration information when the test account accesses the service server.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method, device, equipment and medium for generating a test account. Background Art

[0002] A test account is a user account created for product testing. Through a test account, the product development team or product testers can test the product's functions, performance, security, user experience, etc., to ensure product quality, user experience, etc.

[0003] As the requirements for product quality and user experience become increasingly higher, the efficiency of generating test accounts, as a guarantee of product quality and user experience, is becoming increasingly important. Summary of the invention

[0004] The embodiments of this specification provide a method, apparatus, device and medium for generating a test account to improve the efficiency of generating a test account.

[0005] To solve the above technical problems, the embodiments of this specification are implemented as follows:

[0006] A method for generating a test account provided in an embodiment of the present specification includes:

[0007] The test platform obtains the test scenario determined by the user;

[0008] Based on the test scenario, determine a test account for testing;

[0009] Determining a number of optional configuration information associated with the test scenario;

[0010] Acquire target configuration information determined by the user based on the plurality of optional configuration information;

[0011] Associating the target configuration information with the test account to generate test configuration information associated with the test account;

[0012] The test configuration information is sent to a service server; the service server can feed back test service data corresponding to the test account according to the test configuration information when the test account accesses the service server.

[0013] An embodiment of the present specification provides a device for generating a test account, including:

[0014] The test scenario acquisition module is used for the test platform to acquire the test scenario determined by the user;

[0015] A test account determination module, used to determine a test account for testing based on the test scenario;

[0016] An optional configuration information determination module, used to determine a number of optional configuration information associated with the test scenario;

[0017] A target configuration information acquisition module, used to acquire the target configuration information determined by the user based on the plurality of optional configuration information;

[0018] A test configuration information generating module, used to associate the target configuration information with the test account, and generate test configuration information associated with the test account;

[0019] The sending module is used to send the test configuration information to the service server; the service server can feed back the test service data corresponding to the test account according to the test configuration information when the test account accesses the service server.

[0020] A test account generation device provided in an embodiment of the present specification includes:

[0021] at least one processor; and,

[0022] a memory communicatively connected to the at least one processor; wherein,

[0023] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can implement the above-mentioned method for generating a test account.

[0024] An embodiment of the present specification provides a computer-readable medium on which computer-readable instructions are stored. The computer-readable instructions can be executed by a processor to implement the above-mentioned method for generating a test account.

[0025] At least one embodiment provided in this specification can achieve the following beneficial effects: the embodiment of this specification obtains the test scenario determined by the user through the test platform, determines the test account used for testing based on the test scenario, determines several optional configuration information associated with the test scenario, obtains the target configuration information determined by the user based on the several optional configuration information, associates the target configuration information with the test account, generates test configuration information associated with the test account, and sends the test configuration information to the business server, so that the test account containing the test configuration information can be automatically generated, reducing manual workload and improving the efficiency of generating test accounts.

[0026] On the other hand, in the solution of the embodiment of this specification, the test platform can provide the user with several optional configuration information associated with the scenario according to the test scenario determined by the user, so that the user can determine the target configuration information required for the test account, and the test platform can also associate the test account with the target configuration information, so that the user does not need to have the technology to generate too many test accounts, for example, the user may not have the ability to determine the configuration information associated with the test scenario, or the ability to associate the configuration information with the test account. The test platform in the embodiment of this specification can provide the user with visual configuration information, and generate the test configuration information associated with the test account according to the needs of the test scenario, without the user having to write too much code, and without relying too much on the experience of technical personnel, and the generation of test accounts is more convenient. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0028] Figure 1 This is a schematic diagram of an application scenario of a method for generating a test account provided in an embodiment of the present application;

[0029] Figure 2 It is a flowchart of a method for generating a test account provided by an embodiment of the present application;

[0030] Figure 3 This is a schematic diagram of a process for a test platform to obtain optional configuration information provided by an embodiment of the present application;

[0031] Figure 4 This is a schematic diagram of a process for a user to generate a test account based on a test platform, provided in an embodiment of the present application;

[0032] Figure 5 The embodiments of this specification provide corresponding to Figure 2 A structural diagram of a device for generating a test account;

[0033] Figure 6 The embodiments of this specification provide corresponding to Figure 2 A schematic diagram of the structure of a test account generation device. DETAILED DESCRIPTION

[0034] In order to make the purpose, technical solutions and advantages of one or more embodiments of this specification clearer, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of one or more embodiments of this specification.

[0035] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards in the relevant regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0036] In order to solve the defects in the prior art, this solution provides the following embodiments:

[0037] Figure 1 Schematic diagram of an application scenario of a method for generating a test account provided in an embodiment of the present application. Figure 1 As shown, the application scenario includes a test platform 1 and a business server 2.

[0038] The test platform 1 is a platform that can generate test accounts. Users with product testing needs, such as product development teams, product update and maintenance teams, and product testers, can generate test accounts through the test platform 1 to test the products to be tested.

[0039] Specifically, the test platform 1 can be in hardware form or in software form. When the test platform 1 is in hardware form, it can be various electronic devices, such as Figure 1 desktop computer shown. Optional, although in Figure 1 It is shown that the test platform 1 can be a desktop computer, but in actual application, the test platform 1 can also be other electronic devices, such as smart watches, smart phones, handheld computers, virtual reality terminals or augmented reality terminals, etc., and is not limited to the example types given here. When the test platform 1 is in the form of software, it can be installed in the electronic devices listed above. It can be implemented as multiple software or software modules (for example, software or software modules for providing distributed services), or it can be implemented as a single software or software module. No specific limitation is made here.

[0040] Business server 2 is a server that the product to be tested needs to interact with. Specifically, business server 2 can be an independent physical server, or a server cluster or distributed file system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0041] In the embodiments of the present specification, the test platform 1 and the service server 2 may be directly or indirectly connected via wired or wireless communication.

[0042] Specifically, the test platform 1 may be pre-configured with a variety of test scenarios, and the user may select a test scenario from a variety of test scenarios according to the test requirements, or the user may also create a new test scenario in the test platform. Among them, the test scenario may be various test links set for the test requirements of the product to be tested. If some functions of the product to be tested require the business server 2 to provide some data, when the product to be tested is tested, it can interact with the business server 2 based on the test account to complete the test of the product to be tested. The test platform 1 can obtain the test scenario determined by the user, and can determine the test account for testing based on the test scenario. The test platform 1 can also determine several optional configuration information associated with the test scenario. The user can determine the target configuration information from several optional configuration information through the test platform 1. The test platform 1 can associate the target configuration information with the test account and generate the test configuration information associated with the test account. The test platform 1 can also send the test configuration information to the business server 2, so that when the test account is used for testing, the product to be tested can obtain the test data from the business server 2 to detect the performance of the product to be tested.

[0043] The following describes a method for generating a test account provided in an embodiment of this specification in conjunction with the accompanying drawings.

[0044] Figure 2 1 is a flow chart of a method for generating a test account provided by an embodiment of the present application. From a program perspective, the execution subject of the process may be a program installed in a test platform. From a hardware perspective, the execution subject of the process may be a test platform capable of generating a test account. Figure 2 As shown, the method may include the following steps.

[0045] Step 202: The test platform obtains the test scenario determined by the user.

[0046] In the embodiments of this specification, the test platform is a platform that can generate a test account. A user can generate a test account based on the test platform, and then use the test account to test the product to be tested.

[0047] Furthermore, the test platform in the embodiments of this specification may also be a platform that can test the product to be tested through a test account. The user can generate a test account based on the test platform, and can also use the test account to test the product to be tested based on the test platform.

[0048] In the embodiments of this specification, a test account is a user account created for testing a product. The test account can simulate real user operations to test the product's functions, performance, security, user experience, etc., thereby ensuring the product's quality, user experience, etc.

[0049] In actual applications, the test platform can obtain the test scenario determined by the user. Specifically, the test platform can display a scenario list containing one or more test scenarios, and the user can select a test scenario from the scenario list. Alternatively, the user can input the test scenario to be tested in the test platform, and then the test platform obtains the test scenario input by the user. Alternatively, the user can also create a new test scenario in the test platform.

[0050] In the embodiments of this specification, users refer to users who have product testing needs, such as product development teams, product update and maintenance teams, and product testers.

[0051] The test scenario in the embodiments of this specification may be a test scenario of a product to be tested. The product to be tested may be software, a program, a website, a web page in a website, and the like.

[0052] In actual applications, during normal use of the product under test, in addition to using the services provided by the server to which the product under test belongs, other service servers may also be required. In the embodiments of this specification, the product under test needs to interact with other service servers to obtain service support from the service servers.

[0053] For example, if the product to be tested is an e-commerce platform, the e-commerce platform needs to interact with the business servers of financial systems such as banks to implement the payment function of the e-commerce platform. The e-commerce platform also needs to interact with the business server that stores user credit data to obtain the user's credit data, so as to implement the installment payment function based on the user's credit data.

[0054] For example, the product to be tested is web page A. Web page A needs to interact with web page B through a hyperlink to implement the function of accessing web page B from web page A. Web page A may also need to interact with a file server to implement the function of storing files for users to download.

[0055] In the embodiments of this specification, the test scenarios may include product function test scenarios, product performance test scenarios, product safety test scenarios, and product experience test scenarios. Specifically, the product function test scenario may be a scenario for testing product functions, such as a scenario for testing the payment function of the above-mentioned e-commerce platform. The product performance test scenario may be a scenario for testing product performance, such as a scenario for testing the data concurrency processing performance of an e-commerce platform when multiple users make payments at the same time. The product safety test scenario may be a scenario for testing product safety, such as a scenario for testing the data security of a product when interacting with a business server. The product experience test scenario may be a scenario for testing the user experience of a product, such as a scenario for testing the data interaction efficiency of a product and a business server.

[0056] Optionally, the test scenario determined by the user and obtained by the test platform may be one test scenario or multiple test scenarios, which is not limited here.

[0057] Step 204: Based on the test scenario, determine a test account for testing.

[0058] In practical applications, one test scenario may correspond to one product to be tested. Alternatively, one test scenario may correspond to multiple products to be tested, etc. Based on the test scenario, a test account for testing is determined, specifically, based on the test scenario, a test account for testing the product to be tested corresponding to the test scenario is determined.

[0059] Optionally, different test scenarios may require different attributes of the test account. For example, in a product function test scenario, the required test account attribute may be read-only permission (Read-Only), and in a product security test scenario, the required test account attribute may be management permission (Manage), etc.

[0060] Optionally, different products to be tested may require different attributes of the test account. For example, the login address of the test account required by product to be tested a is city a, and the login address of the test account required by product to be tested b is city b. For another example, the number of resources required by the test account of product to be tested a is A, and the number of resources required by the test account of product to be tested b is B, etc.

[0061] In the embodiments of this specification, the correspondence between the test scenario and the test account may be pre-stored, and the test platform may use the correspondence to determine the test account based on the acquired test scenario.

[0062] Optionally, after selecting or creating a test scenario, the user can fill in one or more test accounts corresponding to the test scenario, and the test platform can then determine the test account to use for the test. Furthermore, the test platform can also save the correspondence between the test scenario and the test account filled in by the user for subsequent testing.

[0063] Optionally, the test account determined for testing may include an account and a password, and the user may then log in to the product to be tested using the account and the password to test the product to be tested.

[0064] In actual applications, different test scenarios can be tested using different numbers of test accounts. For example, a scenario for testing product safety performance can be tested using one test account; a scenario for testing product performance can be tested using multiple test accounts, etc. Optionally, different test scenarios can also be tested using the same number of test accounts. For example, different test scenarios can all be tested using one test account, etc. In the embodiments of this specification, the number of test accounts used for testing can also be determined based on the test scenario.

[0065] Specifically, the test account determined to be used for testing may be one test account or multiple test accounts.

[0066] Step 206: Determine several optional configuration information associated with the test scenario.

[0067] In the embodiment of this specification, the optional configuration information may include configuration information indicating the attributes of the test account. Specifically, the attributes of the test account may include the role attributes, permission level attributes, etc. of the test account.

[0068] The role attribute of a test account may refer to the identity or responsibilities played by the test account in the test scenario. By assigning different role attributes to the test account, the behavior of different users in the real environment can be simulated, thereby comprehensively testing the product to be tested. Specifically, the roles represented by the role attributes of the test account may include regular user, restricted user, administrator, guest, and so on. Alternatively, the role attributes may also be represented by specific characteristics, such as personal characteristic attributes such as date of birth, height, weight, education, occupation, address, and number of resources.

[0069] The permission level attribute of the test account may refer to the operation permission or access permission of the test account in the test scenario. By setting different permission level attributes for the test account, the operation scope and access scope of the test account can be controlled, thereby ensuring the security and effectiveness of the test. Specifically, the permission level represented by the permission level attribute of the test account may include read-only permission, edit permission (Edit), management permission, delete permission (Delete), etc.

[0070] In the embodiment of this specification, the optional configuration information may also represent the interface information of the interface of the service server associated with the test scenario. The interface of the service server associated with the test scenario may be the interface for the interaction between the product to be tested and the service server in the test scenario.

[0071] Optionally, the interface information may include at least one of input parameter information, output parameter information, interface name information, and method name information. Specifically, the input parameter information is the information input to the interface of the business server. The output parameter information is the information output by the interface of the business server. The interface name information is the identification information of the interface of the business server. The method name information is the name information of the method of processing information by the interface of the business server.

[0072] In the embodiment of this specification, different test scenarios can be associated with different optional configuration information. In the embodiment of this specification, the association relationship between the test scenario and the optional configuration information can be pre-stored, so that several optional configuration information associated with the test scenario can be determined based on the association relationship.

[0073] In the embodiment of this specification, the determined several optional configuration information may be one optional configuration information or multiple optional configuration information.

[0074] Furthermore, determining a number of optional configuration information associated with the test scenario may also include displaying the several optional configuration information. For example, the test platform may display the several optional configuration information so that the user can determine the target configuration information from the several optional configuration information.

[0075] Step 208: Obtain target configuration information determined by the user based on the plurality of optional configuration information.

[0076] In the embodiments of the present specification, a user may determine target configuration information from a number of optional configuration information in a test platform, and then the test platform may acquire the target configuration information determined by the user.

[0077] Specifically, the user can select target configuration information from a number of optional configuration information. For example, the test platform can display a control for selecting configuration information, so that the user can select the configuration information corresponding to the control by selecting the control. Furthermore, the test platform can also provide an area for filling in a specific value corresponding to the configuration information, so that the user can fill in the specific value corresponding to the configuration information in the area.

[0078] As a specific implementation, the acquired target configuration information may include the role attribute and the permission level attribute of the test account, and may specifically be at least one of the attribute value corresponding to the role attribute and the attribute value corresponding to the permission level attribute.

[0079] As a specific implementation, the acquired target configuration information may include interface information of an interface of a business server associated with the test scenario, such as at least one of input parameter information, output parameter information, interface name information, and method name information.

[0080] Step 210: Associating the target configuration information with the test account to generate test configuration information associated with the test account.

[0081] In the embodiment of the present specification, associating the target configuration information with the test account may be to determine at least one of the role attribute and the permission level attribute of the test account. Specifically, the attribute value of the role attribute in the target configuration information may be determined as the attribute value of the role attribute of the test account, and / or the attribute value of the permission level attribute in the target configuration may be determined as the attribute value of the permission level attribute of the test account.

[0082] In the embodiments of this specification, the target configuration information is associated with the test account, and the interface information when the test account interacts with the interface of the business server can also be determined based on the interface information of the interface of the business server associated with the test scenario. For example, the interface information of the interface of the business server associated with the test scenario can be directly used as the interface information when the test account interacts with the interface of the business server. Alternatively, at least part of the information in the interface information of the interface of the business server is modified, such as modifying the specific parameter value of the input parameter information, and using the modified interface information as the interface information when the test account interacts with the interface of the business server, etc.

[0083] Optionally, the test configuration information may be information used to test the product to be tested, and may include account information of the test account, such as account number, password, role attributes, permission level attributes, etc.

[0084] Optionally, the test configuration information may also include interface information when the test account interacts with the interface of the business server.

[0085] Step 212: Send the test configuration information to the service server; the service server can feed back the test service data corresponding to the test account according to the test configuration information when the test account accesses the service server.

[0086] The business server in the embodiments of this specification may be a server in normal use, and may represent a server that can provide business services to other products that have been launched, such as terminal application APPs, web pages, etc. that have been launched to provide services.

[0087] Specifically, sending the test configuration information to the service server may be sending the test configuration information to the service server associated with the test scenario.

[0088] In the embodiment of this specification, sending the test configuration information to the service server may be sending the test configuration information to one service server, or may be sending the test configuration information to multiple service servers.

[0089] Specifically, the test configuration information may be sent to the service server through the test platform.

[0090] In the embodiment of the present specification, the test configuration information may also include test service data. The test service data may be set according to the test requirements, and may include service data expected to be fed back by the service server during the process of testing the product to be tested using the test account.

[0091] Specifically, the test business data may be set by a user who has product testing requirements, such as a tester, according to the testing requirements.

[0092] In actual applications, the business server is a server that processes real business. The test account is an account used for product testing, and the attribute information of the test account is virtual or the business server does not actually have relevant information about the test account. When using a test account to access the business server, the business server cannot obtain the real attribute information corresponding to the test account, such as the information of the identity document number corresponding to the test account, and cannot process the business corresponding to the test account, for example, it is impossible to execute the process of querying the user's insurance information based on the identity document number for the test account. The embodiment of this specification can send test configuration information containing test business data to the business server, such as providing the insurance information of the hypothetical user to the business server, and then in the process of using the test account to test the interaction between the product to be tested and the business server, the business server simulates the real business processing process according to the test business data and feeds back the business processing results to the test platform, or feeds back the test business data to the product to be tested or the test platform or server where the product to be tested is located, so as to test the function of the product to be tested.

[0093] For example, a developer has developed an e-commerce platform that can provide users with some rights and interests based on their credit status. For example, users with high credit can enjoy interest-free discounts when using installment payments. In the process of users using the e-commerce platform, the e-commerce platform needs to access a business server that stores or can calculate user credit data. Assuming that the function of providing rights and interests of the e-commerce platform needs to be tested, the test requirement requires the e-commerce platform to interact with the business server that can provide user credit data. In order to enable the business server to feedback the credit information of the user represented by the test account, in the embodiment of this specification, before using the test account for testing, the test platform can send the attribute information of the test account to the business server, such as sending at least one of the role attribute and the authority level attribute to the business server, and the test platform can also send test business data, such as the assumed user credit value, to the business server. When testing the e-commerce platform, the test account can be used to log in to the e-commerce platform. The e-commerce platform can request the credit information of the user corresponding to the test account from the business server based on the test account, such as the credit score. The business server can feedback the test business data sent by the test platform before, such as the assumed credit score corresponding to the test account. If the e-commerce platform obtains the credit information fed back by the business server, it means that the e-commerce platform can interact with the business server, and the e-commerce platform can continue to execute related business processes based on the obtained credit information. This can ensure the accuracy of the test of the e-commerce platform, and the test process will not be unable to be smoothly executed due to the need to access the business server.

[0094] In actual applications, if the product to be tested needs to interact with multiple business servers in the process of completing its own business processing flow, through the method in the embodiment of this specification, when using a test account to test the product to be tested, the test will not be interrupted due to too many access links, and the test efficiency can also be improved.

[0095] In the embodiments of the present specification, a test account containing test configuration information can be automatically generated through the test platform and the test configuration information can be automatically sent to the business server. Compared with manually generating a test account containing test configuration information and manually sending the test configuration information, the test account generation efficiency is higher and the efficiency of using the test account for product testing is higher.

[0096] In the embodiments of the present specification, the test platform can provide the user with several optional configuration information associated with the test scenario based on the test scenario determined by the user, and then the user can determine the target configuration information required for the test account. The test platform can also associate the test account with the target configuration information to generate test configuration information, so that the user does not need to have too much test account generation technology. For example, the user may not have the ability to determine the configuration information associated with the test scenario, or the ability to associate the configuration information with the test account, and the user does not need to write too much code, and the generation of the test account is more convenient.

[0097] based on Figure 2 The method, the examples of this specification also provide some specific implementation plans of the method, which are described below.

[0098] In actual applications, the test platform can obtain the test scenarios determined by the user in a variety of ways.

[0099] For example, the test platform may display a scenario list, thereby obtaining a test scenario selected by a user from the scenario list. Optionally, the method may further include:

[0100] Displays a scenario list containing several test scenarios.

[0101] The test platform obtains the test scenario determined by the user, which may specifically include:

[0102] The test platform obtains the test scenario selected by the user from the scenario list.

[0103] In the embodiments of this specification, the scenario list is a list of test scenarios. Specifically, the scenario list may include one or more test scenarios. Each test scenario may be pre-set by the developer or service provider of the test platform, or may be a historical test scenario recorded by the test platform.

[0104] Optionally, a scenario drop-down list control may be displayed in the test platform. The user may click on the scenario drop-down list control, and the test platform may display a scenario list containing several test scenarios. In an embodiment of the present specification, the display of the scenario list containing several test scenarios may specifically include: based on the operation of the user clicking on the drop-down list control, displaying the scenario list containing several test scenarios.

[0105] Optionally, a slider control corresponding to the scene list may be displayed in the test platform. The user may drag the slider control so that the test platform may display the test scenes in the scene list. For example, the test platform may display the test scenes in the scene list one by one as the user drags the slider control. Optionally, the display of the scene list containing several test scenes may specifically include: based on the user's operation of dragging the slider control, displaying the scene list containing several test scenes.

[0106] Optionally, the scene list in the embodiment of this specification can be displayed on the homepage of the test platform. For example, after the user opens the test platform, the scene list can be displayed on the homepage of the test platform, so that it is convenient for the user to determine the test scene and improve the efficiency of the test platform in acquiring the test scene determined by the user. Optionally, the display of the scene list containing several test scenes can specifically include: the homepage of the test platform displays a scene list containing several test scenes.

[0107] As a specific implementation, the test platform can also display a test scenario search area, and the user can also enter the name or number of the required test scenario and other information in the test scenario search area of ​​the test platform, so that the test platform can obtain the test scenario determined by the user.

[0108] As a specific implementation, a scenario creation control may also be displayed in the test platform. The user may click on the scenario creation control to create a required test scenario, so that the test platform may obtain the test scenario determined by the user.

[0109] In actual applications, the product to be tested may require one or more business servers to provide business data in order to realize the product function. For example, a product that can provide services to users based on the user's credit value, in order to obtain a more accurate credit status of the user, the product needs to obtain the user's credit information from a business server that can provide credit information. In order to enable the business server to correctly provide business services to the test account and ensure that the test platform can smoothly test the product to be tested, the embodiment of this specification can extract relevant parameter information from the actual business processed by the business server, and then ensure that the configuration information of the test account meets the business requirements of the business server, and ensure that the product to be tested interacts with the business server to complete the test. The embodiment of this specification can generate optional configuration information by parsing the interface information of the business server to ensure that the product to be tested can interact with the business server and test each node involved in the product to be tested. Optionally, before determining a number of optional configuration information associated with the test scenario, it may also include:

[0110] Obtain log information generated during the process of the business server processing actual business.

[0111] The log information is parsed and processed to determine the business parameter information corresponding to the business server; the business parameter information includes at least one of input parameter information, output parameter information, interface name information, and method name information.

[0112] Based on the business parameter information, the plurality of optional configuration information is generated; the plurality of optional configuration information includes parameter attribute information in the business parameter information.

[0113] In the embodiments of this specification, the log information generated in the process of the business server processing the actual business may be the log information generated in the process of the business server processing the actual business of other products. For example, a product that has been launched, such as a financial product APP, needs to obtain user credit data from the business server that provides user credit data to recommend financial products to users. Assuming that it is necessary to test a function that the product to be tested obtains user credit data from the business server that provides user credit data to achieve, then the log information of the product in the process of the business server that provides user credit data processing the actual business of the financial product APP can be obtained.

[0114] The actual business of other products processed by the business server may be related to the test requirements for testing the product to be tested. For example, if the test requirement is to test a function implemented by the product to be tested by obtaining user credit data from the business server, the actual business of other products processed by the business server may be the business of the business server providing user credit data to other products.

[0115] Log information refers to a collection of information automatically or manually recorded by the system during the operation of a computer system or application. The information in the information collection records in detail the behavior information, state change information, error data information, etc. of the system or application.

[0116] In practical applications, log information is usually information in a preset format to facilitate processing of the log information. The preset format may be the arrangement position of each information in the log information. The embodiments of this specification may parse the log information through the preset format.

[0117] In the embodiment of this specification, the business parameter information corresponding to the business server can be determined by parsing the log information. The business parameter information corresponding to the business server can refer to the interface information of the interface of the business server, such as at least one of input parameter information, output parameter information, interface name information, and method name information.

[0118] In the embodiments of this specification, the business parameter information may include parameter attribute information and parameter values ​​corresponding to the parameter attribute information. For example, the parameter attribute information of the input parameter information may include a user ID, and the parameter value of the input parameter information may include a character or string representing the user ID. The parameter attribute information of the output parameter information may include information representing the attribute of the data processing state, and the corresponding parameter value of the output parameter information may include an attribute value representing the attribute of the data processing state, such as a character or string representing successful data processing, or a character or string representing failed data processing. The parameter attribute information of the output parameter information may also include information representing the attribute of the data processing result obtained by processing based on the input parameter information, and the corresponding parameter value of the output parameter information may include an attribute value representing the attribute of the data processing result, such as a character or string representing the data processing result. The parameter attribute information of the interface name information may include the interface IDs of the various interfaces of the business server, and the parameter value of the interface name information may include characters or strings representing the interface IDs of the various interfaces. The parameter attribute information of the method name information may include the method IDs of the various methods of the interface processing information, and the parameter value of the method name information may include characters or strings representing the method IDs of the various methods.

[0119] In the embodiments of this specification, the test platform can generate several optional configuration information based on the business parameter information. For example, part of the information in the business parameter information can be used as optional configuration information, such as the name information of some methods in the input parameter information, output parameter information, interface name information, and method name information as optional configuration information. Alternatively, all the information of the business parameter information can be used as optional configuration information, such as the input parameter information, output parameter information, interface name information, and method name information as optional configuration information.

[0120] Optionally, part of the information may be selected from the business parameter information through parameter attribute information or parameter values ​​in the business parameter information as optional configuration information.

[0121] For example, parameter attribute information or parameter values ​​in the business parameter information can be used to select part of the information from the business parameter information according to the test requirements. For example, if the test requirement is to test the interaction between a certain interface of the product and the business server or the interaction with an interface corresponding to a certain interface ID, the interface name information can be selected from the business parameter information as optional configuration information.

[0122] In actual applications, the optional configuration information may include configuration information of editable parameter values. The user may select the required configuration information from a number of optional configuration information, and may also edit specific parameter values ​​or attribute values. Optionally, the generating of the plurality of optional configuration information based on the business configuration information may specifically include:

[0123] The parameter value corresponding to the parameter attribute information in the business parameter information is determined to be in an editable state.

[0124] The plurality of optional configuration information of the editable parameter values ​​is obtained.

[0125] As a specific implementation, the test platform may determine the parameter value corresponding to the parameter attribute information in the business parameter information determined from the log information to be in an editable state.

[0126] For example, the test platform can delete the parameter value corresponding to the parameter attribute information from the business parameter information, and the test platform can display the parameter attribute information and the parameter value area to be edited in the configuration page, wherein the configuration page is used to configure the optional configuration information, and the parameter value area to be edited is used to edit the parameter value corresponding to the parameter attribute information. The user can edit the parameter value corresponding to the parameter attribute information in the parameter value area to be edited on the configuration page.

[0127] As a specific implementation, the test platform can display parameter attribute information and parameter values ​​corresponding to the parameter attribute information in the configuration page. The parameter value displayed in the configuration page can be a parameter value in a highlighted state to remind the user that the parameter value is an editable parameter value. The user can edit the parameter value to a desired parameter value, or the user can choose not to edit the parameter value and use the default parameter value of the parameter attribute information.

[0128] In the embodiments of this specification, the test platform can display several optional configuration information determined, and the user can select initial configuration information from the several optional configuration information and set the parameter value of the selected configuration information to obtain the target configuration information. Optionally, the step of obtaining the target configuration information determined by the user based on the several optional configuration information may specifically include:

[0129] Initial configuration information selected by the user from among several optional configuration information is obtained.

[0130] The initial configuration information is displayed; the initial configuration information includes parameter attribute information of at least one editable parameter value.

[0131] Acquire the parameter values ​​set by the user for the initial configuration information to obtain the target configuration information.

[0132] In actual applications, the user can click or drag required optional configuration information from several optional configuration information to select initial configuration information.

[0133] Optionally, the user may also delete unnecessary optional configuration information from the plurality of optional configuration information, and use the retained optional configuration information as initial configuration information, etc.

[0134] Specifically, the acquired initial configuration information may be one piece of configuration information or multiple pieces of configuration information.

[0135] In the embodiments of this specification, the test platform can also display initial configuration information, such as parameter attribute information of the initial configuration information, and can also display corresponding parameter values.

[0136] In the embodiment of the present specification, the initial configuration information includes parameter attribute information of one or more editable parameter values. The user can set the parameter values ​​of the parameter attribute information of the one or more editable parameter values ​​to obtain the target configuration information.

[0137] In actual applications, the initial configuration information contains parameter attribute information with at least one editable parameter value, which can facilitate users to edit parameter values ​​to meet test requirements. For example, the parameter attribute information of the user ID of the test account. Since the user ID of the test account is virtual, it is necessary to edit the attribute value of the user ID in the initial configuration information to the character or string representing the user ID of the test account to implement product testing. The parameter value of the parameter attribute information of the user ID can be editable. Alternatively, if you want to test whether the product to be tested can display a page or information indicating payment failure when the user payment fails, the business server needs to feedback the parameter value indicating payment failure to the product to be tested. For this test requirement, the tester can edit the parameter value of the attribute representing the data processing result in the configuration information to the character or string representing the data processing failure. Here, the parameter value of the attribute of the data processing result is editable.

[0138] As a specific implementation, the initial configuration information may also include parameter attribute information of at least one non-editable parameter value. In the embodiment of this specification, the initial configuration information of the parameter attribute information of the non-editable parameter value may be used as the target configuration information. Optionally, after filling the account attribute value into the initial configuration information to obtain the target configuration information, the method may further include:

[0139] The initial configuration information of the parameter attribute information of the non-editable parameter value is determined as the target configuration information.

[0140] For example, if the product to be tested can only interact with the business server through a certain interface of the business server, then the parameter value of the interface ID attribute can be non-editable. For another example, if the business server can only interact with the product to be tested through a certain method of interface processing information, then the parameter value of the method ID attribute can be non-editable. The initial configuration information contains parameter attribute information with at least one non-editable parameter value, which can help users understand the editing status of each parameter attribute information and facilitate users to test the product.

[0141] As a specific implementation, the optional configuration information includes configuration information of parameter attribute information of editable parameter values ​​and configuration information of parameter attribute information of non-editable parameter values. The initial configuration information may only include parameter attribute information of editable parameter values. The user may edit the parameter attribute information of the editable parameter values, and the test platform may generate target configuration information based on the parameter attribute information edited by the user and the configuration information of the non-editable parameter values.

[0142] As a specific implementation, the optional configuration information may include attribute information that the test account needs to have during the interaction with the business server. In the embodiment of this specification, the user can pre-set the attributes of the test account through the test platform, and then the test platform automatically generates the target configuration information based on the attributes of the test account set by the user. Optionally, the acquisition of the target configuration information determined by the user based on the plurality of optional configuration information may specifically include:

[0143] The test platform displays a page for configuring test account attributes; the test account attributes include at least one of role attributes and permission level attributes.

[0144] Get the account attribute value provided by the user on the page.

[0145] Initial configuration information selected by the user from a plurality of optional configuration information is obtained; the initial configuration information includes parameter attribute information of at least one editable parameter value.

[0146] Fill the account attribute value into the initial configuration information to obtain the target configuration information.

[0147] In the embodiment of the present specification, the test platform may display a page for configuring the properties of the test account. For example, the test platform may display a page for configuring the properties of the test account before or after the test platform obtains the test scenario determined by the user.

[0148] In actual applications, the page for configuring the attributes of the test account may include an area for the user to provide an account attribute value. The account attribute value in the embodiments of this specification may refer to at least one of an attribute value corresponding to a role attribute and an attribute value corresponding to an authority level attribute.

[0149] Specifically, the role attribute may refer to the identity or responsibility of the test account in the test scenario. The attribute value corresponding to the role attribute may be a character or string representing a normal user, a character or string representing a restricted user, a character or string representing an administrator, a character or string representing a visitor, etc. The permission level attribute may refer to the operation authority or access authority of the test account in the test scenario. The attribute value corresponding to the permission level attribute may be a character or string representing read-only authority, a character or string representing edit authority, a character or string representing management authority, a character or string representing delete authority, etc.

[0150] Optionally, the user can provide account attribute values ​​in the area for users to provide account attribute values. Specifically, the user can fill in the account attribute values ​​in this area, such as filling in one or more account attribute values. For example, the user can fill in the attribute value corresponding to the role attribute of the test account, such as the character or string representing an ordinary user, the character or string representing the date of birth, the character or string representing the occupation, etc. The user can also fill in the attribute value corresponding to the permission level attribute of the test account, such as the character or string representing the read-only permission, etc.

[0151] Optionally, a plurality of candidate account attribute values ​​may be displayed in the area for the user to provide the account attribute value, and the user may select one or more candidate account attribute values ​​from the plurality of candidate account attribute values ​​as the account attribute value provided by the user, etc. For example, the candidate account attribute values ​​may include attribute values ​​corresponding to the role attribute of the test account, such as characters or strings representing ordinary users, characters or strings representing restricted users, characters or strings representing administrators, characters or strings representing visitors, characters or strings representing date of birth, characters or strings representing educational background, characters or strings representing occupations, characters or strings representing the number of resources, etc. The candidate account attribute values ​​may also include attribute values ​​corresponding to the permission level attribute of the test account, such as characters or strings representing read-only permission, characters or strings representing editing permission, characters or strings representing management permission, characters or strings representing deletion permission, etc. For example, the user may select characters or strings representing administrators, characters or strings representing educational background, characters or strings representing occupations, characters or strings representing the number of resources, and characters or strings representing management permission from the candidate account attribute values ​​as the account attribute value provided by the user.

[0152] Furthermore, the test platform may also display several optional configuration information. The user may select initial configuration information from the several optional configuration information displayed by the test platform.

[0153] In the embodiment of the present specification, the initial configuration information includes parameter attribute information of editable parameter values, and the parameter values ​​of the parameter attribute information in the initial configuration information are in an editable state.

[0154] In the embodiment of this specification, the test platform can automatically fill the account attribute value into the initial configuration information to obtain the target configuration information including the specific attribute value, wherein the account attribute value provided by the user can also represent the specific parameter value of the parameter.

[0155] For example, a user fills in the date of birth, education, address, and occupation on the page for configuring the test account attributes. The initial configuration information selected by the user includes configuration information for the date of birth, education, address, and occupation. The test platform can automatically fill the date of birth filled in by the user into the configuration information for the date of birth, fill the education filled in by the user into the configuration information for the education, fill the address filled in by the user into the configuration information for the address, and fill the occupation filled in by the user into the configuration information for the occupation.

[0156] Optionally, the execution order of the two steps of obtaining the account attribute value provided by the user in the page and obtaining the initial configuration information selected by the user from the plurality of optional configuration information can be arbitrary. For example, the account attribute value provided by the user in the page can be obtained first, and then the initial configuration information selected by the user from the plurality of optional configuration information can be obtained, or the initial configuration information selected by the user from the plurality of optional configuration information can be obtained first, and then the account attribute value provided by the user in the page can be obtained, etc.

[0157] In the embodiment of the present specification, the target configuration information includes the account information of the test account, the attribute value information of the test account, and the test service data that the test user expects the service server to feedback for the test account.

[0158] Specifically, the account information of the test account may include at least one of the account number, password, role attribute, and permission level attribute. The attribute value information of the test account may include characters or strings representing the account number, characters or strings representing the password, characters or strings representing the role attribute, and characters or strings representing the permission level attribute. For example, the account information of the test account is the account number, password, role attribute, and permission level, the attribute value information of the account number is 123456, the attribute value information of the password is 654321, and the attribute value information of the role attribute is ordinary user, date of birth is February 2, 2002, education is undergraduate, and occupation is programmer. The test business data is the test business data that the test user expects the business server to feedback for the test account, specifically the test business data that the business server feedbacks according to the test account when the test account is used to log in to the product to be tested and access the business server. For example, the test account using the above account information and attribute value information tests the interaction between the e-commerce platform and the business server storing the user credit data, and the test user expects the business server to feedback the user credit value. The e-commerce platform can access the business server storing user credit data through the test account with the above account information and attribute value information. The business server storing user credit data will feedback test business data, such as user credit value, based on the account information and attribute value information of the test account.

[0159] In actual applications, some business servers can perform business processing based on a set whitelist. For example, for an account in the whitelist, the business server can skip some processing steps to perform business processing on the account; for another example, the business server can manage the access rights of the account based on the whitelist, etc. In order to conduct a more comprehensive test, if the business server associated with the test scenario needs to use a whitelist, the test platform in the embodiment of this specification can also add the test account to the whitelist to ensure the comprehensiveness of the test. Optionally, the method may also include:

[0160] The test account is added to the whitelist to obtain an updated whitelist.

[0161] The updated whitelist is sent to the service server.

[0162] In the embodiments of this specification, a whitelist needs to be used in a test scenario, which means that a service server accessed in the test scenario has a whitelist.

[0163] Among them, a whitelist is a security mechanism used to allow specific entities such as IP addresses, accounts, devices or applications to access system resources or perform operations, while denying other unauthorized entities from accessing system resources or performing operations.

[0164] The whitelist can determine which test accounts can access the business server, thereby limiting unauthorized access to the business server, such as preventing data leakage or malicious data tampering, to ensure the security of the test. In addition, by limiting unauthorized access to the business server through the whitelist, the interference caused by other accounts accessing the business server can be reduced, which helps to ensure the accuracy of the test.

[0165] In the embodiment of this specification, the log information generated by the business server in the process of processing the actual business can be used to determine whether the business server has a whitelist. Optionally, before adding the test account to the whitelist, the method can also include:

[0166] According to the actual business log of the business server, a whitelist corresponding to the business server is determined.

[0167] Adding the test account to the whitelist may specifically include:

[0168] Add the test account to the whitelist corresponding to the business server.

[0169] Optionally, the actual service log of the service server may refer to log information generated during the process of the service server processing actual services.

[0170] Specifically, the actual business log of the business server may be parsed to determine the whitelist, such as by parsing the log information using the preset format of the log as mentioned above.

[0171] In the embodiments of the present specification, adding the test account to the whitelist may be adding the test account to the whitelist corresponding to the business server. Specifically, at least one of the account number, role attribute, and permission level attribute of the test account may be added to the whitelist corresponding to the business server. The updated whitelist obtained may include at least one of the account number, role attribute information, and permission level attribute information of the test account.

[0172] In actual applications, the updated whitelist may be sent to the service server before or after the test configuration information is sent to the service server. Alternatively, the updated whitelist may be sent to the service server at the same time as the test configuration information is sent to the service server. Alternatively, the updated whitelist may be sent to the service server as part of the test configuration information.

[0173] In the embodiments of this specification, the test platform can also specifically generate test accounts in batches. For example, the configuration page provided by the test platform may include an area for filling in or selecting the number of accounts. The test user can fill in or select the number of test accounts required according to the test requirements, so that one or more test accounts can be generated in one operation. Optionally, the method may also include:

[0174] Get the number of test accounts that need to be generated entered by the user.

[0175] Generate the stated number of test accounts.

[0176] In actual applications, the test platform may display an area for the user to fill in the number of test accounts. The user may fill in the number of test accounts to be generated in this area. Alternatively, the test platform may display an area for the user to select the number of accounts, such as the user may select the number of test accounts in this area by using a drop-down control or other operations.

[0177] Specifically, the user may first select a test scenario in the test platform, and then fill in or select the number of test accounts in the test platform. Alternatively, the user may first fill in or select the number of test accounts in the test platform, and then select a test scenario in the test platform. The test platform may then generate the number of test accounts for testing based on the test scenario determined by the user.

[0178] Optionally, in order to distinguish different test accounts, one test account may correspond to one test account ID, and different test accounts may correspond to different test account IDs. Specifically, the test account ID may be a user ID of the test account.

[0179] In practical applications, in order to improve test efficiency and ensure test results, in the embodiments of this specification, the test configuration information can be sent to the business server through the joint debugging environment. Optionally, sending the test configuration information to the business server may specifically include:

[0180] The test configuration information is sent to the business server according to the joint debugging environment label corresponding to the business server; the joint debugging environment label is determined based on the business server that the product to be tested needs to access; the test account is used to test the product to be tested.

[0181] The joint debugging environment refers to a specific environment built during product development and product testing to ensure that various modules or systems can work together. Based on the joint debugging environment, product developers or product testers can test the interaction between various modules or systems by simulating actual usage scenarios.

[0182] In the embodiments of this specification, the business server may be in the joint debugging environment in which it is located. The joint debugging environment in which the business server is located may be determined by a joint debugging environment mark, that is, an identifier of the joint debugging environment. Optionally, according to the joint debugging environment mark corresponding to the business server, the test configuration information is sent to the business server, which may specifically include:

[0183] Determine the joint debugging environment where the business server is located according to the joint debugging environment label corresponding to the business server;

[0184] Based on the joint debugging environment where the business server is located, the test configuration information is sent to the business server.

[0185] In the embodiments of the present specification, the product to be tested may be at least one of software to be tested, a program to be tested, a website to be tested, or a web page to be tested.

[0186] Figure 3 FIG. 1 is a flow chart of a test platform obtaining optional configuration information provided by an embodiment of the present application. Figure 3 As shown, the method may include the following steps.

[0187] Step 302: Obtain log information.

[0188] In the embodiments of this specification, the test platform can obtain log information generated when the business server processes actual business.

[0189] Specifically, the log information of different business servers may be obtained, such as the log information of business server A, the log information of business server B, and the log information of business server C, and so on.

[0190] In the embodiments of this specification, the test platform may be a low-code development platform (Low-code Development Platform). The low-code development platform is a software development tool that provides visual tools and components, allowing users to design and build applications by dragging and dropping components, using model-driven logic and templates, without having to write a lot of traditional handwritten code.

[0191] The embodiments of this specification can use a low-code development platform to generate a test account, which can improve the convenience and efficiency of generating a test account.

[0192] Step 304: Parsing process.

[0193] In the embodiments of this specification, the test platform can parse the log information to obtain the interface information of the interface of the business server.

[0194] In actual applications, log information is usually log information in a preset format. For example, the first placeholder of the log information can be trace, where trace is the HTTP method of the interface connection. The second placeholder can be the data receiving time of the interface, the third placeholder can be the interface name information, the fourth placeholder can be the method name information, and so on. Specifically, the method name information can include query method name information, write method name information, and delete method name information, etc.

[0195] In the embodiment of the present specification, the interface information of the interface of the service server may include at least one of input parameter information, output parameter information, interface name information, and method name information.

[0196] In the embodiments of the present specification, the log information is parsed and processed to obtain interface information of different interfaces, such as interface information of interface A, interface information of interface B, and the like.

[0197] As a specific implementation, if the log information includes whitelist information, the log information can be parsed to obtain whitelist information, which can be whitelist information of the interface of the service server, such as whitelist A, whitelist B, etc.

[0198] As a specific implementation, the log information may also include the attributes of the account associated with the actual business processed by the business server. The account associated with the actual business processed by the business server may be the account that actually interacts with the business server. Optionally, the attributes of the account associated with the actual business processed by the business server may be obtained by parsing the log. The attributes of the account may include the role attributes of the account and the authority level attributes of the account.

[0199] In the embodiment of this specification, a Mock interface can be used to represent the interface of the service server. In other words, in the embodiment of this specification, the interface of the service server can be a Mock interface.

[0200] Mock interface is a technology that simulates the behavior of real APIs, and is designed to support product development and product testing. When developing or testing a product, you often need to rely on external systems or services to obtain data or perform specific operations, but in some cases, these systems or services may not be available. Mock interface can simulate the behavior of external systems or services, and thus product development or testing can be performed without relying on real external systems or services.

[0201] In the embodiment of this specification, the interface information of the interface of the service server obtained by parsing the log information may be the interface information of the Mock interface, which may specifically be the trace, data receiving time, interface name information, method name information, etc. of the Mock interface.

[0202] In practical applications, a parsing rule for parsing log information can be set based on a preset format of log information. The parsing rule can be a rule for parsing log information based on a preset format of log information. The parsing rule can then be used to parse the log information, which can improve the efficiency of log information parsing compared to manual parsing.

[0203] Step 306: Visualization scenario configuration.

[0204] In the embodiments of this specification, the test platform is equipped with a visual scenario configuration tool. Specifically, based on the visual scenario configuration tool, the test platform can provide a visual graphical user interface.

[0205] The visualized graphical user interface can display the parsed information of the log information, such as the interface information of the business server interface, whitelist information, etc., so that the user can configure the parsed information of the log information.

[0206] Specifically, the user can configure the parsed information of the log information in the visual graphical user interface, so that the test platform can obtain optional configuration information. For example, the user can configure whitelist A, configure whitelist B, configure the interface information of interface A, configure the interface information of interface B, and so on.

[0207] Furthermore, the user may also configure the attributes of the account associated with the actual business processed by the business server to obtain the attributes of the test account, such as the role attributes of the test account and the permission level attributes of the test account.

[0208] In actual applications, users can configure the parsed log information according to their test requirements, such as test scenarios.

[0209] Step 308: Save the optional configuration information to the database.

[0210] Optionally, the test platform may save the optional configuration information to a database, so that the user can determine the target configuration information from the optional configuration information and then generate the test configuration information to obtain a test account.

[0211] In the embodiment of this specification, the test platform can obtain log information in advance and parse the log information to obtain optional configuration information, which can facilitate subsequent users to generate test accounts based on the optional configuration information when they need to generate test accounts, thereby improving the efficiency of generating test accounts.

[0212] Figure 4 FIG. 1 is a flow chart of a user generating a test account based on a test platform according to an embodiment of the present application. Figure 4 As shown, the specific steps may include the following steps.

[0213] Step 402: Determine a test scenario.

[0214] In the embodiments of this specification, a variety of test scenarios may be pre-configured in the test platform, and the user may select a test scenario from the multiple test scenarios according to the test requirements, or the user may create a new test scenario in the test platform, so that the test platform can determine the test scenario provided by the user.

[0215] In the embodiments of this specification, the product to be tested needs to interact with other business servers to obtain service support from the business servers.

[0216] Specifically, the test scenario may be at least one of a product function test scenario, a product performance test scenario, a product safety test scenario, and a product experience test scenario.

[0217] In actual applications, after the test platform determines the test scenario, it can also determine the test account used for testing based on the test scenario.

[0218] Step 404: Determine optional configuration information.

[0219] In actual applications, the test platform can determine the optional configuration information associated with the test scenario.

[0220] Optionally, the optional configuration information may include configuration information indicating attributes of the test account. Specifically, the attributes of the test account may include role attributes, permission level attributes, etc. of the test account.

[0221] Optionally, the optional configuration information may further include at least one of interface information of an interface of the business server and attributes of an account associated with actual business processed by the business server.

[0222] In the embodiments of this specification, the test platform may determine one optional configuration information or multiple optional configuration information.

[0223] Step 406: Obtain target configuration information.

[0224] In the embodiment of this specification, the visual graphical user interface in the test platform can display several optional configuration information. The user can determine the target configuration information from the several optional configuration information, for example, the user can select some optional configuration information, and then the test platform obtains the target configuration information determined by the user.

[0225] The user may directly use the optional configuration information as the target configuration information, for example, the interface information of the interface of the business server in the log information and the attributes of the account associated with the actual business processed by the business server as the target configuration information.

[0226] Alternatively, the user may modify at least one of the interface information of the interface of the service server and the attributes of the account associated with the service server processing the actual service to obtain the target configuration information and the like.

[0227] In the embodiment of the present specification, the test platform may also associate the target configuration information with the test account to generate test configuration information associated with the test account.

[0228] Specifically, the target configuration information acquired by the test platform may include the interface information determined in step 408 and the updated whitelist determined in step 410 .

[0229] Step 408: Determine the interface information of the set interface.

[0230] In actual applications, users can set the interface information of the interface in the test platform, such as setting the attribute value of at least one of the input parameter information, output parameter information, interface name information, and method name information in the interface information, and then the test platform can determine the interface information set by the user.

[0231] Step 410: Determine the set whitelist.

[0232] In actual applications, users can also set up whitelists in the test platform, such as adding a test account to the whitelist, and then the test platform can obtain the whitelist set by the user.

[0233] Step 412: Data preservation.

[0234] In the embodiments of the present specification, the test platform may save the target configuration information determined by the user, such as saving it in a database, to facilitate subsequent use by the user.

[0235] Step 414: Send the test configuration information to the configuration delivery module.

[0236] Among them, the configuration delivery module can be a module in the test platform.

[0237] The test platform can send the test configuration information to the configuration delivery module, so that the configuration delivery module can send the test configuration information to the business server.

[0238] In actual applications, the configuration delivery module can send the test configuration information to one or more business servers according to the joint debugging environment mark corresponding to the business server.

[0239] Specifically, the configuration delivery module can determine the joint debugging environment where the business server A is located based on the joint debugging environment label corresponding to the business server A. Then, the test configuration information can be sent to the business server A based on the joint debugging environment where the business server A is located.

[0240] If the test scenario also requires business server B, the configuration delivery module can also send the test configuration information to business server B. If the test scenario also requires business server C, the configuration delivery module can also send the test configuration information to business server C, and so on.

[0241] The specific business servers to which the test platform sends the test configuration information can be determined according to the actual needs of the product to be tested, and no specific limitation is made here.

[0242] In the embodiments of this specification, the test platform can be a low-code development platform (Low-code Development Platform), which can provide visual tools and components, so that users can design and build applications by dragging and dropping components, using model-driven logic and templates. The embodiments of this specification can reduce the complexity of test account generation and improve the convenience of test account generation through visual tools and components; on the other hand, the embodiments of this specification do not require users to have code writing capabilities to generate test accounts to test the products to be tested, further improving the convenience of test account generation.

[0243] In the embodiments of this specification, the test platform can display different test scenarios for users to choose from, and can also display several optional configuration information associated with the test scenarios for users to choose from, thereby meeting different test requirements and providing high test flexibility.

[0244] In the embodiments of this specification, the test platform obtains the log information generated in the process of the business server processing the actual business. In this way, the log information generated in the process of the business server processing the actual business can be used to generate optional configuration information, and then the test configuration information can be generated based on the target configuration information determined in the optional configuration information. It can ensure that the generated test configuration information is highly consistent with the process of the business server processing the actual business, thereby improving the accuracy of the test.

[0245] In the embodiments of this specification, the test platform can also be continuously updated and iterated. Specifically, the test platform can obtain the log information of the business server processing the actual business at a preset frequency, and then parse the log information at a preset frequency, and perform updates and iterations based on the information parsed from the log. For example, if the log information contains new information, the test platform can use the new information as optional configuration information for the user to select, etc.

[0246] In the embodiments of this specification, the test platform can integrate functions such as log information analysis, configuration of interface information of the Mock interface, whitelist setting, test account generation, and test configuration information distribution, providing a more convenient, stable, and reliable testing environment, which is of great significance to improving the quality and efficiency of product development or product testing.

[0247] It should be understood that the order of some steps in the methods described in one or more embodiments of this specification can be interchanged according to actual needs, or some steps can be omitted or deleted.

[0248] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method.

[0249] Figure 5 The embodiments of this specification provide corresponding to Figure 2 A schematic diagram of the structure of a device for generating a test account. Figure 5 As shown, the apparatus may include:

[0250] The test scenario acquisition module 502 is used for the test platform to acquire the test scenario determined by the user.

[0251] The test account determination module 504 is used to determine a test account for testing based on the test scenario.

[0252] The optional configuration information determination module 506 is used to determine several optional configuration information associated with the test scenario.

[0253] The target configuration information acquisition module 508 is used to acquire the target configuration information determined by the user based on the plurality of optional configuration information.

[0254] The test configuration information generating module 510 is used to associate the target configuration information with the test account, and generate the test configuration information associated with the test account.

[0255] The sending module 512 is used to send the test configuration information to the service server; the service server can feed back the test service data corresponding to the test account according to the test configuration information when the test account accesses the service server.

[0256] Optionally, the device may further include:

[0257] A scenario list display module is used to display a scenario list containing several test scenarios;

[0258] The test scenario acquisition module 502 may be specifically used for:

[0259] The test platform obtains the test scenario selected by the user from the scenario list.

[0260] Optionally, the device may further include:

[0261] The log information acquisition module is used to acquire the log information generated in the process of the business server processing actual business.

[0262] The parsing and processing module is used to parse and process the log information to determine the business parameter information corresponding to the business server; the business parameter information includes at least one of input parameter information, output parameter information, interface name information, and method name information.

[0263] The optional configuration information generating module is used to generate the plurality of optional configuration information based on the business parameter information; the plurality of optional configuration information includes parameter attribute information in the business parameter information.

[0264] Optionally, the optional configuration information generating module may be specifically used for:

[0265] The parameter value corresponding to the parameter attribute information in the business parameter information is determined to be in an editable state.

[0266] The plurality of optional configuration information of the editable parameter values ​​is obtained.

[0267] Optionally, the target configuration information acquisition module 508 may be specifically used to:

[0268] Initial configuration information selected by the user from among several optional configuration information is obtained.

[0269] The initial configuration information is displayed; the initial configuration information includes parameter attribute information of at least one editable parameter value.

[0270] Acquire the parameter values ​​set by the user for the initial configuration information to obtain the target configuration information.

[0271] Optionally, the target configuration information acquisition module 508 may be specifically used to:

[0272] The test platform displays a page for configuring test account attributes; the test account attributes include at least one of role attributes and permission level attributes.

[0273] Get the account attribute value provided by the user on the page.

[0274] Initial configuration information selected by the user from a plurality of optional configuration information is obtained; the initial configuration information includes parameter attribute information of at least one editable parameter value.

[0275] Fill the account attribute value into the initial configuration information to obtain the target configuration information.

[0276] Optionally, the target configuration information includes account information of the test account, attribute value information of the test account, and test service data that the test user expects the service server to feedback for the test account.

[0277] Optionally, if a whitelist is required in the test scenario, the device may further include:

[0278] A whitelist adding module, used to add the test account to the whitelist to obtain an updated whitelist;

[0279] The whitelist sending module is used to send the updated whitelist to the service server.

[0280] Optionally, the device may further include:

[0281] The whitelist determination module is used to determine the whitelist corresponding to the business server according to the actual business log of the business server.

[0282] The whitelist adding module can be specifically used for:

[0283] Add the test account to the whitelist corresponding to the business server.

[0284] Optionally, the device may further include:

[0285] The quantity acquisition module is used to obtain the number of test accounts that need to be generated input by the user;

[0286] The account generation module is used to generate the number of test accounts.

[0287] Optionally, the sending module 512 may be specifically configured to:

[0288] The test configuration information is sent to the business server according to the joint debugging environment label corresponding to the business server; the joint debugging environment label is determined based on the business server that the program to be tested needs to access; the test account is used to test the program to be tested.

[0289] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method.

[0290] Figure 6 The embodiments of this specification provide corresponding to Figure 2 A schematic diagram of the structure of a test account generation device. Figure 6 As shown, the device 600 may include:

[0291] at least one processor 610; and,

[0292] A memory 630 is communicatively connected to the at least one processor 610; wherein,

[0293] The memory 630 stores instructions 620 that can be executed by the at least one processor 610. The instructions 620 are executed by the at least one processor 610 so that the at least one processor 610 can implement the above-mentioned method for generating a test account.

[0294] Based on the same idea, the embodiment of this specification also provides a computer-readable storage medium corresponding to the above method, on which computer instructions are stored. When the computer instructions are executed by the processor, the above test account generation method is implemented.

[0295] Each embodiment in this specification is described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. Figure 6 As for the test account generation device shown, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0296] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0297] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0298] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0299] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0300] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0301] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0302] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0303] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0304] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0305] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0306] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0307] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0308] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0309] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0310] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A method for generating a test account, comprising: The test platform obtains the test scenario determined by the user; Based on the test scenario, determine a test account for testing; Determining a number of optional configuration information associated with the test scenario; Acquire target configuration information determined by the user based on the plurality of optional configuration information; Associating the target configuration information with the test account to generate test configuration information associated with the test account; Sending the test configuration information to a service server; The service server can feed back test service data corresponding to the test account according to the test configuration information when the test account accesses the service server.

2. The method of claim 1, further comprising: Display a scenario list containing several test scenarios; The test platform obtains the test scenario determined by the user, specifically including: The test platform obtains the test scenario selected by the user from the scenario list.

3. The method according to claim 1, before determining the plurality of optional configuration information associated with the test scenario, further comprising: Obtaining log information generated during the process of the business server processing actual business; Parsing the log information to determine the service parameter information corresponding to the service server; The business parameter information includes at least one of input parameter information, output parameter information, interface name information, and method name information; Based on the business parameter information, the plurality of optional configuration information is generated; the plurality of optional configuration information includes parameter attribute information in the business parameter information.

4. The method according to claim 3, wherein generating the plurality of optional configuration information based on the service configuration information specifically comprises: Determine the parameter value corresponding to the parameter attribute information in the business parameter information as an editable state; The plurality of optional configuration information of the editable parameter values ​​is obtained.

5. The method according to claim 1, wherein obtaining the target configuration information determined by the user based on the plurality of optional configuration information comprises: Acquire initial configuration information selected by the user from a plurality of optional configuration information; Displaying the initial configuration information; The initial configuration information includes parameter attribute information of at least one editable parameter value; Acquire the parameter values ​​set by the user for the initial configuration information to obtain the target configuration information.

6. The method according to claim 1, wherein obtaining the target configuration information determined by the user based on the plurality of optional configuration information comprises: The test platform displays a page for configuring test account attributes; the test account attributes include at least one of role attributes and permission level attributes; Obtain the account attribute value provided by the user on the page; Acquire initial configuration information selected by the user from a plurality of optional configuration information; The initial configuration information includes parameter attribute information of at least one editable parameter value; Fill the account attribute value into the initial configuration information to obtain the target configuration information.

7. The method according to claim 1, wherein the target configuration information includes account information of the test account, attribute value information of the test account, and test service data that the test user expects the service server to feedback for the test account.

8. The method according to claim 1, if a whitelist is required in the test scenario; the method further comprises: Add the test account to the whitelist to obtain an updated whitelist; The updated whitelist is sent to the service server.

9. The method according to claim 8, before adding the test account to the whitelist, further comprising: Determine a whitelist corresponding to the business server according to the actual business log of the business server; Adding the test account to the whitelist specifically includes: Add the test account to the whitelist corresponding to the business server.

10. The method of claim 1, further comprising: Get the number of test accounts that need to be generated entered by the user; Generate the stated number of test accounts.

11. The method according to claim 1, wherein sending the test configuration information to the service server comprises: Sending the test configuration information to the business server according to the joint debugging environment mark corresponding to the business server; The joint debugging environment identifier is determined based on the business server that the program to be tested needs to access; the test account is used to test the program to be tested.

12. A device for generating a test account, comprising: The test scenario acquisition module is used for the test platform to acquire the test scenario determined by the user; A test account determination module, used to determine a test account for testing based on the test scenario; An optional configuration information determination module, used to determine a number of optional configuration information associated with the test scenario; A target configuration information acquisition module, used to acquire the target configuration information determined by the user based on the plurality of optional configuration information; A test configuration information generating module, used to associate the target configuration information with the test account, and generate test configuration information associated with the test account; A sending module, used for sending the test configuration information to a service server; The service server can feed back test service data corresponding to the test account according to the test configuration information when the test account accesses the service server.

13. A device for generating a test account, comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can implement the method for generating a test account according to any one of claims 1 to 11.

14. A computer-readable medium having computer-readable instructions stored thereon, wherein the computer-readable instructions can be executed by a processor to implement the method for generating a test account according to any one of claims 1 to 11.

Images