CN113515438A

CN113515438A - Test account management method, device, equipment and storage medium

Info

Publication number: CN113515438A
Application number: CN202010279574.2A
Authority: CN
Inventors: 郑申申; 蒋剑琴; 黄飞
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-04-10
Filing date: 2020-04-10
Publication date: 2021-10-19

Abstract

The embodiment of the application provides a test account management method, a test account management device, test account management equipment and a storage medium; the method comprises the following steps: determining a target test account for completing the test requirement according to the acquired test requirement; searching candidate test accounts with inheritance relationship with the target test account in a tree structure from a test data platform adopting the tree structure to store at least one test account; determining a first step set required for creating the target test account according to the test requirement; acquiring a second step set included by the candidate test account; creating the target test account according to at least one of the first step set and the second step set; therefore, the target test account is created on the basis of the candidate test accounts in the test data platform, and the utilization rate of the test accounts in the test data platform is improved.

Description

Test account management method, device, equipment and storage medium

Technical Field

The present application relates to the field of software testing, and in particular, to a method, an apparatus, a device, and a storage medium for managing a test account.

Background

In the research and development test process, the requirements for the related test data structures are more and more frequent, so that the data structures in a plurality of test account numbers are in conflict with each other, and the test account numbers are continuously increased and even repeatedly constructed. The test account number using process easily causes a lot of dirty data, causes obstacles to subsequent use, is difficult to maintain, and has low utilization rate.

Disclosure of Invention

The embodiment of the application provides a test account management method, device, equipment and storage medium, which can improve the automatic test efficiency and the utilization rate of test accounts in a test data platform.

The technical scheme of the embodiment of the application is realized as follows:

in a first aspect, an embodiment of the present application provides a test account management method, including:

determining a target test account for completing the test requirement according to the acquired test requirement;

searching candidate test accounts with inheritance relationship with the target test account in a tree structure from a test data platform adopting the tree structure to store at least one test account;

determining a first step set required for creating the target test account according to the test requirement; wherein the first set of steps includes steps required to create the target test account;

acquiring a second step set included by the candidate test account; wherein the second set of steps includes steps required to create the candidate test account;

creating the target test account according to at least one of the first step set and the second step set

In a second aspect, an embodiment of the present application provides a test account management apparatus, including:

the first determination module is used for determining a target test account for completing the test requirement according to the acquired test requirement;

the first searching module is used for searching candidate test accounts which have inheritance relationship with the target test account in a tree structure from a test data platform which adopts the tree structure to store at least one test account;

the second determination module is used for determining a first step set required by creating the target test account according to the test requirement; wherein the first set of steps includes steps required to create the target test account;

the first acquisition module is used for acquiring a second step set included by the candidate test account; wherein the second set of steps includes steps required to create the candidate test account;

and the first creating module is used for creating the target test account according to at least one set of the first step set and the second step set.

In a third aspect, an embodiment of the present application provides a computer storage medium, which stores executable instructions for causing a processor to execute the computer storage medium, so as to implement the test account management method provided in the embodiment of the present application.

The embodiment of the application has the following beneficial effects: after the test requirement is obtained, obtaining a target test account number which completes the test requirement, and searching a candidate test account number which has an inheritance relationship with the target test account number from a test data platform which adopts a tree structure to store at least one test account number; therefore, after the test requirements are acquired, the candidate test account with the inheritance relationship is preferentially searched from the test data platform, and the automatic test efficiency can be greatly improved; then, on the basis of the candidate test account, the target test account is created by combining the step set required for realizing the test requirement; therefore, the target test account is created on the basis of the candidate test accounts in the test data platform for storing the test accounts by adopting the tree structure, and the utilization rate of the test accounts in the test data platform is improved.

Drawings

Fig. 1 is an alternative architecture diagram of a test account management system according to an embodiment of the present disclosure;

fig. 2A is a schematic diagram of another alternative architecture of a test account management system according to an embodiment of the present application;

fig. 2B is a schematic structural diagram of a test account management system according to an embodiment of the present application;

fig. 3 is a schematic flow chart illustrating an implementation of a test account management method according to an embodiment of the present application;

fig. 4A is a schematic flowchart of another implementation flow of the test account management method according to the embodiment of the present application;

fig. 4B is a schematic flowchart of another implementation flow of the test account management method according to the embodiment of the present application;

fig. 5 is a schematic page diagram of a test account management system according to an embodiment of the present application;

fig. 6 is a schematic view of another page of the test account management system provided in the embodiment of the present application;

fig. 7 is a schematic view of another page of the test account management system according to the embodiment of the present application;

fig. 8 is a schematic structural diagram of a component implementing a test account management method according to an embodiment of the present application;

FIG. 9 is a schematic diagram of a component structure for implementing tag inheritance according to an embodiment of the present application;

fig. 10 is a schematic view of an account application flow provided in the embodiment of the present application.

Detailed Description

In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be described in further detail with reference to the attached drawings, the described embodiments should not be considered as limiting the present application, and all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict.

In the following description, references to the terms "first \ second \ third" are only to distinguish similar objects and do not denote a particular order, but rather the terms "first \ second \ third" are used to interchange specific orders or sequences, where appropriate, so as to enable the embodiments of the application described herein to be practiced in other than the order shown or described herein.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the present application only and is not intended to be limiting of the application.

Before further detailed description of the embodiments of the present application, terms and expressions referred to in the embodiments of the present application will be described, and the terms and expressions referred to in the embodiments of the present application will be used for the following explanation.

1) The dynamic test method comprises the following steps: the method comprises the steps of checking the difference between an operation result and an expected result by operating a tested program, and analyzing the performance such as operation efficiency, correctness, robustness and the like. This method consists of three parts: and constructing output results of the test case, the executive program and the analysis program.

2) And (3) dynamic testing: the measured value changes along with the change of time or space, the input quantity of the instrument and the test result (data or signals) also change along with the change of time, and the measurement error has correlation under the dynamic condition of the measurement system. The dynamic test data contains a large amount of information about the measured physical quantity, the measuring instrument used, the interference added by the external environment and the like, and the dynamic test data is correctly analyzed and processed to obtain a lot of useful information reflecting the law of objective objects.

3) During the testing process, the tester (or developer) always needs to construct various kinds of test data to meet its own needs. The data factory has the function of providing a uniform interface, so that a tester or a developer can quickly and simply generate test data, and the test efficiency is improved. The term "fast and simple" means that it is possible for other testing and developing personnel (who are not the service line) to generate the required test data by simple input, and construct the data by calling the interface or directly writing the database without knowing the design of the interface or the database. The data factory is simply a framework whose business logic (modules) to construct the test data requires the development of testers for each line of business.

4) Common Gateway Interface (CGI) is a specification of an external program when a World Wide Web (World Wide Web) server operates, and a program written according to the CGI can extend the functions of the server. The CGI application can interact with the browser and can also communicate with an external data source such as a database server through a data API to obtain data from the database server.

5) Remote Procedure Call (RPC), the principle of system RPC Call is really simple, there are some operating systems similar to three-layer framework, the client program of the third party calls the standard or self-defined function inside the system through the interface, and the data returned by the function is obtained to be displayed or printed after being processed; a simple understanding is that one node requests a service provided by another node.

6) The design style and The development mode (RESTFUL) of The network application program are suitable for a scene that a mobile internet manufacturer serves as a service enabling interface, and various application services (Over The Top, OTT) are provided for a user through The internet by a third party, wherein The RESTFUL refers to The function of calling mobile network resources, and The action type is to add, change or delete The called resources.

7) An Application Programming Interface (API) is a predefined function or convention for linking different components of a software system. The goal is to provide applications and developers the ability to access a set of routines based on certain software or hardware without having to access native code or understand the details of the internal workings.

8) Blockchain (Blockchain): an encrypted, chained transactional memory structure formed of blocks (blocks).

9) Block chain Network (Blockchain Network): the new block is incorporated into the set of a series of nodes of the block chain in a consensus manner.

In the related art, the test data factory is an archive of existing test account numbers. In the research and development test process, the requirements on the construction of related test data are more and more frequent; as time passes, research and development or testing personnel have a certain number of test account numbers, and data structures are in conflict with each other, are continuously increased and even can be repeatedly constructed. The account number using process easily causes a lot of dirty data, causes obstacles to subsequent use and is difficult to maintain. Meanwhile, a test data factory cannot dynamically generate test accounts and perform batch attribute setting on the test accounts, and the problems of high data preparation threshold, long time consumption and the like cannot be solved.

In view of the foregoing technical problems, embodiments of the present application provide a method, an apparatus, a device, and a storage medium for managing test data, which support to serially connect attribute setting processes of multiple steps in a pipeline manner so as to quickly set attributes for a test account by quickly creating a required test account according to a requirement. Meanwhile, the capability of dynamically managing the test account is provided, and the capability comprises the steps of managing data attributes, acquiring and locking the test account, releasing the test account and dynamically expanding the test account.

An exemplary application of the device for testing account management according to the embodiment of the present application is described below, and the device according to the embodiment of the present application may be implemented as various types of user devices such as a notebook computer, a tablet computer, a desktop computer, a set-top box, a mobile device (e.g., a mobile phone, a portable music player, a personal digital assistant, a dedicated messaging device, and a portable game device), and may also be implemented as a server. In the following, an exemplary application will be explained when the device is implemented as a device or a server.

Referring to fig. 1, fig. 1 is an optional architecture diagram of a test account management system provided in an embodiment of the present application, and in order to implement supporting an exemplary application, first, after a test account request sent by a client 10 is received, a target test account 101 requested by the test account request is determined, and a target label 102 of the target test account 101 is obtained in combination with attribute information of the target test account 101, and a candidate label 103 having an inheritance relationship with the target label is searched from a test data platform 12; then, on the basis of the candidate test account 104 to which the candidate tag 103 belongs, the target test account 101 is created in combination with the set of steps required for realizing the test requirement; finally, encrypting the target test account 101 and feeding back the encrypted target test account to the user; therefore, the existing test account number of the target label in the test data platform is preferentially allocated, and the automatic test efficiency can be improved; and moreover, on the basis of the candidate test account, the target test account is created, so that the utilization rate of the test account in the test data platform is improved.

Referring to fig. 2A, fig. 2A is another alternative architecture schematic diagram of the test account management system provided in the embodiment of the present application, and includes a blockchain network 20 (exemplarily showing a server 200 as a native node), a monitoring system 30 (exemplarily showing a device 300 belonging to the monitoring system 30 and a graphical interface 301 thereof), which are described below.

The blockchain network 20 is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, etc. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block includes information of a batch of network transactions for verifying the validity (anti-counterfeiting) of the information and generating a next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer.

The type of blockchain network 20 is flexible and may be, for example, any of a public chain, a private chain, or a federation chain. Taking a public link as an example, electronic devices such as user equipment and servers of any service entity can access the blockchain network 20 without authorization; taking a federation chain as an example, an electronic device (e.g., a device/server) under the jurisdiction of a service entity after obtaining authorization may access the blockchain network 20, and at this time, become a special type of node in the blockchain network 20, i.e., a client node.

Note that the client node may provide only functionality to support the initiation of transactions by the business entity (e.g., for uplink storage of data or querying of data on the chain), and may be implemented by default or selectively (e.g., depending on the specific business requirements of the business entity) for the functions of the native nodes of the blockchain network 20, such as the ranking function, consensus service, ledger function, etc., described below. Therefore, the data and the service processing logic of the service subject can be migrated to the blockchain network 20 to the maximum extent, and the credibility and traceability of the data and service processing process are realized through the blockchain network 20.

Blockchain network 20 receives a transaction submitted by a client node (e.g., device 300 shown in fig. 2A as belonging to monitoring system 30) from a business entity (e.g., monitoring system 30 shown in fig. 2A), executes the transaction to update or query the ledger, and displays various intermediate or final results of executing the transaction on a user interface of the device (e.g., graphical interface 301 of device 300).

An exemplary application of the blockchain network is described below by taking an example of monitoring system access to the blockchain network to achieve creation of an uplink of a target test account.

The device 300 of the monitoring system 30 accesses the blockchain network 20 to become a client node of the blockchain network 20. The device 300 acquires a test account request, and then searches for a candidate tag having an inheritance relationship from a test data platform based on a target tag of a requested target test account; finally, on the basis of the candidate test account to which the candidate label belongs, the target test account is created by combining the steps required for realizing the test requirement; and, the target test account number is given to the server 200 in the blockchain network 20 or saved in the device 300; in the case where the upload logic has been deployed to the device 300 or the user has performed an operation, the device 300 generates a transaction corresponding to the update operation/query operation according to the to-be-processed item/synchronization time query request, specifies an intelligent contract to be called to implement the update operation/query operation and parameters transferred to the intelligent contract in the transaction, and the transaction also carries a digital signature signed by the monitoring system 30 (for example, a digest of the transaction is encrypted by using a private key in a digital certificate of the monitoring system 30), and broadcasts the transaction to the blockchain network 20. The digital certificate can be obtained by registering the monitoring system 30 with the certificate authority 31.

A native node in the blockchain network 20, for example, the server 200 verifies a digital signature carried by the transaction when receiving the transaction, and after the verification of the digital signature is successful, it is determined whether the monitoring system 30 has a transaction right according to the identity of the monitoring system 30 carried in the transaction, and any verification judgment of the digital signature and the right verification will result in a transaction failure. After successful verification, the native node signs its own digital signature (e.g., by encrypting a digest of the transaction using the native node's private key) and continues to broadcast in the blockchain network 20.

After the node with the sorting function in the blockchain network 20 receives the transaction successfully verified, the transaction is filled into a new block and broadcasted to the node providing the consensus service in the blockchain network 20.

The nodes in the blockchain network 20 that provide the consensus service perform a consensus process on the new block to reach agreement, the nodes that provide the ledger function append the new block to the end of the blockchain, and perform the transaction in the new block: and searching for a candidate label taking the target label as a root according to the inheritance relation of the label for the received test account request, and creating the target test account on the basis of the candidate label. The obtained target test account number and the synchronization time may be displayed in the graphical interface 301 of the device 300.

The native node in the blockchain network 20 may read the target article set from the blockchain, and present the target article set on the monitoring page of the native node, and the native node may also respond to the test account request, search according to the inheritance relationship of the tag, search for a candidate tag using the target tag as a root, and create the target test account on the basis of the candidate tag.

In practical applications, different functions may be set for different native nodes of the blockchain network 20, for example, the server 200 is configured to have a test account management function and an accounting function, for example, the server responds to a test account request uploaded by a device. For this situation, in the transaction process, the server 200 receives a test account request sent by the device 300, acquires a target label of the target test account by using the server 200, searches for a candidate label taking the target label as a root according to the inheritance relationship of the label, and creates a target test account on the basis of the candidate label; therefore, the target test account is created on the basis of the existing candidate test accounts, and the utilization rate of the test accounts in the test data platform is improved.

Referring to fig. 2B, fig. 2B is a schematic structural diagram of a test account management system according to an embodiment of the present application, and the apparatus 400 shown in fig. 2B includes: at least one processor 410, memory 450, at least one network interface 420, and a user interface 430. The various components in device 400 are coupled together by a bus system 440. It is understood that the bus system 440 is used to enable communications among the components. The bus system 440 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are labeled as bus system 440 in FIG. 2B.

The processor 410 may be an integrated circuit chip having signal processing capabilities such as a general purpose processor, a digital signal processor, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, etc., wherein the general purpose processor may be a microprocessor or any conventional processor, etc.

The user interface 430 includes one or more output devices 431, including one or more speakers and/or one or more visual displays, that enable the presentation of media content. The user interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, in some examples, a keyboard, a mouse, a microphone, a touch screen display, a camera, other input buttons and controls.

The memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid state memory, hard disk drives, optical disk drives, and the like. Memory 450 optionally includes one or more storage devices physically located remote from processor 410.

The memory 450 includes either volatile memory or nonvolatile memory, and may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read Only Memory (ROM), and the volatile Memory may be a Random Access Memory (RAM). The memory 450 described in embodiments herein is intended to comprise any suitable type of memory.

In some embodiments, memory 450 is capable of storing data, examples of which include programs, modules, and data structures, or a subset or superset thereof, to support various operations, as exemplified below.

An operating system 451, including system programs for handling various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and handling hardware-based tasks;

a network communication module 452 for communicating to other computing devices via one or more (wired or wireless) network interfaces 420, exemplary network interfaces 420 including: bluetooth, wireless compatibility authentication, and Universal Serial Bus (USB), etc.;

a presentation module 453 for enabling presentation of information (e.g., user interfaces for operating peripherals and displaying content and information) via one or more output devices 431 (e.g., display screens, speakers, etc.) associated with user interface 430;

an input processing module 454 for detecting one or more user inputs or interactions from one of the one or more input devices 432 and translating the detected inputs or interactions.

In some embodiments, the apparatus provided in this embodiment of the present application may be implemented in software, and fig. 2B illustrates a test account management server 455 stored in the memory 450, which may be software in the form of programs and plug-ins, and includes the following software modules: a first determination module 4551, a first search module 4552, a second determination module 4553, a first acquisition module 4554, and a first creation module 4555; these modules are logical and thus may be combined or further split according to the functionality implemented. The functions of the respective modules will be explained below.

In other embodiments, the apparatus provided in this embodiment may be implemented in hardware, and for example, the apparatus provided in this embodiment may be a processor in the form of a hardware decoding processor, which is programmed to execute the test account management method provided in this embodiment, for example, the processor in the form of the hardware decoding processor may be implemented by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), Complex Programmable Logic Devices (CPLDs), Field-Programmable Gate arrays (FPGAs), or other electronic components.

The test account management method provided by the embodiment of the present application will be described with reference to exemplary applications and implementations of the device provided by the embodiment of the present application.

Referring to fig. 3, fig. 3 is a schematic flow chart of an implementation of a test account management method according to an embodiment of the present application, and is described with reference to the steps shown in fig. 3.

Step S301, according to the obtained test requirement, determining a target test account for completing the test requirement.

Here, the test requirement may be carried in a test account request sent by other equipment, or may be a test requirement automatically obtained, for example, a test account request for requesting a target test account is obtained, the account request carries the test requirement, and then the target test account to be created is determined according to the test requirement. The test account request may be any request information for requesting a target test account. The target test account stores a test case for realizing the test requirement, namely, a user can obtain the target test account completing the test requirement by logging in the target test account.

Step S302, searching candidate test accounts with inheritance relationship with the target test account in the tree structure from the test data platform adopting the tree structure to store at least one test account.

At least one test account is stored in a test data platform in a tree structure according to different labels, wherein each test account at least comprises one label.

In some possible implementation manners, the test requirement is carried in the test account request, when the request is obtained, a target label of the target test account is determined, and then, based on the target label, a candidate label is searched from a structure tree of the test data platform to obtain a candidate test account, where the process is as follows:

firstly, a test account request carrying test requirements is obtained. Here, the test account request may carry a test requirement, and may also carry a target tag, for example, a target tag is set in advance based on the test requirement, and then the target tag is carried in the request. The test account request may be input in a webpage by a tester through an operation page, or may be sent to the test data platform by other devices. In some possible implementation manners, when a test requirement is received, a tester requests to obtain a target test account capable of realizing the test requirement by operating a test account request input by a page in a webpage. The target test account may be stored in the test data platform, and after obtaining the target test account, the tester logs in the account, and may use the test case corresponding to the account to complete the test requirement.

