A SaaS user scenario simulation test method, device and system

Abstract

The present invention relates to a SaaS user scenario simulation test method. This method integrates the capabilities of multi-resource testing, conducts in-depth simulation of SaaS service scenarios, integrates the network, computing and storage resources of the IaaS layer in the SaaS user scenario, and realizes a full range of simulation testing of the SaaS user scenario. It can more accurately predict and evaluate the performance of services in actual applications and user experience. This method can be used for multi-dimensional quality testing of cloud services and can comprehensively evaluate the performance and stability of cloud services. In addition, this method also realizes end-to-end data link automation testing from data source to destination, ensuring the integrity and reliability of data transmission; this method is compatible with multiple operating systems such as CentOS, Ubuntu, Kylin, etc.; this method can dynamically adjust and flexibly manage test costs and resources according to test requirements, optimize resource allocation and cost-effectiveness; this method adopts a single platform integrated deployment, which improves test efficiency and operational convenience.

Description

Technical Field

[0001] The present invention belongs to the technical field of SaaS user scenario simulation testing, and in particular relates to a SaaS user scenario simulation testing method, device and system. Background Art

[0002] In the current field of hyper-convergence and cloud computing testing technology, research and practice are primarily focused on the Infrastructure as a Service (IaaS) level, particularly in the three core areas of computing, networking, and storage. With the proliferation of cloud services and the increasing reliance of enterprises on cloud infrastructure, testing the performance, reliability, and functionality of these services has become crucial. For example, for performance testing, mature test guidelines have been developed that focus on evaluating service performance under high load, including response time and throughput. Reliability testing, for example, ensures service stability and data persistence by simulating failures and outages. Furthermore, automation is integrated with CICD, with automated test scripts widely used in CICD processes to achieve comprehensive coverage of interface testing and ensure software quality.

[0003] Although single-domain testing technology at the IaaS level is relatively mature, it still has some obvious flaws and shortcomings:

[0004] 1. Lack of end-to-end business scenario simulation: Most tests focus on the technical level and lack simulation of actual user scenarios, which may lead to unforeseen problems in real-world use.

[0005] 2. Insufficient testing at the SaaS layer: There is relatively little testing at the Software as a Service (SaaS) layer, especially simulation testing for specific business logic and user interactions.

[0006] 3. Differences between test environment and production environment: Automated testing is often performed in a controlled test environment and may not be able to fully simulate the complexity and unpredictability of the production environment.

[0007] 4. Cost and resource limitations: Comprehensive testing can require significant computing resources and costs, which is a challenge for many organizations.

[0008] 5. Integration issues of testing tools: There may be integration issues between different testing tools and platforms, resulting in a less smooth and efficient testing process. Summary of the Invention

[0009] To overcome the aforementioned shortcomings of existing testing technologies, this paper proposes a novel SaaS user scenario simulation testing method. By integrating multi-resource testing capabilities and conducting in-depth simulations of SaaS service usage scenarios, this method achieves comprehensive simulation testing of SaaS user scenarios. Furthermore, this method exhibits excellent cross-operating system adaptability and utilizes a single platform for integrated deployment, improving testing efficiency and operational convenience.

[0010] Specifically, the present invention provides a SaaS user scenario simulation test method, such as Figure 1 As shown, the method includes the following steps:

[0011] S1. Preset a JSON file, fill in the IP addresses of the client and server machines, read the JSON file, obtain the IP addresses of the client and server machines, and write them into memory;

[0012] S2. The controller adapts to multiple operating systems by updating the configuration information and cache of all client and server machines;

[0013] S3. The controller checks whether the client and server have closed the designated port firewall. If both are closed, it proceeds to the next step; if not, it closes the designated port firewall.

[0014] S4. The controller checks whether the server has the same version of minio components and service processes. If so, it kills the minio service process and redeploys the service. If not, it asynchronously updates minio and related components to all servers and deploys them. Then, the live task accesses the minio web service of all servers through multiple ports. If the access is successful, it proceeds to the next step. If the access fails, it returns to step S3.

[0015] S5. The controller checks whether the client has the same version of the s3cmd component and service process. If so, it kills the s3cmd service process and restarts the service. If not, it asynchronously updates s3cmd and related components to all clients and deploys them. The detection task then accesses the client through the port. If the access is successful, it proceeds to the next step. If the access fails, it returns to this step and rechecks whether the client has the same version of the s3cmd component and service process.

[0016] S6. The controller updates the s3cmd default configuration file, updates the server IP address to the configuration file, sends it to the corresponding client, and starts the s3cmd service.

