CN116991713B - Method, device, computer equipment and storage medium for executing use cases across environments - Google Patents
Method, device, computer equipment and storage medium for executing use cases across environments Download PDFInfo
- Publication number
- CN116991713B CN116991713B CN202310870433.1A CN202310870433A CN116991713B CN 116991713 B CN116991713 B CN 116991713B CN 202310870433 A CN202310870433 A CN 202310870433A CN 116991713 B CN116991713 B CN 116991713B
- Authority
- CN
- China
- Prior art keywords
- environment
- use case
- cross
- information
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 69
- 238000003860 storage Methods 0.000 title claims abstract description 19
- 238000012360 testing method Methods 0.000 claims description 79
- 238000004519 manufacturing process Methods 0.000 claims description 26
- 238000004590 computer program Methods 0.000 claims description 25
- 230000007613 environmental effect Effects 0.000 claims description 10
- 238000011161 development Methods 0.000 abstract description 13
- 230000008569 process Effects 0.000 description 21
- 230000006870 function Effects 0.000 description 11
- 230000004044 response Effects 0.000 description 11
- 238000010586 diagram Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 8
- 238000012795 verification Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 5
- 238000013475 authorization Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 4
- 238000010276 construction Methods 0.000 description 4
- 238000013461 design Methods 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000000605 extraction Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000003068 static effect Effects 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 238000004904 shortening Methods 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000000739 chaotic effect Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000011056 performance test Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000013522 software testing Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application relates to a method, an apparatus, a computer device and a storage medium for executing use cases across environments. The method comprises the following steps: acquiring the environment parameter information of the use case content and the target environment in the current environment; 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; and 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. By adopting the method, the use cases can be executed across environments, so that the development period of the application program is shortened, the cost of writing the use cases is reduced, and the development efficiency is improved.
Description
Technical Field
The present invention relates to the field of computer applications, and in particular, to a method, an apparatus, a computer device, and a storage medium for executing use cases across environments.
Background
With development of application programs and development of testing technologies, at present, technicians test the application programs through a plurality of different environments, so that more comprehensive testing results are obtained, and the effect of the application programs after being on line is ensured to meet expectations. The test cases adopted in different environments are different and can not be mutually called, and the content of the case added, deleted or modified for a single environment only acts on one current environment, so that the cases of other environments are not affected. Therefore, if the test process under different environments is to be completed, the corresponding application case needs to be written under each environment, which results in high cost and low efficiency of writing the application case.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a method, an apparatus, a computer device, and a storage medium for executing use cases across environments, which can enable use cases to be executed across environments, thereby shortening the development cycle of an application program, reducing the cost of writing use cases, and improving the development efficiency.
In a first aspect, the present application provides a method of cross-environment execution of use cases. The method comprises the following steps:
acquiring the environment parameter information of the use case content and the target environment in the current environment;
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;
and 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.
In one embodiment, the use case content includes environment parameter information of a current environment, and values indicated by the environment parameter information corresponding to different environments are different; the obtaining the 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.
In one embodiment, the obtaining the token information corresponding to the target environment in a 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 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.
In one embodiment, the first call is a generalization call.
In one embodiment, the constructing cross-environment configuration information according to the token information includes:
acquiring 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 the obtaining the corresponding token information according to the environmental parameter information of the target environment, the method further includes:
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.
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 a second aspect, the present application further provides an apparatus for executing use cases across environments. The device comprises:
the use case acquisition module is used for acquiring the use case content and the environment parameter information of the target environment in the current environment;
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 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.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the steps of the first aspect when the processor executes the computer program.
In a fourth aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps as described in the first aspect.
According to the method, the device, the computer equipment and the storage medium for executing the use cases in the cross-environment mode, the corresponding token information can be obtained through the environment parameter information of the target environment, and therefore the construction of the cross-environment configuration information is completed. When the cross-environment execution use case is performed, the interface gateway of the target environment needs to be ensured to be capable of identifying the relevant information of the execution use case, at this time, the cross-environment configuration information can be used for the interface gateway of the target environment to identify, so that an interface is called, the cross-environment use case which can be executed in the target environment is generated, and the process of the cross-environment execution use case is completed. The cross-environment configuration information can be constructed in real time when cross-environment calling is needed, and the needed token information is acquired in real time, so that the validity of the token information is ensured, the maintenance cost of the token information is reduced to a great extent, the condition of failure of the manually maintained token information is avoided, the interference of the failure problem of the token information is eliminated, and the error reporting reason in the process of executing a user is easier to locate ， Thereby shortening the development period of the application program. Meanwhile, the cross-environment execution use cases can multiplex use cases in different environments, and the same use cases do not need to be written for different environments, becauseThe cost of writing the use cases can be reduced, and the development efficiency is improved.
Drawings
FIG. 1 is an application environment diagram of a method of cross-environment execution of use cases in one embodiment;
FIG. 2 is a flow diagram of a method of cross-environment execution of use cases in one embodiment;
FIG. 3 is a flow chart of step S204 in one embodiment;
FIG. 4 is a flowchart illustrating step S304 in one embodiment;
FIG. 5 is a flow chart of step S206 in one embodiment;
FIG. 6 is a diagram of a method of cross-environment execution of use cases in an embodiment;
FIG. 7 is an execution architecture diagram of a method of cross-environment execution use case in one embodiment;
FIG. 8 is a block diagram of an apparatus for cross-environment execution of use cases in one embodiment;
FIG. 9 is an internal block diagram of a computer device in one embodiment;
FIG. 10 is an internal block diagram of another computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
The method for executing the use case by the cross-environment embodiment of the application can be applied to an application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The data storage system may store data that the server 104 needs to process. The data storage system may be integrated on the server 104 or may be located on a cloud or other network server. The terminal 102 obtains the example content and the environment parameter information of the target environment, and then obtains the corresponding token information through the environment parameter information of the target environment, thereby completing the construction of the cross-environment configuration information. When the cross-environment execution use case is performed, the interface gateway of the target environment needs to be ensured to be capable of identifying the relevant information of the execution use case, at this time, the cross-environment configuration information can be used for the interface gateway of the target environment to identify, so that the interface is communicated, the cross-environment use case which can be executed in the target environment is generated, and the process of the cross-environment execution use case is completed. The terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices, etc. The server 104 may be implemented as a stand-alone server or as a server cluster of multiple servers.
In one embodiment, as shown in fig. 2, a cross-environment execution use case method is provided, and this embodiment is applied to a terminal for illustration by using the method, it is understood that the method may also be applied to a server, and may also be applied to a system including the terminal and the server, and implemented through interaction between the terminal and the server. In this embodiment, the method includes the steps of:
step 202, acquiring the environment parameter information of the use case content and the target environment in the current environment.
When the use case is executed across environments, the corresponding use case content originally exists in the current environment, and the environment can be the writing environment of the use case content; correspondingly, the target environment refers to an interface environment which needs to be called when the use case is executed across environments.
Wherein, the use case content refers to information describing the complete process of the test. Optionally, the use case content describes specific steps of testing the application, the interface between the terminal and the server, etc., inputting data, expected results, verification points, etc. It is used to guide a tester or an automated test tool to perform a test operation and to verify that the behavior and output of the system under specific conditions are in line with expectations. Further, use case content may generally include the following elements: case name: the function or scene of the test is briefly and clearly described; the pre-condition is as follows: describing preconditions or environmental requirements before test execution, ensuring the test's executability; input data: input data or parameters used in the test are designated, wherein the input data or parameters comprise data types, value ranges, boundary conditions and the like; the example steps are as follows: specific testing steps and operations comprise user interface operation, interface calling, data input and the like, so that the repeatability of the test is ensured; the expected results are: the output, state, or behavior of the desired system after performing the test steps is typically a desired response or effect; verification point: specific criteria or conditions for verifying the expected outcome are typically used to determine whether the test passes by comparing the actual outcome with the expected outcome; post conditions: describing expected states or cleaning operations after test execution, ensuring the recovery of the test environment or the executability of the next test case. The content of the test case has the characteristics of clarity, accuracy and repeatability, so as to ensure the consistency and effectiveness of the test. It is the core document of the testing effort to plan, execute and track the testing process, help discover defects and problems in the system, and verify if the system meets the expected requirements and quality criteria.
The environment parameter information of the target environment refers to identity information used for representing which environment the target environment belongs to, and the environment parameter information can be defined to the only one determined environment, so that the target environment of the cross-environment execution use case can be determined.
Illustratively, the current environment and the target environment described above may be any one of a test environment, a pre-release environment, and a production environment, respectively. And the current environment and the target environment may be the same or different, and are not limited in this embodiment.
And step 204, obtaining corresponding token information according to the environment parameter information of the target environment.
The Token information may be Token, which essentially is a data structure representing an identity, a right or an access credential. It is a way used in authentication and authorization processes to verify the identity of a user and grant corresponding rights or access to resources. Typically, token is a string of characters, either a randomly generated string of characters or encrypted or signed data. The nature of Token depends on the context and implementation in which it is used. For example, in authentication, token is used to authenticate the identity information of a user. When a user logs in or authenticates, the system generates a Token and returns it to the user. The user carries the Token as an identity credential in a subsequent request to prove the legal identity of the user; in authorization and access control, token is used to grant a user specific right or access rights. The system generates a corresponding Token according to the identity and the authority of the user, verifies the validity and the authority of the Token when the user requests the resource, and decides whether to allow the access.
Advantages of Token include: stateless, scalable, and secure. Optionally, stateless means that Token itself contains identity and rights information of the user, and in some embodiments, the server does not need to maintain session state, so that the system can implement stateless distributed authentication and authorization; expandability means that Token can contain custom data fields, in some embodiments, additional information can be added as required, thereby meeting specific business requirements and expanding the application universality of cross-environment execution case methods; the security refers to ensuring the security of Token through proper encryption and signature mechanisms, preventing falsification or counterfeiting, and providing security guarantee for cross-environment execution use cases.
Illustratively, when a case needs to be executed across environments, the case may be written by the terminal 102, or the written case may be invoked, while the environment parameters of the target environment are acquired. And sending a request to the server according to the acquired environment parameter information of the target environment, wherein the server generates token information corresponding to the target environment according to the environment parameter information and returns the token information to the terminal, and the terminal can finish storing the token information.
And 206, constructing cross-environment configuration information according to the token information, wherein the cross-environment configuration information is used for the interface gateway of the target environment to identify.
The cross-environment configuration information may be Header information (Header), which is a mechanism for transmitting additional information in an HTTP request or response, and is composed of key value pairs, and is used for carrying metadata in an HTTP message, and describing attributes, formats and other relevant information of the message. The Header information is located in the Header (Header) portion of the HTTP message, located after the request line or the response line, and is represented in the form of a key pair. In some embodiments, the header information may be request header information or response header information, where the request header information is used to provide additional information about the client or the request in the HTTP request. Common request header information includes User-Agent, content-Type, authorization, etc.; the response header information means that in the HTTP response, additional information about the response is provided. Common response header information includes Content-Type, content-Length, set-Cookie, and the like.
Further, in the system architecture, requests entering the system are routed and identified through the interface gateway. The interface gateway is used as an entry point of the system and is responsible for receiving the request and forwarding the request to a corresponding service or back-end system according to predefined rules. The cross-environment configuration information is constructed according to the token information corresponding to the target environment, so that the interface gateway of the target environment can identify the cross-environment configuration information, and the interface of the target environment is communicated.
Step 208, 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 use case content exists in the current environment, and the cross-environment use case generated according to the cross-environment configuration information has the characteristic of being capable of adjusting and communicating with the target environment interface, so that the cross-environment use case generated according to the use case content and the cross-environment configuration information can be directly synchronized to the target environment, and the data of the target environment is called through the interface of the target environment to execute the cross-environment use case containing the well-written use case content in the current environment, thereby completing the operation of executing the use case in the cross-environment.
In the method for executing the use case in the cross-environment mode, the corresponding token information can be acquired through the environment parameter information of the target environment, so that the construction of the cross-environment configuration information is completed. When the cross-environment execution use case is performed, the interface gateway of the target environment needs to be ensured to be capable of identifying the relevant information of the execution use case, at this time, the cross-environment configuration information can be used for the interface gateway of the target environment to identify, so that the interface is communicated, the cross-environment use case which can be executed in the target environment is generated, and the process of the cross-environment execution use case is completed. By adopting the technical scheme, the use cases written in one environment can be executed in a plurality of different environments, interfaces in different environments are called to take data, the process of testing different environments in the development process of the application program is simplified, the situation that the use cases are repeatedly written in different environments is avoided, and the development efficiency of the application program is improved. Furthermore, the cross-environment configuration information can be constructed in real time when cross-environment calling is needed, and the needed token information is acquired in real time, so that the validity of the token information is ensured, the maintenance cost of the token information is reduced to a great extent, the condition that the manually maintained token information fails is avoided, the interference of the problem of failure of the token information is eliminated, and the error reporting reason in the process of executing the user is easier to locate. In addition, the method of instantly obtaining the token information is used for completing construction of cross-environment configuration information, access of a third party is avoided, and safety and stability of application program development can be improved.
In one embodiment, as shown in fig. 3, the use case content includes environment parameter information of the current environment, and the step 204 of obtaining the corresponding token information according to the environment parameter information of the target environment includes:
step 302, comparing the values indicated by the environmental parameter information corresponding to the current environment and the target environment.
In some embodiments, the different environments are ordered in sequence according to their importance degrees in the application program development stage, and the values indicated by the corresponding environment parameter information are sequentially increased, that is, the higher the importance degree is, the larger the corresponding value is.
Illustratively, in one embodiment, the current environment and the target environment described above are any one of a test environment, a pre-release environment, and a production environment, respectively.
The test environment is an environment for performing software testing. It is typically an environment set up inside a development team or in a specialized test team. The purpose of the test environment is to simulate hardware, software and network environments in the production environment and to provide similar conditions to the production environment for system testing, integration testing, performance testing, regression testing, etc. The test environment may be used to discover and repair defects in the software, verify that the functionality meets requirements, evaluate system performance, and the like. The pre-release environment is an environment in which verification and testing are performed last time before the software is released. The method is used for simulating a final production environment, performing final function verification, performance test, security audit and the like, and ensuring that software is stable, reliable and expected before being released to the production environment. In the pre-release environment, final adjustment and repair can be performed, and user acceptance testing can be performed to ensure that software can run normally in the production environment. The production environment is the actual running environment of the software, also known as an online environment or formal environment. It is an end-user oriented environment for providing actual services and functions. The production environment has the requirements of high availability, high performance and safety, and the stable operation of the software system must be ensured. In a production environment, software is comprehensively tested, verified and deployed to meet user requirements and support business operation. Thus, an important essential difference in executing use cases in different environments is that the sources of data used in executing use cases are different, e.g., the data of a test environment may be written or created by a development team and often knows the expected results of the test in advance, while the data of a production environment is data that is directly user-oriented, real and changing in real time.
Therefore, the ranking is performed according to the importance degree, the obtained environment parameter information of the test environment indicates the smallest value, the environment parameter information of the production environment indicates the largest value, and the pre-release environment corresponds to a value larger than the test environment and smaller than the production environment.
If the use case in the environment with low importance is executed in the environment with high importance, for example, the use case content of the use case in the test environment is executed in the production environment, the following problems may occur: firstly, the test cases of the test environment may modify, delete or create the data in the production environment, which results in inconsistent or chaotic data of the production environment and causes data pollution; second, the test environment is typically not provided with the same security measures and rights restrictions as the production environment; again, if the use case of the test environment can access sensitive data of the production environment, security risks may be raised, resulting in data leakage or malicious use, and potential safety hazards exist.
Therefore, the importance degree of the current environment and the target environment can be obtained by comparing the values indicated by the environment parameter information corresponding to the current environment and the test environment, and the use cases of the environments with smaller importance degree can be prevented from calling the data of the environments with higher importance degree.
Step 304, obtaining 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.
Illustratively, according to the foregoing importance judgment on different environments, the current environment is a pre-release environment, the target environment is a test environment, and since 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, it is determined that the cross-environment execution use case in this case will not cause the foregoing problem, it is possible to continue to acquire the token information corresponding to the target environment and to continue to execute the subsequent steps.
If the current environment is a test environment and the target environment is a production environment, the above problems are judged to exist, and the token information corresponding to the target environment can be forbidden to be continuously acquired and error reporting processing can be performed.
According to the scheme, the data of the production environment is forbidden to be called by the test environment, so that the operation in the test process can not influence the data integrity and consistency of the production environment, the data isolation can be kept, the safety risk can be reduced, the test environment can not access the sensitive data in the production environment, the leakage of sensitive information and the potential safety attack can be avoided, and the stability of the production environment and the reliability of the data are ensured.
Optionally, in one embodiment, as shown in fig. 4, the step 304 may include:
in step 402, in the case that the value indicated by the environmental parameter information of the current environment is equal to the value indicated by the environmental parameter information of the target environment, the token information corresponding to the target environment is directly acquired in the first calling mode.
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, and the current environment and the target environment are the same environment, so that the corresponding token information can be directly obtained. Illustratively, the first call manner described above may be a generalized call.
Alternatively, generalization call refers to using generalization in programming to implement a generic call approach so that code can be reused and generalized across different types. The purpose of generalization calls is to improve code reusability and flexibility. In conventional programming languages, functions or methods are typically defined and implemented for a particular data type. For example, a function may accept an integer as a parameter and return an integer type of result. In this case, if the same function is intended to be used on different data types, it is necessary to define a function separately for each data type. This results in redundancy of the code and a decrease in maintainability. And this problem can be solved using generalized calls. The generalization call defines a function or method by using a generalization so that it can be applied to different data types. A generic type is an abstract data type that can specify a specific type at programming time. By using generic parameters in the definition of a function or method, a particular data type may be deferred until it is time to call the function or method.
Thus, using a generalized call may provide the following benefits: the code can be multiplexed on different data types, repeated writing of the code is reduced, and maintainability of the code is improved; different data types and requirements can be flexibly adapted, so that codes have higher universality; the compiler can perform type checking to ensure that the specific type used in the calling process is consistent with the generic parameters, thereby improving the type security of the code. In summary, the token information is acquired by adopting the generalized calling mode, the version upgrading of the interface is not required to be concerned, and the calling efficiency and stability are higher.
Further, the generalized call mode may be a Dubbo call. Optionally, the Dubbo call refers to the manner in which remote calls are made using an interface in the Dubbo framework, requiring the same interface definition to be shared between the service provider and the service consumer. The calling mode is based on static type checking and compiling of the interface, and has higher performance and efficiency.
Step 404, under the condition that 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, acquiring the interface gateway proxy address of the target environment, and acquiring the token information corresponding to the target environment in a first calling mode according to the interface gateway proxy address.
Optionally, the interface gateway proxy address of the target environment refers to a gateway proxy address of the platform served by the platform itself using the method, for example, the platform using the method in this embodiment is an interface automation platform, and then the interface gateway proxy address of the target environment refers to an interface gateway proxy address served by the platform itself. Therefore, in this embodiment, the gateway address of the token information acquisition interface is not directly called, so that the problem of high gateway pressure caused by too large call volume is avoided.
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, the current environment is different from the target environment, and the problem of executing the use case across environments does not occur. Cross-context calls first require the acquisition of the interface gateway address of the target context. Illustratively, the http client may be used to obtain the interface gateway address of the target environment. Illustratively, the acquisition process generally includes: initializing HttpClient, constructing request object, sending pre-request, resolving response of pre-request, updating URL of request object, and finally sending actual request, etc. The specific implementation steps depend on the httplient library and framework used. In actual development, the httpconservation documents and examples were required to obtain more detailed guidance and specific implementations, with corresponding configurations and operations being performed according to library requirements.
Further, the first call manner may be a generalization call, which is the same as the explanation in the step 402, and will not be described herein. In addition, in some embodiments, the token information may also be obtained using a second call, which may be, for example, a dynamic proxy call, a RESTful call, a gRPC call, and the like.
In one embodiment, as shown in fig. 5, step 206, building cross-environment configuration information from the token information includes:
step 502, header information of use case content is acquired.
The header information is a mechanism for transmitting additional information in an HTTP request or response, and consists of key value pairs, and is used for carrying metadata in an HTTP message, and describing the attribute, format and other relevant information of the message. The header information is located in the header portion of the HTTP message, located after the request line or the response line, and is represented in the form of a key-value pair. The header information may be request header information, which is used to provide additional information about the client or the request in the HTTP request, for example.
Step 504, concatenates the token information into header information to construct cross-environment configuration information.
Optionally, the token information is spliced into the header information, so that the token information can be used for accessing identity verification of the target environment.
In one embodiment, step 202 further includes, before obtaining the corresponding token information according to the environmental parameter information of the target environment:
first, use case contents are executed to obtain a result log.
When the user case content is executed, the cross-environment action is not executed yet, and the user case content is executed in the current environment, so that the current user case can be tested and verified first.
The result log refers to log information for recording and storing operation results in the process of software development or system operation. The method records the result, state and related information of program execution so as to facilitate the purposes of subsequent analysis, fault detection or performance optimization. The result log generally contains information such as operation results, operation-related information, status change conditions, abnormality information, performance indexes, and the like.
For example, the use case content may include one or more use case steps, when the use case is executed, related information of the use case steps is obtained first, parameters extracted from each step and global parameters are placed in a use case context, so that each step can be referred to the extracted parameters when the use case is executed, identity information of a step node is stored in a stack, each step is conveniently executed, next steps are taken out, each step is initially loaded through a container when executed, a step type loaded by each step is allocated to a corresponding executor, for example, an executor of an http interface, an asserted executor, an executor of parameter extraction, and the executor type information of an executing step needs to be allocated to a corresponding executor (for example, the executor of the http interface, the asserted executor, the executor of parameter extraction) by a scheduler, when one step node is executed, a next node is changed to a current node, a next node is changed to a next node, and a linked list is similarly changed, so that steps can be conveniently circulated.
And secondly, verifying whether the result log meets a preset standard.
The verification of the result log can reflect the problems of whether the use case writing in the current environment is accurate or not and the like, and guarantees the safety and the accuracy of the subsequent cross-environment execution use case.
And finally, under the condition that the result log accords with a preset standard, executing the step of acquiring corresponding token information according to the environmental parameter information of the target environment.
In the embodiment, by performing the execution test on the use case in the current environment and verifying the result log, the problem of whether the use case in the current environment is accurately written or not can be reflected, and the security and the accuracy of the subsequent cross-environment execution use case are ensured.
In one embodiment, as shown in fig. 6 and 7, the execution bodies of the above steps are divided into a use case server 602, a use case executor 604, a step scheduler 606, an http step executor 608, a login authentication processor 610, and a Dubbo service processor 612. And the execution bodies described above are distributed among the data layer 702, the traffic layer 704, the presentation layer 706, and the operation layer 708.
Wherein the business layer 704 includes a data driven sub-level 7041, a scenario use example level 7042, a test plan sub-level 7043, a test result sub-level 7044, and a log record sub-level 7045. The initialization operation of the data design and the test scene design is completed in the data driving sub-level 7041, and parameters input in each stage are received; the use case and the creation of the scene, the import and call of the interface, the setting of the execution state (including timing execution, manual execution) and the like are completed in the scene use case level 7042, so that the use case is executed; completing the creation of the test plan at the test plan sub-level 7043, correlating different scenes, configuring an interface calling mode and a timing task state, and executing the test plan; displaying the execution result of the test plan in a test result sub-level 7044, and sending a corresponding notification to the terminal; the operation recording of the above-described process is completed in the log record sub-level 7045. The following is a specific implementation process of each level:
After creating the use case in the service layer 704, the use case server 602 executes the caching, storing, calling the custom function and the read-write instruction of the database on the data layer 702, and persists the information in the content of the use case into the database, where the content of the use case includes the specific steps of testing the application program, the interface between the terminal and the server, etc., inputting the data, the expected result, the verification point, etc.
The creation and execution process of the use case are as follows:
the use case server 602 acquires data such as global parameters and use case step parameters in a data driving sub-level 7041 of the service layer 704, and completes design of front data according to the acquired data, thereby completing design of a test scene; the use case executor 604 creates a use case in the current environment in the scene use case hierarchy 7042, and executes the use case.
The content of the use case to be executed may include one or more use case steps, when the use case is executed, related information of the use case steps is obtained first, parameters extracted from each step and global parameters are placed in the use case context, so that each step can refer to the extracted parameters when the use case is executed, identity information of step nodes is stored in a stack, and the following steps can be conveniently taken out after the execution of each step is completed. Each step, when executed, is assigned by the step scheduler 606 to a corresponding actuator, e.g., an actuator of an http interface, an asserted actuator, an actuator of parameter extraction, etc., by the step type of container initialization load. The type information of the executor of the execution step needs to be distributed to the corresponding executor by the scheduler, when the node of one step is executed, the next node of the stack is changed to the current node, the next node is changed to the next node, and the pointer address of the linked list is similarly changed so as to facilitate the circulation step.
Subsequently, correlating a plurality of use cases in a test technology sub-level to form and execute a complete test plan; and generating a result log under the current environment in the test result sub-level 7044, verifying whether the result log meets a preset standard, verifying the result log, reflecting the problems of whether the use case writing under the current environment is accurate or not and the like, and guaranteeing the safety and the accuracy of the subsequent cross-environment execution use case.
Next, under the condition that the result log meets the preset standard, the use case server 602 obtains the environment parameter information of the target environment at the data driving sub-level 7041 of the service layer 704, defines the environment parameter information to a unique determined environment, thereby determining the target environment of the present cross-environment use case, when the cross-environment use case is required to be executed, obtains the environment parameters of the target environment at the same time, and 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, the target environment is a production environment, and at the moment, continuous obtaining of token information corresponding to the target environment is forbidden, and error reporting processing is performed; if the current environment is a pre-release environment and the target environment is a test environment, the Dubbo service processor 612 obtains the interface gateway proxy address of the test environment, and obtains the token information corresponding to the test environment in a Dubbo calling mode according to the interface gateway proxy address.
Then, the http step executor 608 obtains the header information of the authenticated use case in the scene use case hierarchy 7042 of the service layer 704, and splices the token information into the header information to construct cross-environment configuration information which can be identified by the target environment interface, and then generates a cross-environment use case according to the use case content of the use case and the cross-environment configuration information obtained by splicing. Alternatively, in some embodiments, the http step executor 608 may choose to splice the token information acquired through the above process in the header information, thereby constructing cross-environment configuration information, or may choose to acquire the token information in other manners to construct new header information.
When the use case needs to be executed across environments, only the account in the authentication mode needs to be changed into the account in the target environment. In the scenario use case layer 7042 of the service layer 704, the cross-environment configuration information may be used to invoke an interface of the target environment, so as to synchronize the cross-environment use case to the target environment, and further, with reference to the process of executing the current environment use case, execute the cross-environment use case in the target environment, form a use case set from a plurality of use cases, reference the use case set to form a test plan, and execute the test plan.
Finally, the execution result of the test technique is output as a report in the presentation layer 706. The operational layer 708 provides an extensible platform for building, testing, and deploying software items, all of which are deployed on an integration tool of the operational layer 708, which may be, for example, jenkins, for configuring timing tasks, performing interface scheduling, and the like.
In addition, the execution main body of each step is subjected to load balancing processing, and starts from the internal cluster, and performs data call with the external functional service cluster to complete each required functional service, for example: interface service, general service, scene service, directory service, trace log service, change record service, test plan service, parameter pool service; and the micro service cluster, the registration center and the external business service cluster are used for carrying out data call to complete all needed business services, for example: the system comprises a pressure platform business service, an authorized data shielding inquiry service, a general subscription service, a general message sending service, an instant subscription service and a public time axis service.
It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.
Based on the same inventive concept, the embodiment of the application also provides a device for realizing the cross-environment execution use case of the method for realizing the cross-environment execution use case. The implementation of the solution provided by the apparatus is similar to the implementation described in the above method, so the specific limitation in the apparatus embodiments of one or more cross-environment execution cases provided below may refer to the limitation of the method of the cross-environment execution case hereinabove, and will not be repeated herein.
In one embodiment, as shown in fig. 8, there is provided an apparatus for executing use cases across environments, including: the system comprises a use case acquisition module, a token generation module, an environment configuration module and a use case synchronization module, wherein:
a use case acquisition module 802, configured to acquire environment parameter information of use case content and a target environment in a current environment;
the token generation module 804 is configured to obtain corresponding token information according to environmental parameter information of the target environment;
an environment configuration module 806, configured to construct cross-environment configuration information according to the token information, where the cross-environment configuration information is used for the interface gateway of the target environment to identify;
and the use case synchronization module 808 is configured to 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, so as to execute the cross-environment use case in the target environment.
In one embodiment, the use case content includes environment parameter information of a current environment, values indicated by the environment parameter information corresponding to different environments are different, and the token generating module includes a parameter comparing sub-module and an authentication executing sub-module, where:
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 the 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 authentication execution submodule includes a direct call unit and an indirect call unit, where:
the direct calling unit is used for directly acquiring the token information corresponding to the target environment in a first calling mode 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;
and the indirect calling unit is used for acquiring the interface gateway proxy address of the target environment 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, and acquiring the token information corresponding to the target environment in a first calling mode according to the interface gateway proxy address.
In one embodiment, the first call is a generalization call.
In one embodiment, the environment configuration module includes an initial module and a configuration module, where:
the initial module is used for acquiring the header information of the case content;
and the configuration module is used for splicing the token information into the header information to construct cross-environment configuration information.
In one embodiment, the apparatus for executing the use case across environments further includes:
the test module is used for executing the use case content to obtain a result log;
the verification module is used for verifying whether the result log accords with a preset standard;
and the execution module is used for executing the acquisition of the corresponding token information according to the environment parameter information of the target environment under the condition that the result log accords with the preset standard.
The various modules in the above-described cross-environment execution use case apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a server, and the internal structure of which may be as shown in fig. 9. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a 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 configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for storing use case related data. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements a method of cross-environment execution of use cases.
In one embodiment, a computer device is provided, which may be a terminal, and an internal structure diagram thereof may be as shown in fig. 10. The computer device includes a processor, a memory, an input/output interface, a communication interface, a display unit, and an input means. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program, when executed by a processor, implements a method of cross-environment execution of use cases.
It will be appreciated by those skilled in the art that the structure shown in fig. 10 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program performing the steps of: acquiring the environment parameter information of the use case content and the target environment in the current environment; 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 the interface gateway of the target environment to identify; and 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.
In one embodiment, the processor when executing the computer program further performs the steps of: comparing the values indicated by the environment parameter information corresponding to the current environment and the target environment; and 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, obtaining the token information corresponding to the target environment.
In one embodiment, the processor when executing the computer program further performs the steps of: 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 the interface gateway proxy address of the target environment, and acquiring the token information corresponding to the target environment in a first calling mode according to the interface gateway proxy address.
In one embodiment, the processor when executing the computer program further performs the steps of: acquiring header information of the example content; the token information is spliced into the header information to construct cross-environment configuration information.
In one embodiment, the processor when executing the computer program further performs the steps of: executing the use case content to obtain a result log; verifying whether the result log meets a preset standard or not; and under the condition that the result log accords with a preset standard, executing the step of acquiring corresponding token information according to the environment parameter information of the target environment.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of: acquiring the environment parameter information of the use case content and the target environment in the current environment; 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 the interface gateway of the target environment to identify; and 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.
In one embodiment, the computer program when executed by the processor further performs the steps of: comparing the values indicated by the environment parameter information corresponding to the current environment and the target environment; and 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, obtaining the token information corresponding to the target environment.
In one embodiment, the computer program when executed by the processor further performs the steps of: 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 the interface gateway proxy address of the target environment, and acquiring the token information corresponding to the target environment in a first calling mode according to the interface gateway proxy address.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring header information of the example content; the token information is spliced into the header information to construct cross-environment configuration information.
In one embodiment, the computer program when executed by the processor further performs the steps of: executing the use case content to obtain a result log; verifying whether the result log meets a preset standard or not; and under the condition that the result log accords with a preset standard, executing the step of acquiring corresponding token information according to the environment parameter information of the target environment.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the various embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the various embodiments provided herein may include at least one of relational databases and non-relational databases. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic units, quantum computing-based data processing logic units, etc., without being limited thereto.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to 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.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310870433.1A CN116991713B (en) | 2023-07-17 | 2023-07-17 | Method, device, computer equipment and storage medium for executing use cases across environments |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310870433.1A CN116991713B (en) | 2023-07-17 | 2023-07-17 | Method, device, computer equipment and storage medium for executing use cases across environments |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116991713A CN116991713A (en) | 2023-11-03 |
| CN116991713B true CN116991713B (en) | 2024-02-20 |
Family
ID=88529360
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310870433.1A Active CN116991713B (en) | 2023-07-17 | 2023-07-17 | Method, device, computer equipment and storage medium for executing use cases across environments |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116991713B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118092943B (en) * | 2024-04-26 | 2024-08-06 | 杭州数云信息技术有限公司 | Application release method and device, computer readable storage medium and terminal |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107908543A (en) * | 2017-07-26 | 2018-04-13 | 平安壹钱包电子商务有限公司 | Applied program testing method, device, computer equipment and storage medium |
| CN112667506A (en) * | 2020-12-26 | 2021-04-16 | 一城一家网络科技有限公司 | Interface testing method and related device |
| CN113127347A (en) * | 2021-04-14 | 2021-07-16 | 广联达科技股份有限公司 | Interface testing method, device, equipment and readable storage medium |
| CN114168471A (en) * | 2021-12-09 | 2022-03-11 | 挂号网（杭州）科技有限公司 | Test method, test device, electronic equipment and storage medium |
| CN114816965A (en) * | 2021-01-18 | 2022-07-29 | 腾讯科技（深圳）有限公司 | Data verification method and device |
| CN115269424A (en) * | 2022-08-04 | 2022-11-01 | 中国平安财产保险股份有限公司 | Automatic regression testing method, device, equipment and storage medium for production flow |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10261893B2 (en) * | 2016-12-05 | 2019-04-16 | Salesforce.Com, Inc. | Implicit coordination of deployment and regression testing across data centers and system clusters |
-
2023
- 2023-07-17 CN CN202310870433.1A patent/CN116991713B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107908543A (en) * | 2017-07-26 | 2018-04-13 | 平安壹钱包电子商务有限公司 | Applied program testing method, device, computer equipment and storage medium |
| CN112667506A (en) * | 2020-12-26 | 2021-04-16 | 一城一家网络科技有限公司 | Interface testing method and related device |
| CN114816965A (en) * | 2021-01-18 | 2022-07-29 | 腾讯科技（深圳）有限公司 | Data verification method and device |
| CN113127347A (en) * | 2021-04-14 | 2021-07-16 | 广联达科技股份有限公司 | Interface testing method, device, equipment and readable storage medium |
| CN114168471A (en) * | 2021-12-09 | 2022-03-11 | 挂号网（杭州）科技有限公司 | Test method, test device, electronic equipment and storage medium |
| CN115269424A (en) * | 2022-08-04 | 2022-11-01 | 中国平安财产保险股份有限公司 | Automatic regression testing method, device, equipment and storage medium for production flow |
Non-Patent Citations (2)
| Title |
|---|
| Secure Token–Key Implications in an Enterprise Multi-Tenancy Environment Using BGV–EHC Hybrid Homomorphic Encryption;Pooja Dhiman等;《Electronics 2022》;第11卷(第13期);1-17 * |
| SQLMVED：基于多变体执行的SQL注入运行时防御系统;马博林 等;《通信学报》;第42卷(第04期);127-138 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116991713A (en) | 2023-11-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11281457B2 (en) | Deployment of infrastructure in pipelines | |
| CN107370786B (en) | General information management system based on micro-service architecture | |
| US10735429B2 (en) | Controlling user creation of data resources on a data processing platform | |
| US9858177B2 (en) | Automated test generation for multi-interface enterprise virtualization management environment | |
| CN110569035B (en) | Code compiling method, device, equipment and storage medium of software development project | |
| US10305962B1 (en) | Unit testing clients of web services | |
| CN106415480B (en) | High-speed application for installation on a mobile device for enabling remote configuration of the mobile device | |
| CN112486547B (en) | Application program updating method and device under multi-tenant scene and electronic equipment | |
| US10411961B2 (en) | Image management in cloud environments | |
| CN111782535A (en) | Test method and device | |
| US20220253297A1 (en) | Automated deployment of changes to applications on a cloud computing platform | |
| CN116450107B (en) | Method and device for secondary development of software by low-code platform and electronic equipment | |
| Poccia | AWS Lambda in Action: Event-driven serverless applications | |
| US10803166B1 (en) | Automated determination of application privileges | |
| KR20220143705A (en) | Computing services for a platform of blockchain-related services | |
| CN116991713B (en) | Method, device, computer equipment and storage medium for executing use cases across environments | |
| CN116055308B (en) | Bottom layer blockchain network deployment method and device of supply chain financial platform | |
| US11531763B1 (en) | Automated code generation using analysis of design diagrams | |
| CN116257438A (en) | Updating method of interface test case and related equipment | |
| US10176011B2 (en) | Automatically generating and executing a service operation implementation for executing a task | |
| CN106990974B (en) | APP updating method and device and electronic equipment | |
| US11783049B2 (en) | Automated code analysis tool | |
| CN110806935A (en) | Application program construction method, device and system | |
| US11693643B2 (en) | Network-based solution module deployment platform | |
| US11573975B2 (en) | Data migration method, data migration system, and node |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |