Demonstration method, device, computer device and storage medium of test process

Abstract

This application relates to a method, apparatus, computer device, and storage medium for demonstrating a testing process. The method includes: acquiring test requirements and matching multiple target metrics corresponding to the test requirements from a set of metrics; determining at least one target functional use case corresponding to each target metric; orchestrating the multiple target functional use cases according to the deployment elements corresponding to each target functional use case to obtain an initial demonstration plan for the test requirements; obtaining test instructions corresponding to the test requirements based on the template elements corresponding to each target functional use case and the initial demonstration plan; and demonstrating the process of testing multiple target functional use cases using the test instructions. This method improves the flexibility of test process demonstration.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a demonstration method, apparatus, computer device, and storage medium for a testing process. Background Technology

[0002] With the development of computer technology, after configuring a test plan for the user's testing needs, it is necessary to demonstrate the test plan through a demonstration system to determine the configuration effect of the test plan.

[0003] Currently, the common approach is to simply overlay functional test cases from a test plan before demonstrating it. If the test plan fails to meet expectations, the updated functional test cases need to be overlaid and demonstrated again. However, this mechanical overlay demonstration method cannot achieve automated demonstration of the entire test plan. Therefore, improving the flexibility of test plan demonstration is the problem this application aims to solve. Summary of the Invention

[0004] Therefore, it is necessary to provide a demonstration method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can improve the demonstration flexibility of the test process in response to the above-mentioned technical problems.

[0005] Firstly, this application provides a method for demonstrating a testing process. The method includes:

[0006] Obtain test requirements and match multiple target metrics corresponding to the test requirements from the set of metrics;

[0007] Determine at least one target functional use case corresponding to each of the target metric items; the target functional use case includes element information; the element information includes deployment elements and template elements;

[0008] Based on the deployment elements corresponding to each of the target functional use cases, the multiple target functional use cases are orchestrated to obtain the initial demonstration plan of the test requirements;

[0009] Based on the template elements corresponding to each of the target functional use cases and the initial demonstration plan, the test guidelines corresponding to the test requirements are obtained;

[0010] The test guidelines demonstrate the process of testing multiple target functional use cases.

[0011] In one embodiment, matching multiple target metrics corresponding to a test requirement from a set of metrics includes: converting the test requirement into a standard format requirement document and extracting multiple keywords from the requirement document; displaying a matching interface; the matching interface includes a list of metrics corresponding to the set of metrics; the list of metrics includes multiple metric types and multiple tag systems; in response to a matching operation between each keyword and the list of metrics, obtaining multiple target metrics corresponding to the test requirement; the target metrics include at least one of metric types and tag systems.

[0012] In one embodiment, the set of indicator items includes multiple indicator items; before determining at least one target functional use case corresponding to each of the target indicator items, the method further includes: acquiring multiple functional use cases and determining the environment deployment scheme corresponding to the test requirement; the environment deployment scheme includes resource specifications required for test demonstration; filtering multiple functional use cases according to the environment deployment scheme to obtain multiple candidate functional use cases; in response to the association operation between each candidate functional use case and the indicator item, obtaining the mapping relationship between the candidate functional use case and the indicator item; determining at least one target functional use case corresponding to each of the target indicator items includes: determining at least one target functional use case corresponding to each of the target indicator items according to each target indicator item and the mapping relationship.

[0013] In one embodiment, based on the deployment elements corresponding to each target functional use case, multiple target functional use cases are orchestrated to obtain an initial demonstration plan for the test requirement. This includes: selecting multiple identified functional use cases carrying association identifiers from the multiple target functional use cases and determining the association relationships between different identified functional use cases; sorting the multiple identified functional use cases according to the association relationships to obtain at least one set of functional use cases; and grouping and sorting the target functional use cases without association identifiers and the at least one set of functional use cases according to preset orchestration rules and the deployment elements to obtain the initial demonstration plan for the test requirement.

[0014] In one embodiment, the template elements include a scenario template; the test guidance includes an execution plan; obtaining the test guidance corresponding to the test requirement based on the template elements corresponding to each of the target functional use cases and the initial demonstration plan includes: determining the template type of the scenario template for each of the multiple target functional use cases; determining the demonstration sub-plan corresponding to the current target functional use case based on the template type; combining the demonstration sub-plans corresponding to each of the target functional use cases and the initial demonstration plan to obtain the target demonstration plan corresponding to the test requirement; and performing a directory conversion on the target demonstration plan to obtain the execution plan corresponding to the test requirement.

[0015] In one embodiment, the template type includes a single-scenario template or a multi-scenario template; determining the demonstration sub-plan corresponding to the current target functional use case according to the template type includes: when the template type is a multi-scenario template, determining multiple demonstration scenarios corresponding to the current target functional use case; determining the demonstration method corresponding to each demonstration scenario; the demonstration method includes at least one of scenario embedding and scenario navigation; and arranging the current target functional use case into the corresponding demonstration scenario according to each demonstration method to obtain the demonstration sub-plan corresponding to the current target functional use case.

[0016] In one embodiment, the test guide further includes an environment deployment plan; the execution plan includes multiple entry lines; the test requirement includes multiple sub-requirements; after converting the target demonstration plan to obtain the execution plan corresponding to the test requirement, the method further includes: determining the environment information corresponding to the test requirement; the environment information includes at least user roles, user permissions, configuration center address, and monitoring center address; converting the environment information using preset conversion rules to obtain an environment deployment plan; determining the target entry line corresponding to each target functional use case in the execution plan, and recording each sub-requirement in the corresponding target entry line; combining the environment deployment plan and the execution plan to obtain the test guide for the test requirement.

