CN116991713B - Method, device, computer equipment and storage medium for executing use cases across environments - Google Patents

Abstract

This application relates to methods, devices, computer equipment and storage media for executing use cases across environments. The method includes: obtaining the use case content and the environment parameter information of the target environment in the current environment; obtaining the corresponding token information according to the environment parameter information of the target environment; and constructing the cross-environment configuration information according to the token information, wherein , the cross-environment configuration information is used for identification by the interface gateway of the target environment; generate a cross-environment use case according to the use case content and the cross-environment configuration information, and synchronize the cross-environment use case to the target environment, to execute the cross-environment use case in the target environment. Using this method can enable use cases to be executed across environments, thereby shortening the application development cycle, reducing the cost of writing use cases, and improving development efficiency.

Description

Methods, devices, computer equipment and storage media for executing use cases across environments

Technical field

The present application relates to the field of computer applications, and in particular to a method, device, computer equipment and storage medium for executing use cases across environments.

Background technique

With the development of application development and testing technology, technicians currently test applications in multiple different environments to obtain more comprehensive test results and ensure that the effects of the application after it is launched meet expectations. The test cases used in different environments are different and cannot be called between each other. Use case content added, deleted or modified for a single environment only affects the current environment, and use cases in other environments are not affected. Therefore, if you want to complete the testing process in different environments, you need to write corresponding use cases in each environment, which results in high cost and low efficiency in writing use cases.

Contents of the invention

Based on this, it is necessary to address the above technical issues and provide a method, device, and computer equipment for cross-environment execution of use cases that can enable use cases to be executed across environments, thereby shortening the application development cycle, reducing the cost of writing use cases, and improving development efficiency. and storage media.

In the first aspect, this application provides a method for executing use cases across environments. The methods include:

In the current environment, obtain the use case content and environment parameter information of the target environment;

Obtain corresponding token information according to the environmental parameter information of the target environment;

Construct cross-environment configuration information according to the token information, wherein the cross-environment configuration information is used for identification by the interface gateway of the target environment;

A cross-environment use case is generated according to the use case content and the cross-environment configuration information, and the cross-environment use case is synchronized to the target environment to execute the cross-environment use case in the target environment.

In one embodiment, the use case content includes environmental parameter information of the current environment, and the numerical values indicated by the environmental parameter information corresponding to different environments are different; the corresponding token is obtained according to the environmental parameter information of the target environment. Information includes:

Compare the values indicated by the environment parameter information corresponding to the current environment and the target environment;

When the value indicated by the environment parameter information of the current environment is greater than or equal to the value indicated by the environment parameter information of the target environment, token information corresponding to the target environment is obtained.

In one embodiment, when the value indicated by the environment parameter information of the current environment is greater than or equal to the value indicated by the environment parameter information of the target environment, obtaining the value corresponding to the target environment. Token information includes:

When the value indicated by the environment parameter information of the current environment is equal to the value indicated by the environment parameter information of the target environment, directly obtain the token information corresponding to the target environment in the first calling method;

When the value indicated by the environment parameter information of the current environment is greater than the value indicated by the environment parameter information of the target environment, obtain the interface gateway proxy address of the target environment, and based on the interface gateway proxy address, Obtain token information corresponding to the target environment in a first calling manner.

In one embodiment, the first calling method is a generalized calling.

In one embodiment, constructing cross-environment configuration information based on the token information includes:

Obtain the header information of the use case content;

The token information is spliced into the header information to construct cross-environment configuration information.

In one embodiment, before obtaining the corresponding token information according to the environmental parameter information of the target environment, the method further includes:

Execute the use case content to obtain the result log;

Verify that the result log meets preset standards;

If the result log meets the preset standard, the step of obtaining corresponding token information according to the environment parameter information of the target environment is performed.

In one embodiment, the current environment and the target environment are any one of a test environment, a pre-release environment and a production environment respectively _.

In the second aspect, this application also provides a device for executing use cases across environments. The device includes:

The use case acquisition module is used to obtain the use case content and environment parameter information of the target environment in the current environment;

A token generation module, configured to obtain corresponding token information according to the environmental parameter information of the target environment;

An environment configuration module, configured to construct cross-environment configuration information based on the token information, wherein the cross-environment configuration information is used for identification by the interface gateway of the target environment;

A use case synchronization module, configured to generate a cross-environment use case based on the use case content and the cross-environment configuration information, and synchronize the cross-environment use case to the target environment to execute the cross-environment use case in the target environment. .

In a third aspect, this application also provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the steps described in the first aspect when executing the computer program.

In a fourth aspect, this application also provides a computer-readable storage medium. The computer-readable storage medium has a computer program stored thereon, and when the computer program is executed by a processor, the steps described in the first aspect are implemented.

The above-mentioned methods, devices, computer equipment and storage media for executing use cases across environments can obtain corresponding token information through the environment parameter information of the target environment, thereby completing the construction of cross-environment configuration information. When executing a use case across environments, it is necessary to ensure that the interface gateway of the target environment can identify the relevant information for executing the use case. At this time, the above cross-environment configuration information can be recognized by the interface gateway of the target environment, thereby calling the interface and generating a function that can be used in the target environment. Cross-environment use cases are executed to complete the process of cross-environment execution of use cases. The above cross-environment configuration information can be constructed in real time when it needs to be called across environments, and the required token information can be obtained in real time, thus ensuring the validity of the token information and greatly reducing the maintenance cost of the token information. It avoids the invalidation of manually maintained token information and eliminates the interference of token information invalidation, making it easier to locate the cause of errors during use case execution _, thereby shortening the application development cycle. At the same time, cross-environment execution of use cases can reuse use cases in different environments. There is no need to write the same use cases for different environments, so it can reduce the cost of writing use cases and improve development efficiency.

