Quality testing method, device and equipment for multi-tenant system

Abstract

The invention provides a quality testing method, device and equipment for a multi-tenant system, and relates to the technical field of multi-tenant system testing.The method comprises the steps that a corresponding metadata combination is obtained when a user operates in the multi-tenant system; determining a meta operation scene according to the metadata combination; generating a scenarized test case according to the meta-operation scene; and performing quality testing on the multi-tenant system according to the scenarized test case. According to the method provided by the embodiment of the invention, the real-time quality test of the user operation scene is realized, the quality test of the multi-tenant system is accurately and timely completed, and the performance and safety of the multi-tenant system are effectively improved; and quality guarantee difficulties and pain points caused by high complexity of an actual business scene of a customer and opaqueness of an actual use scene of the customer are solved.

Description

Technical Field

[0001] The present invention relates to the technical field of multi-tenant system testing, and in particular to a quality testing method, device and equipment for a multi-tenant system. Background Art

[0002] The multi-tenancy of Software as a Service (SaaS) system is a tenant system driven by metadata. Due to the particularity of its technical implementation and the diversity of customer-oriented services, it is characterized by high business complexity and flexible configuration features.

[0003] In the related technologies, the quality assurance methods of multi-tenant systems, including unit testing, application programming interface (API) testing, user interface (UI) testing and other verification methods, cannot meet the high-level business characteristics and cannot achieve effective and comprehensive quality assurance. If you want to achieve coverage that meets the expected requirements of all customer business scenarios, you need to exhaustively verify the business scenarios used by all customers, but the actual operation scenarios of online customers are not transparent, and even if you invest a lot of resources, you cannot guarantee the effectiveness of regression. Summary of the invention

[0004] The present invention provides a quality testing method, device and equipment for a multi-tenant system, which realizes real-time quality testing of user operation scenarios, accurately and timely completes the quality testing of the multi-tenant system, effectively improves the performance and security of the multi-tenant system, and solves the quality assurance difficulties and pain points caused by the high complexity of customers' actual business scenarios and the opacity of customers' actual usage scenarios.

[0005] The present invention provides a quality testing method for a multi-tenant system, comprising the following steps.

[0006] Obtain the metadata combination corresponding to the business operations performed by users in the multi-tenant system; Determining a meta-operation scenario according to the metadata combination; Generate scenario-based test cases based on the meta-operation scenario; Perform quality testing on the multi-tenant system based on the scenario-based test cases.

[0007] According to a quality testing method for a multi-tenant system provided by the present invention, determining a meta-operation scenario according to the metadata combination includes: The meta-operation scenario is determined according to the metadata combination and a preset first correspondence relationship; wherein the preset first correspondence relationship includes a correspondence relationship between the metadata combination and the meta-operation scenario.

[0008] According to a quality testing method for a multi-tenant system provided by the present invention, generating scenario-based test cases according to the meta-operation scenario includes: Determine a plurality of atomic test cases according to the meta-operation scenario and a preset second correspondence relationship; wherein the preset second correspondence relationship includes a correspondence relationship between the meta-operation scenario and the atomic test case; The scenario-based test case is obtained according to the multiple atomic test cases.

[0009] According to a quality testing method for a multi-tenant system provided by the present invention, obtaining the scenario-based test case according to the atomic test case includes: The multiple atomic test cases are combined to obtain the scenario-based test cases.

[0010] According to a quality testing method for a multi-tenant system provided by the present invention, after obtaining the metadata combination corresponding to the business operation performed by the user in the multi-tenant system, the method further includes: determining the frequency of each metadata combination obtained; The execution order of each of the scenario-based test cases is determined according to the frequencies of each of the metadata combinations obtained.

[0011] According to a quality testing method for a multi-tenant system provided by the present invention, determining the execution order of each scenario-based test case according to the frequencies of each metadata combination obtained includes: The higher the frequency of acquiring the metadata combination, the higher the execution order priority of the scenario-based test case corresponding to the metadata combination.

[0012] According to a quality testing method for a multi-tenant system provided by the present invention, the first corresponding relationship is obtained according to historical operation scenarios of users in the multi-tenant system and metadata corresponding to the historical operation scenarios.

[0013] The present invention also provides a quality testing device for a multi-tenant system, comprising the following modules: The acquisition module is used to obtain the metadata combination corresponding to the business operation performed by the user in the multi-tenant system; A determination module, used to determine a meta-operation scenario according to the metadata combination; A generation module, used to generate scenario-based test cases according to the meta-operation scenario; A testing module is used to perform quality testing on the multi-tenant system according to the scenario-based test cases.

[0014] The present invention also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, a quality testing method for a multi-tenant system as described above is implemented.

[0015] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a quality testing method for a multi-tenant system as described in any one of the above.

[0016] The present invention also provides a computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the quality testing method for a multi-tenant system as described in any one of the above is implemented.

[0017] The quality testing method, device and equipment of the multi-tenant system provided by the present invention realize real-time quality testing of user operation scenarios, accurately and timely complete the quality testing of the multi-tenant system, effectively improve the performance and security of the multi-tenant system, and solve the quality assurance difficulties and pain points caused by the high complexity of customers' actual business scenarios and the opacity of customers' actual usage scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0019] Figure 1 It is one of the schematic diagrams of the quality testing method of the multi-tenant system provided by the present invention.

[0020] Figure 2 This is the second schematic diagram of the quality testing method for a multi-tenant system provided by the present invention.

[0021] Figure 3 This is the third schematic diagram of the quality testing method for a multi-tenant system provided by the present invention.

[0022] Figure 4 This is the fourth schematic diagram of the quality testing method for a multi-tenant system provided by the present invention.

[0023] Figure 5 It is a schematic diagram of a quality testing device for a multi-tenant system provided by the present invention.

[0024] Figure 6 It is a structural schematic diagram of the electronic device provided by the present invention. DETAILED DESCRIPTION

[0025] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0026] Combine the following Figure 1-Figure 6 The present invention describes a method, apparatus and device for quality testing of a multi-tenant system.

[0027] In order to facilitate a clearer understanding of the technical solutions of the embodiments of the present application, some technical contents related to the embodiments of the present application are first introduced.

[0028] In a multi-tenant system (such as CRM) under the SaaS model, the system service provider can provide customers with a set of standard application systems and provide customers with personalized configuration capabilities to support business expansion. Due to the diversity of customer industries and the complexity of their businesses, the business scenarios used by customers under different tenants are intricate, resulting in the inability to accurately cover business scenarios that support different industries and all business fields in terms of quality assurance, and it is impossible to complete comprehensive quality assurance based on business scenarios.

[0029] SaaS supports multi-tenant mode. Due to the opacity of the actual business tenants' usage scenarios, and the dual blessing of high business complexity and flexible configuration features, relying solely on the business accumulation of personnel or the coverage of a single business scenario cannot cover all customer business usage. Once a situation cannot be covered, it may lead to omissions in scenario coverage and potential logical processing loopholes. Under the multi-tenant technical characteristics and complex business characteristics, the shortcomings of traditional quality assurance methods are: (1) Unit testing: It is impossible to verify the personalized configuration capabilities in a multi-tenant system.

[0030] (2) API testing: The API complexity is high in a multi-tenant system. The actual value generated in the API depends on the actual business scenarios that occur under the tenant, and it is impossible to simulate the input.

[0031] (3) Scenario-based testing: Scenarios based on a single point cannot guarantee comprehensiveness.

[0032] (4) Traffic replay: The technology involved is relatively complex. When tenant data is protected, the API and data used by customers cannot be obtained. In other words, the existing traffic replay technology requires obtaining the tenant API and replaying it. In fact, the data layer has sensitive characteristics, and it is impossible to obtain comprehensive and effective information from both the API and data levels.

[0033] Figure 1 It is one of the flow charts of the quality testing method of the multi-tenant system provided by the present invention, such as Figure 1 As shown, the method includes the following: Step 101: Obtain a metadata combination corresponding to a user's business operation in a multi-tenant system.

[0034] Specifically, in the related art, due to the sensitive nature of the data layer, it is impossible to fully and effectively determine which business scenarios the user is operating from both the API and data levels, and thus it is impossible to implement quality testing of multi-tenant systems based on business scenarios. For example, the log data of each customer is confidential and sensitive, and the maintenance and management of the SaaS system cannot directly obtain and use the log data of each customer, and thus it is impossible to fully and effectively determine which business scenarios the user is operating from, and thus it is impossible to implement quality testing of multi-tenant systems based on business scenarios.

[0035] In order to solve the above problems, in the embodiment of the present application, the metadata combination corresponding to the business operation performed by the user in the multi-tenant system is first obtained. That is, the metadata information of the SaaS system is not the real data of the customer, but a further abstraction of the data, and does not carry sensitive information. The user's operation scenario can be effectively carried through the metadata of the SaaS system and the combined record of the metadata. That is, in this application, based on the metadata information of the SaaS system, it is possible to effectively determine which business scenarios the user performs operations on, and it is also possible to implement quality testing of the multi-tenant system based on business scenarios. This avoids the problem that the API and data layers in the related technology have sensitive characteristics and cannot be directly obtained and used by the maintainers and managers of the SaaS system.

[0036] Step 102: Determine a meta-operation scenario based on the metadata combination.

[0037] Specifically, after obtaining the metadata combination corresponding to the business operation performed by the user in the multi-tenant system, the meta-operation scenario can be determined based on the metadata combination. Optionally, the meta-operation scenario is the scenario in which the user performs business operations in the multi-tenant system. Optionally, the meta-operation scenario includes a checkout business scenario, an approval business scenario, and the like. Optionally, each type of meta-operation scenario requires access to different metadata, that is, there is a corresponding relationship between the meta-operation scenario and the metadata, and thus based on the metadata accessed by the user, it is possible to determine which business operations the user performs. Optionally, the corresponding relationship between the business operation scenario and the metadata can be determined based on the metadata accessed corresponding to the user's business operation scenario in the historical period.

[0038] Step 103: Generate scenario-based test cases based on the meta-operation scenario.

[0039] Specifically, after determining the meta-operation scenario according to the metadata combination, the embodiment of the present application further generates scenario-based test cases according to the meta-operation scenario. That is, according to the user's real-time operation scenario, the corresponding scenario-based test cases are generated, which realizes the real-time quality test of the user's operation scenario, thereby accurately and timely completing the quality test of the multi-tenant system and improving the performance and security of the multi-tenant system.

[0040] Step 104: Perform quality testing on the multi-tenant system based on scenario-based test cases.

[0041] Specifically, after generating scenario-based test cases based on meta-operation scenarios, real-time quality testing of user operation scenarios can be achieved, thereby improving the quality, performance, stability and security of the multi-tenant system.

[0042] For example, Figure 2 As shown, this application collects the actual scenarios used by customers based on the business scenarios actually used by customers under different tenants, and analyzes the organization form of metadata under different usage scenarios based on certain metadata carriers. Finally, the corresponding atomic granularity test cases are retrieved through the parsed metadata, and multiple atomic test cases are dynamically combined into scenario-based use cases. The dynamic use case library can generate corresponding test cases in real time every day to complete the verification based on online customer usage scenarios, and realize a metadata-driven quality assurance method based on a multi-tenant system, effectively solving the quality assurance difficulties and pain points caused by the high complexity of customers' actual business scenarios and the opacity of customers' actual usage scenarios when customers use the system at the same time in the SaaS multi-tenant system.

[0043] In the method of the above embodiment, each type of meta-operation scenario needs to access different metadata, that is, there is a corresponding relationship between the meta-operation scenario and the metadata. Therefore, based on the metadata information of the SaaS system, it is possible to effectively determine which business scenarios the user is performing operations on. Moreover, the metadata information of the SaaS system is not the customer's real data, but a further abstraction of the data, and does not carry sensitive information. This can effectively avoid the problem that the API and data layers have sensitive characteristics and cannot be directly obtained and used by the maintainers and managers of the SaaS system. Furthermore, according to the real-time user operation scenarios, corresponding scenario-based test cases are generated, which realizes real-time quality testing of user operation scenarios, accurately and timely completes the quality testing of multi-tenant systems, effectively improves the performance and security of multi-tenant systems, and solves the quality assurance difficulties and pain points caused by the high complexity of customers' actual business scenarios and the opacity of customers' actual usage scenarios.

[0044] In one embodiment, determining a meta-operation scenario according to a metadata combination includes: According to the metadata combination and the preset first corresponding relationship, a meta-operation scenario is determined; wherein the preset first corresponding relationship includes a corresponding relationship between the metadata combination and the meta-operation scenario.

[0045] Specifically, in the embodiment of the present application, the meta-operation scenario is determined according to the metadata combination and the preset first correspondence relationship; wherein the preset first correspondence relationship includes the correspondence relationship between the metadata combination and the meta-operation scenario. Optionally, the first correspondence relationship can be established according to the historical operation scenarios of the user in the multi-tenant system and the metadata corresponding to the historical operation scenarios. Based on the first correspondence relationship, the meta-operation scenario corresponding to the current metadata combination can also be determined.

[0046] The method of the above embodiment can quickly and accurately determine the user's current business operation scenario based on the metadata combination and the preset first correspondence, and then generate scenario-based test cases based on the current business operation scenario, thereby realizing real-time quality testing of the user's operation scenario and improving the performance and security of the multi-tenant system.

[0047] In one embodiment, a scenario-based test case is generated according to a meta-operation scenario, including: Determine a plurality of atomic test cases according to the meta-operation scenario and the preset second corresponding relationship; wherein the preset second corresponding relationship includes a corresponding relationship between the meta-operation scenario and the atomic test case; Based on multiple atomic test cases, scenario-based test cases are obtained.

[0048] Specifically, in the embodiment of the present application, multiple atomic test cases are determined based on the meta-operation scenario and the preset second correspondence; wherein the preset second correspondence includes the correspondence between the meta-operation scenario and the atomic test case, thereby achieving rapid and accurate generation of scenario-based test cases, and efficiently realizing real-time quality testing of user operation scenarios.

[0049] In one embodiment, a scenario-based test case is obtained based on the atomic test case, including: Combine multiple atomic test cases to obtain scenario-based test cases.

[0050] Specifically, after a plurality of atomic test cases are determined according to the meta-operation scenario and the preset second corresponding relationship, the plurality of atomic test cases may be combined according to a preset rule or sequence to obtain scenario-based test cases corresponding to the meta-operation scenario.

[0051] For example, Figure 3 and Figure 4As shown, there is a mapping relationship between meta-operation scenarios and meta-test cases. When a meta-operation scenario is hit, the meta-test case will be retrieved from the use case baseline library through the mapping relationship. A metadata combination unit is composed of multiple operation scenarios. Each meta-entity operation scenario corresponds to an atomic test case. The retrieved multiple different atomic test cases will be spliced ​​by the dynamic generator to form dynamic test cases. These generated scenario-based dynamic test cases will be executed every day to form customer test case coverage, realize real-time quality testing of user operation scenarios, improve the coverage of multiple scenarios, and thus improve the quality, performance, stability and security of the multi-tenant system.

[0052] In one embodiment, after obtaining the metadata combination corresponding to the business operation performed by the user in the multi-tenant system, the method further includes: determining the frequency of each metadata combination obtained; According to the frequencies of the obtained metadata combinations, the execution order of each scenario-based test case is determined.

[0053] Specifically, after obtaining the metadata combination corresponding to the business operation performed by the user in the multi-tenant system, the frequency of each metadata combination obtained can be determined. For example, within one day, the number of times metadata combination a corresponding to business scenario A is obtained is 5 times, and the number of times metadata combination b corresponding to business scenario B is obtained is 3 times. Then, according to the frequency of each metadata combination obtained, the execution order of each scenario test case corresponding to each metadata combination is determined.

[0054] In one embodiment, determining the execution order of each scenario-based test case according to the frequencies of each metadata combination obtained includes: The higher the frequency of obtaining the metadata combination, the higher the execution order priority of the scenario-based test cases corresponding to the metadata combination.

[0055] Specifically, in the embodiment of the present application, the higher the frequency of obtaining metadata combinations, the higher the execution order priority of the scenario-based test cases corresponding to the metadata combinations. For example, within one day, the number of times metadata combination a corresponding to business scenario A is obtained is 5 times, and the number of times metadata combination b corresponding to business scenario B is obtained is 3 times, then the execution order priority of the test cases corresponding to business scenario B is higher than the execution order of the test cases corresponding to business scenario A, so that the business scenarios frequently used by users can be quality tested in a timely manner, effectively improving the performance and security of the multi-tenant system.

[0056] Exemplarily, in the customer usage scenarios under SaaS multi-tenancy, the frequency and frequency of user usage in different scenarios can be observed through the recorded metadata access volume. All system metadata for each scenario operation is parsed to form a metadata combination record, and all metadata information is clearly presented by classification. Obtain metadata information and metadata combination information used by online customers in real time, and effectively retrieve the meta-operation scenario corresponding to the metadata combination by retrieving the mapping relationship library between metadata combinations and entity meta-operation scenarios. Retrieve the relationship between meta-operation scenarios and atomic use cases, and retrieve the mapping relationship between each meta-operation scenario and atomic test case in the mapping relationship library between meta-operation scenarios and atomic test cases. The use case generator splices the atomic test cases to generate a combined scenario, and dynamically combines atomic test cases to achieve comprehensive coverage of business scenarios, realize real-time quality testing of user operation scenarios, and improve the performance and security of multi-tenant systems.

[0057] In the method of the above embodiment, the higher the frequency of obtaining metadata combinations, the higher the execution order priority of the scenario-based test cases corresponding to the metadata combinations, so that the business scenarios frequently used by users can be quality tested in a timely manner, effectively improving the performance and security of the multi-tenant system.

[0058] It should be noted that the existing technology verifies from the customer's input scenario. The customer scenario is singular. The system capabilities provided by the actual service provider are generally abstracted. A single instance cannot cover all actual uses on the customer side. The existing quality assurance methods and technical implementation methods such as traffic playback cannot be effectively implemented under the multi-tenant characteristics and multi-tenant data sensitivity protection. Other methods such as unit testing cannot match the instantiation use cases of multi-tenant characteristics and cannot be effectively implemented. However, this application starts from the actual scenario of online customers, can collect all customer usage scenarios, and record and transform the metadata layer, record and carry the actual use of multiple tenants; the metadata-driven method of this application is consistent with the overall design of the system, and no additional development support is required, that is, it is implemented from the metadata-driven method to ensure that the customer's business ultimately falls within the metadata range. The customer's scenario is effectively carried through metadata and metadata combined records, which can realize real-time quality testing of user operation scenarios and improve the performance and security of multi-tenant systems.

[0059] That is, in the quality testing method of the multi-tenant system in the embodiment of the present application, the scene collection and verification of different entities and customers' actual business configurations can be carried out, making the quality assurance process more reliable and the coverage of business scenes more accurate. Moreover, the metadata-driven approach in the present application is consistent with the system implementation method, does not require a lot of additional development, and reduces the development and implementation costs; the final information obtained from the customer scene does not contain the customer's real data, is not sensitive, and the metadata information cannot be effectively interpreted. The information is reliable and safe, and effectively solves the quality assurance difficulties and pain points caused by the high complexity of the customer's actual business scene and the opacity of the customer's actual usage scene when the customer uses the system at the same time in the SaaS multi-tenant system; generates dynamic test scenario use cases, which can obtain the use of online customers every day, achieve comprehensive coverage of business scenarios, and realize real-time quality testing of users' operation scenarios, improving the performance and security of multi-tenant systems; the test case generation from the scenario is more intelligent, reducing manual input and improving efficiency.

[0060] The quality testing device for a multi-tenant system provided by the present invention is described below. The quality testing device for a multi-tenant system described below and the quality testing method for a multi-tenant system described above can be referred to in correspondence with each other. Figure 5 As shown, including: An acquisition module 510 is used to acquire a metadata combination corresponding to a user's operation in a multi-tenant system; A determination module 520, configured to determine a meta-operation scenario according to the metadata combination; A generating module 530, used to generate scenario-based test cases according to the meta-operation scenario; The testing module 540 is used to perform quality testing on the multi-tenant system based on scenario-based test cases.

[0061] Optionally, the determination module 520 is specifically configured to: According to the metadata combination and the preset first corresponding relationship, a meta-operation scenario is determined; wherein the preset first corresponding relationship includes a corresponding relationship between the metadata combination and the meta-operation scenario.

[0062] Optionally, the generating module 530 is specifically configured to: Determine a plurality of atomic test cases according to the meta-operation scenario and the preset second corresponding relationship; wherein the preset second corresponding relationship includes a corresponding relationship between the meta-operation scenario and the atomic test case; Based on multiple atomic test cases, scenario-based test cases are obtained.

[0063] Optionally, the generating module 530 is specifically configured to: Combine multiple atomic test cases to obtain scenario-based test cases.

[0064] Optionally, the acquisition module 510 is further configured to: determining the frequency of each metadata combination obtained; According to the frequencies of the obtained metadata combinations, the execution order of each scenario-based test case is determined.

[0065] Optionally, the higher the frequency of acquiring the metadata combination, the higher the execution order priority of the scenario-based test cases corresponding to the metadata combination.

[0066] Figure 6 An example of a physical structure diagram of an electronic device is provided, and the electronic device may include: a processor 610, a communication interface 620, a memory 630, and a communication bus 640, wherein the processor 610, the communication interface 620, and the memory 630 communicate with each other through the communication bus 640. The processor 610 may call the logic instructions in the memory 630 to execute a quality testing method for a multi-tenant system, and the method includes: obtaining a metadata combination corresponding to a user's operation in the multi-tenant system; determining a meta-operation scenario according to the metadata combination; generating a scenario-based test case according to the meta-operation scenario; and performing a quality test on the multi-tenant system according to the scenario-based test case.

[0067] In addition, the logic instructions in the above-mentioned memory 630 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a disk or an optical disk.

[0068] On the other hand, the present invention also provides a computer program product, which includes a computer program. The computer program can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the quality testing method of the multi-tenant system provided by the above methods, and the method includes: obtaining a metadata combination corresponding to a user's operation in the multi-tenant system; determining a meta-operation scenario based on the metadata combination; generating a scenario-based test case based on the meta-operation scenario; and performing a quality test on the multi-tenant system based on the scenario-based test case.

[0069] On the other hand, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, is implemented to execute the quality testing method for a multi-tenant system provided by the above methods, the method comprising: obtaining a metadata combination corresponding to a user's operation in the multi-tenant system; determining a meta-operation scenario based on the metadata combination; generating a scenario-based test case based on the meta-operation scenario; and performing a quality test on the multi-tenant system based on the scenario-based test case.

[0070] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0071] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution can be essentially or in other words, the part that contributes to the prior art can be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as ROM / RAM, a magnetic disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the method described in the embodiment or some parts of the embodiment.

[0072] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A quality testing method for a multi-tenant system, characterized in that: include: Obtain the metadata combination corresponding to the business operations performed by users in the multi-tenant system; Determining a meta-operation scenario according to the metadata combination; Generate scenario-based test cases based on the meta-operation scenario; Perform quality testing on the multi-tenant system based on the scenario-based test cases.

2. The quality testing method of a multi-tenant system according to claim 1, characterized in that: Determining the meta-operation scenario according to the metadata combination includes: The meta-operation scenario is determined according to the metadata combination and a preset first correspondence relationship; wherein the preset first correspondence relationship includes a correspondence relationship between the metadata combination and the meta-operation scenario.

3. The quality testing method of a multi-tenant system according to claim 1, characterized in that: Generating scenario-based test cases according to the meta-operation scenario includes: Determine a plurality of atomic test cases according to the meta-operation scenario and a preset second correspondence relationship; wherein the preset second correspondence relationship includes a correspondence relationship between the meta-operation scenario and the atomic test case; The scenario-based test case is obtained according to the multiple atomic test cases.

4. The quality testing method of a multi-tenant system according to claim 3, characterized in that: The step of obtaining the scenario-based test case according to the atomic test case includes: The multiple atomic test cases are combined to obtain the scenario-based test cases.

5. The quality testing method for a multi-tenant system according to any one of claims 1 to 4, characterized in that: After obtaining the metadata combination corresponding to the business operation performed by the user in the multi-tenant system, the method further includes: determining the frequency of each metadata combination obtained; The execution order of each of the scenario-based test cases is determined according to the frequencies of each of the metadata combinations obtained.

6. The quality testing method of a multi-tenant system according to claim 5, characterized in that: Determining the execution order of each scenario-based test case according to the frequencies of each metadata combination obtained includes: The higher the frequency of acquiring the metadata combination, the higher the execution order priority of the scenario-based test case corresponding to the metadata combination.

7. The quality testing method of a multi-tenant system according to claim 2, characterized in that: The method further comprises: A first corresponding relationship is obtained according to historical operation scenarios of users in the multi-tenant system and metadata corresponding to the historical operation scenarios.

8. A quality testing device for a multi-tenant system, characterized in that: include: The acquisition module is used to obtain the metadata combination corresponding to the business operation performed by the user in the multi-tenant system; A determination module, used to determine a meta-operation scenario according to the metadata combination; A generation module, used to generate scenario-based test cases according to the meta-operation scenario; A testing module is used to perform quality testing on the multi-tenant system according to the scenario-based test cases.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the quality testing method for the multi-tenant system as described in any one of claims 1 to 7 is implemented.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the quality testing method for a multi-tenant system as claimed in any one of claims 1 to 7 is implemented.

Images