[0017] S7. The controller asynchronously updates the Minio native interface test suite to the client and deploys and runs it to simulate user web operations.

[0018] S8. The active task accesses the client to check whether the s3cmd process task is running normally. If it is running normally, it simulates user read and write operations. If not, it reports an error indicating that the client is not running.

[0019] Furthermore, the preset JSON file described in step S1 of the SaaS user scenario simulation test method of the present invention is filled with the IP addresses of the client and server machines, with the server IP address as the key and the client IP address as the value.

[0020] Furthermore, if reading the JSON file fails in step S1 of the SaaS user scenario simulation test method of the present invention, an error is reported to check the configuration file, and the method returns to re-preset the JSON file.

[0021] Furthermore, the configuration information of the client and server machines updated by the controller in step S2 of the SaaS user scenario simulation test method of the present invention includes but is not limited to: yum, dnf, epel-release;

[0022] Compatible operating systems include but are not limited to: CentOS, Ubuntu, and Kylin.

[0023] Furthermore, in step S2 of the SaaS user scenario simulation test method of the present invention, if the controller fails to update the configuration information and cache of the client and server machines, the method returns to step S1 to re-preset the JSON file.

[0024] Furthermore, in step S3 of the SaaS user scenario simulation test method of the present invention, the controller closes the designated port firewall. If the setting fails for more than 4 times, the task is terminated.

[0025] In a second aspect, the present invention further provides a SaaS user scenario simulation test device, which implements the steps of the above-mentioned SaaS user scenario simulation test method when running.

[0026] In a third aspect, the present invention further provides a SaaS user scenario simulation test system, which implements the steps of the above-mentioned SaaS user scenario simulation test method when running.

[0027] In addition, the present invention also provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the steps of the above-mentioned SaaS user scenario simulation test method are implemented.

[0028] In summary, the SaaS user scenario simulation test method of the present invention achieves the following beneficial effects by comprehensively considering the integration of network, computing, and storage resources of the IaaS layer in the SaaS user scenario:

[0029] (1) Multi-resource comprehensive testing: This method combines the testing of network, computing, and storage resources, providing a comprehensive IaaS layer resource evaluation strategy that can be used for multi-dimensional quality testing of cloud services and comprehensively evaluate the performance and stability of cloud services.

[0030] (2) SaaS service scenario simulation: By simulating the user's usage scenarios in SaaS services, this method can more accurately predict and evaluate the performance of the service in actual applications and the user experience.

[0031] (3) End-to-end data link testing: This enables automated testing of the end-to-end data link from the data source to the destination, ensuring the integrity and reliability of data transmission.

[0032] (4) Cross-operating system compatibility: It is compatible with multiple operating systems including CentOS, Ubuntu, and Kylin, enhancing the versatility and applicability of the solution.

[0033] (5) Cost and resource elasticity: Dynamic adjustment and elastic management of test costs and resources are achieved based on the number of configured clients and servers, optimizing resource allocation and cost-effectiveness.

[0034] (6) Integrated deployment: The test environment and all tools are integrated and deployed on a single platform, which simplifies the deployment process, eliminates the complexity and inconvenience caused by physical isolation, speeds up test implementation, and improves the efficiency and convenience of operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments of the present invention. Obviously, the following drawings are only some embodiments recorded in the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0036] Figure 1 4 is an implementation flow chart of the method of the present invention.

[0037] Figure 2 The figure is a schematic diagram of the operation flow of a testing method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0038] To make the objectives, technical solutions, and advantages of the present invention more clearly apparent, the technical solutions of the present invention will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. The present invention may also be implemented or applied through different specific implementation methods, and the details in this specification may be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention.

[0039] At the same time, it should be understood that the scope of protection of the present invention is not limited to the specific embodiments described below; it should also be understood that the terms used in the embodiments of the present invention are for describing specific embodiments rather than for limiting the scope of protection of the present invention.

[0040] Example: A SaaS user scenario simulation testing method

[0041] like Figure 2 As shown, the method includes the following steps:

[0042] Step 1. Preset the JSON file and fill in the client and server machine IP addresses, with the server IP address as the key and the client IP address as the value.

[0043] Step 2. Read the JSON file, obtain the key and value, that is, the client and server machine IP addresses, and write them into memory. If the reading fails, for example, because the format does not match the expected format, an error is reported, the configuration file is checked, and the program returns to step 1 and starts again.

[0044] Step 3. The controller updates the yum, dnf, epel-release and other configuration information and caches of all client+server machines to adapt to operating systems such as CentOS, Ubuntu, and Kylin (adaptive system support extensions); if the update fails, return to step 1 and restart the execution.

