Test case maintenance system for travel saas platform

Abstract

The invention provides a travel saas platform-oriented test case maintenance system. The travel saas platform-oriented test case maintenance system comprises the following steps: S1, providing entities contained in a saas travel platform based on an ontology; s2, defining a relationship existing in the entity; s3, establishing links among the entities by using the relationship to form a triple; s4, an inference rule is established, and all test sets needing to be executed can be inferred according to new tenant configuration; s5, a system is constructed and comprises an ontology-based knowledge graph module, an inference engine module, a configuration tool module, a single-tenant test column set module and a rule set module, the inference engine module is connected with the configuration tool module, the single-tenant test column set module and the rule set module, and the knowledge graph module is interactively connected with the inference engine module; s6, inputting tenant configuration information by the user through a page; through the system, the mode of maintaining the test case according to the tenant dimension can be changed into the mode of only maintaining the tenant configuration information, and the storage space is reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of online car-hailing platforms, and in particular to a test case maintenance system for a travel SaaS platform. Background Art

[0002] In the SaaS (Software as a Service) field, personalized configuration of applications is a key feature. Different users may require different configurations to meet their specific needs. For the test team, managing test cases with different configurations for each tenant becomes cumbersome and complicated. When a new tenant joins, how to quickly generate subset test cases from the full set of test cases, reduce the scope of test regression, and improve labor efficiency is also a challenge that the SaaS-oriented test case management system needs to face.

[0003] The current test case management system is mainly designed for a single application entity and lacks support for the master-slave configurable SaaS model. When a new tenant joins, a set of test case sets must be re-maintained in the platform. As the number of tenants increases, a large number of duplicate cases will appear, and when a basic scenario changes, all test case sets need to be modified. Therefore, a test case maintenance system for travel SaaS platform is proposed. Summary of the invention

[0004] In view of this, an embodiment of the present invention hopes to provide a test case maintenance system for a travel SaaS platform to solve or alleviate the technical problems existing in the prior art and at least provide a beneficial option.

[0005] The technical solution of the embodiment of the present invention is implemented as follows: a test case maintenance system for a travel SaaS platform, comprising the above steps:

[0006] S1. Based on the ontology, the entities contained in the SaaS travel platform are given;

[0007] S2. Define the relationships among the above entities;

[0008] S3, use relationships to link entities to form triples;

[0009] S4. Establish inference rules to infer all test sets that need to be executed based on the new tenant configuration;

[0010] S5. Build a system, including an ontology-based knowledge graph module, an inference engine module, a configuration tool module, a single-tenant test column set module, and a rule set module. The inference engine module is connected to the configuration tool module, the single-tenant test column set module, and the rule set module. The knowledge graph module is interactively connected to the inference engine module.

[0011] S6. The user enters the tenant configuration information through the page, and the system automatically generates a single-tenant test case set corresponding to the tenant.

[0012] In some embodiments, in S5, the rule set module is used to store inference rules, and examples of inference rules are as follows:

[0013] i sTenant(a)^hasConfig(a,b)^hasConta in(b,c)^hasCase(c,d)=>hasCase(a,d);

[0014] Rule description: If a is a tenant, and a and b are in a configuration relationship, and b and c are in a containment relationship, and c and d are in an association relationship, then it can be inferred that a and d are in an association relationship (tenant a contains test case d);

[0015] i sFun(a)^i sFun(b)^hasReference(a,b)^hasCase(a,c)=>hasCase(b,c);

[0016] The rule states that if a and b are functions, and a and b are in a reference relationship, and a and c are in an association relationship, then it follows that b and c also have an association relationship.

[0017] In some embodiments, in S5, the configuration tool is used to configure the tenant, that is, the tenant configures the tenant type and the operating scope, the tenant type is divided into types according to the set value, and the operating scope is divided into types according to the set value.

[0018] In some embodiments, in S5, the inference engine module infers that the tenant includes the following single-tenant test case set according to the input tenant configuration and the rule set.

[0019] In some embodiments, in S5, the knowledge graph module stores data based on the ontology structure, mainly including a configuration item set, a function set, a single-tenant use case library set, and a tenant set.