Description of the drawings

Figure 1 is an application environment diagram of a method for executing use cases across environments in one embodiment;

Figure 2 is a schematic flowchart of a method for executing use cases across environments in one embodiment;

Figure 3 is a schematic flowchart of step S204 in one embodiment;

Figure 4 is a schematic flowchart of step S304 in one embodiment;

Figure 5 is a schematic flowchart of step S206 in one embodiment;

Figure 6 is an execution subject relationship diagram of a method for executing use cases across environments in one embodiment;

Figure 7 is an execution architecture diagram of a method for executing use cases across environments in one embodiment;

Figure 8 is a structural block diagram of a device for executing use cases across environments in one embodiment;

Figure 9 is an internal structure diagram of a computer device in one embodiment;

Figure 10 is an internal structure diagram of another computer device in an embodiment.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application more clear, the present application will be further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application and are not used to limit the present application.

The method for executing use cases across environments provided by the embodiments of this application can be applied to the application environment as shown in Figure 1. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system may store data that server 104 needs to process. The data storage system can be integrated on the server 104, or placed on the cloud or other network servers. The use case content and the environment parameter information of the target environment are obtained through the terminal 102, and the corresponding token information is obtained through the environment parameter information of the target environment, thereby completing the construction of the cross-environment configuration information. When executing a use case across environments, it is necessary to ensure that the interface gateway of the target environment can identify the relevant information for executing the use case. At this time, the above cross-environment configuration information can be identified by the interface gateway of the target environment, so as to adjust the interface and generate the information that can be used in the target environment. Cross-environment use cases executed under the environment, thereby completing the process of cross-environment execution use cases. Among them, the terminal 102 can be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, Internet of Things devices, etc. The server 104 can be implemented as an independent server or a server cluster composed of multiple servers.

In one embodiment, as shown in Figure 2, a cross-environment execution use case method is provided. In this embodiment, the method is applied to the terminal as an example. It can be understood that the method can also be applied to the server, and can also be It is applied to systems including terminals and servers, and is implemented through the interaction between terminals and servers. In this embodiment, the method includes the following steps:

Step 202: In the current environment, obtain the use case content and the environment parameter information of the target environment.

Among them, the current environment refers to the environment where the corresponding use case content originally exists when the use case is executed across environments, and can be the writing environment for the use case content; correspondingly, the above target environment refers to the interface environment that needs to be called when the use case is executed across environments.

Among them, the use case content refers to the information that describes the complete process of testing. Optionally, the use case content describes the specific steps, input data, expected results, verification points and other information for testing the application, terminal and server interface, etc. It is used to guide testers or automated testing tools to perform test operations and verify that the system's behavior and output are as expected under specific conditions. Furthermore, the use case content can usually include the following elements: use case name: concisely and clearly describe the function or scenario of the test; preconditions: describe the prerequisites or environmental requirements before the test is executed to ensure the executability of the test; input data: specify Input data or parameters used during testing, including data types, value ranges, boundary conditions, etc.; use case steps: specific test steps and operations, including user interface operations, interface calls, data input, etc., to ensure test repeatability ; Expected result: The expected output, state, or behavior of the system after performing a test step, usually an expected response or effect; Verification point: The specific standard or condition used to verify the expected result, usually by comparing the actual result with the expected result The results are used to determine whether the test passes; post-conditions: describe the expected state or cleanup operation after the test is executed to ensure the recovery of the test environment or the executability of the next test case. The test case content must be clear, accurate and repeatable to ensure the consistency and effectiveness of the test. It is the core document of testing work and is used to plan, execute and track the testing process, help discover system defects and problems, and verify whether the system meets expected requirements and quality standards.

Among them, the environment parameter information of the target environment refers to the identity information used to characterize which environment the target environment belongs to. Through this environment parameter information, a unique and certain environment can be defined, thereby determining the target environment of this cross-environment execution use case.

For example, the above-mentioned current environment and target environment may be any one of a test environment, a pre-release environment, and a production environment respectively. Moreover, the current environment and the target environment may be the same or different, and are not limited in this embodiment.

Step 204: Obtain corresponding token information according to the environment parameter information of the target environment.

Among them, the token information can be Token, which is essentially a data structure representing identity, permissions or access credentials. It is a means used during authentication and authorization processes to verify a user's identity and grant appropriate permissions or access to resources. Typically, a Token is a string, which can be a randomly generated string of characters, or encrypted or signed data. The nature of a token depends on the context in which it is used and how it is implemented. For example, in authentication, Token is used to verify the user's identity information. When a user logs in or authenticates, the system generates a Token and returns it to the user. The user carries this Token as an identity credential in subsequent requests to prove his legal identity; in authorization and access control, Token is used to grant users specific permissions or access rights. The system generates the corresponding Token based on the user's identity and permissions, verifies the validity and permissions of the Token when the user requests resources, and decides whether to allow access.