[0017] In one embodiment, the method further includes: recording specific questions raised by users during the demonstration; the test guide includes a question record; after demonstrating the process of testing multiple target functional use cases using the test guide, the method further includes: storing the specific questions in the question record and determining optimized target functional use cases; using the optimized target functional use cases as new target functional use cases and returning to the process of orchestrating multiple target functional use cases according to the deployment elements corresponding to each target functional use case until a new test guide is obtained; and demonstrating the process of testing multiple target functional use cases again using the new test guide.

[0018] In one embodiment, determining the optimized target functional use case includes: generating a test report at the end of the demonstration and extracting the target data of the special problem in the test report; performing statistical analysis on the target data to obtain analysis results; the statistical analysis includes at least personnel cost analysis, use case satisfaction analysis, application user structure analysis, and user concern analysis; and optimizing the target functional use case corresponding to the target data based on the analysis results to obtain the optimized target functional use case.

[0019] Secondly, this application also provides a demonstration device for a testing process. The device includes:

[0020] The use case determination module is used to obtain test requirements and match multiple target indicators corresponding to the test requirements from the indicator item set; determine at least one target functional use case corresponding to each target indicator item; the target functional use case includes element information; the element information includes deployment elements and template elements;

[0021] The demonstration plan determination module is used to orchestrate multiple target functional use cases according to the deployment elements corresponding to each of the target functional use cases, so as to obtain the initial demonstration plan of the test requirements.

[0022] The test guidance determination module is used to obtain the test guidance corresponding to the test requirements based on the template elements corresponding to each of the target functional use cases and the initial demonstration plan; and to demonstrate the process of testing multiple target functional use cases through the test guidance.

[0023] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0024] Obtain test requirements and match multiple target metrics corresponding to the test requirements from the set of metrics;

[0025] Determine at least one target functional use case corresponding to each of the target metric items; the target functional use case includes element information; the element information includes deployment elements and template elements;

[0026] Based on the deployment elements corresponding to each of the target functional use cases, the multiple target functional use cases are orchestrated to obtain the initial demonstration plan of the test requirements;

[0027] Based on the template elements corresponding to each of the target functional use cases and the initial demonstration plan, the test guidelines corresponding to the test requirements are obtained;

[0028] The test guidelines demonstrate the process of testing multiple target functional use cases.

[0029] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, which, when executed by a processor, performs the following steps:

[0030] Obtain test requirements and match multiple target metrics corresponding to the test requirements from the set of metrics;

[0031] Determine at least one target functional use case corresponding to each of the target metric items; the target functional use case includes element information; the element information includes deployment elements and template elements;

[0032] Based on the deployment elements corresponding to each of the target functional use cases, the multiple target functional use cases are orchestrated to obtain the initial demonstration plan of the test requirements;

[0033] Based on the template elements corresponding to each of the target functional use cases and the initial demonstration plan, the test guidelines corresponding to the test requirements are obtained;

[0034] The test guidelines demonstrate the process of testing multiple target functional use cases.

[0035] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0036] Obtain test requirements and match multiple target metrics corresponding to the test requirements from the set of metrics;

[0037] Determine at least one target functional use case corresponding to each of the target metric items; the target functional use case includes element information; the element information includes deployment elements and template elements;

[0038] Based on the deployment elements corresponding to each of the target functional use cases, the multiple target functional use cases are orchestrated to obtain the initial demonstration plan of the test requirements;

[0039] Based on the template elements corresponding to each of the target functional use cases and the initial demonstration plan, the test guidelines corresponding to the test requirements are obtained;

[0040] The test guidelines demonstrate the process of testing multiple target functional use cases.

[0041] The demonstration method, apparatus, computer equipment, storage medium, and computer program product of the above-mentioned testing process, by acquiring test requirements and matching multiple target indicators corresponding to the test requirements from the indicator item set, can determine at least one target functional use case corresponding to each target indicator item. Based on the deployment elements corresponding to each target functional use case, multiple target functional use cases are orchestrated to obtain an initial demonstration plan for the test requirements. Based on the template elements corresponding to each target functional use case and the initial demonstration plan, test guidelines corresponding to the test requirements can be obtained. Thus, the process of testing multiple target functional use cases can be demonstrated through the test guidelines. Because the test guidelines are flexibly generated based on template elements after the target functional use cases are orchestrated, compared to the traditional method of simply stacking functional use cases, this application can prioritize the orchestration of issues of greater user concern when orchestrating target functional use cases. Furthermore, after defining functional use cases through template elements, different test guidelines can be generated, thus achieving flexible deployment and demonstration of target functional use cases.

[0042] Furthermore, since the demonstration process involves the entire process from obtaining test requirements to generating test guidelines, it automates the verification testing of user functions. At the same time, when test guidelines are generated, users can adjust the demonstration progress according to the test guidelines, thus improving the convenience of demonstrating the test process and lowering the barrier to entry for demonstrating the test process. Attached Figure Description

[0043] Figure 1 This is a diagram illustrating the application environment of a testing process demonstration method in one embodiment;

[0044] Figure 2 This is a flowchart illustrating a testing process in one embodiment;

[0045] Figure 3 This is a flowchart illustrating a demonstration of user functionality verification testing in one embodiment;

[0046] Figure 4 This is a schematic diagram illustrating the relationship between the index matching domain and the system demonstration domain in one embodiment.

[0047] Figure 5 This is a demonstration model architecture diagram based on user functional verification testing in one embodiment;

[0048] Figure 6 This is a schematic diagram of the template relationships corresponding to the target functional use cases in one embodiment;

[0049] Figure 7 This is a schematic diagram demonstrating the iterative application of functional use cases in one embodiment;

[0050] Figure 8 This is a structural block diagram of a demonstration device for the testing process in one embodiment;

