Application test method based on cloud management platform, and cloud management platform

Abstract

Disclosed in the present application are an application test method based on a cloud management platform, and a cloud management platform. A tenant may implement an application test without purchasing an engineering sample, such that the resource costs and labor costs required by the tenant for carrying out the application test can be reduced. The method of the present application comprises: when a tenant needs to test an application thereof, the tenant sending an application test request to a cloud management platform; since the application test request is used for indicating a first test case associated with the application of the tenant, and an execution policy with respect to the first test case, the cloud management platform selecting, from a cloud phone cluster of the tenant, a first cloud phone that can execute the first test case; and the cloud management platform making the first cloud phone execute the first test case according to the execution policy, so as to obtain a test result of the first test case.

Description

An application testing method based on a cloud management platform and the cloud management platform itself.

[0001] This application claims priority to Chinese Patent Application No. 202410509864.X, filed on April 23, 2024, entitled "A Cloud Phone Testing Method and Cloud Management Platform Based on a Cloud Management Platform", and to Chinese Patent Application No. 202410865496.2, filed on June 28, 2024, entitled "An Application Testing Method and Cloud Management Platform Based on a Cloud Management Platform", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of cloud technology, and in particular to an application testing method based on a cloud management platform and a cloud management platform. Background Technology

[0003] With the rapid development of smartphones, mobile applications have become an indispensable part of people's daily lives. Therefore, testing applications on different phone models allows application developers to ensure compatibility across various devices, enabling them to release applications that can be installed on different phone models.

[0004] In related technologies, application developers typically purchase engineering prototypes to test their applications. Specifically, application developers can first install their developed applications on different models of engineering prototypes and have the prototypes run these applications to handle certain preset tasks. Therefore, based on the results of the task processing, application developers can determine the functionality and performance of these applications on different mobile phone models.

[0005] In the above process, application developers need to purchase a large number of different models of engineering machines, resulting in high resource costs. Moreover, this testing method often requires application developers' maintenance personnel to manually test the application, resulting in high labor costs. Summary of the Invention

[0006] This application provides an application testing method and a cloud management platform based on a cloud management platform. This eliminates the need for tenants to purchase engineering machines to perform application testing, thereby reducing the resource and labor costs required for tenants to conduct application testing.

[0007] The first aspect of this application provides an application testing method based on a cloud management platform. The cloud management platform implementing this method can manage infrastructure providing cloud services, including cloud phone clusters created by the cloud management platform for tenants. The method includes:

[0008] When a tenant needs to test its application, the cloud management platform can provide a testing interface. The tenant can then input an application test request for its application into the testing interface. In this way, the cloud management platform can receive the application test request sent by the tenant through the testing interface. This application test request specifies the first test case associated with the tenant's application, as well as the execution strategy for that first test case.

[0009] Upon receiving the application testing request, the cloud management platform can determine the first test case to be executed and the execution strategy for that first test case. Then, the cloud management platform can select the first cloud phone from the cloud phone cluster serving the tenant that can execute the first test case.

[0010] Once the first cloud phone is identified, the cloud management platform can instruct it to execute the first test case according to the execution strategy for that test case, thereby obtaining the test results and returning them to the tenant. This satisfies the tenant's testing needs for their application.

[0011] As can be seen from the above method, tenants can use the cloud phone provided by the cloud management platform (i.e., the first cloud phone mentioned above) to complete the testing of their applications. This eliminates the need for tenants to purchase additional engineering machines, which helps reduce the resource costs required for tenants to conduct application testing. Furthermore, during the application testing process, tenants only need to send an application testing request to the cloud management platform, which will automatically call the cloud phone to complete the application testing without requiring any additional operations from the tenants, thus reducing the labor costs for tenants to conduct application testing.

[0012] In one possible implementation, the application test request further indicates a first number of cloud phones to execute the first test case. Based on the application test request, the cloud management platform selects first cloud phones from the cloud phone cluster capable of executing the first test case, including: the cloud management platform determining a second number of second cloud phones capable of executing the first test case from the cloud phone cluster; if the second number is greater than or equal to the first number indicated by the application test request, the cloud management platform selects a first number of first cloud phones capable of executing the first test case from the second number of second cloud phones; if the second number is less than the first number, the cloud management platform adds a third number of third cloud phones capable of executing the first test case to the cloud phone cluster, and selects a first number of first cloud phones capable of executing the first test case from the second number of second cloud phones and the third number of third cloud phones, wherein the sum of the second and third numbers is greater than or equal to the first number. In the aforementioned implementation, since the application test request also indicates a first number of cloud phones specified by the tenant to execute the first test case, after receiving the application test request, the cloud management platform can parse the application test request to determine the first number of cloud phones required to execute the first test case. Next, the cloud management platform can determine a second number of second cloud phones capable of executing the first test case from the cloud phone cluster serving the tenant. Since the tenant has specified a first number of cloud phones for executing the first test case, if the second number is greater than or equal to the first number, it indicates that the number of second cloud phones is sufficient. Therefore, the cloud management platform can select the first number of first cloud phones capable of executing the first test case from the second number of second cloud phones. If the second number is less than the first number, it indicates that the number of second cloud phones is insufficient. Therefore, the cloud management platform adds a third number of third cloud phones capable of executing the first test case to the cloud phone cluster, and selects the first number of first cloud phones capable of executing the first test case from the second number of second cloud phones and the third number of third cloud phones. It can be understood that the sum of the second and third numbers is greater than or equal to the first number. Therefore, the cloud management platform can detect in real time whether there are enough second cloud phones in the tenant's cloud phone cluster to execute the first test case required by the tenant. If there are enough, the platform will select the first cloud phone to be used to execute the test case from these cloud phones. If there are not enough, the cloud phone cluster will be expanded directly, and the first cloud phone to be used to execute the test case will be selected from the existing second cloud phones and the newly added third cloud phones, thereby automating the selection of cloud phones.

[0013] In one possible implementation, the first cloud phone capable of executing the first test case includes a cloud phone whose operating system type matches the first test case. In the aforementioned implementation, the operating system type of the first cloud phone is adapted to the first test case, and it is capable of executing the first test case.

[0014] In one possible implementation, the execution strategy includes at least one of the following: the time of execution of the first test case, the period of execution of the first test case, and the number of times the first test case is executed. The cloud management platform instructs the first cloud phone to execute the first test case according to the execution strategy indicated by the application test request. Obtaining the test result of the first test case includes: the cloud management platform instructs the first cloud phone to execute the first test case according to at least one of the time, period, and number of times indicated by the application test request, and obtains the test result of the first test case. In the aforementioned implementation, since the execution strategy formulated by the tenant for the first test case includes one or more of the information such as the time of execution of the first test case, the period of execution of the first test case, and the number of times the first test case is executed, the cloud management platform instructs the first cloud phone to execute the first test case according to one or more of the information such as the time of execution of the first test case, the period of execution of the first test case, and the number of times the first test case is executed, thereby obtaining the test result of the first test case. Therefore, the cloud management platform can execute the first cloud phone according to the execution strategy defined by the tenant for the first test case, thereby meeting the tenant's customized needs for application testing and improving the user experience.