And secondly, determining a target label of the target test account according to the test requirement carried in the request and the attribute information of the target test account. Here, after receiving the test account request, a target tag may be set for the account according to the attribute information of the target test account carried in the request; the target label represents the main functions realized by the test case included in the target test account; in some possible implementation manners, the attribute information of the account is determined first, and a label is set for each test account, which may be implemented by the following steps: firstly, determining attribute information of a target test account according to a test requirement carried by a test account request; the attribute information of the test account at least comprises one of the following items: the account number includes an IDentity (ID) of a device to which the account number belongs, a role of the account number, friend information of the account number, a current session amount, card punching data, examination and approval data, an account number occupation condition and the like. In a specific example, the test requirement may be to test a function related to customer service, and the attribute information includes: the ID of the device to which the customer service staff account belongs, the occupation conditions of the customer service staff and the created customer service staff account, and the like. And then, determining a target label according to the attribute information of the target test account. For example, taking the target test account as the customer service staff account, if it can be determined from the attribute information of the target test account that the main function of the account is a problem occurring in the customer service test process, the target label can be set as the customer service staff.

And thirdly, searching candidate labels in the tree structure, which have inheritance relationship with the target labels, from the test data platform. Here, the inheritance relationship can be understood as that a node to which the target label belongs is searched for as a parent node of a child node in a tree structure; that is to say, the inheritance relationship between the labels of the test account stored in the test data platform is established according to the tree structure, the node to which the target label belongs is searched from the test data platform as the father node of the child node, and the label recorded in the father node is the candidate label.

And finally, determining the test account with the candidate label as a candidate test account. For example, the test account numbers stored in the nodes with the candidate tags in the tree structure are used as the candidate test account numbers.

Step S303, determining a first step set required by creating the target test account according to the test requirement.

Here, the first set of steps includes the steps required to create the target test account number. And analyzing the test requirements and combining the attribute information of the target test account to determine a first step set required for creating the target test account.

Step S304, a second step set included in the candidate test account is obtained.

Here, the second set of steps includes steps required to create the candidate test account; acquiring a second step set and a first step set of candidate test accounts, for example, a target test account to be created is an account with an external contact person with WeChat, and the required first step set includes: creating account number-real name authentication-configured as customer service person-add a slightly trusted external contact friend; the candidate test account is an account of the customer service staff, and the second step set comprises the following steps: creating an account, real-name authentication, and setting the account as a customer service person.

Step S305, creating a target test account according to at least one of the first step set and the second step set.

Here, since the inheritance relationship is stored between the first step set and the second step set, the target test account can be created by combining different steps in the two step sets on the basis of the second step set, and as can be seen from the above example, the first step set has one more step than the second step set, and then the one more step can be connected in series on the basis of the second step set, so that the target test account can be obtained; therefore, the target test account is created on the basis of the existing candidate test accounts, and the utilization rate of the test accounts in the test data platform is improved.

In some embodiments, in order to set an inheritance relationship between labels of a test account, before step S303, the method further includes the following steps, referring to fig. 4A, where fig. 4A is a schematic flow chart of another implementation of the test account management method provided in this embodiment, and is described with reference to the steps shown in fig. 3:

step S401, a plurality of used test accounts are acquired.

Here, the plurality of used test account numbers may be test account numbers created by a plurality of testers, or may be test account numbers created by the same tester.

Step S402, setting a used label of each used test account according to the attribute information of each used test account.

In some possible implementation manners, the main function of the account is determined by the attribute information of the used test account, so that the used label of the account is set based on the main function.

Step S403, setting an inheritance relationship between the used tags corresponding to the third step set according to the association relationship between the third step sets included in the plurality of used test account numbers.

Here, the third set of steps includes the steps required to create a used test account number. And setting inheritance relationships among the used labels corresponding to the multiple third step sets according to the association relationships and the tree structures. For example, there are three test account numbers that have been used: the customer service staff account number, the account number of the external contact person with the WeChat and the account number of the external contact person with the WeChat; wherein:

the third step set of the customer service staff account is as follows: creating account number-real name authentication-configured as a customer service person;

the third step set of the account number of the external contact person with the WeChat is as follows: creating account number-real name authentication-configured as customer service person-add a slightly trusted external contact friend;

the third step set of the account number of the external contact group with the WeChat is as follows: creating an account, real-name authentication, configured as a customer service person, adding a friend of a slightly-trusted external contact person, creating a friend group of the slightly-trusted external group chat, pulling the friend of the slightly-trusted external contact person;

in some possible implementation manners, the inheritance relationship between the tags is set according to the precedence relationship of the step set on the execution time sequence, and the inheritance relationship can be realized through the following processes:

firstly, determining the precedence relationship between the third step sets in the execution time sequence according to the incidence relationship between the third step sets included in each used test account.

For example, the sequence of the third step set of the customer service staff account, the external contact account with WeChat and the external contact account with WeChat in the execution time sequence is as follows: the customer service staff account number, the account number of the external contact person with the WeChat and the account number of the external contact person with the WeChat.

And then, sequencing the step sets of the used test accounts according to the precedence relationship to obtain a sequencing result.

For example, the 3 accounts are sorted according to the precedence relationship as follows: the customer service staff account number, the account number of the external contact person with the WeChat and the account number of the external contact person with the WeChat.

And finally, setting the inheritance relationship between the used labels corresponding to the step sets according to the sorting result.

Here, first, the used labels corresponding to the step sets arranged at specific positions in the sorted results are given to the root node; for example, the sorting result is arranged from small to large according to the execution time sequence, and the used label with the first arrangement result is given to the root node; then, endowing a used label corresponding to the next step set of the step set to which the root node belongs to the child node of the root node; for example, the step of ranking in the second step assigns the child nodes of the root node in combination with the corresponding used labels. And finally, the step set which is executed finally in the arrangement result is given to the leaf nodes of the child nodes so as to obtain the inheritance relationship. For example, since the arrangement result is arranged according to the execution time sequence, the arrangement in the last step set is the most complex step combination, and the used label corresponding to the step set arranged in the last step in the arrangement result is assigned to the leaf node; thus, an inheritance relationship among the labels of the multiple accounts is established.

For the above example, the correlation relationship of the customer service staff account, the external contact account with WeChat and the external contact group account with WeChat is that a step is added on the basis of the customer service staff account for the external contact account with WeChat; the account number of the external contact person with the WeChat is added with two steps on the basis of the account number of the external contact person with the WeChat; based on the incidence relation, determining that the account number of the customer service staff in the 3 account numbers is used as the account number in the root node according to a tree structure, and then using the node which the account number of the external contact person with the WeChat belongs to as a child node of the root node which the account number of the customer service staff belongs to; and finally, taking the node to which the account of the external contact person with the WeChat belongs as a leaf node of the node to which the account of the external contact person with the WeChat belongs, and thus establishing an inheritance relationship among the labels of the plurality of account numbers.

Step S404, storing the inheritance relationship, the plurality of used test account numbers and the used label of each used test account number in the test data platform.