The advantages of Token include: statelessness, scalability and security. Optionally, statelessness means that the Token itself contains the user's identity and permission information. In some embodiments, the server does not need to maintain session state, allowing the system to implement stateless distributed authentication and authorization; scalability It means that the Token can contain customized data fields. In some embodiments, additional information can be added as needed to meet specific business needs and expand the application scope of the cross-environment execution use case method; security means that through appropriate The encryption and signature mechanism can ensure the security of Token, prevent it from being tampered with or forged, and provide security guarantee for cross-environment execution of use cases.

For example, when a use case needs to be executed across environments, the use case can be written through the terminal 102, or a completed use case can be called, and the environment parameters of the above-mentioned target environment can be obtained at the same time. Based on the acquired environment parameter information of the target environment, a request is made to the server. At this time, the server will generate token information corresponding to the target environment based on the environment parameter information and return it to the terminal, and the terminal will complete the storage of the token information. .

Step 206: Construct cross-environment configuration information based on the token information, where the cross-environment configuration information is used for identification by the interface gateway of the target environment.

Among them, the cross-environment configuration information can be header information (Header), which is a mechanism for transmitting additional information in HTTP requests or responses. It consists of key-value pairs and is used to carry metadata in HTTP messages and describe the message. The properties, format and other relevant information of the document. The header information is located in the header part of the HTTP message, located after the request line or response line, and is expressed in the form of key-value pairs. In some embodiments, the above-mentioned header information may be request header information or response header information, etc. The request header information refers to the HTTP request and is used to provide additional information about the client or the request. Common request header information includes User-Agent (user agent), Content-Type (content type), Authorization (authorization information), etc.; response header information refers to the HTTP response and is used to provide additional information about the response. Common response header information includes Content-Type (content type), Content-Length (content length), Set-Cookie (set cookie), etc.

Further, in the system architecture, requests entering the system are routed and identified through the interface gateway. As the entry point of the system, the interface gateway is responsible for receiving requests and forwarding the requests to the corresponding services or back-end systems according to predefined rules. The above-mentioned cross-environment configuration information is constructed based on the token information corresponding to the target environment. Therefore, the interface gateway of the target environment can identify the above-mentioned cross-environment configuration information, thereby adjusting the interface of the target environment.

Step 208: Generate a cross-environment use case based on the use case content and cross-environment configuration information, and synchronize the cross-environment use case to the target environment to execute the cross-environment use case in the target environment.

The above use case content exists in the current environment, and the cross-environment use case generated based on the above-mentioned cross-environment configuration information has the characteristics of being able to adjust the target environment interface. Therefore, the cross-environment use case generated based on the above-mentioned use case content and cross-environment configuration information, It can directly synchronize to the target environment, call the data of the target environment through the interface of the target environment, and execute cross-environment use cases that contain the use case content written in the current environment, thereby completing the operation of cross-environment execution of use cases.

In the above method of executing use cases across environments, the corresponding token information can be obtained through the environment parameter information of the target environment, thereby completing the construction of cross-environment configuration information. When executing a use case across environments, it is necessary to ensure that the interface gateway of the target environment can identify the relevant information for executing the use case. At this time, the above cross-environment configuration information can be identified by the interface gateway of the target environment, so as to adjust the interface and generate the information that can be used in the target environment. Cross-environment use cases executed in the environment, thereby completing the process of cross-environment execution of use cases. By adopting the above technical solution, use cases written in one environment can be executed in multiple different environments, calling the interfaces of different environments to obtain data, simplifying the process of testing in different environments during the application development process, and avoiding the need for Repeated writing of use cases occurs in different environments, which improves application development efficiency. Furthermore, the above-mentioned cross-environment configuration information can be constructed in real time when cross-environment calls are needed, and the required token information can be obtained in real time, thus ensuring the validity of the token information and greatly reducing the maintenance of the token information. Cost, and avoids the occurrence of invalidation of manually maintained token information, eliminates the interference of token information invalidation, and makes it easier to locate the cause of errors during use case execution. In addition, using instant access to token information to complete the construction of cross-environment configuration information avoids third-party access and can also improve the security and stability of application development.

In one embodiment, as shown in Figure 3, the above use case content includes the environment parameter information of the current environment. The above step 204 to obtain the corresponding token information according to the environment parameter information of the target environment includes:

Step 302: Compare the values indicated by the environment parameter information corresponding to the current environment and the target environment.

Among them, the numerical values indicated by the environmental parameter information corresponding to different environments are different. In some embodiments, different environments are sorted according to their importance in the application development stage, and the numerical values indicated by the corresponding environmental parameter information increase sequentially. Large, that is, the higher the importance of the environment, the larger the corresponding value.

For example, in one embodiment, the above-mentioned current environment and target environment are any one of a test environment, a pre-release environment, and a production environment respectively.

Among them, the test environment is the environment used for software testing. It is typically an environment set up within a development team or within a dedicated testing team. The purpose of the test environment is to simulate the hardware, software and network environment in the production environment and provide conditions similar to the production environment for system testing, integration testing, performance testing, regression testing, etc. The testing environment can be used to discover and repair defects in software, verify whether functions meet requirements, evaluate system performance, etc. A pre-release environment is the environment where software is verified and tested for the last time before release. It is used to simulate the final production environment and conduct final functional verification, performance testing, security audits, etc. The purpose of the pre-release environment is to ensure that the software is stable, reliable and meets expectations before being released to the production environment. In a pre-release environment, final tweaks and fixes can be made, and user acceptance testing can be conducted to ensure that the software will function properly in a production environment. The production environment is the actual running environment of the software, also known as the online environment or formal environment. It is the end-user facing environment used to provide actual services and functionality. The production environment has high availability, high performance and security requirements, and the stable operation of the software system must be ensured. In a production environment, software is thoroughly tested, validated, and deployed to meet user needs and support business operations. Therefore, an important essential difference in executing use cases in different environments is that the data sources used in executing use cases are different. For example, the data in the test environment may be written or created by the development team, and the expectations of the test are often known in advance. As a result, the data in the production environment is data that is directly facing users, real and changing in real time.