[0015] In one possible implementation, the method further includes: a cloud management platform receiving a cloud phone creation request sent by a tenant through a first creation interface. The cloud phone creation request indicates a fourth number of cloud phones included in the cloud phone cluster, and the type of operating system for each cloud phone in the cluster. Based on the cloud phone creation request, the cloud management platform creates a fourth number of cloud phones and deploys operating systems in these fourth number of cloud phones according to their types. These fourth number of cloud phones constitute the cloud phone cluster. In the aforementioned implementation, when a tenant needs to create a dedicated cloud phone cluster, the cloud management platform can provide the tenant with a first creation interface. The tenant can then input a cloud phone creation request for the cloud phone cluster into the first creation interface. In this way, the cloud management platform can receive the cloud phone creation request sent by the tenant through the first creation interface, wherein the cloud phone creation request indicates a fourth number of cloud phones included in the cloud phone cluster required by the tenant, and the type of operating system for each cloud phone in the cloud phone cluster. Upon receiving the cloud phone creation request, the cloud management platform can determine the fourth number of cloud phones included in the cloud phone cluster, as well as the operating system type of each cloud phone in the cluster. Therefore, the cloud management platform can directly create the fourth number of cloud phones and deploy the corresponding operating system on each of them according to its operating system type. This demonstrates that the cloud management platform can create cloud phone clusters containing multiple cloud phones in the cloud according to the tenant's needs, which is beneficial for tenants to conduct application testing in the cloud subsequently.

[0016] In one possible implementation, the cloud phone creation request is also used to indicate the expansion and contraction conditions for the cloud phone cluster. The method further includes: if the cloud phone cluster meets the expansion conditions, the cloud management platform adds cloud phones to the cluster, so that the cluster contains a fifth number of cloud phones, which is greater than the fourth number; if the cloud phone cluster meets the contraction conditions, the cloud management platform deletes cloud phones from the cluster, so that the cluster contains a sixth number of cloud phones, which is greater than the fourth number. In the aforementioned implementation, since the cloud phone creation request can also be used to indicate the expansion and contraction conditions specified by the tenant for the cloud phone cluster, the cloud management platform can monitor the tenant's cloud phone cluster in real time to determine whether the cluster meets the expansion or contraction conditions. If the cluster meets the expansion conditions, the cloud management platform adds new cloud phones to the cluster containing the fourth number, resulting in an expanded cluster containing a fifth number of cloud phones. If the cloud phone cluster meets the scaling-down conditions, the cloud management platform removes cloud phones from the cluster, so that the scaled-down cluster contains a sixth number of cloud phones. Therefore, the cloud management platform can automatically scale up or down the tenant's cloud phone cluster according to the tenant's elastic scaling strategy (the aforementioned scaling-up and scaling-down conditions), thereby satisfying the tenant's unified resource management needs for their cloud phone cluster.

[0017] In one possible implementation, the method further includes: the cloud management platform receiving a test case creation request sent by a tenant through a second creation interface. The test case creation request indicates parameters for multiple second test cases associated with the application, including the type of operating system matching the multiple second test cases, and the multiple second test cases include the first test case. The cloud management platform creates multiple second test cases based on the parameters indicated in the test case creation request. In the aforementioned implementation, when a tenant needs to create test cases for its application, the cloud management platform can provide the tenant with a second creation interface. The tenant can then input a test case creation request for its application into the second creation interface. In this way, the cloud management platform can receive the test case creation request sent by the tenant through the second creation interface, wherein the test case creation request indicates parameters for multiple second test cases associated with the tenant's application (these multiple second test cases include the aforementioned first test case). After receiving the test case creation request, the cloud management platform can determine the parameters of the multiple second test cases, and therefore, the cloud management platform can create and save multiple second test cases based on these parameters. Therefore, the cloud management platform can create multiple second test cases in the cloud that are specific to the tenant's application, according to the tenant's customized requirements for test cases. These multiple second test cases can then be presented to the tenant in the future, allowing the user to select the first test case to be executed, thereby achieving the application testing required by the tenant.

[0018] In one possible implementation, the first cloud phone includes any of the following: a virtual machine, a container, and a micro virtual machine.

[0019] A second aspect of this application provides a cloud management platform for managing infrastructure that provides cloud services. The infrastructure includes a cloud phone cluster created by the cloud management platform for a tenant. The cloud management platform includes: a first receiving module for receiving an application test request sent by a tenant through a test interface, wherein the application test request indicates a first test case associated with the tenant's application and an execution strategy for the first test case; a selection module for selecting a first cloud phone from the cloud phone cluster that can execute the first test case based on the application test request; and an execution module for instructing the first cloud phone to execute the first test case according to the execution strategy indicated by the application test request, thereby obtaining the test result of the first test case.

[0020] In one possible implementation, the application test request is further used to indicate a first number of cloud phones executing the first test case. The selection module is used to: determine a second number of second cloud phones from the cloud phone cluster that can execute the first test case; if the second number is greater than or equal to the first number indicated by the application test request, select a first number of first cloud phones that can execute the first test case from the second number of second cloud phones; if the second number is less than the first number, add a third number of third cloud phones that can execute the first test case to the cloud phone cluster, and select a first number of first cloud phones that can execute the first test case from the second number of second cloud phones and the third number of third cloud phones, wherein the sum of the second number and the third number is greater than or equal to the first number.

[0021] In one possible implementation, the first cloud phone capable of executing the first test case includes a cloud phone whose operating system type matches the first test case.

[0022] In one possible implementation, the execution strategy includes at least one of the following: the time of execution of the first test case, the period of execution of the first test case, and the number of times the first test case is executed; and the execution module is used to instruct the first cloud phone to execute the first test case according to at least one of the time, period, and number of times indicated by the application test request, and to obtain the test result of the first test case.

[0023] In one possible implementation, the cloud management platform further includes: a second receiving module, configured to receive a cloud phone creation request sent by a tenant through a first creation interface, the cloud phone creation request indicating a fourth number of cloud phones included in the cloud phone cluster, and the type of operating system of the cloud phones included in the cloud phone cluster; and a first creation module, configured to create a fourth number of cloud phones based on the cloud phone creation request, and deploy an operating system in the fourth number of cloud phones according to the type, the fourth number of cloud phones constituting a cloud phone cluster.

[0024] In one possible implementation, the cloud phone creation request is also used to indicate the scaling-up and scaling-down conditions for the cloud phone cluster. The cloud management platform also includes: a scaling-up module, used to add cloud phones to the cloud phone cluster if the cloud phone cluster meets the scaling-up conditions, so that the cloud phone cluster contains a fifth number of cloud phones, the fifth number being greater than the fourth number; and a scaling-down module, used to delete cloud phones from the cloud phone cluster if the cloud phone cluster meets the scaling-down conditions, so that the cloud phone cluster contains a sixth number of cloud phones, the sixth number being greater than the fourth number.

[0025] In one possible implementation, the cloud management platform further includes: a third receiving module, used to receive a test case creation request sent by a tenant through a second creation interface, the test case creation request indicating parameters of multiple second test cases associated with the application, the parameters including the type of operating system matching the multiple second test cases, the multiple second test cases including the first test case; and a second creation module, used to create multiple second test cases based on the parameters indicated by the test case creation request.