[0045] Step 4. The controller checks whether the server and client have closed the designated port firewall (supports extension modification). If both are closed, proceed to the next step; if not, close the designated port firewall; if the setting exceeds 4 times, the task is terminated.

[0046] Step 5. The controller checks whether the server has the same version of minio components and service processes. If so, it kills the minio service process and redeploys the service, and then proceeds to the next step. If not, it asynchronously updates minio and related components to all servers and deploys them, then proceeds to the next step.

[0047] Step 6. The live detection task accesses the minio web service of all servers through multiple ports. If the access is successful, it proceeds to the next step; if the access fails, it returns to step 4 and starts again.

[0048] Step 7. The controller checks whether the client has the same version of the s3cmd component and service process. If so, it kills the s3cmd service process and restarts the service, and then proceeds to the next step. If not, it asynchronously updates s3cmd and components to all clients and deploys them, then proceeds to the next step.

[0049] Step 8. The live detection task accesses the client through the port. If the access is successful, it proceeds to the next step; if the access fails, it returns to step 7 and starts again.

[0050] Step 9. The controller updates the s3cmd default configuration file, updates the server IP address to the configuration file, sends it to the corresponding client, and starts the s3cmd service.

[0051] Step 10. The controller asynchronously updates the minio native interface test suite to the client and deploys and runs it to simulate user web operations.

[0052] Step 11. The active task accesses the client to check whether the s3cmd process task is running normally and simulates user read and write operations. If it is not running, an error message will be displayed indicating that the client is not running.

[0053] The above description is only a preferred embodiment of the present invention and does not limit the present invention in any form. Any technician familiar with the profession can make some changes or modifications to the technical content disclosed above without departing from the scope of the technical solution of the present invention to obtain equivalent embodiments with equivalent changes. However, any simple modifications, equivalent changes and modifications made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solution of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A SaaS user scenario simulation test method, characterized in that: The method comprises: S1. Preset a JSON file, fill in the client and server machine IP addresses, read the JSON file, obtain the client and server machine IP addresses, and write them into memory; S2. The controller adapts to multiple operating systems by updating the configuration information and cache of all client and server machines. S3. The controller checks whether the client and server have disabled the designated port firewall. If so, it proceeds to the next step. If not, it disables the designated port firewall. S4. The controller checks whether the server has the same version of Minio components and service processes. If so, it kills the Minio service process and redeploys the service. If not, it asynchronously updates Minio and related components to all servers and deploys them. The detection task then accesses the Minio web service on all servers through multiple ports. If the access is successful, it proceeds to the next step. If the access fails, it returns to step S3. S5. The controller checks whether the client has the same version of the s3cmd component and service process. If so, it kills the s3cmd service process and restarts the service. If not, it asynchronously updates s3cmd and related components to all clients and deploys them. The detection task then accesses the client through the port. If the access is successful, it proceeds to the next step. If the access fails, it returns to this step and rechecks whether the client has the same version of the s3cmd component and service process. S6. The controller updates the s3cmd default configuration file, adds the server IP address to the configuration file, sends it to the corresponding client, and starts the s3cmd service. S7. The controller asynchronously updates the Minio native interface test suite to the client and deploys and runs it, simulating user web operations. S8. The active task accesses the client to check whether the s3cmd process is running properly. If it is running properly, it simulates user read and write operations. If not, it reports an error indicating that the client is not running.

2. The SaaS user scenario simulation test method according to claim 1, characterized in that: In the pre-set JSON file described in step S1, fill in the IP addresses of the client and server machines, with the server IP address as the key and the client IP address as the value.

3. The SaaS user scenario simulation test method according to claim 1, characterized in that: If reading the JSON file fails in step S1, an error is reported to check the configuration file, and the process returns to re-preset the JSON file.

4. The SaaS user scenario simulation test method according to claim 1, characterized in that: The configuration information of the client and server machines updated by the controller in step S2 includes: yum, dnf, and epel-release; Compatible operating systems include: CentOS, Ubuntu, and Kylin.

5. The SaaS user scenario simulation test method according to claim 1, characterized in that: If the controller fails to update the configuration information and cache of the client and server machines in step S2, it returns to step S1 to re-preset the JSON file.

6. The SaaS user scenario simulation test method according to claim 1, characterized in that: In step S3, the controller closes the designated port firewall. If the setting fails more than 4 times, the task is terminated.

7. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the steps of the SaaS user scenario simulation test method according to any one of claims 1 to 6 are implemented.

Images