[0051] Figure 9 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0053] The demonstration method of the testing process provided in this application embodiment can be applied to, for example, Figure 1 In the application environment shown, terminal 102 can communicate with server 104 via a network. Both terminal 102 and server 104 can be used independently to execute the demonstration method of the testing process provided in this embodiment, or they can be used collaboratively to execute the demonstration method of the testing process provided in this embodiment. Taking the demonstration method of terminal 102 and server 104 collaboratively executing the testing process as an example, terminal 102 sends the acquired test requirements to server 104. Server 104 matches multiple target indicator items corresponding to the test requirements from the indicator item set and determines at least one target functional use case corresponding to each target indicator item. Server 104 orchestrates multiple target functional use cases according to the deployment elements corresponding to each target functional use case to obtain an initial demonstration plan for the test requirements; according to the template elements corresponding to each target functional use case and the initial demonstration plan, it obtains test instructions corresponding to the test requirements and returns the test instructions to terminal 102, enabling terminal 102 to demonstrate the process of testing multiple target functional use cases through the test instructions. The terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices, and the server 104 can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0054] In one embodiment, such as Figure 2As shown, a demonstration method for a testing process is provided, using the application of this method to a computer device as an example for illustration. This computer device can provide... Figure 1 The terminal or server in the system. The demonstration method for the testing process includes the following steps:

[0055] Step 202: Obtain test requirements and match multiple target metrics corresponding to the test requirements from the set of metrics.

[0056] Among them, test requirements can be a test document submitted by users, such as the system needing low-code development capabilities and support for containerized deployment; users include customers who provide test requirements; target indicators represent a standard or method used to define, evaluate and describe a specific thing, for example, when the test requirement is low-code development capabilities, the target indicators can correspond to the configurability of the process model, support for metadata modeling, and visualization of form development.

[0057] Specifically, the computer device can display a requirements retrieval interface. When a user edits a test document in the requirements retrieval interface, a test task corresponding to the test document is generated. Based on the test task, the computer device matches multiple target metrics corresponding to the test requirements from a set of metrics.

[0058] In one embodiment, matching multiple target metrics corresponding to test requirements from a set of metrics includes: converting test requirements into a standard format requirement document and extracting multiple keywords from the requirement document; displaying a matching interface; and obtaining multiple target metrics corresponding to test requirements in response to a matching operation between each keyword and the list of metrics.

[0059] The matching interface includes a list of indicator items corresponding to the indicator item set; the indicator item set includes multiple indicator items; the indicator item list includes multiple indicator types and multiple tag systems, the indicator type represents the hierarchical directory structure of the indicator item, and the tag system represents a set of highly refined feature identifiers that are manually set and obtained by applying certain algorithms to the target object according to the needs of the business scenario; the target indicator item includes at least one of the indicator type and the tag system.

[0060] Specifically, such as Figure 3 As shown, Figure 3This is a flowchart demonstrating user functional verification testing, also known as Proof of Concept (POC) testing. The computer equipment pre-determines whether the user has provided test requirements, or test needs. If not, the pre-set standard test requirement sheet in the system is used as the user's test requirements. If so, initial parsing of the test requirements is required. When the parsed test requirements are in a standard format, multiple keywords are extracted directly from the test requirements, where the requirement sheet is a standard test requirement sheet. When the parsed test requirements are not in a standard format, the test requirements must first be converted into a standard format requirement sheet before extracting multiple keywords from the requirement sheet.

[0061] The computer device can display a requirement matching interface. Configuration personnel can pre-match each keyword and indicator list using this interface. When the computer device identifies multiple keywords in the test requirement, it can determine the target indicator that matches each keyword. For example, if the test requirement is to support pushing engineering code to a repository and pulling code from the repository to build a pipeline for rapid containerized deployment, the keyword could be "pipeline." Therefore, the target indicator would be the indicator that linearly matches the pipeline.

[0062] In one embodiment, such as Figure 4 As shown, Figure 4 This is a diagram illustrating the relationship between the indicator matching domain and the system demonstration domain. The set of indicator items corresponds to the indicator matching domain. Since the combination of indicator type, label system, and indicator type and label system can all yield an indicator item, the relationship between indicator type and indicator item is one-to-many, and the relationship between label system and indicator item is also one-to-many.

[0063] In one embodiment, reference Figure 3 As shown, when a computer device receives a standard test requirement sheet, it can generate a test plan based on the standard test requirements, and automatically generate test instructions based on the test plan, until finally generating a test report.

[0064] In one embodiment, such as Figure 5 As shown, Figure 5 This is a demonstration model architecture diagram based on user function verification testing. The demonstration model consists of two parts: a management document module and a content module. The management document module provides end-to-end support for testing requirements and generating test guidelines, while the content module provides basic data and functional use cases independent of the management document module. The content module includes a set of indicator items.

[0065] In one embodiment, the indicator types in the indicator set include technical capability platform, business capability building platform, open platform, and data capability platform. The tag system in the indicator set includes low-code platform, extension and adaptation, cloud-native elements, distributed systems, and system integration and openness.

[0066] Step 204: Determine at least one target functional use case corresponding to each target metric item.

[0067] The target functional use cases include element information; the element information includes deployment elements and template elements.

[0068] In one embodiment, before determining at least one target functional use case corresponding to each target metric item, the method further includes: acquiring multiple functional use cases and determining the environment deployment scheme corresponding to the test requirements; filtering the multiple functional use cases according to the environment deployment scheme to obtain multiple candidate functional use cases; obtaining the mapping relationship between the candidate functional use cases and the metric items in response to the association operation between each candidate functional use case and the metric item; and determining at least one target functional use case corresponding to each target metric item, including: determining at least one target functional use case corresponding to each target metric item according to each target metric item and the mapping relationship.

[0069] The environment deployment plan includes the resource specifications required for testing and demonstration. As is easy to understand, the configuration of the environment deployment will change as the functions to be demonstrated need to be different. For example, if the test requirement is that the service supports high availability, then the environment deployment plan will involve starting more than 2n+1 service instances to meet the demonstration requirements corresponding to the test requirements.

[0070] Specifically, the computer equipment acquires multiple functional use cases designed by configuration personnel and filters candidate functional use cases from them. For example, when determining the environment deployment scheme corresponding to high availability support for a service, use cases testing the high availability performance of the service can be used as candidate functional use cases. Configuration personnel can also perform association operations between each candidate functional use case and indicator items to obtain the mapping relationship between the candidate functional use cases and indicator items. For example, indicator item 1 corresponds to functional use cases a and b, indicator item 2 corresponds to functional use cases c, d, and e, etc. When the mapping relationship is determined, the computer equipment can quickly filter and match at least one target functional use case corresponding to each target indicator item.

[0071] In one embodiment, reference Figure 4 As shown, each functional use case includes at least one scenario use case, and each metric item corresponds to at least one functional use case. That is, the functional use case and the scenario use case have a one-to-many relationship, and the metric item and the functional use case have a many-to-many relationship.

[0072] Step 206: Based on the deployment elements corresponding to each target functional use case, orchestrate multiple target functional use cases to obtain an initial demonstration plan for the test requirements.

[0073] The deployment elements include environment requirements and account requirements. For example, in target functional use case a, the environment requirements include environment 1 and environment 2, and the account requirements include user 1 and user 2; in target functional use case b, the environment requirements include environment 1, and the account requirements include user 2; in target functional use case c, the environment requirements include environment 2, and the account requirements include user 1, and so on. The initial demonstration plan represents the demonstration order when testing multiple target functional use cases.

[0074] Specifically, the computer equipment acquires preset orchestration rules, which include either environment orchestration rules corresponding to environment requirements or account orchestration rules corresponding to account requirements. Environment orchestration rules are used to group and sort target functional use cases according to their respective environment requirements; account orchestration rules are used to group and sort target functional use cases according to their respective account requirements. When using account orchestration rules, the computer equipment can orchestrate multiple target functional use cases based on the account requirements in each deployment element. For example, target functional use cases a and c corresponding to user 1 are orchestrated first, followed by target functional use case b corresponding to user 2, etc. Therefore, the demonstration order of the initial demonstration plan for the test requirements is target functional use case a, target functional use case c, and then target functional use case b.

[0075] In one embodiment, target functional use cases with the same account requirements can be reordered according to environment orchestration rules. For example, if target functional use case a and target functional use case c have the same account requirements, target functional use case c corresponding to environment 2 can be orchestrated first.

[0076] In one embodiment, the computer device acquires all test account information involved in the POC test demonstration process, such as the demonstrator account, administrator account, configuration center account, etc. within the system environment.

[0077] Step 208: Based on the template elements corresponding to each target function use case and the initial demonstration plan, obtain the test guidelines corresponding to the test requirements.

[0078] The template elements include test case templates and scenario templates; the test guidelines include execution plans.

[0079] In one embodiment, test guidelines corresponding to test requirements are obtained based on the template elements corresponding to each target functional use case and the initial demonstration plan. This includes: determining the template type of the scenario template for each target functional use case among multiple target functional use cases; determining the demonstration sub-plan corresponding to the current target functional use case based on the template type; combining the demonstration sub-plans corresponding to each target functional use case and the initial demonstration plan to obtain the target demonstration plan corresponding to the test requirements; and performing directory conversion on the target demonstration plan to obtain the execution plan corresponding to the test requirements.

[0080] The demonstration sub-plan represents the specific process of demonstrating each target functional use case in at least one demonstration scenario.

[0081] Specifically, the computer device first determines the use case template corresponding to the target functional use case from the template elements carried by the target functional use case, and then determines the template type of the scenario template of the target functional use case from the use case template. The demonstration scenarios corresponding to different template types are not the same, and each demonstration scenario is pre-configured with a scenario form template. Based on the scenario form template corresponding to each demonstration scenario, the computer device can determine the specific process of the target functional use case being demonstrated in at least one demonstration scenario.

[0082] The computer device integrates the demonstration sub-plans corresponding to each target functional use case and the initial demonstration plan to obtain the target demonstration plan corresponding to the test requirements. The computer device performs directory transformation on the target demonstration plan and adds execute buttons, etc., to obtain the execution plan corresponding to the test requirements. The execution plan is used to guide users through the demonstration step by step, making the demonstration process coherent and orderly.

[0083] In one embodiment, reference Figure 5 As shown, the comprehensive deployment plan for computer equipment environment, target demonstration plan and test account information are used to obtain the test plan corresponding to the test requirements.

[0084] Step 210 demonstrates the process of testing multiple target functional test cases using the test guide.

[0085] Specifically, when computer equipment demonstrates the process of testing multiple target functional use cases according to the test guidelines, it records key demonstration result screenshots and demonstration duration for each target functional use case demonstration, and generates corresponding test reports for reference. Figure 5 As shown, the test report includes a test overview demonstrating the POC test, environment description, and test execution result data.

[0086] In one embodiment, the test overview includes environmental information, evaluation metrics, statistical data, and personnel input. The test overview also includes hardware resources, software resources, system deployment architecture diagrams, and user account information.

[0087] In the demonstration method of the above testing process, by obtaining the test requirements and matching multiple target indicators corresponding to the test requirements from the indicator set, at least one target functional use case corresponding to each target indicator can be determined. Based on the deployment elements corresponding to each target functional use case, the multiple target functional use cases are orchestrated to obtain an initial demonstration plan for the test requirements. Based on the template elements corresponding to each target functional use case and the initial demonstration plan, test guidelines corresponding to the test requirements can be obtained. Thus, the process of testing multiple target functional use cases can be demonstrated through the test guidelines. Because test guidelines can be flexibly generated based on template elements after the target functional use cases are orchestrated, compared to the traditional method of simply stacking functional use cases, this application can prioritize the orchestration of issues that users are more concerned about when orchestrating target functional use cases. Furthermore, after defining functional use cases through template elements, different test guidelines can be generated, thus achieving flexible deployment and demonstration of target functional use cases.

[0088] In one embodiment, based on the deployment elements corresponding to each target functional use case, multiple target functional use cases are orchestrated to obtain an initial demonstration plan for test requirements. This includes: selecting multiple identified functional use cases with association identifiers from multiple target functional use cases and determining the association relationships between different identified functional use cases; sorting the multiple identified functional use cases according to the association relationships to obtain at least one set of functional use cases; and grouping and sorting the target functional use cases without association identifiers and at least one set of functional use cases according to preset orchestration rules and deployment elements to obtain an initial demonstration plan for test requirements.

[0089] Specifically, to meet certain testing requirements, multiple functional test cases may need to be executed collaboratively. Therefore, during the design of functional test cases, configuration personnel need to pre-mark the collaborative functional test cases and configure the collaboration between different functional test cases to obtain the association relationships between each functional test case. When the computer device identifies multiple target functional test cases, it can perform preliminary screening, obtaining multiple identified functional test cases with association identifiers, and the remaining target functional test cases without association identifiers. The computer device determines the association relationships between different identified functional test cases and sorts the multiple identified functional test cases according to the association relationships to obtain at least one set of functional test cases. For example, if functional test case a and functional test case c are determined to be associated, they can be regarded as a set of functional test cases, and the order of the functional test case set is functional test case c, functional test case a.

[0090] The specific implementation process of the computer device grouping and sorting target functional use cases without associated identifiers and at least one set of functional use cases according to preset orchestration rules and deployment elements can be referred to step 206. When the orchestration rule is an account orchestration rule, the computer device can orchestrate multiple target functional use cases according to the account requirements in each deployment element to obtain an initial demonstration plan of the test requirements. For example, target functional use case b corresponding to user 2 can be prioritized, and then the set of functional use cases corresponding to user 1 can be orchestrated, etc. It is easy to understand that the orchestration method of target functional use cases in this embodiment is only an example, and in actual use, flexible sorting can be carried out based on the example.

[0091] In this embodiment, by associating and sorting related functional test cases, a functional test case set is obtained, which makes the testing process of functional test cases more in line with the requirements of the test plan. At the same time, by flexibly sorting the target functional test cases, multiple initial demonstration plans corresponding to the test requirements can be obtained, which are more in line with the customer's demonstration requirements.

[0092] In one embodiment, determining the demonstration sub-plan corresponding to the current target functional use case based on the template type includes: when the template type is a multi-scenario template, determining multiple demonstration scenarios corresponding to the current target functional use case; determining the demonstration method corresponding to each demonstration scenario; and arranging the current target functional use case into the corresponding demonstration scenario according to each demonstration method to obtain the demonstration sub-plan corresponding to the current target functional use case.

[0093] The template types include single-scene templates or multi-scene templates; the demonstration methods include at least one of scene embedding and scene navigation. Scene embedding represents the target functional use case being embedded into the demonstration scene page in the form of a link or pop-up; scene navigation represents the ability to directly jump between different demonstration scenes with the same target functional use case, such as embedding a link in demonstration scene A to jump to demonstration scene B, etc. It is easy to understand that the demonstration methods in this application are only examples, and the specific demonstration methods in actual use can be flexibly modified based on scene embedding or scene navigation.

[0094] Specifically, since each target function use case is designed based on a different use case template, and each use case template includes multiple scenario templates, a single scenario template corresponds to a single demonstration scenario, while a multi-scenario template corresponds to multiple demonstration scenarios. Each demonstration scenario is pre-configured with a scenario form template, which defines how the target function use case is demonstrated in that scenario.

[0095] like Figure 6 As shown, Figure 6 This diagram illustrates the template relationships for target functional use cases. For each target functional use case among multiple target functional use cases, when the template type is a multi-scenario template, the computer device determines multiple demonstration scenarios corresponding to the current target functional use case and determines the demonstration method in the corresponding scenario form template for each demonstration scenario. The computer device arranges the current target functional use case into the corresponding demonstration scenario according to the demonstration method, obtaining the demonstration sub-plan corresponding to the current target functional use case. For example, when target functional use case a corresponds to demonstration scenario A and demonstration scenario B, and the demonstration method for both demonstration scenario A and demonstration scenario B is scenario navigation, the demonstration sub-plan for target functional use case a is to perform a test demonstration of target functional use case a in demonstration scenario A, and then directly jump to demonstration scenario B, so that target functional use case a continues to perform a test demonstration in demonstration scenario B. Similarly, when the template type is a single-scenario template, the computer device determines a single demonstration scenario corresponding to the target functional use case until the target functional use case is arranged into a single demonstration scenario, obtaining the demonstration sub-plan corresponding to the target functional use case.

[0096] In one embodiment, reference Figure 6 As shown, the element information in the target functional use case also includes communication elements and iteration elements. Communication elements include technical specifications and customer case studies; iteration elements include customer concerns, which are used to iteratively optimize the target functional use case.