[0026] In one possible implementation, the first cloud phone includes any of the following: a virtual machine, a container, and a micro virtual machine.

[0027] A third aspect of this application provides a computing device cluster, which includes at least one computing device, each computing device including a processor and a memory: the memory is used to store instructions; the processor is used to cause the computing device cluster to perform the method described in the first aspect or any possible implementation of the first aspect according to the instructions.

[0028] A fourth aspect of this application provides a computer storage medium storing one or more instructions that, when executed by one or more computers, cause the one or more computers to perform the method described in the first aspect or any possible implementation of the first aspect.

[0029] A fifth aspect of this application provides a computer program product storing instructions that, when executed by a computer, cause the computer to perform the method described in the first aspect or any possible implementation of the first aspect.

[0030] In this embodiment, when a tenant needs to test its application, it can send an application test request to the cloud management platform. Since the application test request indicates the first test case associated with the tenant's application and the execution strategy for the first test case, the cloud management platform can select a first cloud phone from the tenant's cloud phone cluster capable of executing the first test case, and instruct the first cloud phone to execute the first test case according to the execution strategy, thereby obtaining the test result of the first test case. In the aforementioned process, the tenant can complete the testing of its application using the cloud phone provided by the cloud management platform (i.e., the aforementioned first cloud phone). This eliminates the need for the tenant to purchase additional engineering machines, reducing the resource costs required for application testing. Furthermore, during application testing, the tenant only needs to send an application test request to the cloud management platform, which will automatically call the cloud phone to complete the application test without requiring additional operation from the tenant, further reducing the labor costs for application testing. Attached Figure Description

[0031] Figure 1 is a schematic diagram of a cloud service system provided in an embodiment of this application;

[0032] Figure 2 is a schematic diagram of the structure of a cloud management platform provided in an embodiment of this application;

[0033] Figure 3 is a flowchart illustrating an application testing method based on a cloud management platform provided in an embodiment of this application.

[0034] Figure 4 is a schematic diagram of an application test provided in an embodiment of this application;

[0035] Figure 5 is a schematic diagram of cloud phone cluster creation provided in an embodiment of this application;

[0036] Figure 6 is a schematic diagram of test case creation provided in an embodiment of this application;

[0037] Figure 7 is a schematic diagram of the structure of a cloud management platform provided in an embodiment of this application;

[0038] Figure 8 is a schematic diagram of a computing device provided in an embodiment of this application;

[0039] Figure 9 is a schematic diagram of a computing device cluster provided in an embodiment of this application;

[0040] Figure 10 is a schematic diagram of computer devices in a computer cluster connected via a network according to an embodiment of this application. Detailed Implementation

[0041] This application provides an application testing method and a cloud management platform based on a cloud management platform. This eliminates the need for tenants to purchase engineering machines to perform application testing, thereby reducing the resource and labor costs required for tenants to conduct application testing.

[0042] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of elements is not necessarily limited to those elements but may include other elements not explicitly listed or inherent to those processes, methods, products, or apparatuses.

[0043] With the rapid development of smartphones, mobile applications have become an indispensable part of people's daily lives. Therefore, testing applications on different phone models allows application developers to ensure compatibility across various devices, enabling them to release applications that can be installed on different phone models.

[0044] In related technologies, application developers typically purchase engineering prototypes to test their applications. Specifically, application developers can first install their developed applications on different models of engineering prototypes and have the prototypes run these applications to handle certain preset tasks. Therefore, based on the results of the task processing, application developers can determine the functionality and performance of these applications on different mobile phone models.

[0045] In the above process, application developers need to purchase a large number of different models of engineering machines, resulting in high resource costs. Moreover, this testing method often requires application developers' maintenance personnel to manually test the application, resulting in high labor costs.

[0046] Furthermore, due to the existence of different models of engineering machines, the number of engineering machines is relatively large, which often makes it difficult to manage them centrally, resulting in low efficiency in resource management.

[0047] Furthermore, since application testing often requires manual intervention from operations and maintenance personnel and lacks automated testing solutions, this leads to low efficiency in application testing.

[0048] To address the aforementioned problems, this application provides an application testing method based on a cloud management platform. This method can be implemented through a cloud service system. Figure 1 is a schematic diagram of the structure of the cloud service system provided in this application embodiment. As shown in Figure 1, the cloud service system includes infrastructure that can provide cloud services and a cloud management platform that manages this infrastructure. The cloud management platform and the infrastructure are described in detail below:

[0049] A cloud management platform can centrally manage the infrastructure of the entire cloud service system. (For example, within the infrastructure, it can create a cluster of cloud phones for the tenant according to the tenant's instructions. This cluster can be viewed as a simulation environment containing multiple cloud phones, which can be used to test the tenant's applications, etc.) The cloud management platform can also be open to tenants outside the cloud service system and respond to their requests. For example, the cloud management platform can provide various interfaces such as login, creation, and testing interfaces for tenant clients (e.g., the terminal devices used by the tenant or the browsers on those devices) to access. Specifically, the cloud management platform can authenticate the tenant's client through the login interface, allowing the client to log in after successful authentication. Similarly, the cloud management platform can also allow the tenant's client to send a cloud phone creation request to the platform through the creation interface. Based on this request, the platform can create a dedicated cloud phone cluster for the tenant, typically containing a certain number of cloud phones and deploying a specific type of operating system on these phones. For example, the cloud management platform can also create an interface that allows tenant clients to send test case creation requests to the cloud management platform. Based on these requests, the cloud management platform can create multiple test cases associated with the tenant's (application developer's) application. These test cases can be considered as multiple functions or modules to be tested within the tenant's application. Furthermore, the cloud management platform can also use a test interface to allow tenant clients to send application test requests. Since these requests specify one or more test cases associated with the tenant's application, the cloud management platform can select one or more cloud phones from the cloud phone cluster capable of executing these test cases. The platform then instructs these cloud phones to execute the test cases according to the execution strategy indicated in the request, thereby obtaining the test results. These test results can then be considered as the test results of the tenant's application.

[0050] The infrastructure comprises a cluster of compute nodes, which in turn contains multiple compute nodes. It's important to note that the compute nodes referred to here are physical instances within the infrastructure. These physical instances can take various forms; for example, they can be physical servers or bare-metal servers. Therefore, when a tenant needs to create cloud phones, the cloud management platform can use virtualization to create a cluster of cloud phones serving the tenant across one or more compute nodes in this compute node cluster. In other words, a tenant's cloud phone cluster can be deployed on one compute node or across multiple compute nodes.