[0020] In some embodiments, the configuration item set includes a tenant type and an operation scope, the tenant type is divided into type 1 and type 2 according to a set value, the operation scope is divided into scope 1 and scope 2 according to a set value, and the tenant type and operation scope include a function set.

[0021] In some embodiments, the function set includes an order module and an asset module, the order module includes function 1 and function 2, the type 1 and the type 2 include function 1 and function 2 corresponding to the order module, the asset module includes function 1 and function 2, the scope 1 and the scope 2 include function 1 and function 2 corresponding to the asset module, function 2 in the asset module references function 2 in the order module, and the order module and the asset module are associated with a single-tenant use case library set.

[0022] In some embodiments, the single-tenant use case library set includes use case 1, use case 2 and use case 3, the use case 1 includes two steps, the latter step depends on the former step, the order module function 1 is associated with use case 1, the order module function 2 is associated with use case 3, and the asset module function 2 is associated with use case 2.

[0023] The embodiment of the present invention has the following advantages due to the adoption of the above technical solution:

[0024] 1. Through the system, the present invention can transform the mode of maintaining test cases by tenant dimension into maintaining only tenant configuration information, thereby reducing storage space.

[0025] 2. Through this system, the present invention breaks down test case management into three levels: functional module-configuration-test case. The levels do not affect each other and establish relationships through triples. When the functional module or test case changes, only updates are required within this layer. This ensures that the test case sets generated by all tenants are the latest, without the need to change the test case sets of each tenant, greatly improving efficiency.

[0026] 3. The present invention realizes automatic reasoning by maintaining rule sets, and can adjust the generation rules of use case sets according to actual needs, without manual adjustment of the use case sets of each tenant.

[0027] The above summary is for illustrative purposes only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments and features described above, further aspects, embodiments and features of the present invention will be readily apparent by reference to the accompanying drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0029] Figure 1 is a system block diagram of the present invention;

[0030] Figure 2 This is a system block diagram of the knowledge graph module of the present invention;

[0031] Figure 3 This is a system block diagram of the configuration tool module of the present invention. DETAILED DESCRIPTION

[0032] In the following, only some exemplary embodiments are briefly described. As those skilled in the art will appreciate, the described embodiments may be modified in various ways without departing from the spirit or scope of the present invention. Therefore, the drawings and descriptions are considered to be exemplary and non-restrictive in nature.

[0033] It should be noted that the terms "first", "second", "symmetrical", "array", etc. are only used to distinguish between description and position description purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the definition of "first", "symmetrical", etc. can explicitly or implicitly include one or more of these features; similarly, when the quantity of certain features is not limited in the form of words such as "two" or "three", it should be noted that this feature also explicitly or implicitly includes one or more feature quantities;

[0034] In the present invention, unless otherwise clearly specified and limited, the terms such as "installation", "connection", "fixation" and the like should be understood in a broad sense; for example, it can be a fixed connection, a detachable connection, or an integral molding; it can be a mechanical connection, a direct connection, welding, or an indirect connection through an intermediate medium, or it can be the internal connection of two elements or the interaction relationship between two elements. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood based on the description and drawings combined with specific circumstances.

[0035] The embodiments of the present invention are described in detail below with reference to the accompanying drawings.

[0036] Embodiment 1

[0037] like Figure 1-Figure 3 As shown, an embodiment of the present invention provides a test case maintenance system for a travel SaaS platform, comprising the above steps:

[0038] S1. Based on the ontology, the entities included in the SaaS travel platform are given, such as modules, functions, configuration items, configuration values, use case sets, use case steps and assertions;

[0039] S2. Define the relationships among the above entities, such as inclusion relationship, value relationship, reference relationship, dependency relationship, influence relationship and configuration relationship;

[0040] S3. Use relationships to link entities to form triplets, such as order module-include-order function, order function-use case-use case set; order function-dependency-inquiry function, etc.

[0041] S4. Establish inference rules to infer all test sets that need to be executed based on the new tenant configuration;

[0042] S5. Build a system, including an ontology-based knowledge graph module, an inference engine module, a configuration tool module, a single-tenant test column set module, and a rule set module. The inference engine module is connected to the configuration tool module, the single-tenant test column set module, and the rule set module. The knowledge graph module is interactively connected to the inference engine module.

[0043] S6. The user enters the tenant configuration information through the page, and the system automatically generates a single-tenant test case set corresponding to the tenant.

[0044] In this embodiment, specifically, in S5, the rule set module is used to store inference rules, and examples of inference rules are as follows:

[0045] i sTenant(a)^hasConfig(a,b)^hasConta in(b,c)^hasCase(c,d)=>hasCase(a,d);

[0046] Rule description: If a is a tenant, and a and b are in a configuration relationship, and b and c are in a containment relationship, and c and d are in an association relationship, then it can be inferred that a and d are in an association relationship (tenant a contains test case d).

[0047] In this embodiment, specifically, in S5, the configuration tool is used to configure the tenant, that is, the tenant configures the tenant type and the operation scope, the tenant type is divided into types according to the set value, and the operation scope is divided into types according to the set value.

[0048] In this embodiment, specifically, in S5, the inference engine module infers that the tenant includes the following single-tenant test case set according to the input tenant configuration and the rule set.

[0049] In this embodiment, specifically, in S5, the knowledge graph module stores data based on the ontology structure, mainly including a configuration item set, a function set, a single-tenant use case library set, and a tenant set.

[0050] In this embodiment, specifically, the configuration item set includes a tenant type and an operation scope, the tenant type is divided into type 1 and type 2 according to a set value, the operation scope is divided into range 1 and range 2 according to a set value, and the tenant type and the operation scope include a function set.

[0051] In this embodiment, specifically, the function set includes an order module and an asset module, the order module includes function 1 and function 2, type 1 and type 2 include function 1 and function 2 in the corresponding order module, the asset module includes function 1 and function 2, scope 1 and scope 2 include function 1 and function 2 in the corresponding asset module, function 2 in the asset module references function 2 in the order module, and the order module and the asset module are associated with a single-tenant use case library set.

[0052] In this embodiment, specifically, the single-tenant use case library set includes use case 1, use case 2 and use case 3. Use case 1 includes two steps, the latter step depends on the former step, the order module function 1 is associated with use case 1, the order module function 2 is associated with use case 3, and the asset module function 2 is associated with use case 2.

[0053] In this embodiment, specifically, in system design and management, triples can be used to describe or represent various relationships or configurations in the system. Here, triples in a database management system (DBMS) are taken as an example to explain its application:

[0054] In a database, a triple can be represented as a tuple in a relation, which consists of three attributes. For example, suppose there is a relational database table about students, in which each student record can be represented as a triple, including the student ID, name, and age. Then, for a specific student record in the student table, such as the student with the student ID 123, whose name is "Zhang San" and whose age is 20, this record can be represented as a triple.

[0055] In this embodiment, specifically, with the continuous advancement of cloud computing and big data technologies, SaaS (Software as a Service) is gradually being applied to various fields, including travel platforms.

[0056] In this embodiment, specifically, when establishing inference rules, we need to clarify several key points:

[0057] Configuration information for new tenants: This includes basic information about new tenants (such as name, contact information, tenant type, etc.), as well as their specific requirements and configuration details (such as test set priority, execution time, dependencies, etc.).

[0058] Test set: A test set is a collection of test cases used to verify the functionality and performance of a system. Each test set may have multiple test cases, each with a specific purpose and expected results.

[0059] Goal of inference rules: Our goal is to infer all the inference rules in the test set that need to be executed based on the configuration information of the new tenant.

[0060] Based on the above information, we can establish the following inference rules:

[0061] Rule 1: If the new tenant is a premium user, enable the premium functional test suite for them.

[0062] Rule 2: If the tenant type of a new tenant is enterprise, then execute the performance test suite and enterprise functional test suite for them;

[0063] Rule 3: If the new tenant's requirement document mentions a particular focus on a certain feature, then test cases related to that feature should be executed first;

[0064] Rule 4: If a time window for test execution is specified in the configuration of the new tenant, the test set is executed within the specified time;

[0065] Rule 5: If there are dependencies between test sets, execute the predecessor test set in the dependency first.

[0066] Embodiment 2

[0067] like Figure 1-Figure 3 As shown, an embodiment of the present invention provides a test case maintenance system for a travel SaaS platform, comprising the above steps:

[0068] S1. Based on the ontology, the entities included in the SaaS travel platform are given, such as modules, functions, configuration items, configuration values, use case sets, use case steps and assertions;

[0069] S2. Define the relationships among the above entities, such as inclusion relationship, value relationship, reference relationship, dependency relationship, influence relationship and configuration relationship;

[0070] S3. Use relationships to link entities to form triplets, such as order module-include-order function, order function-use case-use case set; order function-dependency-inquiry function, etc.

[0071] S4. Establish inference rules to infer all test sets that need to be executed based on the new tenant configuration;

[0072] S5. Build a system, including an ontology-based knowledge graph module, an inference engine module, a configuration tool module, a single-tenant test column set module, and a rule set module. The inference engine module is connected to the configuration tool module, the single-tenant test column set module, and the rule set module. The knowledge graph module is interactively connected to the inference engine module.

[0073] S6. The user enters the tenant configuration information through the page, and the system automatically generates a single-tenant test case set corresponding to the tenant.

[0074] In this embodiment, specifically, in S5, the rule set module is used to store inference rules, and examples of inference rules are as follows:

[0075] i sFun(a)^i sFun(b)^hasReference(a,b)^hasCase(a,c)=>hasCase(b,c);

[0076] The rule states that if a and b are functions, and a and b are in a reference relationship, and a and c are in an association relationship, then it follows that b and c also have an association relationship.

[0077] In this embodiment, specifically, in S5, the configuration tool is used to configure the tenant, that is, the tenant configures the tenant type and the operation scope, the tenant type is divided into types according to the set value, and the operation scope is divided into types according to the set value.

[0078] In this embodiment, specifically, in S5, the inference engine module infers that the tenant includes the following single-tenant test case set according to the input tenant configuration and the rule set.

[0079] In this embodiment, specifically, in S5, the knowledge graph module stores data based on the ontology structure, mainly including a configuration item set, a function set, a single-tenant use case library set, and a tenant set.

[0080] In this embodiment, specifically, the configuration item set includes a tenant type and an operation scope, the tenant type is divided into type 1 and type 2 according to a set value, the operation scope is divided into range 1 and range 2 according to a set value, and the tenant type and the operation scope include a function set.

[0081] In this embodiment, specifically, the function set includes an order module and an asset module, the order module includes function 1 and function 2, type 1 and type 2 include function 1 and function 2 in the corresponding order module, the asset module includes function 1 and function 2, scope 1 and scope 2 include function 1 and function 2 in the corresponding asset module, function 2 in the asset module references function 2 in the order module, and the order module and the asset module are associated with a single-tenant use case library set.

[0082] In this embodiment, specifically, the single-tenant use case library set includes use case 1, use case 2 and use case 3. Use case 1 includes two steps, the latter step depends on the former step, the order module function 1 is associated with use case 1, the order module function 2 is associated with use case 3, and the asset module function 2 is associated with use case 2.

[0083] In this embodiment, specifically, in system design and management, triples can be used to describe or represent various relationships or configurations in the system. Here, triples in a database management system (DBMS) are taken as an example to explain its application:

[0084] In a database, a triple can be represented as a tuple in a relation, which consists of three attributes. For example, suppose there is a relational database table about students, in which each student record can be represented as a triple, including the student ID, name, and age. Then, for a specific student record in the student table, such as the student with the student ID 123, whose name is "Zhang San" and whose age is 20, this record can be represented as a triple.

[0085] In this embodiment, specifically, with the continuous advancement of cloud computing and big data technologies, SaaS (Software as a Service) is gradually being applied to various fields, including travel platforms.

[0086] In this embodiment, specifically, when establishing inference rules, we need to clarify several key points:

[0087] Configuration information for new tenants: This includes basic information about new tenants (such as name, contact information, tenant type, etc.), as well as their specific requirements and configuration details (such as test set priority, execution time, dependencies, etc.).