[0097] In this embodiment, since the target functional use cases are designed based on use case templates and scenario templates, further expansion of the target functional use cases is ensured. Simultaneously, the consistency of the target functional use case demonstrations is ensured through the demonstration scenarios in the scenario templates. Because the scenario form templates corresponding to each demonstration scenario can be modified, the demonstration sub-plans corresponding to the target functional use cases are more flexible, and the content of the entire demonstration process is richer.

[0098] In one embodiment, after converting the target demonstration plan into a directory to obtain the execution plan corresponding to the test requirements, the method further includes: determining the environment information corresponding to the test requirements; converting the environment information using preset conversion rules to obtain an environment deployment plan; determining the target entry line corresponding to each target functional use case in the execution plan, and recording each sub-requirement in the corresponding target entry line; and combining the environment deployment plan and the execution plan to obtain the test guidelines for the test requirements.

[0099] The testing guidelines include an environment deployment plan; the execution plan includes multiple entry lines; the testing requirements include multiple sub-requirements; and the environment information includes at least user roles, user permissions, configuration center address, and monitoring center address.

[0100] Specifically, the execution plan corresponding to the test requirements can be viewed as a user-recognizable catalog. Each entry line in the execution plan records a target functional test case, and each sub-requirement in the test requirements corresponds to at least one target functional test case. The computer equipment can then record each sub-requirement in its corresponding target entry line, allowing users to easily identify the target functional test case corresponding to the sub-requirement. Since the environmental information originates from the environment deployment plan in the test solution, which is configured by personnel and typically carries a large amount of system background information, it is not easily presented directly to users for identification. Therefore, the computer equipment needs to convert the environmental information using preset conversion rules, that is, to transform the complex environmental information in the test solution into a simplified, easily identifiable environment deployment plan. (Reference) Figure 5 As shown, the comprehensive environment deployment plan and execution plan for computer equipment provide test guidelines corresponding to the test requirements.

[0101] In this embodiment, by recording sub-requirements in the corresponding entry lines of the execution plan, users can intuitively compare and review the test plans. Furthermore, the execution plan with multiple entry lines guides users through different adjustments during the demonstration process, improving the convenience of demonstrating the test process.

[0102] In one embodiment, the method further includes: recording specific questions raised by users during the demonstration; after demonstrating the process of testing multiple target functional use cases using test guidelines, the method includes: storing specific questions in a question record and determining optimized target functional use cases; using the optimized target functional use cases as new target functional use cases and returning to the process of orchestrating multiple target functional use cases according to the deployment elements corresponding to each target functional use case until a new test guide is obtained; and demonstrating the process of testing multiple target functional use cases again using the new test guide.

[0103] Among them, reference Figure 5 As shown, the testing guidelines also include a problem log.

[0104] Specifically, since the demonstration of POC testing is a closed-loop iterative process, such as Figure 7 As shown, Figure 7 This is a schematic diagram for the iterative demonstration of functional use cases. During the initial demonstration, users may point out that the target functional use case does not meet certain sub-requirements. In this case, the computer device treats the problem as a special problem and records it in the problem log. When it is necessary to optimize the target functional use case, the computer device can use the contents of the problem log as the optimization basis. After determining the test report after the initial demonstration, the computer device optimizes the target functional use case according to the test report, and uses the optimized target functional use case as the new target functional use case before re-entering the demonstration process. Since the process of generating new test instructions from the new target functional use case is the same as steps 206 and 208, it will not be described again in this embodiment.

[0105] In one embodiment, determining the optimized target functional use case includes: generating a test report at the end of the demonstration and extracting target data for specific issues from the test report; performing statistical analysis on the target data to obtain analysis results; and optimizing the target functional use case corresponding to the target data based on the analysis results to obtain the optimized target functional use case.

[0106] The statistical analysis includes at least personnel expenditure analysis, use case satisfaction analysis, application user structure analysis, and user concern analysis.

[0107] Specifically, computer equipment can employ a lightweight analytics engine to extract target data from test reports related to specific issues, display the data through analytical reports, and then perform statistical analysis on the target data to obtain analysis results. When the analysis results show a significant difference from the target functional use cases, it may be necessary to redesign new functional use cases. If the analysis results indicate that the target functional use cases basically meet the test requirements, but the functionality corresponding to the test requirements is not clearly demonstrated, or the customer's concerns are not reflected, then only simple optimization based on the existing target functional use cases is required.

[0108] In this embodiment, the target functional test cases are demonstrated multiple times by adopting a closed-loop iterative process. When the test plan does not meet the expected results, the target functional test cases can be optimized efficiently and accurately. This allows for the generation of test guidelines with richer demonstration content while archiving the test report.

[0109] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0110] Based on the same inventive concept, this application also provides a demonstration device for a test process to implement the demonstration method of the test process involved above. The solution provided by this device is similar to the implementation solution described in the above method. Therefore, the specific limitations of one or more demonstration device embodiments of the test process provided below can be found in the limitations of the demonstration method of the test process above, and will not be repeated here.

[0111] In one embodiment, such as Figure 8 As shown, a demonstration device 800 for a testing process is provided, including: a test case determination module 802, a demonstration plan determination module 804, and a test guidance determination module 806, wherein:

[0112] The use case determination module 802 is used to obtain test requirements and match multiple target indicators corresponding to the test requirements from the indicator item set; determine at least one target functional use case corresponding to each target indicator item; the target functional use case includes element information; the element information includes deployment elements and template elements;

[0113] The demonstration plan determination module 804 is used to orchestrate multiple target functional use cases based on the deployment elements corresponding to each target functional use case, and obtain an initial demonstration plan for the test requirements.

[0114] The test guide determination module 806 is used to obtain the test guide corresponding to the test requirements based on the template elements corresponding to each target functional use case and the initial demonstration plan; the test guide demonstrates the process of testing multiple target functional use cases.