[0051] Further, Figure 2 is a structural diagram of the cloud management platform provided in the embodiment of this application. As shown in Figure 2, the cloud management platform may include a cloud phone cluster management component, a test case management component, and a test case execution component. The functions of the cloud phone cluster management component include: (1) creating a cloud phone cluster for the tenant under the tenant's instruction and deploying a dedicated operating system (OS) for each cloud phone in the cloud phone cluster; (2) configuring an elastic scaling strategy for the cloud phone cluster under the tenant's instruction, and subsequently expanding or shrinking the cloud phone cluster based on the elastic scaling strategy; (3) releasing the cloud phone cluster or the cloud phones in the cloud phone cluster as needed. The functions of the test case management component include: (1) creating multiple test cases associated with the tenant's application under the tenant's instruction, and these multiple test cases contain certain relevant parameters; (2) allowing the tenant to select one or more test cases to be executed from the multiple test cases that have been created. The functions of the test case execution component include: (1) under the call of the test case management component, the test cases to be executed can be determined, and the cloud mobile phone cluster management component can be requested to execute these test cases; (2) the cloud mobile phone obtained by the request can be controlled to execute these test cases according to a certain execution strategy, and the test results can be returned to the test case management component for further provision to the tenant.

[0052] Furthermore, the cloud phone cluster management component supports the creation of multiple cloud phone clusters by the same tenant, meaning it supports the creation of multiple simulation environments by the same tenant. In addition, the component supports elastic scaling of cloud phone clusters, allowing users to add or remove cloud phones. It also provides scaling interfaces to other components, enabling other tenants to use these interfaces to scale the cloud phone clusters. Moreover, the component can release cloud phone clusters, but this requires all cloud phones in the cluster to be idle before releasing the entire cluster and simultaneously deleting all cloud phones. Furthermore, the component supports tenants uploading images of cloud phone clusters and operating systems for cloud phones, and uses these images to create cloud phone clusters and their respective operating systems, such as Android or HarmonyOS.

[0053] Furthermore, for the test case management component, it supports tenants uploading parameters (e.g., test case variables, test case constants, and the operating system type matched by the test cases) for multiple test cases belonging to the tenant's application (or project), and creating these multiple test cases based on these parameters. In addition, the test case management component also supports tenants specifying one or more test cases to be executed and uploading execution strategies for these test cases, and instructing the test case execution component to request cloud phones from the cloud phone cluster management component that can execute these test cases. This allows the test case execution component to instruct these cloud phones to execute these test cases according to the execution strategies (e.g., the timing, frequency, and number of times to execute these test cases), obtaining the test results. Furthermore, it can return the test results of these test cases to the tenant.

[0054] Furthermore, the test case execution component can be invoked by the test case management component to request cloud phones from the cloud phone cluster management component that can execute these test cases. After obtaining the cloud phones, the test case execution component can call the test case execution plugins of these cloud phones via Android command-line tools (Android Debug Bridge, ADB), HarmonyOS device connector (HDC), and application programming interfaces (APIs). This allows the cloud phones to execute the test cases according to the execution strategy and return the test results to the test case execution component. The test case execution component can also return the test results to the test case management component. Finally, after executing the test cases, the test case execution component can also invoke the cloud phone cluster management component to release the corresponding cloud phones.

[0055] Furthermore, for a tenant's cloud phone cluster, each cloud phone in the cluster can be a virtual instance in the infrastructure. For example, these virtual instances can be virtual machines (VMs) created on physical servers by the cloud management platform using virtualization technology. Alternatively, these virtual instances can be containers (Docker) created on physical servers by the cloud management platform using virtualization technology. Or, these virtual instances can be micro virtual machines (microVMs) created on physical servers by the cloud management platform using virtualization technology, and so on.

[0056] Furthermore, for a tenant's cloud phone cluster, multiple cloud phone computing nodes in the cloud phone cluster can be deployed in the same site or different sites. The site can be presented in various forms, such as a region in the infrastructure, an availability zone in the infrastructure, a data center (DC) in the infrastructure, a room in the infrastructure, a rack in the infrastructure, etc.

[0057] Based on the aforementioned cloud service system, when a tenant needs to test its application, it can send an application test request to the cloud management platform. Since the application test request specifies the test cases associated with the tenant's application and the execution strategy for these test cases, the cloud management platform can select cloud phones from the tenant's cloud phone cluster capable of executing these test cases and instruct these cloud phones to execute the test cases according to the execution strategy, thereby obtaining the test results. Therefore, tenants can complete application testing using cloud phones provided by the cloud management platform, eliminating the need for tenants to purchase additional engineering machines. This reduces the resource costs required for application testing. Furthermore, during application testing, the tenant only needs to send an application test request to the cloud management platform, which automatically calls upon the cloud phones to complete the application test, requiring no additional action from the tenant, thus reducing the manual costs associated with application testing. To further understand the workflow of the aforementioned cloud service platform, the following description, in conjunction with Figure 3, illustrates this workflow. Figure 3 is a flowchart illustrating an application testing method based on a cloud management platform provided in this application embodiment. As shown in Figure 3, this method can be implemented through the cloud service system shown in Figure 1. The cloud service system includes infrastructure that provides cloud services to tenants and a cloud management platform that manages this infrastructure. This infrastructure includes cloud phone clusters created by the cloud management platform for tenants. The method includes:

[0058] 301. The cloud management platform receives application test requests sent by tenants through the test interface. The application test request is used to indicate the first test case associated with the tenant's application and the execution strategy for the first test case.

[0059] In this embodiment, when a tenant needs to test its application, the cloud management platform can provide a testing interface to the tenant's client (e.g., a test request input field on the tenant's interface). The tenant can then input an application test request for its application into the testing interface through its client. In this way, the cloud management platform can receive the application test request sent by the tenant through its client via the testing interface. It is worth noting that this application test request is used to indicate the first test case associated with the tenant's application, and the execution strategy for the first test case. The number of first test cases can be one or more, and each first test case can refer to one or more functions to be tested in the tenant's application. The execution strategy for the first test case can include the conditions specified by the tenant for executing the first test case, etc.

[0060] For example, as shown in Figure 4 (Figure 4 is a schematic diagram of application testing provided in an embodiment of this application), when a tenant needs to test a music software, the tenant can first log in to the cloud management platform. The test case management component of the cloud management platform can provide the tenant with a tenant interface, which includes an application test request input field. The tenant can then input an application test request for the music software into the application test request input field, so that the test case management component receives the application test request for the music software through the application test request input field. The application test request for the music software is used to indicate the test case 1 associated with the music software, and the execution strategy for the test case. The test case 1 could be the music playback function of the music software, etc.

[0061] Specifically, before sending an application test request to the cloud management platform, the tenant can also perform the following operations:

[0062] When a tenant needs to create a dedicated cloud phone cluster, the cloud management platform can provide a primary creation interface to the tenant's client (e.g., the cloud phone creation section on the tenant's interface). The tenant can then input a cloud phone creation request for the cluster into this primary creation interface through their client. In this way, the cloud management platform can receive the cloud phone creation request sent by the tenant through their client via the primary creation interface. It is worth noting that this cloud phone creation request indicates a fourth number of cloud phones (the size of this fourth number can be determined according to actual needs and is not limited here) and the operating system type of each cloud phone in the cluster.

[0063] Upon receiving the cloud phone creation request, the cloud management platform can parse it to determine the fourth number of cloud phones in the cluster and the operating system type of each phone. The platform can then directly create this fourth number of cloud phones and deploy the corresponding operating systems on them according to their operating system types (the operating system types of different cloud phones can be the same or different, without restriction). In this way, this fourth number of cloud phones can be considered a cloud phone cluster serving the tenant, i.e., a cloud phone cluster dedicated to the tenant.