Here, the related information of the account is stored in the test data platform, so that a uniform interface is provided for testers using the platform, the platform is convenient to access, and the established account is used.

In the embodiment of the application, multiple used test accounts and used labels of each used test account are stored in the test data platform according to the inheritance relationship among the labels of the used test accounts, so that the platform can be quickly used in automatic test scenes such as protocol tests, user interface automatic tests, unit tests and the like.

In some embodiments, in order to improve the utilization rate of the test account, on the basis of the candidate test account of the candidate tag having an inheritance relationship, the steps required for implementing the test requirement are connected in series, and the target test account is created, and step S303 may be implemented in a plurality of ways:

the first method is as follows: referring to fig. 4B, fig. 4B is a schematic flowchart of another implementation flow of the test account management method provided in the embodiment of the present application, and is described with reference to the steps shown in fig. 3:

step S421, find the label identical to the target label from the test data platform.

Here, the label identical to the target label may be a label of a test account used last time by a device that issues a request, or may be a label that is not used by the device but is identical to the target label.

Step S422, if the test data platform includes the label identical to the target label, and the test account to which the label identical to the target label belongs is in an unoccupied state.

Here, if the test account to which the same tag as the target tag belongs is in the idle state, it indicates that the test account is currently available.

In step S423, the same tag as the target tag is set as a candidate tag.

In the above-mentioned step S421 to step S423, a manner of "searching for a candidate label having an inheritance relationship with the target label in the tree structure from the test data platform" is provided, in this manner, after receiving a test account request, a used test account having the target label is preferentially searched from the test data platform, and if the test data platform includes a label identical to the target label, the label identical to the target label is used as the candidate label.

Step S424, determine the candidate test account with the candidate label as the target test account.

Here, the test account corresponding to the candidate label is directly used as a target test account, and the target test account does not need to be created again; therefore, the test account number used by the target label in the test data platform is preferentially distributed, and the automatic test efficiency can be greatly improved.

The second method comprises the following steps: after step S421, if the test account to which the label identical to the target label belongs is in an occupied state, or the test data platform does not include the label identical to the target label, the candidate label may be determined by the following steps:

firstly, if the test account number to which the label same as the target label belongs is in an occupied state or the test data platform does not include the label same as the target label, determining a father node having an inheritance relationship with the node to which the target label belongs from a tree structure of the test platform to obtain a father target node.

Here, if the test account to which the same label as the target label belongs is in an occupied state, or the test data platform does not include the used test account to which the target label belongs, which indicates that no test account available for the test requirement currently exists, the parent node of the node to which the target label belongs, which has an inheritance relationship, is searched from the tree structure of the test data platform, so as to obtain the parent target node.

And secondly, searching the label which is the same as the label stored on the father target node from the tree structure to obtain a label to be candidate.

Here, from the tags stored in the test data platform, the same tags as the tags stored in the parent target node are searched for to-be-candidate tags.

And thirdly, if the test account number to which the label to be candidate belongs is in an unoccupied state, determining the label to be candidate as the candidate label.

When the target label has no idle account, searching is carried out according to the inheritance relationship of the target label, and a father node which takes the target label as a child node is searched, so that the utilization rate of the test account can be improved to a greater extent.

The first step to the third step realize that the candidate label with the inheritance relationship with the target label is searched from the test data platform storing at least one label of the test account, and the candidate label with the inheritance relationship with the target label is searched from the data platform storing the used test account, so that the account used by the target label in the test data platform is preferentially distributed, and the automatic test efficiency can be greatly improved.

And step four, determining different steps between the first step set and the second step set.

Here, since the node of the candidate tag to which the second step set belongs is a parent node of the target tag, the steps included in the first step set overlap with the steps included in the second step set, for example, the steps included in the first step set are more than the steps included in the second step set, for example, the second step set includes 5 steps, and then the first step set includes a 6 th step on the basis of including 5 steps.

And fifthly, executing different steps on the basis of the candidate test account to create a target test account.

Here, the part of the first step set exceeding the second step set is connected to the second step set in a serial manner and executed to create the target test account, for example, if the second step set includes 5 steps, then the first step set includes a 6 th step on the basis of including 5 steps. And accessing the 6 th step into the second step set as the last step of the second step set, and executing the 6 th step to create the target test account.

In some embodiments, after "searching for a label identical to a label stored on a parent target node from a tree structure" in the second step is executed, if a to-be-candidate label having an inheritance relationship with a target label cannot be found from the test data platform, or a test account to which the to-be-candidate label belongs is in an occupied state, dynamically creating a target test account capable of meeting the test requirement according to the content of the test requirement, and creating the target test account by the following process:

firstly, if the tree structure does not include the label to be candidate or the test account number to which the label to be candidate belongs is in an occupied state, acquiring a first step set for realizing the test requirement and attribute information of the target test account number.

Here, if there is no free test account available for implementing the test requirement in the test data platform, and there is no label storing an inheritance relationship with the label of the target test account, then the target test account is automatically created, and first, a first step set required for creating the target test account and attribute information of the target test account are obtained, for example, 5 steps are required for creating the target test account, and the target test account: the ID of the device, the role of the account, friend information of the account, the current session volume, the data of card punching, the data of the examination and approval sheet, the account occupation condition and the like.

And secondly, creating a target test account according to the first step set and the attribute information of the target test account.

Carrying the attribute information in the corresponding step in the first step set, and creating a target test account; therefore, under the condition that the test data platform does not include the node having the inheritance relationship with the node of the target label, the target test account is automatically created, and the condition that other processes are blocked due to insufficient test accounts is reduced.

In some embodiments, after creating the target test account, locking the target test account, feeding the locked target test account back to the user, and after the user finishes using the target test account, releasing the test account so that other users can use the test account, which may be implemented by the following steps:

firstly, encrypting a target test account and feeding back the encrypted target test account.

Here, the target test account is locked, so that other users cannot use the encrypted target test account, and it is ensured that the encrypted target test account is not used by other users at present.

And then, when an instruction for representing that the encrypted target test account is used completely is received, decrypting the encrypted target test account.

Here, after the current user finishes using, the encrypted target test account is decrypted, that is, the target test account is released and stored in the test data platform, so that other users can use the target test account repeatedly, and the utilization rate of the test account is improved.

An exemplary application of the embodiment of the present application in an actual application scenario will be described below, taking an example of implementing dynamic generation of a test account and dynamic management of a test account on a data platform as an example, and performing the following description:

in the related art, a test data factory platform is basically a file of existing test account numbers, and firstly, data preparation threshold is high due to the fact that data are required to be generated one by one according to requirements and attributes are set for the account numbers through complex steps; secondly, as a part of the test account numbers have a pass attribute but cannot be effectively multiplexed, data utilization is low; finally, the use of account attributes and accounts cannot be effectively managed, which results in high data maintenance cost.