[0115] In one embodiment, the use case determination module 802 further includes an indicator item determination module 8021, which is used to convert test requirements into a standard format requirement document and extract multiple keywords from the requirement document; display a matching interface; the matching interface includes an indicator item list corresponding to the indicator item set; the indicator item list includes multiple indicator types and multiple tag systems; in response to the matching operation between each keyword and the indicator item list, multiple target indicator items corresponding to the test requirements are obtained; the target indicator items include at least one of the indicator types and tag systems.

[0116] In one embodiment, the use case determination module 802 further includes a use case association module 8022, used to acquire multiple functional use cases and determine the environment deployment scheme corresponding to the test requirements; the environment deployment scheme includes the resource specification required for test demonstration; the multiple functional use cases are filtered according to the environment deployment scheme to obtain multiple candidate functional use cases; in response to the association operation between each candidate functional use case and the indicator item, the mapping relationship between the candidate functional use case and the indicator item is obtained; based on each target indicator item and the mapping relationship, at least one target functional use case corresponding to each target indicator item is determined.

[0117] In one embodiment, the demonstration plan determination module 804 is further configured to filter out multiple identified functional use cases carrying association identifiers from multiple target functional use cases, and determine the association relationship between different identified functional use cases; sort the multiple identified functional use cases according to the association relationship to obtain at least one set of functional use cases; and group and sort the target functional use cases without association identifiers and at least one set of functional use cases according to preset orchestration rules and deployment elements to obtain an initial demonstration plan for test requirements.

[0118] In one embodiment, the test guidance determination module 806 includes an execution plan module 8061, which is used to determine the template type of the scenario template for each of the multiple target functional use cases; determine the demonstration sub-plan corresponding to the current target functional use case based on the template type; combine the demonstration sub-plans corresponding to each target functional use case and the initial demonstration plan to obtain the target demonstration plan corresponding to the test requirement; and perform directory conversion on the target demonstration plan to obtain the execution plan corresponding to the test requirement.

[0119] In one embodiment, the execution plan module 8061 is further configured to, when the template type is a multi-scenario template, determine multiple demonstration scenarios corresponding to the current target functional use case; determine the demonstration method corresponding to each demonstration scenario; the demonstration method includes at least one of scenario embedding and scenario navigation; and arrange the current target functional use case into the corresponding demonstration scenario according to each demonstration method to obtain the demonstration sub-plan corresponding to the current target functional use case.

[0120] In one embodiment, the test guidance determination module 806 is further used to determine the environmental information corresponding to the test requirements; the environmental information includes at least user roles, user permissions, configuration center address, and monitoring center address; the environmental information is converted through preset conversion rules to obtain an environment deployment plan; the target entry line corresponding to each target functional use case in the execution plan is determined, and each sub-requirement is recorded in the corresponding target entry line; the test guidance for the test requirements is obtained by combining the environment deployment plan and the execution plan.

[0121] In one embodiment, the test guide determination module 806 further includes an update module 8062, which records special questions raised by users during the demonstration; stores the special questions in the test guide's question record, and determines the optimized target functional use cases; uses the optimized target functional use cases as new target functional use cases, and returns to the process of orchestrating multiple target functional use cases according to the deployment elements corresponding to each target functional use case, until a new test guide is obtained; and demonstrates the process of testing multiple target functional use cases again using the new test guide.

[0122] In one embodiment, the update module 8062 is further configured to generate a test report at the end of the demonstration and extract target data for special issues in the test report; perform statistical analysis on the target data to obtain analysis results; the statistical analysis includes at least personnel cost analysis, use case satisfaction analysis, application user structure analysis, and user concern analysis; and optimize the target functional use cases corresponding to the target data based on the analysis results to obtain optimized target functional use cases.

[0123] The modules in the demonstration device for the above testing process can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device, or stored in the memory of the computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0124] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 9 As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database stores demonstration data for the testing process. The network interface communicates with external terminals via a network connection. When the computer program is executed by the processor, it implements a demonstration method for a testing process.

[0125] Those skilled in the art will understand that Figure 9 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0126] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0127] In one embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0128] In one embodiment, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and executes the computer instructions, causing the computer device to perform the steps in the above method embodiments.

[0129] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0130] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0131] The above embodiments merely illustrate several implementation methods of this application, and their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of this application's patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for demonstrating a testing process, characterized in that, The method includes: Obtain test requirements and match multiple target metrics corresponding to the test requirements from the set of metrics; Determine at least one target functional use case corresponding to each of the target metric items; the target functional use case includes element information; the element information includes deployment elements and template elements; Based on the deployment elements corresponding to each of the target functional use cases, the multiple target functional use cases are orchestrated to obtain the initial demonstration plan of the test requirements; Based on the template elements corresponding to each of the target functional use cases and the initial demonstration plan, the test guidelines corresponding to the test requirements are obtained; The test guidelines demonstrate the process of testing multiple target functional test cases. The process of matching multiple target metrics corresponding to the test requirements from the set of metrics includes: The test requirements are converted into a standard format requirement document, and multiple keywords are extracted from the requirement document. Display the matching interface; the matching interface includes a list of indicator items corresponding to the set of indicator items; the list of indicator items includes multiple indicator types and multiple tag systems; the indicator type represents the hierarchical directory structure of the indicator items, and the tag system represents a set of highly refined feature identifiers that are manually set and obtained by applying certain algorithms to the target object according to the needs of the business scenario. In response to the matching operation between each keyword and the list of indicator items, multiple target indicator items corresponding to the test requirement are obtained; the target indicator items include at least one of indicator type and tag system.