[0088] Test set: A test set is a collection of test cases used to verify the functionality and performance of a system. Each test set may have multiple test cases, each with a specific purpose and expected results.

[0089] Goal of inference rules: Our goal is to infer all the inference rules in the test set that need to be executed based on the configuration information of the new tenant.

[0090] Based on the above information, we can establish the following inference rules:

[0091] Rule 1: If the new tenant is a premium user, enable the premium functional test suite for them.

[0092] Rule 2: If the tenant type of a new tenant is enterprise, then execute the performance test suite and enterprise functional test suite for them;

[0093] Rule 3: If the new tenant's requirement document mentions a particular focus on a certain feature, then test cases related to that feature should be executed first;

[0094] Rule 4: If a time window for test execution is specified in the configuration of the new tenant, the test set is executed within the specified time;

[0095] Rule 5: If there are dependencies between test sets, execute the predecessor test set in the dependency first.

[0096] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of various changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A test case maintenance system for a travel SaaS platform, characterized in that: Including the above steps: S1. Based on the ontology, the entities contained in the SaaS travel platform are given; S2. Define the relationships among the above entities; S3, use relationships to link entities to form triples; S4. Establish inference rules to infer all test sets that need to be executed based on the new tenant configuration; S5. Build a system, including an ontology-based knowledge graph module, an inference engine module, a configuration tool module, a single-tenant test column set module, and a rule set module. The inference engine module is connected to the configuration tool module, the single-tenant test column set module, and the rule set module. The knowledge graph module is interactively connected to the inference engine module. S6. The user enters the tenant configuration information through the page, and the system automatically generates a single-tenant test case set corresponding to the tenant.

2. The test case maintenance system for the travel SaaS platform according to claim 1 is characterized in that: In S5, the rule set module is used to store inference rules. Examples of inference rules are as follows: isTenant(a)^hasConfig(a,b)^hasContain(b,c)^hasCase(c,d)=>hasCase(a,d); Rule description: If a is a tenant, and a and b are in a configuration relationship, and b and c are in a containment relationship, and c and d are in an association relationship, then it can be inferred that a and d are in an association relationship (tenant a contains test case d); isFun(a)^isFun(b)^hasReference(a,b)^hasCase(a,c)=>hasCase(b,c); The rule states that if a and b are functions, and a and b are in a reference relationship, and a and c are in an association relationship, then it follows that b and c also have an association relationship.

3. The test case maintenance system for the travel SaaS platform according to claim 1 is characterized in that: In S5, the configuration tool is used to configure the tenant, that is, the tenant configures the tenant type and the operation scope, the tenant type is divided into types according to the set value, and the operation scope is divided into types according to the set value.

4. The test case maintenance system for the travel SaaS platform according to claim 1 is characterized in that: In S5, the inference engine module infers that the tenant includes the following single-tenant test case set according to the input tenant configuration and the rule set.

5. The test case maintenance system for the travel SaaS platform according to claim 1, characterized in that: In S5, the knowledge graph module stores data based on the ontology structure, which mainly includes a configuration item set, a function set, a single-tenant use case library set, and a tenant set.

6. The test case maintenance system for the travel SaaS platform according to claim 5 is characterized by: The configuration item set includes a tenant type and an operation scope. The tenant type is divided into type 1 and type 2 according to a set value. The operation scope is divided into scope 1 and scope 2 according to a set value. The tenant type and the operation scope include a function set.

7. The test case maintenance system for the travel SaaS platform according to claim 6 is characterized by: The function set includes an order module and an asset module, the order module includes function 1 and function 2, the type 1 and the type 2 include function 1 and function 2 corresponding to the order module, the asset module includes function 1 and function 2, the scope 1 and the scope 2 include function 1 and function 2 corresponding to the asset module, function 2 in the asset module references function 2 in the order module, and the order module and the asset module are associated with a single-tenant use case library set.

8. The test case maintenance system for the travel SaaS platform according to claim 7 is characterized in that: The single-tenant use case library set includes use case 1, use case 2 and use case 3. Use case 1 includes two steps, the latter step depends on the former step, the order module function 1 is associated with use case 1, the order module function 2 is associated with use case 3, and the asset module function 2 is associated with use case 2.

Images