Therefore, by sorting according to the degree of importance, the value indicated by the environment parameter information of the test environment is the smallest, the value indicated by the environment parameter information of the production environment is the largest, and the value corresponding to the pre-release environment is greater than the value corresponding to the test environment. , smaller than the value corresponding to the production environment.

If use cases in a lower importance environment are executed in a higher importance environment, for example, if the use case contents of the test environment use cases are executed in the production environment, the following problems may arise: First, the test cases in the test environment may have an impact on the production environment. Modification, deletion or creation of data in the environment will lead to inconsistency or confusion in the production environment data, causing data pollution; secondly, the test environment usually does not have the same security measures and permission restrictions as the production environment; thirdly, if the use cases of the test environment Access to sensitive data in the production environment may cause security risks, lead to data leakage or malicious use, and pose security risks.

Therefore, by comparing the values indicated by the environment parameter information corresponding to the current environment and the test environment, the importance of the current environment and the target environment can be known, so as to avoid the use cases of the environment with a lower degree of importance over the data of the environment with a higher degree of importance. A call was made.

Step 304: If the value indicated by the environment parameter information of the current environment is greater than or equal to the value indicated by the environment parameter information of the target environment, obtain token information corresponding to the target environment.

For example, based on the aforementioned judgment of the importance of different environments, the current environment is a pre-release environment and the target environment is a test environment, because the value indicated by the environment parameter information of the pre-release environment is greater than the value indicated by the environment parameter information of the test environment. , Therefore, it is determined that cross-environment execution of the use case in this case will not cause the above problems, and you can continue to obtain the token information corresponding to the target environment and continue to perform subsequent steps.

If the current environment is a test environment and the target environment is a production environment, it is judged that the above problems will exist. At this time, you can prohibit further acquisition of token information corresponding to the target environment and perform error processing.

By prohibiting the test environment from calling data from the production environment, the above solution can ensure that operations during the test process will not affect the data integrity and consistency of the production environment, maintain data isolation, and reduce security risks. The test environment cannot access the production environment. Sensitive data in the environment can avoid leaking sensitive information and suffering potential security attacks, ensuring the stability of the production environment and the reliability of data.

Optionally, in one embodiment, as shown in Figure 4, the above step 304 may include:

Step 402: If the value indicated by the environment parameter information of the current environment is equal to the value indicated by the environment parameter information of the target environment, directly obtain the token information corresponding to the target environment in the first calling method.

Among them, since the value indicated by the environment parameter information of the current environment is equal to the value indicated by the environment parameter information of the target environment, the current environment and the target environment are the same environment, and the corresponding token information can be directly obtained at this time. For example, the above-mentioned first calling method may be a generalized calling.

Optionally, generalized calling refers to using generics in programming to implement a common calling method, so that the code can be reused and generalized on different types. The purpose of generalized calling is to improve code reusability and flexibility. In traditional programming languages, functions or methods are usually defined and implemented for specific data types. For example, a function might accept integers as parameters and return a result of type integer. In this case, if you want to use the same function on different data types, you need to define a separate function for each data type. This will lead to code redundancy and reduced maintainability. Using generalized calls can solve this problem. Generalized calls define functions or methods using generics so that they can be applied to different data types. Generics are an abstract data type that can specify specific types during programming. By using generic parameters in the definition of a function or method, you can defer determining the specific data type until the time the function or method is called.

Therefore, using generalized calls can bring the following benefits: it can make the code reusable on different data types, reduce the duplication of code, and improve the maintainability of the code; it can be more flexibly adapted to different data types. and requirements, making the code more versatile; the compiler can perform type checking to ensure that the specific type used during the call matches the generic parameter, thus improving the type safety of the code. To sum up, by using generalized calling to obtain token information, there is no need to worry about the version upgrade of the interface, and it has higher calling efficiency and stability.

Furthermore, the above generalized calling method can be called by Dubbo. Optionally, Dubbo calling refers to the method of using interfaces to make remote calls in the Dubbo framework, which requires the service provider and service consumer to share the same interface definition. This calling method is based on static type checking and compilation of interfaces, and has high performance and efficiency.

Step 404: When the value indicated by the environment parameter information of the current environment is greater than the value indicated by the environment parameter information of the target environment, obtain the interface gateway proxy address of the target environment, and use the first calling method according to the interface gateway proxy address. Get the token information corresponding to the target environment.

Optionally, the interface gateway proxy address of the target environment refers to the gateway proxy address of the platform itself using this method. For example, in this embodiment, the platform using this method is an interface automation platform, then the interface gateway proxy address of the target environment is It refers to the interface gateway proxy address of the interface automation platform's own service. Therefore, in this embodiment, the gateway address of the interface for obtaining token information is not directly called, thereby avoiding the problem of heavy pressure on the gateway caused by too large a call volume.