Based on the method and the system, a test data factory platform for dynamic generation and management is realized, and the test data are quickly, conveniently and systematically constructed and maintained in a standardized way. The method has the following characteristics: firstly, encapsulating common test data attribute setting units, and simultaneously supporting the serial connection of the units in a pipeline mode to cover the requirements on test accounts and data in a common scene, thereby realizing rapid data construction; secondly, managing the test account by taking the label as a dimension, supporting label inheritance, improving the reusability of the test account and realizing label type management of the account; thirdly, static and dynamic attributes of the account can be acquired through the platform, secondary processing of the constructed data is supported, and account attributes and account number are dynamically expanded, so that dynamic account attribute management is realized; finally, a simple human-computer interaction network page is provided, so that any role member can quickly construct and acquire a test account, and the capability of quickly using the platform in automatic test scenes such as protocol test, user interface automatic test, unit test and the like is realized.

The embodiment of the present application provides a concise web page, which facilitates rapid data construction and management of team members of various roles, and the schematic representation on the product side is shown in fig. 5, where fig. 5 is a page schematic diagram of the test account management system provided in the embodiment of the present application, and the following description is performed in combination with fig. 5:

in the operation page 501, a menu bar includes: my enterprise 502, data constructs 503, task list 504, advanced schema 505, Q & a documents 506, location tool 507, operating instructions 508, and API documents 509; the enterprise list used to map the test account for the service includes: administrator name 511, administrator VID512, company name 513, company ID514, company size 515, phone number 516, expiration date 517, and operation 518; each row in this list characterizes a test account number, i.e. a total of 8 test account numbers are displayed in the operation page 501. Taking an enterprise social application scenario as an example, the test account list is shown in the operation page 501.

Fig. 6 is another page schematic diagram of the test account management system provided in the embodiment of the present application, and the following description is made with reference to fig. 6:

in the data structuring page 601, the menu bar includes: my enterprise 502, data constructs 503, task lists 504, advanced schemas 505, question & Answers (Q & a) documents 506, location tools 507, operating instructions 508, and API documents 509; when the tester selects the data construct 503, an editable window is displayed in area 602 for setting the properties of a test account, including: creating content 611, an enterprise name 612, an administrator name 613, a member number 614, a department number 615 (the limited condition is that the number of new departments can be set to be 5 thousand at most), a mobile phone number 616 (the limited condition is that the new enterprises are used for login and a test account number is allocated by default when the new enterprises are not filled in), a login account number 617 (the limited condition is that a default mobile phone number is allocated and the new enterprises can be directly logged in by using a data number and an authentication code and 10 persons at most) and a destination 618 (the limited condition is that when more than 10 ten thousand enterprises are created, the operation VID exceeds 1 thousand and the enterprise identification (Corporate Identity, Corporate Identity) exceeds 50, a background fault group is notified); in this way, corresponding content can be input in each editable frame to set the attribute of the test account; for example, the common items that have been set in the creating content 611 (e.g., creating a business 621, creating an internal group chat 622, creating an external group chat 623, sending a message 624, adding a friend 625, and setting an application 626) can be selected, and the common items can also be a custom input.

Here, the data construction page 601 covers the high-frequency account demand construction capability in the enterprise social application test scene, and the test accounts and data can be created and batch attribute setting can be performed on the test accounts through simple selection and parameter transmission of the page.

Fig. 7 is another page schematic diagram of the test account management system according to the embodiment of the present application, and the following description is made with reference to fig. 7:

in the operation page 701 in the advanced mode, a menu bar includes: my enterprise 502, data constructs 503, task list 504, advanced schema 505, Q & a documents 506, location tool 507, operating instructions 508, and API documents 509; when a tester selects the advanced mode 505, in the area 702, an interface supporting a user to call a platform is provided, so that the user can conveniently perform custom setting on a test account, and the steps of test account generation and test account attribute setting in series of complex steps are performed, so that the account is conveniently and rapidly expanded.

Fig. 8 is a schematic diagram of a composition structure of a method for implementing test account management according to an embodiment of the present application, and as shown in fig. 8, the method includes the following modules: a concise human-computer interaction web page 801, a tag management module 802, an attribute setting unit 803, an account attribute management module 804, an account usage management module 805, a tag and account storage 806, and an open restul API 807, wherein:

the concise human-computer interaction web page 801 is used for providing an interface for inputting instructions for a tester to perform human-computer interaction.

The label management module 802 is configured to manage the test account with a label as a dimension.

Here, the tag management module 802 provides two core capabilities:

firstly, defining a label, and setting information such as a label name, inheritance relationship, use, remark and the like.

Secondly, defining an account attribute generation mode corresponding to the label, for example, creating a target test account directly based on the target label, or performing a series connection of subsequent steps based on the existing test accounts to obtain the target test account.

According to the embodiment of the application, certain attributes of the test account are abstracted into a label concept, one test account can have a plurality of labels, and inheritance relationships exist among the labels. This means that: the test account can be used according to the label inheritance relationship so as to improve the utilization rate of the test account. And the generation of the account and the setting mode of the attribute also have an inheritance relationship, so that the generation efficiency of the account can be further improved.

Here, as shown in fig. 9, fig. 9 is a schematic diagram of a composition structure for implementing tag inheritance according to an embodiment of the present application, and in fig. 9, taking an external contact tag of an enterprise social application as an example, a tag is an account of a customer service person 901 as a root node, where child nodes of the tag include: owning social application external contacts 902 and owning external business contacts 903, where owning social application external contacts 902 is for leaf node owning social application external contacts group 904.

In one specific example, assume there are 10 accounts of a customer service person, a contact outside of the social application, and a contact outside of the social application, each of the 4 types of accounts. In the test account management system provided by the embodiment of the application, if a customer service staff account is to be used, the account attribute is abstracted into a tag, and the inheritance relationship of the tag is defined. The 3 types of labels of the contact persons outside the social application, the external enterprise contact and the contact persons outside the social application are directly or indirectly inherited from the labels of the customer service personnel. Therefore, when the customer service personnel label is obtained, 40 available test account numbers exist, and therefore the utilization rate of the test account numbers is greatly improved.

The attribute setting unit 803 is configured to set an attribute for each test account through call between interfaces.

According to business requirements, the common account attribute setting unit in the development, test and experience processes is packaged and provided. The account attribute setting unit realizes attribute setting through a service open interface 808, a service private CGI809, a service background RPC 810, a service background tool 811 and the like. Meanwhile, the method also supports that a plurality of attribute setting units are strung in a pipeline mode to realize the setting of the complex attribute. Meanwhile, the attribute setting method is inheritable by combining the inheritable characteristic of the label of the application. For example:

the step of creating the customer service staff account comprises the following steps: creating account number-real name authentication-configured as a customer service person;

the step of creating an external contact account with a social application comprises: creating an account, real-name authentication, configured as a customer service person, adding a friend of a contact person outside the social application;

the step of creating an account of the group of people who have external contacts to the social application comprises: creating an account, real-name authentication, configured as a customer service person, adding a friend of a contact person outside the social application, creating a group chat outside the social application, pulling a friend of a contact person outside the social application to enter a group;

as can be seen, the steps for generating test accounts with contacts external to the social application are complex. However, in this embodiment, the creation process of the test data has an inheritance relationship as with the label. Therefore, the account of the external contact person of the social application is owned, and two steps of operations of creating external group chat of the social application and pulling friends of the external contact person of the social application into a group can be added on the basis of inheriting the account of the external contact person of the social application, so that maintainability and efficiency of setting the generation attribute of the account are greatly improved.

And the account attribute management module 804 is used for creating and storing the test account.

Here, in the embodiment of the application, based on the inheritance relationship between the labels of the account numbers, on the basis of the used test account numbers, the steps occurring after the steps included in the used test account numbers in the target test account numbers are connected in series to obtain the target test account numbers, so that the use efficiency and the test efficiency of the account numbers are further improved.

In some possible implementation manners, a test account application flow is shown in fig. 10, where fig. 10 is a schematic view of an account application flow provided in an embodiment of the present application, and the following description is performed in combination with the steps shown in fig. 10:

step S1001, acquires a test account request.

Here, the request includes a target tag and a device ID of a target test account to be requested; in some possible implementations, when the test account request is obtained using a system page or API, the required account tag and a device ID for identifying the device identity are transferred.

Step S1002 determines whether the target tag matches the tag used last time by the device, based on the device ID in the request.

In some possible implementation manners, the system preferentially identifies whether a tag of the test account applied for the ID last time is consistent with a target tag applied for this time, determines that the tag used for the equipment last time is a candidate tag if the consistent target tag is consistent with the tag used for the equipment last time, and then proceeds to step S1003, otherwise, proceeds to step S1005.

Step S1003, determining whether the test account used by the device last time is occupied.

Here, it is determined whether the test account corresponding to the candidate tag is used, whether the account used by the device last time is occupied by other IDs is determined, and if not, the process goes to step S1004; if it is occupied, step S1005 is executed.

Step S1004, acquiring the static and dynamic attributes of the candidate account, locking the account, and returning to the user.

Here, the static attributes include: the ID of the account, the role, some friends of the account, etc.; the dynamic attributes include: the current conversation quantity, the card punching data, the examination and approval data, the account occupation condition testing and the like can be changed at any time.

Step S1005, determining whether there is an idle test account including the target tag.

Here, whether the target tag has an idle test account is searched, if so, the method goes to step S1004, that is, the static and dynamic attributes of the account are acquired, and the account is locked and returned to the user; otherwise, the process advances to step S1006.

Step S1006, determining whether the label of the father node having an inheritance relationship with the target label exists in the idle test account.

Here, an inheritance tree rooted at a target label is searched for according to the inheritance property of the label. If the idle account exists, step S1004 is entered, that is, the static and dynamic attributes of the account are obtained, and the account is locked and returned to the user; otherwise, the process advances to step S1007.

Step 1007, according to the attribute information, a target test account is dynamically created.

Here, after the target test account is dynamically created, step S1004 is performed, that is, the static and dynamic attributes of the target test account are obtained, and the account is locked and returned to the user.

The account usage management module 805 is configured to lock the created target test account, feed the locked target test account back to the user, and release the target test account when the use is completed, so that other people can use the account.

And the label and account storage 806 stores the labels, the inheritance relationship among the labels and the test accounts in the data platform.

The RESTFUL API 807 is opened, and is used for providing a set of complete and rich API interfaces, so that the capability of the platform can be quickly used in automatic test scenes such as protocol tests, User Interface (UI) automatic tests, unit tests and the like.

Under the automatic test scenes of protocol test, UI automatic test, unit test and the like, when the account numbers allocated at each time are different, the account number switching consumption is high, and the account numbers used by the ID last time are preferentially allocated when the test account numbers are acquired, so that the automatic test efficiency can be greatly improved. In addition, when a test account is applied, and when the target label has no idle account, the inheritance tree taking the target label as the root is searched according to the inheritance relationship of the target label, so that the utilization rate of the test account can be improved to a greater extent; and meanwhile, when the idle account is not obtained, the test account is automatically created, so that the condition that other processes are blocked due to insufficient test accounts is reduced.

Continuing with the exemplary structure of the test account management server 455 provided in this embodiment of the present application implemented as software modules, in some embodiments, as shown in fig. 2, the software modules stored in the test account management server 455 of the memory 450 may include:

a first determining module 4551, configured to determine, according to the obtained test requirement, a target test account for completing the test requirement;

the first searching module 4552 is configured to search, from a test data platform that stores at least one test account in a tree structure, a candidate test account in the tree structure that has an inheritance relationship with the target test account;

a second determining module 4553, configured to determine, according to the test requirement, a first step set required for creating the target test account; wherein the first set of steps includes steps required to create the target test account;

a first obtaining module 4554, configured to obtain a second step set included in the candidate test account; wherein the second set of steps includes steps required to create the candidate test account;

a first creating module 4555, configured to create the target test account according to at least one of the first step set and the second step set.

In some embodiments, the first determining module 4551 is further configured to: determining attribute information of the target test account according to the test requirement; determining the target label according to the attribute information of the target test account; correspondingly, searching candidate labels in the tree structure, which have inheritance relationship with the target labels, from the test data platform; and determining the test account with the candidate label as the candidate test account.

In some embodiments, the first lookup module 4552 is further configured to: acquiring a plurality of used test account numbers; setting a used label of each used test account according to the attribute information of each used test account; setting inheritance relationships among used labels corresponding to a third step set according to the tree structure according to the incidence relationships among the third step sets included in the used test account numbers; and storing the inheritance relationship, the plurality of used test account numbers and the used label of each used test account number in the test data platform.

In some embodiments, the first lookup module 4552 is further configured to: determining the precedence relationship of the third step sets of each used test account in the execution time sequence according to the incidence relationship of the third step sets of each used test account; sequencing the third step set of the used test accounts according to the sequence relation to obtain a sequencing result; and setting the inheritance relationship between the used labels corresponding to the set in the third step according to the tree structure according to the sequencing result.