[0064] As in the example above, as shown in Figure 5 (Figure 5 is a schematic diagram of cloud phone cluster creation provided in this application embodiment, and Figure 5 is drawn based on Figure 4), before the tenant sends an application test request for the music software to the cloud management platform, the tenant can first create a cloud phone cluster dedicated to the tenant. Therefore, the tenant can first log in to the cloud management platform. The cloud phone cluster management component of the cloud management platform can provide the tenant with a tenant interface, which includes a cloud phone creation field. Then, the tenant can input a cloud phone creation request for simulation environment 1 (i.e., cloud phone cluster 1) into the cloud phone creation field, so that the cloud phone cluster management component can receive the cloud phone creation request for simulation environment 1 through the cloud phone creation field. The cloud phone creation request for simulation environment 1 is used to indicate the number n (n is a positive integer greater than or equal to 2) of cloud phones contained in simulation environment 1, and the type of operating system of these n cloud phones. For example, the operating system of cloud phone 1 is HarmonyOS single-frame operating system, the operating system of cloud phone 2 is HarmonyOS dual-frame operating system, ..., and the operating system of cloud phone n is Android operating system.

[0065] The cloud phone cluster management component can then parse the cloud phone creation request for simulation environment 1 to determine the number n of cloud phones contained in simulation environment 1 and the operating system type of these n cloud phones. Then, the cloud phone cluster management component can create cloud phones 1 to n, and according to the operating system type of these n cloud phones, deploy the HarmonyOS single-framework operating system in cloud phone 1, the HarmonyOS dual-framework operating system in cloud phone 2, ..., and the Android operating system in cloud phone n.

[0066] More specifically, before sending an application test request to the cloud management platform, the tenant can also perform the following operations:

[0067] When a tenant needs to create test cases for its application, the cloud management platform can provide a second creation interface to the tenant's client (e.g., a test case creation section on the tenant's interface). The tenant can then input a test case creation request for its application into the second creation interface through its client. In this way, the cloud management platform can receive the test case creation request sent by the tenant through the client via the second creation interface. It is worth noting that this test case creation request indicates the parameters of multiple second test cases associated with the tenant's application. For any one of these multiple second test cases, the parameters include the variables, constants, and the type of operating system matching the second test case, etc. Furthermore, the first test case specified by the tenant is one or more second test cases selected by the tenant from among the multiple second test cases; that is, the multiple second test cases include the first test case.

[0068] Upon receiving the test case creation request, the cloud management platform can parse it to obtain parameters for multiple second test cases. Based on these parameters, the platform can then create and save multiple second test cases. Understandably, when a tenant needs to test its application, the cloud management platform can display these multiple second test cases associated with the tenant's application through the application testing interface. The tenant can then select a first test case from these options, generate a corresponding application testing request, and send the request to the cloud management platform via the application testing interface.

[0069] As in the example above, as shown in Figure 6 (Figure 6 is a schematic diagram of test case creation provided in this application embodiment, and Figure 6 is drawn based on Figure 4), before the tenant sends an application test request for the music software to the cloud management platform, the tenant can first create multiple test cases for the music software. Therefore, the tenant can first log in to the cloud management platform. The test case management component of the cloud management platform can provide a tenant interface, which includes a test case creation bar. Then, the tenant can input a test case creation request for the music software into the test case creation bar, so that the test case management component can receive the test case creation request for the music software through the test case creation bar. The test case creation request is used to indicate the parameters of test case 1 (e.g., the music playback function of the music software), the parameters of test case 2 (e.g., the music sharing function of the music software), ..., the parameters of test case m (e.g., the music video viewing function of the music software). It should be noted that for any test case parameter of this music software, the test case parameter includes the test case variable, the test case constant, and the type of operating system to which the test case is adapted, etc. This music software may share the test case parameter with other music software, or it may not share the test case parameter; there are no restrictions here.

[0070] Then, the test case management component can parse the test case creation request to obtain the parameters of test case 1, the parameters of test case 2 of the music software, ..., the parameters of test case m of the music software. Based on these parameters, the test case management component can create test cases 1 to m of the music software and save test cases 1 to m of the music software.

[0071] It should be understood that the first creation interface and the second creation interface involved in this embodiment can be the same creation interface or different creation interfaces. That is to say, the tenant can send cloud phone creation request and test case creation request to the cloud management platform at the same time, or send cloud phone creation request and test case creation request to the cloud management platform one after the other. There is no restriction here.

[0072] 302. Based on the application test request, the cloud management platform selects the first cloud phone from the cloud phone cluster that can execute the first test case.

[0073] Upon receiving an application testing request for a tenant's application, the cloud management platform can determine the first test case to be executed and the execution strategy for that first test case based on the request. Then, the cloud management platform can select a first cloud phone from the cloud phone cluster serving the tenant that can execute the first test case. It should be noted that the first cloud phone capable of executing the first test case typically refers to a cloud phone whose operating system type matches the first test case; that is, the operating system type of the first cloud phone is compatible with the first test case, and therefore it can execute the first test case.

[0074] Specifically, the cloud management platform can identify the first cloud phone in the following ways:

[0075] Since the application test request is also used to indicate the first number of cloud phones specified by the tenant to execute the first test case, after receiving the application test request, the cloud management platform can parse the application test request to determine the first test case to be executed, the execution strategy for the first test case, and the first number of cloud phones required to execute the first test case.

[0076] Next, the cloud management platform can determine a second number of second cloud phones from the cloud phone cluster serving the tenant that can execute the first test case. It should be noted that since the cloud phone cluster contains a fourth number of cloud phones, the cloud management platform can select a second number of second cloud phones from the fourth number of cloud phones that can execute the first test case. It is understood that the second number is usually less than the fourth number.

[0077] Since the tenant has specified a first number of cloud phones to execute the first test case, the cloud management platform can compare the size between the first number and the second number.

[0078] If the second quantity is greater than or equal to the first quantity, it means that the number of second cloud phones is sufficient. Therefore, the cloud management platform can select the first quantity of first cloud phones that can ultimately execute the first test case from the second quantity of second cloud phones.

[0079] If the second number is less than the first number, it means that the number of second cloud phones is insufficient. Therefore, the cloud management platform adds a third number of third cloud phones capable of executing the first test case to the cloud phone cluster, thereby completing the real-time expansion of the cloud phone cluster. Then, the cloud management platform selects the final first number of first cloud phones capable of executing the first test case from the second and third number of second and third cloud phones. It can be understood that the sum of the second and third numbers is greater than or equal to the first number.

[0080] As in the example above, as shown in Figure 4, an application test request for the music software is obtained. The test case management component of the cloud management platform can parse the application test request to determine the information such as the tenant needs to execute test case 1 for the music software, the execution strategy for test case 1, and the number of cloud phones required to execute test case 1.