Among them, the value indicated by the environment parameter information of the current environment is greater than the value indicated by the environment parameter information of the target environment. At this time, the current environment is different from the target environment, and the above-mentioned cross-environment execution use case problem does not occur. Cross-environment calls first need to obtain the interface gateway address of the target environment. For example, HttpClient can be used to obtain the interface gateway address of the target environment. For example, the acquisition process usually includes: initializing HttpClient, building a request object, sending a pre-request, parsing the response of the pre-request, updating the URL of the request object, and finally sending the actual request, etc. The specific implementation steps depend on the HttpClient library and framework used. In actual development, you need to obtain more detailed guidance and specific implementation methods according to the documentation and examples of HttpClient, and perform corresponding configuration and operations according to the requirements of the library.

Further, the first calling method may be a generalized calling, which is the same as the explanation in step 402 above, and will not be described again here. In addition, in some embodiments, a second calling method can also be used to obtain the token information. For example, the second calling method can be a dynamic proxy call, a RESTful call, a gRPC call, etc.

In one embodiment, as shown in Figure 5, step 206, building cross-environment configuration information based on the token information includes:

Step 502: Obtain the header information of the use case content.

Among them, header information is a mechanism for transmitting additional information in HTTP requests or responses. It consists of key-value pairs and is used to carry metadata in HTTP messages. It describes the attributes, format and other related information of the message. The header information is located in the header part of the HTTP message, located after the request line or response line, and is expressed in the form of key-value pairs. For example, the above-mentioned header information may be request header information, which is used to provide additional information about the client or the request in an HTTP request.

Step 504: Splice the token information into the header information to construct cross-environment configuration information.

Optionally, splice the token information into the header information, which can be used for authentication to access the target environment.

In one embodiment, step 202, before obtaining the corresponding token information according to the environment parameter information of the target environment, also includes:

First, execute the use case content to obtain the result log.

When this step executes the use case content, cross-environment actions have not yet started. When executing the use case content in the current environment, the current use case can be tested and verified first.

Among them, the result log refers to the log information that records and stores the operation results during the software development or system operation process. It records the results, status and related information of program execution for subsequent analysis, troubleshooting or performance optimization purposes. Result logs usually include operation results, operation-related information, status changes, exception information, performance indicators and other information.

For example, the above use case content may include one or more use case steps. When executing the use case, the relevant information of the use case steps is first obtained, and the parameters and global parameters extracted from each step are placed in the use case context to ensure that the use case is executed. Each step can reference the extracted parameters, and then store the identity information of the step node in the stack, so that after each step is executed, the following steps are taken out, and each step is allocated through the step type loaded by the container initialization during execution. To the corresponding executor, such as the executor of the http interface, the executor of assertion, the executor of parameter extraction, etc., the executor type information of the execution step needs to be assigned by the scheduler to the corresponding executor (such as the execution of the above http interface executor, assertion executor, parameter extraction executor), when a step node is executed, the next node of the stack is changed to the current node, and the next node is changed to the next node, similar to changing the linked list pointer address so that Just follow the transfer step.

Second, verify that the resulting logs meet preset criteria.

Verification of the above result logs can reflect issues such as whether the use cases written in the current environment are accurate and ensure the security and accuracy of subsequent cross-environment execution of use cases.

Finally, when the result log meets the preset standards, the step of obtaining the corresponding token information based on the environment parameter information of the target environment is performed.

In this embodiment, by executing the test on the use cases in the current environment and verifying the result logs, it can reflect issues such as whether the use cases in the current environment are written accurately and ensure the safety and accuracy of subsequent cross-environment execution of use cases. Sex provides protection.

In one embodiment, as shown in Figures 6 and 7, the execution subjects of the above steps are divided into use case server 602, use case executor 604, step scheduler 606, http step executor 608, login authentication processor 610 and Dubbo Service processor 612. And the above execution subjects are distributed in the data layer 702, business layer 704, presentation layer 706 and operation layer 708.

The business layer 704 includes a data driver sub-level 7041, a scenario use sub-level 7042, a test plan sub-level 7043, a test result sub-level 7044 and a logging sub-level 7045. Among them, the initialization operations of data design and test scenario design are completed in the data-driven sub-level 7041, and parameters input at each stage are received; the creation of use cases and scenarios, the import and call of interfaces, and execution status are completed in the scenario use sub-level 7042. settings (including scheduled execution, manual execution) and other operations to execute the use case; complete the creation of the test plan at the test plan sub-level 7043, associate different scenarios with each other, configure the interface calling method and scheduled task status, and execute the test plan ; In the test result sub-level 7044, the execution results of the test plan are displayed and corresponding notifications are sent to the terminal; in the logging sub-level 7045, the operation record of the above process is completed. The following is the specific execution process at each level:

After the use case is created in the business layer 704, the use case server 602 executes data caching, storage, calling custom functions and database read and write instructions in the data layer 702, and persists the information in the use case content to the database, where , The use case content includes specific steps, input data, expected results, verification points and other information for testing the application, terminal and server interfaces.

Among them, the creation and execution process of use cases are as follows:

The use case server 602 obtains data such as global parameters and use case step parameters in the data-driven sub-level 7041 of the business layer 704, and completes the design of pre-data based on the obtained data, thereby completing the design of the test scenario; the use case executor 604 operates in the scenario Create a use case in the current environment in use case level 7042 and execute the use case.