In some embodiments, the first lookup module 4552 is further configured to: assigning the used labels corresponding to the step sets arranged at the specific positions in the sequencing result to the root nodes of the tree structure; giving a used label corresponding to a step set next to the step set to which the root node belongs to a child node of the root node; and step sets which are executed finally in the arrangement result are given to leaf nodes of the child nodes so as to obtain the inheritance relationship.

In some embodiments, the first lookup module 4552 is further configured to: searching for a label which is the same as the target label from the test data platform; if the test data platform comprises the label which is the same as the target label, and the test account number to which the label which is the same as the target label belongs is in an unoccupied state; taking the label which is the same as the target label as the candidate label;

correspondingly, the first creating module 4555 is further configured to: and determining the candidate test account which comprises the second step set and has the candidate label as the target test account.

In some embodiments, the first lookup module 4552 is further configured to: if the test account number to which the label identical to the target label belongs is in an occupied state, or the test data platform does not include the label identical to the target label, determining a parent node having an inheritance relationship with the node to which the target label belongs from a tree structure of the test platform to obtain a parent target node; searching a label which is the same as the label stored on the father target node from the tree structure to obtain the label to be candidate; and if the test account number to which the label to be candidate belongs is in an unoccupied state, determining that the label to be candidate is a candidate label.

In some embodiments, the first creating module 4555 is further configured to: determining a difference between the first set of steps and the second set of steps; and executing the different steps on the basis of the candidate test account to create the target test account.

In some embodiments, the first lookup module 4552 is further configured to: if the tree structure does not include the label to be candidate or the test account number to which the label to be candidate belongs is in an occupied state, acquiring a first step set for creating the target test account number and attribute information of the target test account number; and creating the target test account according to the first step set and the attribute information of the target test account.

In some embodiments, the first creating module 4555 is further configured to: encrypting the target test account and feeding back the encrypted target test account; and when an instruction for representing that the encrypted target test account is used completely is received, decrypting the encrypted target test account.

Embodiments of the present application provide a storage medium storing executable instructions, which when executed by a processor, will cause the processor to execute the method provided by the embodiments of the present application. In some embodiments, the storage medium may be memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or may be various devices including one or any combination of the above memories. In some embodiments, executable instructions may be written in any form of programming language (including compiled or interpreted languages), in the form of programs, software modules, scripts or code, and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. By way of example, executable instructions may, but need not, correspond to files in a file system, and may be stored in a portion of a file that holds other programs or data, such as in one or more scripts in a hypertext Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). By way of example, executable instructions may be deployed to be executed on one in-vehicle computing device or on multiple computing devices located at one site or distributed across multiple sites and interconnected by a communication network. In summary, in the embodiment of the present application, after receiving a test account request, a candidate tag having an inheritance relationship is searched for from a test data platform based on a target tag of a requested target test account; then, on the basis of the candidate test account to which the candidate label belongs, the target test account is created by combining the step set required for realizing the test requirement; therefore, the used test account number of the target label in the test data platform is preferentially distributed, and the automatic test efficiency can be greatly improved; and moreover, the target test account is created on the basis of the candidate test accounts in the test data platform, so that the utilization rate of the test accounts in the test data platform is improved. The above description is only an example of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, and improvement made within the spirit and scope of the present application are included in the protection scope of the present application.

Claims

1. A test account management method is characterized by comprising the following steps:

and creating the target test account according to at least one of the first step set and the second step set.

2. The method according to claim 1, wherein after determining a target test account for completing the test requirement according to the obtained test requirement, the method further comprises:

determining attribute information of the target test account according to the test requirement;

determining the target label according to the attribute information of the target test account;

correspondingly, the searching for the candidate test account having an inheritance relationship with the target test account in the tree structure from the test data platform storing at least one test account in the tree structure includes:

searching candidate labels in the tree structure, which have inheritance relationship with the target labels, from the test data platform;

and determining the test account with the candidate label as the candidate test account.

3. The method of claim 2, wherein prior to said searching for a candidate tag in said tree structure that has an inheritance relationship with said target tag from said test data platform, said method further comprises:

acquiring a plurality of used test account numbers;

setting a used label of each used test account according to the attribute information of each used test account;

setting inheritance relationships among used labels corresponding to a third step set according to the tree structure according to the incidence relationships among the third step sets included in the used test account numbers; wherein the third set of steps includes steps required to create the used test account;

and storing the inheritance relationship, the plurality of used test account numbers and the used label of each used test account number in the test data platform.

4. The method according to claim 3, wherein the setting, according to the association relationship among the third step sets included in the plurality of used test account numbers, the inheritance relationship among the used labels corresponding to the third step sets according to the tree structure includes:

determining the precedence relationship of the third step sets of each used test account in the execution time sequence according to the incidence relationship of the third step sets of each used test account;

sequencing the third step set of the used test accounts according to the sequence relation to obtain a sequencing result;

and setting the inheritance relationship between the used labels corresponding to the set in the third step according to the tree structure according to the sequencing result.

5. The method according to claim 4, wherein said setting, according to the sorting result, an inheritance relationship between used labels corresponding to the third step set according to the tree structure includes:

assigning the used labels corresponding to the step sets arranged at the specific positions in the sequencing result to the root nodes of the tree structure;

giving a used label corresponding to a step set next to the step set to which the root node belongs to a child node of the root node;

and step sets which are executed finally in the arrangement result are given to leaf nodes of the child nodes so as to obtain the inheritance relationship.

6. The method according to any one of claims 2 to 5, wherein said searching for a candidate label in the tree structure having an inheritance relationship with the target label from the test data platform comprises:

searching for a label which is the same as the target label from the test data platform;

if the test data platform comprises the label which is the same as the target label, and the test account number to which the label which is the same as the target label belongs is in an unoccupied state;

taking the label which is the same as the target label as the candidate label;

correspondingly, the creating the target test account according to at least one of the first step set and the second step set includes:

and determining the candidate test account with the candidate label as the target test account.

7. The method of claim 6, wherein said searching for candidate tags in the tree structure that have an inheritance relationship with the target tag from the test data platform comprises:

if the test account number to which the label identical to the target label belongs is in an occupied state, or the test data platform does not include the label identical to the target label, determining a parent node having an inheritance relationship with the node to which the target label belongs from a tree structure of the test platform to obtain a parent target node;

searching a label which is the same as the label stored on the father target node from the tree structure to obtain the label to be candidate;

and if the test account number to which the label to be candidate belongs is in an unoccupied state, determining that the label to be candidate is a candidate label.

8. A test account management apparatus, the apparatus comprising:

9. An apparatus for testing account management, comprising:

a memory for storing executable instructions;

a processor for implementing the method of any one of claims 1 to 7 when executing executable instructions stored in the memory.

10. A computer storage medium having stored thereon executable instructions for causing a processor to perform the method of any one of claims 1 to 7 when executed.