[0081] The test case management component can then send this information to the test case execution component, causing the execution component to send a cloud phone request to the cloud phone cluster management component. This request indicates the tenant's cloud phone cluster identifier, test case 1, and that the number of cloud phones required to execute test case 1 is 1. Based on this request, the cloud phone cluster management component can determine from the tenant's cloud phone cluster whether cloud phone 1 or cloud phone 2 can execute test case 1 (assuming test case 1 requires a cloud phone running HarmonyOS to execute). Since there are two cloud phones that can execute test case 1, it means there are enough cloud phones available. Therefore, the cloud phone cluster management component can randomly select cloud phone 1 as the final cloud phone to execute test case 1 and return a list of cloud phones containing cloud phone 1 to the test case execution component.

[0082] 303. The cloud management platform instructs the first cloud phone to execute the first test case according to the execution strategy indicated by the application test request, and obtains the test results of the first test case.

[0083] Once the primary cloud phone is identified, the cloud management platform can control it to execute the first test case according to the execution strategy for that test case, thereby obtaining the test results and returning them to the tenant. This satisfies the tenant's testing needs for their application.

[0084] Specifically, the cloud management platform can instruct the first cloud phone to execute the first test case in the following ways:

[0085] Since the execution strategy defined by the tenant for the first test case includes one or more of the following information: the time of execution of the first test case, the period of execution of the first test case, and the number of times the first test case is executed, the cloud management platform instructs the first cloud phone to execute the first test case according to one or more of the following information: the time of execution of the first test case (e.g., the current time or a time after the current time), the period of execution of the first test case (e.g., the period refers to the time interval between two consecutive executions of the first test case, which can be minutes, hours, days, weeks, etc.), and the number of times the first test case is executed (e.g., the number of times the first test case needs to be executed in total), thereby obtaining the test result of the first test case.

[0086] As in the example above, as shown in Figure 4, after the test case execution component receives the list of cloud phones returned by the cloud phone cluster management component, it can determine that cloud phone 1 needs to execute test case 1 of the music software. Therefore, the test case execution component can send a test case execution request to the test case execution plugin of cloud phone 1 through ADB channel, HDC channel, and API. This request is used to indicate the execution strategy and other information for test case 1. Based on this request, the test case execution plugin of cloud phone 1 can execute test case 1 according to the time, period, and number of times to execute test case 1 contained in the execution strategy, thereby obtaining the test result of test case 1 and returning the test result of test case 1 to the test case execution component. In turn, the test case execution component returns the test result of test case 1 to the test case management component, which then returns the test result of test case 1 to the tenant for use.

[0087] In addition, after obtaining and returning the test results of test case 1, the test case execution component can call the cloud phone cluster management component to release cloud phone 1.

[0088] More specifically, the cloud management platform can also perform the following operations:

[0089] In the cloud phone creation request sent by the tenant to the cloud management platform, the request can also be used to instruct the tenant on the elastic scaling policy for the cloud phone cluster. This elastic scaling policy includes expansion and contraction conditions for the cloud phone cluster. The cloud management platform can then monitor the tenant's cloud phone cluster in real time to determine whether the cloud phone cluster containing a fourth number of cloud phones meets the expansion or contraction conditions.

[0090] If the cloud phone cluster is determined to meet the expansion conditions (for example, the resource utilization rate of the cloud phones in the cloud phone cluster (including computing resource utilization rate, storage resource utilization rate, or network resource utilization rate, etc.) is greater than the upper limit of the utilization rate threshold, or the number of cloud phones in the cloud phone cluster that are in an idle state is less than the lower limit of idleness, etc.), the cloud management platform will add new cloud phones to the cloud phone cluster, so that the expanded cloud phone cluster contains a fifth number of cloud phones, and the fifth number is greater than the fourth number.

[0091] If the cloud phone cluster meets the scaling-down conditions (for example, the resource utilization rate of the cloud phones in the cloud phone cluster is less than the lower limit of utilization, or the number of idle cloud phones in the cloud phone cluster is greater than or equal to the upper limit of idle, etc.), the cloud management platform deletes cloud phones from the cloud phone cluster so that the scaled-down cloud phone cluster contains a sixth number of cloud phones, and the sixth number is greater than the fourth number.

[0092] In this embodiment, when a tenant needs to test its application, it can send an application test request to the cloud management platform. Since the application test request indicates the first test case associated with the tenant's application and the execution strategy for the first test case, the cloud management platform can select a first cloud phone from the tenant's cloud phone cluster capable of executing the first test case, and instruct the first cloud phone to execute the first test case according to the execution strategy, thereby obtaining the test result of the first test case. In the aforementioned process, the tenant can complete the testing of its application using the cloud phone provided by the cloud management platform (i.e., the aforementioned first cloud phone). This eliminates the need for the tenant to purchase additional engineering machines, reducing the resource costs required for application testing. Furthermore, during application testing, the tenant only needs to send an application test request to the cloud management platform, which will automatically call the cloud phone to complete the application test without requiring additional operation from the tenant, further reducing the labor costs for application testing.

[0093] Furthermore, in this embodiment of the application, the tenant can create a cloud phone cluster in the cloud through the cloud management platform. Multiple cloud phones in the cloud phone cluster can simulate engineering machines or smartphones with different operating systems. Since these cloud phones are deployed in the same cluster, it is beneficial for the tenant to perform unified management through the cloud management platform (e.g., creation, deletion, expansion, reduction, etc.), thereby improving the efficiency of resource management.

[0094] Furthermore, in this embodiment of the application, the tenant can call the cloud phone in the cloud phone cluster through the cloud management platform to complete the application test. The application test process only requires the tenant to issue a request, and the entire process does not require any other operations from the tenant, which can realize the automated process of application testing and help improve the efficiency of application testing.

[0095] The above is a detailed description of the application testing method based on a cloud management platform provided in the embodiments of this application. The cloud management platform provided in the embodiments of this application will be described below. Figure 7 is a structural schematic diagram of the cloud management platform provided in the embodiments of this application. As shown in Figure 7, the cloud management platform is used to manage the infrastructure providing cloud services. The infrastructure includes a cloud phone cluster created by the cloud management platform for tenants. The cloud management platform includes:

[0096] The first receiving module 701 is used to receive an application test request sent by a tenant through a test interface. The application test request is used to indicate a first test case associated with the tenant's application and an execution strategy for the first test case. For example, the first receiving module 701 is used to implement step 301 in the embodiment shown in FIG3.

[0097] Selection module 702 is used to select a first cloud phone from the cloud phone cluster that can execute the first test case based on the application test request; for example, selection module 702 is used to implement step 303 in the embodiment shown in Figure 3.

[0098] The execution module 703 is used to instruct the first cloud phone to execute the first test case according to the execution strategy indicated by the application test request, and obtain the test results of the first test case. For example, the execution module 703 is used to implement step 303 in the embodiment shown in Figure 3.

[0099] In one possible implementation, the application test request is further used to indicate a first number of cloud phones executing the first test case. The selection module is used to: determine a second number of second cloud phones from the cloud phone cluster that can execute the first test case; if the second number is greater than or equal to the first number indicated by the application test request, select a first number of first cloud phones that can execute the first test case from the second number of second cloud phones; if the second number is less than the first number, add a third number of third cloud phones that can execute the first test case to the cloud phone cluster, and select a first number of first cloud phones that can execute the first test case from the second number of second cloud phones and the third number of third cloud phones, wherein the sum of the second number and the third number is greater than or equal to the first number.