2. The method according to claim 1, wherein the set of indicator items includes multiple indicator items; Before determining at least one target functional use case corresponding to each of the target metric items, the method further includes: Obtain multiple functional test cases and determine the environment deployment plan corresponding to the test requirements; the environment deployment plan includes the resource specifications required for test demonstration; Based on the aforementioned environment deployment scheme, multiple functional use cases are filtered to obtain multiple candidate functional use cases; In response to the association operation between each candidate functional use case and the indicator item, the mapping relationship between the candidate functional use case and the indicator item is obtained; The step of determining at least one target functional use case corresponding to each of the target metric items includes: Based on each target indicator item and the mapping relationship, at least one target functional use case corresponding to each target indicator item is determined.

3. The method according to claim 1, characterized in that, The step of orchestrating multiple target functional use cases based on the deployment elements corresponding to each target functional use case to obtain an initial demonstration plan for the test requirements includes: Filter out multiple target functional use cases that carry association identifiers, and determine the association relationships between different functional use cases with different identifiers; Based on the association relationship, multiple identification function use cases are associated and sorted to obtain at least one set of function use cases; Based on the preset orchestration rules and the deployment elements, the target functional use cases without associated identifiers and the at least one set of functional use cases are grouped and sorted to obtain the initial demonstration plan of the test requirements.

4. The method according to claim 1, characterized in that, The template elements include scenario templates; the test guidelines include execution plans; obtaining the test guidelines corresponding to the test requirements based on the template elements corresponding to each of the target function use cases and the initial demonstration plan includes: For each target functional use case in a plurality of target functional use cases, the template type of the scenario template for the current target functional use case is determined; Based on the template type, determine the demonstration sub-plan corresponding to the current target functional use case; By combining the demonstration sub-plans corresponding to each of the target functional use cases and the initial demonstration plan, the target demonstration plan corresponding to the test requirement is obtained; The target demonstration plan is transformed into a directory to obtain the execution plan corresponding to the test requirements.

5. The method according to claim 4, characterized in that, The template type includes single-scenario templates or multi-scenario templates: Determining the demonstration sub-plan corresponding to the current target functional use case based on the template type includes: When the template type is a multi-scenario template, multiple demonstration scenarios corresponding to the current target function use case are determined; Determine the corresponding demonstration method for each of the demonstration scenarios; the demonstration method includes at least one of scene embedding and scene navigation. According to each of the aforementioned demonstration methods, the current target function use case is arranged into the corresponding demonstration scenario to obtain the demonstration sub-plan corresponding to the current target function use case.

6. The method according to claim 4, characterized in that, The testing guidelines also include an environment deployment plan; the execution plan includes multiple journal entries; and the testing requirements include multiple sub-requirements. After performing directory transformation on the target demonstration plan to obtain the execution plan corresponding to the test requirements, the method further includes: Determine the environment information corresponding to the test requirements; the environment information includes at least user roles, user permissions, configuration center address, and monitoring center address. The environmental information is transformed using preset transformation rules to obtain an environmental deployment plan; Determine the target entry line corresponding to each of the target functional use cases in the execution plan, and record each of the sub-requirements in the corresponding target entry line; By combining the aforementioned environment deployment plan and execution plan, test guidelines for the aforementioned test requirements are obtained.

7. The method according to claim 1, characterized in that, The method further includes: Record any specific questions raised by users during the demonstration; The test guide includes a problem log; after demonstrating the process of testing multiple target functional use cases through the test guide, the method further includes: The specific issues are stored in the issue record, and the optimized target functional use cases are determined; The optimized target functional test cases are used as new target functional test cases, and the process of orchestrating multiple target functional test cases according to the deployment elements corresponding to each target functional test case continues until new test guidelines are obtained. The new testing guidelines demonstrate once again the process of testing multiple target functional use cases.

8. The method according to claim 7, characterized in that, The determination of the optimized target function use cases includes: Generate a test report at the end of the demonstration and extract the target data for the specific issues in the test report; Statistical analysis is performed on the target data to obtain analysis results; the statistical analysis includes at least personnel expenditure analysis, use case satisfaction analysis, application user structure analysis, and user concern analysis. Based on the analysis results, the target functional use cases corresponding to the target data are optimized to obtain optimized target functional use cases.

9. A demonstration device for a testing process, characterized in that, The device includes: The use case determination module is used to obtain test requirements and match multiple target indicators corresponding to the test requirements from the indicator item set; determine at least one target functional use case corresponding to each target indicator item; the target functional use case includes element information; the element information includes deployment elements and template elements; The demonstration plan determination module is used to orchestrate multiple target functional use cases according to the deployment elements corresponding to each of the target functional use cases, so as to obtain the initial demonstration plan of the test requirements. The test guidance determination module is used to obtain the test guidance corresponding to the test requirement based on the template elements corresponding to each of the target functional use cases and the initial demonstration plan; and to demonstrate the process of testing multiple target functional use cases through the test guidance. The use case determination module is further configured to convert the test requirement into a standard format requirement document and extract multiple keywords from the requirement document; display a matching interface; the matching interface includes a list of indicator items corresponding to the indicator item set; the indicator item list includes multiple indicator types and multiple tag systems; the indicator type represents the hierarchical directory structure of the indicator item, and the tag system represents a set of highly refined feature identifiers that are manually set and obtained by applying a certain algorithm to the target object according to the business scenario requirements; in response to the matching operation between each keyword and the indicator item list, multiple target indicator items corresponding to the test requirement are obtained; the target indicator items include at least one of the indicator type and the tag system.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 8.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 8.

12. A computer program product comprising computer instructions stored in a computer-readable storage medium, wherein a processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions to cause the computer device to perform the steps of the method according to any one of claims 1 to 8.

Images