Among them, the executed use case content can include one or more use case steps. When executing the use case, the relevant information of the use case steps is first obtained, and the parameters and global parameters extracted from each step are placed in the use case context to ensure that the use case is executed. At this time, each step can reference the extracted parameters, and then store the identity information of the step node in the stack, so that the following steps can be taken out after each step is completed. When each step is executed, the step type loaded by the step scheduler 606 through container initialization is assigned to the corresponding executor, such as the executor of the http interface, the executor of assertions, the executor of parameter extraction, etc. The executor type information of the execution step needs to be allocated to the corresponding executor by the scheduler. When a step node is executed, the next node of the stack is changed to the current node, and the next node is changed to the next node, similar to changing a linked list. Pointer address to facilitate flow steps.

Subsequently, multiple use cases are related to each other in the test technology sub-level to form and execute a complete test plan; in the test result sub-level 7044, the result log in the current environment is generated and verified whether the result log meets the preset standards. For the above Verification of the result log can reflect issues such as whether the use case writing in the current environment is accurate, and provide guarantees for the security and accuracy of subsequent cross-environment execution of use cases.

Next, when the result log meets the preset standards, the use case server 602 obtains the environment parameter information of the target environment at the data-driven sub-level 7041 of the business layer 704, and defines the only determined environment through the environment parameter information, thereby determining The target environment of this cross-environment execution use case. When the use case needs to be executed across environments, the environment parameters of the above-mentioned target environment are obtained at the same time. The login authentication processor 610 compares the values indicated by the environment parameter information corresponding to the current environment and the target environment, and If the current environment is a test environment and the target environment is a production environment, it is prohibited to continue to obtain the token information corresponding to the target environment and perform error processing; if the current environment is a pre-release environment and the target environment is a test environment, Dubbo The service processor 612 obtains the interface gateway proxy address of the test environment, and obtains token information corresponding to the test environment by calling Dubbo based on the interface gateway proxy address.

Subsequently, the http step executor 608 obtains the header information of the above-mentioned verified use case in the scenario use sub-level 7042 of the business layer 704, and splices the above-mentioned token information into the header information to construct a program that can be recognized by the target environment interface. Cross-environment configuration information, and then generate a cross-environment use case based on the use case content of the above use case and the cross-environment configuration information obtained by splicing. Optionally, in some embodiments, in the http step executor 608, you can choose to splice the token information obtained through the above process into the header information to construct cross-environment configuration information, or you can choose to obtain the token information through other methods. , to construct new header information.

When you need to execute a use case across environments, you only need to change the account in the authentication method to the account in the target environment. In the scenario use case level 7042 of the business layer 704, the interface of the target environment can be called through the above cross-environment configuration information, thereby synchronizing the cross-environment use case to the target environment, and then referring to the above-mentioned process of executing the current environment use case, in the target environment Execute the cross-environment use case, combine multiple use cases into a use case set, refer to the use case set to form a test plan, and execute the test plan.

Finally, in the presentation layer 706, the execution results of the test technology are output as a report. The operation layer 708 provides an extensible platform for building, testing, and deploying software projects. The above processes are all deployed on the integration tool of the operation layer 708. For example, the integration tool can be Jenkins, which is used to configure scheduled tasks. , perform interface scheduling, etc.

In addition, the execution subjects of each of the above steps have been processed by load balancing, and starting from the internal cluster, they complete the required functional services through data calls with the external functional service cluster, such as: interface services, general services, scene services, directories services, tracking log services, change record services, test plan services, and parameter pool services; and perform data calls through microservice clusters, registration centers, and external business service clusters to complete various required business services, such as: pressure platform business services , authorized data shielding query service, general ordering service, general message sending service, real-time ordering service, and public timeline service.

It should be understood that although the steps in the flowcharts involved in the above-mentioned embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated in this article, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least some of the steps in the flowcharts involved in the above embodiments may include multiple steps or stages. These steps or stages are not necessarily executed at the same time, but may be completed at different times. The execution order of these steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

Based on the same inventive concept, embodiments of the present application also provide a device for cross-environment execution of use cases for implementing the above-mentioned method of cross-environment execution of use cases. The problem-solving solution provided by this device is similar to the solution recorded in the above method. Therefore, for the specific limitations in the device embodiments of one or more cross-environment execution use cases provided below, please refer to the cross-environment execution above. The limitations of the use case method will not be repeated here.

In one embodiment, as shown in Figure 8, a device for executing use cases across environments is provided, including: a use case acquisition module, a token generation module, an environment configuration module and a use case synchronization module, wherein:

The use case acquisition module 802 is used to obtain the use case content and the environment parameter information of the target environment in the current environment;

The token generation module 804 is used to obtain corresponding token information according to the environmental parameter information of the target environment;

The environment configuration module 806 is used to construct cross-environment configuration information based on the token information, where the cross-environment configuration information is used for identification by the interface gateway of the target environment;

The use case synchronization module 808 is used to generate cross-environment use cases based on the use case content and cross-environment configuration information, and synchronize the cross-environment use cases to the target environment to execute the cross-environment use cases in the target environment.

In one embodiment, the use case content includes the environment parameter information of the current environment. The environment parameter information corresponding to different environments indicates different values, and the above-mentioned token generation module includes a parameter comparison sub-module and an authentication execution sub-module, where:

The parameter comparison submodule is used to compare the values indicated by the environment parameter information corresponding to the current environment and the target environment;

The authentication execution submodule is used to obtain token information corresponding to the target environment when the value indicated by the environment parameter information of the current environment is greater than or equal to the value indicated by the environment parameter information of the target environment.

In one embodiment, the above authentication execution sub-module includes a direct calling unit and an indirect calling unit, where:

A direct calling unit, configured to directly obtain the token information corresponding to the target environment in the first calling method when the value indicated by the environment parameter information of the current environment is equal to the value indicated by the environment parameter information of the target environment;

The indirect calling unit is used to obtain the interface gateway proxy address of the target environment when the value indicated by the environment parameter information of the current environment is greater than the value indicated by the environment parameter information of the target environment, and based on the interface gateway proxy address, the third One call method to obtain the token information corresponding to the target environment.

In one embodiment, the above-mentioned first calling method is a generalized calling.

In one embodiment, the above-mentioned environment configuration module includes an initial module and a configuration module, where:

Initial module, used to obtain the header information of the use case content;

The configuration module is used to splice token information into header information to build cross-environment configuration information.

In one embodiment, the above-mentioned device for executing use cases across environments further includes:

Test module, used to execute the use case content to obtain result logs;

Verification module, used to verify whether the result log meets the preset standards;

The execution module is used to obtain the corresponding token information based on the environment parameter information of the target environment when the result log meets the preset standards.

Each module in the above-mentioned device for executing use cases across environments can be implemented in whole or in part by software, hardware, and combinations thereof. Each of the above modules may be embedded in or independent of the processor of the computer device in the form of hardware, or may be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in Figure 9. The computer device includes a processor, a memory, an input/output interface (Input/Output, referred to as I/O), and a communication interface. Among them, the processor, memory and input/output interface are connected through the system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes non-volatile storage media and internal memory. The non-volatile storage medium stores operating systems, computer programs and databases. This internal memory provides an environment for the execution of operating systems and computer programs in non-volatile storage media. The computer device's database is used to store use case related data. The input/output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with an external terminal through a network connection. The computer program is executed by the processor to implement a method of executing use cases across environments.

In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. 10 . The computer device includes a processor, memory, input/output interface, communication interface, display unit and input device. Among them, the processor, memory and input/output interface are connected through the system bus, and the communication interface, display unit and input device are connected to the system bus through the input/output interface. Wherein, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes non-volatile storage media and internal memory. The non-volatile storage medium stores operating systems and computer programs. This internal memory provides an environment for the execution of operating systems and computer programs in non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used for wired or wireless communication with external terminals. The wireless mode can be implemented through WIFI, mobile cellular network, NFC (Near Field Communication) or other technologies. The computer program is executed by the processor to implement a method of executing use cases across environments.

Those skilled in the art can understand that the structure shown in Figure 10 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied. Specific computer equipment can May include more or fewer parts than shown, or combine certain parts, or have a different arrangement of parts.

In one embodiment, a computer device is provided, including a memory and a processor. A computer program is stored in the memory. When the processor executes the computer program, it implements the following steps: in the current environment, obtain the use case content and the environment of the target environment. Parameter information; obtain the corresponding token information based on the environment parameter information of the target environment; construct cross-environment configuration information based on the token information, where the cross-environment configuration information is used for identification by the interface gateway of the target environment; based on the use case content and cross-environment configuration The information generates cross-environment use cases and synchronizes the cross-environment use cases to the target environment to execute the cross-environment use cases in the target environment.

In one embodiment, the processor also implements the following steps when executing the computer program: comparing the values indicated by the environment parameter information corresponding to the current environment and the target environment; when the value indicated by the environment parameter information of the current environment is greater than or equal to that of the target environment If the value indicated by the environment parameter information is obtained, the token information corresponding to the target environment is obtained.

In one embodiment, when the processor executes the computer program, the processor also implements the following steps: when the value indicated by the environment parameter information of the current environment is equal to the value indicated by the environment parameter information of the target environment, obtain directly by the first calling method Token information corresponding to the target environment; when the value indicated by the environment parameter information of the current environment is greater than the value indicated by the environment parameter information of the target environment, the interface gateway proxy address of the target environment is obtained, and the interface gateway proxy address is obtained according to the interface gateway proxy Address, use the first calling method to obtain the token information corresponding to the target environment.

In one embodiment, when the processor executes the computer program, the following steps are also implemented: obtaining the header information of the use case content; and splicing the token information into the header information to construct cross-environment configuration information.

In one embodiment, when the processor executes the computer program, it also implements the following steps: execute the use case content to obtain a result log; verify whether the result log meets the preset standards; when the result log meets the preset standards, execute the test according to the target environment Steps to obtain the corresponding token information based on the environment parameter information.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented: in the current environment, obtain the use case content and the environment parameter information of the target environment; Obtain the corresponding token information based on the environment parameter information of the target environment; construct cross-environment configuration information based on the token information, where the cross-environment configuration information is used for identification by the interface gateway of the target environment; generate cross-environment configuration information based on the use case content and cross-environment configuration information. environment use cases, and synchronize the cross-environment use cases to the target environment to execute the cross-environment use cases in the target environment.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: comparing the values indicated by the environment parameter information corresponding to the current environment and the target environment; when the value indicated by the environment parameter information of the current environment is greater than or equal to the target environment If the value indicated by the environment parameter information is obtained, the token information corresponding to the target environment is obtained.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: when the value indicated by the environment parameter information of the current environment is equal to the value indicated by the environment parameter information of the target environment, directly using the first calling method Obtain the token information corresponding to the target environment; when the value indicated by the environment parameter information of the current environment is greater than the value indicated by the environment parameter information of the target environment, obtain the interface gateway proxy address of the target environment, and based on the interface gateway The proxy address is used to obtain the token information corresponding to the target environment in the first calling method.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: obtaining header information of the use case content; and splicing token information into the header information to construct cross-environment configuration information.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: execute the use case content to obtain a result log; verify whether the result log meets the preset standards; when the result log meets the preset standards, execute the Steps to obtain the corresponding token information from the environment parameter information.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage. In the medium, when the computer program is executed, it may include the processes of the embodiments of the above methods. Any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive memory (ReRAM), magnetic variable memory (Magnetoresistive Random) Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (PCM), graphene memory, etc. Volatile memory may include random access memory (Random Access Memory, RAM) or external cache memory. By way of illustration but not limitation, RAM can be in various forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM). The databases involved in the various embodiments provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include blockchain-based distributed databases, etc., but are not limited thereto. The processors involved in the various embodiments provided in this application may be general-purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to this.