[0100] In one possible implementation, the first cloud phone capable of executing the first test case includes a cloud phone whose operating system type matches the first test case.

[0101] In one possible implementation, the execution strategy includes at least one of the following: the time of execution of the first test case, the period of execution of the first test case, and the number of times the first test case is executed; and the execution module is used to instruct the first cloud phone to execute the first test case according to at least one of the time, period, and number of times indicated by the application test request, and to obtain the test result of the first test case.

[0102] In one possible implementation, the cloud management platform further includes: a second receiving module, configured to receive a cloud phone creation request sent by a tenant through a first creation interface, the cloud phone creation request indicating a fourth number of cloud phones included in the cloud phone cluster, and the type of operating system of the cloud phones included in the cloud phone cluster; and a first creation module, configured to create a fourth number of cloud phones based on the cloud phone creation request, and deploy an operating system in the fourth number of cloud phones according to the type, the fourth number of cloud phones constituting a cloud phone cluster.

[0103] In one possible implementation, the cloud phone creation request is also used to indicate the scaling-up and scaling-down conditions for the cloud phone cluster. The cloud management platform also includes: a scaling-up module, used to add cloud phones to the cloud phone cluster if the cloud phone cluster meets the scaling-up conditions, so that the cloud phone cluster contains a fifth number of cloud phones, the fifth number being greater than the fourth number; and a scaling-down module, used to delete cloud phones from the cloud phone cluster if the cloud phone cluster meets the scaling-down conditions, so that the cloud phone cluster contains a sixth number of cloud phones, the sixth number being greater than the fourth number.

[0104] In one possible implementation, the cloud management platform further includes: a third receiving module, used to receive a test case creation request sent by a tenant through a second creation interface, the test case creation request indicating parameters of multiple second test cases associated with the application, the parameters including the type of operating system matching the multiple second test cases, the multiple second test cases including the first test case; and a second creation module, used to create multiple second test cases based on the parameters indicated by the test case creation request.

[0105] In one possible implementation, the first cloud phone includes any of the following: a virtual machine, a container, and a micro virtual machine.

[0106] It should be noted that the information interaction and implementation process between the modules / units of the above-mentioned device are based on the same concept as the method embodiments of this application, and the resulting technical effects are the same as those of the method embodiments of this application. For details, please refer to the description in the method embodiments shown above in the embodiments of this application, and will not be repeated here.

[0107] Please refer to Figure 8, which is a schematic diagram of a computing device provided in an embodiment of this application. As shown in Figure 8, the computing device 800 (which can be used to present the aforementioned cloud management platform) includes: a processor 801, a memory 802, a communication interface 803, and a bus 804. The processor 801, the memory 802, and the communication interface 803 are coupled through the bus (not labeled in the figure). The memory 802 stores instructions. When the execution instructions in the memory 802 are executed, the computing device 800 executes the method performed by the cloud management platform in the above method embodiment.

[0108] The computing device 800 may be one or more integrated circuits configured to implement the methods described above, such as: one or more application-specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these forms of integrated circuits. Furthermore, when the units in the device can be implemented in the form of a processing element scheduler, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor capable of calling programs. Alternatively, these units may be integrated together to implement a system-on-a-chip (SOC).

[0109] The processor 801 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0110] The memory 802 can be volatile memory or non-volatile memory, or it can include both. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0111] The memory 802 stores executable program code, and the processor 801 executes this executable program code to implement the functions of the aforementioned first receiving module, selection module, and execution module, thereby realizing the application testing method based on the cloud management platform. That is, the memory 802 stores instructions for executing the aforementioned application testing method based on the cloud management platform.

[0112] The communication interface 803 uses transceiver modules, such as, but not limited to, network interface cards and transceivers, to enable communication between the computing device 800 and other devices or communication networks.

[0113] In addition to the data bus, the 804 bus can also include a power bus, a control bus, and a status signal bus. The bus can be a Peripheral Component Interconnect Express (PCIe) bus, an Extended Industry Standard Architecture (EISA) bus, a Unified Bus (Ubus or UB), a Compute Express Link (CXL) bus, a Cache Coherent Interconnect for Accelerators (CCIX) bus, etc. The bus can be divided into address bus, data bus, and control bus.

[0114] Please refer to Figure 9, which is a schematic diagram of a computing device cluster provided in an embodiment of this application. As shown in Figure 9, the computing device cluster 900 includes at least one computing device 800.

[0115] As shown in Figure 9, the computing device cluster 900 includes at least one computing device 800. The memory 802 of one or more computing devices 800 in the computing device cluster 900 may store the same instructions for executing the application testing method based on the cloud management platform described above.

[0116] In some possible implementations, the memory 802 of one or more computing devices 800 in the computing device cluster 900 may also store partial instructions for executing the application testing method based on the cloud management platform described above. In other words, a combination of one or more computing devices 800 can jointly execute the application testing method based on the cloud management platform described above.

[0117] It should be noted that the memory 802 in different computing devices 800 within the computing device cluster 900 can store different instructions, each used to execute a portion of the functions of the aforementioned cloud management platform. That is, the instructions stored in the memory 802 of different computing devices 800 can implement the functions of one or more modules, such as the first receiving module, the selection module, and the execution module.

[0118] In some possible implementations, one or more computing devices 800 in the computing device cluster 900 can be connected via a network. This network can be a wide area network (WAN) or a local area network (LAN), etc.

[0119] Please refer to Figure 10, which is a schematic diagram of computer devices in a computer cluster provided in this application embodiment being connected via a network. As shown in Figure 10, two computing devices 800A and 800B are connected via a network. Specifically, they are connected to the network through the communication interfaces in each computing device.

[0120] In one possible implementation, the memory in computing device 800A stores instructions for performing the functions of modules such as the first receiving module. Meanwhile, the memory in computing device 800B stores instructions for performing the functions of modules such as the selection module and the execution module.

[0121] It should be understood that the functions of computing device 800A shown in Figure 10 can also be performed by multiple computing devices. Similarly, the functions of computing device 800B can also be performed by multiple computing devices.

[0122] This application also relates to a computer storage medium storing a program for signal processing, which, when run on a computer, causes the computer to perform the steps executed by the cloud management platform in the embodiment shown in FIG3.

[0123] This application also relates to a computer program product that stores instructions that, when executed by a computer, cause the computer to perform the steps performed by the cloud management platform in the embodiment shown in FIG3.

[0124] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0125] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0126] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0127] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0128] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. An application testing method based on a cloud management platform, characterized in that, The cloud management platform is used to manage the infrastructure that provides cloud services, the infrastructure including a cloud phone cluster created by the cloud management platform for the tenant, and the method includes: The cloud management platform receives application test requests sent by the tenant through a test interface. The application test requests are used to indicate a first test case associated with the tenant's application and an execution strategy for the first test case. Based on the application test request, the cloud management platform selects a first cloud phone from the cloud phone cluster that can execute the first test case; The cloud management platform instructs the first cloud phone to execute the first test case according to the execution strategy indicated by the application test request, and obtains the test result of the first test case.

2. The method according to claim 1, characterized in that, The application test request is further used to indicate a first number of cloud phones executing the first test case. Based on the application test request, the cloud management platform selects a first cloud phone from the cloud phone cluster capable of executing the first test case, including: The cloud management platform determines a second number of second cloud phones from the cloud phone cluster that can execute the first test case; If the second quantity is greater than or equal to the first quantity indicated by the application test request, the cloud management platform selects a first quantity of first cloud phones from the second quantity of second cloud phones that can execute the first test case; If the second quantity is less than the first quantity, the cloud management platform adds a third quantity of third cloud phones capable of executing the first test case to the cloud phone cluster, and selects a first quantity of first cloud phones capable of executing the first test case from the second quantity of second cloud phones and the third quantity of third cloud phones, wherein the sum of the second quantity and the third quantity is greater than or equal to the first quantity.

3. The method according to claim 1 or 2, characterized in that, The first cloud phone capable of executing the first test case includes a cloud phone whose operating system type matches the first test case.

4. The method according to any one of claims 1 to 3, characterized in that, The execution strategy includes at least one of the following: the timing of executing the first test case, the period for executing the first test case, and the number of times the first test case is executed. The cloud management platform instructs the first cloud phone to execute the first test case according to the execution strategy indicated by the application test request, and the test results of the first test case include: The cloud management platform instructs the first cloud phone to execute the first test case at at least one of the time, period, and number of times indicated by the application test request, and obtain the test result of the first test case.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: The cloud management platform receives a cloud phone creation request sent by the tenant through a first creation interface. The cloud phone creation request is used to indicate the fourth number of cloud phones included in the cloud phone cluster, and the type of operating system of the cloud phones included in the cloud phone cluster. The cloud management platform creates the fourth number of cloud phones based on the cloud phone creation request, and deploys an operating system on the fourth number of cloud phones according to the type. The fourth number of cloud phones constitute the cloud phone cluster.

6. The method according to claim 5, characterized in that, The cloud phone creation request is also used to indicate the scaling-up and scaling-down conditions for the cloud phone cluster, and the method further includes: If the cloud phone cluster meets the expansion conditions, the cloud management platform adds cloud phones to the cloud phone cluster so that the cloud phone cluster contains a fifth number of cloud phones, the fifth number being greater than the fourth number; If the cloud phone cluster meets the scaling-down condition, the cloud management platform deletes cloud phones from the cloud phone cluster so that the cloud phone cluster contains a sixth number of cloud phones, which is greater than the fourth number.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: The cloud management platform receives a test case creation request sent by the tenant through a second creation interface. The test case creation request is used to indicate parameters of multiple second test cases associated with the application. The parameters include the type of operating system that matches the multiple second test cases. The multiple second test cases include the first test case. The cloud management platform creates the plurality of second test cases based on the parameters indicated by the test case creation request.

8. The method according to any one of claims 1 to 7, characterized in that, The first cloud phone includes any of the following: virtual machine, container, and micro virtual machine.

9. A cloud management platform, characterized in that, The cloud management platform is used to manage the infrastructure that provides cloud services. The infrastructure includes a cloud phone cluster created by the cloud management platform for the tenant. The cloud management platform includes: The first receiving module is configured to receive an application test request sent by the tenant through a test interface. The application test request is used to indicate a first test case associated with the tenant's application and an execution strategy for the first test case. The selection module is used to select a first cloud phone from the cloud phone cluster that can execute the first test case based on the application test request. The execution module is used to instruct the first cloud phone to execute the first test case according to the execution strategy indicated by the application test request, and to obtain the test result of the first test case.

10. The cloud management platform according to claim 9, characterized in that, The application test request is also used to indicate a first number of cloud phones executing the first test case, and the selection module is used to: From the cloud phone cluster, determine a second number of second cloud phones capable of executing the first test case; If the second quantity is greater than or equal to the first quantity indicated by the application test request, select a first quantity of first cloud phones from the second quantity of second cloud phones that can execute the first test case; If the second quantity is less than the first quantity, add a third quantity of third cloud phones capable of executing the first test case to the cloud phone cluster, and select a first quantity of first cloud phones capable of executing the first test case from the second quantity of second cloud phones and the third quantity of third cloud phones, wherein the sum of the second quantity and the third quantity is greater than or equal to the first quantity.

11. The cloud management platform according to claim 9 or 10, characterized in that, The first cloud phone capable of executing the first test case includes a cloud phone whose operating system type matches the first test case.

12. The cloud management platform according to any one of claims 9 to 11, characterized in that, The execution strategy includes at least one of the following: the time of execution of the first test case, the period of execution of the first test case, and the number of times the first test case is executed. The execution module is used to instruct the first cloud phone to execute the first test case according to at least one of the time, the period, and the number of times indicated by the application test request, and to obtain the test result of the first test case.

13. The cloud management platform according to any one of claims 9 to 12, characterized in that, The cloud management platform also includes: The second receiving module is used to receive a cloud phone creation request sent by the tenant through the first creation interface. The cloud phone creation request is used to indicate the fourth number of cloud phones included in the cloud phone cluster, and the type of operating system of the cloud phones included in the cloud phone cluster. The first creation module is used to create the fourth number of cloud phones based on the cloud phone creation request, and to deploy an operating system in the fourth number of cloud phones according to the type, wherein the fourth number of cloud phones constitute the cloud phone cluster.

14. The cloud management platform according to claim 13, characterized in that, The cloud phone creation request is also used to indicate the scaling-up and scaling-down conditions for the cloud phone cluster, and the cloud management platform further includes: The expansion module is used to add cloud phones to the cloud phone cluster if the cloud phone cluster meets the expansion conditions, so that the cloud phone cluster contains a fifth number of cloud phones, the fifth number being greater than the fourth number. The scaling-down module is used to delete cloud phones from the cloud phone cluster if the cloud phone cluster meets the scaling-down conditions, so that the cloud phone cluster contains a sixth number of cloud phones, the sixth number being greater than the fourth number.

15. The cloud management platform according to any one of claims 9 to 14, characterized in that, The cloud management platform also includes: The third receiving module is configured to receive a test case creation request sent by the tenant through the second creation interface. The test case creation request is used to indicate parameters of a plurality of second test cases associated with the application. The parameters include the type of operating system that matches the plurality of second test cases. The plurality of second test cases include the first test case. The second creation module is used to create the plurality of second test cases based on the parameters indicated by the test case creation request.

16. The cloud management platform according to any one of claims 9 to 15, characterized in that, The first cloud phone includes any of the following: virtual machine, container, and micro virtual machine.

17. A computing device cluster, characterized in that, The computing device cluster includes at least one computing device, each computing device including a processor and memory: The memory is used to store instructions; The processor is configured to, according to the instructions, cause the computing device cluster to perform the method of any one of claims 1 to 8.

18. A computer storage medium, characterized in that, The computer storage medium stores one or more instructions that, when executed by one or more computers, cause the one or more computers to perform the method of any one of claims 1 to 8.

19. A computer program product, characterized in that, The computer program product stores instructions that, when executed by a computer, cause the computer to perform the method described in any one of claims 1 to 8.

Images