The technical features of the above embodiments can be combined in any way. To simplify the description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, all possible combinations should be used. It is considered to be within the scope of this manual.

The above-described embodiments only express several implementation modes of the present application, and their descriptions are relatively specific and detailed, but should not be construed as limiting the patent scope of the present application. It should be noted that, for those of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all fall within the protection scope of the present application. Therefore, the scope of protection of this application should be determined by the appended claims.

Claims (10)

1. A method of cross-environment execution of use cases, the method comprising the steps of:

under the current environment, acquiring use case content and environment parameter information of a target environment, wherein the environment parameter information of the target environment is identity information used for representing the target environment, the use case content comprises the environment parameter information of the current environment, and the values indicated by the environment parameter information corresponding to different environments are different; according to the importance degree of the environment in the application program development stage, order relation exists among different environments, and the larger the importance degree is, the larger the value indicated by the environment parameter information corresponding to the environment is;

Acquiring corresponding token information according to the environment parameter information of the target environment;

constructing cross-environment configuration information according to the token information, wherein the cross-environment configuration information is used for being identified by an interface gateway of the target environment;

generating a cross-environment use case according to the use case content and the cross-environment configuration information, and synchronizing the cross-environment use case to the target environment so as to execute the cross-environment use case in the target environment;

the constructing cross-environment configuration information according to the token information comprises the following steps:

acquiring header information of the use case content;

the token information is spliced into the header information to construct cross-environment configuration information.

2. The method of cross-environment execution use case according to claim 1, wherein the obtaining corresponding token information according to the environment parameter information of the target environment includes:

comparing the values indicated by the environment parameter information corresponding to the current environment and the target environment;

and acquiring token information corresponding to the target environment under the condition that the value indicated by the environment parameter information of the current environment is larger than or equal to the value indicated by the environment parameter information of the target environment.

3. The method according to claim 2, wherein, in the case where the value indicated by the environment parameter information of the current environment is greater than or equal to the value indicated by the environment parameter information of the target environment, acquiring the token information corresponding to the target environment includes:

under the condition that the value indicated by the environment parameter information of the current environment is equal to the value indicated by the environment parameter information of the target environment, directly acquiring token information corresponding to the target environment in a first calling mode;

and under the condition that the value indicated by the environment parameter information of the current environment is larger than the value indicated by the environment parameter information of the target environment, acquiring an interface gateway proxy address of the target environment, and acquiring token information corresponding to the target environment in a first calling mode according to the interface gateway proxy address.

4. A method of cross-environment execution of use cases as recited in claim 3, wherein the first call manner is a generalized call.

5. The method of cross-environment execution use case according to claim 1, wherein before the obtaining the corresponding token information according to the environment parameter information of the target environment, further comprises:

Executing the use case content to obtain a result log;

verifying whether the result log meets a preset standard or not;

and executing the step of acquiring corresponding token information according to the environmental parameter information of the target environment under the condition that the result log accords with the preset standard.

6. The method of cross-environment execution use case of any one of claims 1 to 5, wherein the current environment and the target environment are any one of a test environment, a pre-release environment, and a production environment, respectively _。

7. An apparatus for cross-environment execution of use cases, the apparatus comprising:

the system comprises a use case acquisition module, a storage module and a storage module, wherein the use case acquisition module is used for acquiring use case content and environment parameter information of a target environment under a current environment, the environment parameter information of the target environment is identity information used for representing the target environment, the use case content comprises the environment parameter information of the current environment, and the values indicated by the environment parameter information corresponding to different environments are different; according to the importance degree of the environment in the application program development stage, order relation exists among different environments, and the larger the importance degree is, the larger the value indicated by the environment parameter information corresponding to the environment is;

The token generation module is used for acquiring corresponding token information according to the environment parameter information of the target environment;

the environment configuration module is used for constructing cross-environment configuration information according to the token information, wherein the cross-environment configuration information is used for being identified by an interface gateway of the target environment, and is also used for acquiring header information of the use case content and splicing the token information into the header information to construct the cross-environment configuration information;

and the use case synchronization module is used for generating a cross-environment use case according to the use case content and the cross-environment configuration information and synchronizing the cross-environment use case to the target environment so as to execute the cross-environment use case in the target environment.

8. The apparatus of cross-environment execution use case of claim 7, wherein the token generation module comprises:

the parameter comparison sub-module is used for comparing the numerical value indicated by the environment parameter information corresponding to the current environment and the target environment;

and the authentication execution sub-module is used for acquiring token information corresponding to the target environment when the value indicated by the environment parameter information of the current environment is greater than or equal to the value indicated by the environment parameter information of the target environment.

9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 6 when the computer program is executed.

10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.