CN115080403A - Templated use case testing system, method, medium and device - Google Patents

Abstract

The present disclosure provides a templated use case testing system, method, storage medium and electronic device, and relates to the technical field of computers. The system includes: a template management module, a tool registration module, an operation and follow-up module, and a report management module; the template management module is used for setting template attributes of a use case in response to a setting operation; the tool registration module , used to register the tool, and the tool is used to execute the use case; the operation management and follow-up module is used to obtain the template attribute of the use case, and call the corresponding tool to test the use case according to the template attribute. Record the test result; the report management module is used for displaying the test result according to the preset analysis standard. Implementing the technical solutions of the embodiments of the present disclosure can reduce the difficulty of test case management and improve the ease of evaluation of the test process.

Description

Templated use case testing system, method, medium and device

technical field

The present disclosure relates to the field of computer technology, and in particular, to a templated use case testing system, a templated use case testing method, a computer storage medium, and a terminal device.

Background technique

Before the software is released, it is necessary to perform functional tests or stress tests on the software to improve the functions and make the software meet the needs of users.

The current solution is to manage the tests through separate management for specific test types, test methods, and test tools. However, a variety of test types, test methods and test tools are usually included in the test, which leads to many and confusing management methods, and it is impossible to fully view and understand the entire test process, and it is difficult to evaluate the test results in a unified manner.

It should be noted that the information disclosed in the above Background section is only for enhancement of understanding of the background of the present disclosure, and therefore may contain information that does not form the prior art that is already known to a person of ordinary skill in the art.

SUMMARY OF THE INVENTION

The purpose of the embodiments of the present disclosure is to provide a templated use case testing system and method, thereby reducing the management difficulty of use case testing and improving the ease of evaluation of the testing process at least to a certain extent.

According to an aspect of the present disclosure, a templated use case testing system is provided, which is characterized by comprising: a template management module, a tool registration module, an operation and follow-up module, and a report management module:

The template management module is used for setting the template attribute of the use case in response to the setting operation;

The tool registration module is used to register a tool, and the tool is used to execute the use case;

The operation management and follow-up module is used to obtain the template attribute of the use case, and according to the template attribute, call a corresponding tool to test the use case and record the test result;

The report management module is used to display the test results according to preset analysis standards.

In an exemplary embodiment of the present disclosure, the tool registration module is used to:

After the tool is registered, the tool is tested to determine that the tool is available for use case testing.

In an exemplary embodiment of the present disclosure, the operation and follow-up module is used to:

classifying use cases according to their template attributes after responding to the triggering action;

The use cases are classified to include non-manual use cases and manual use cases.

In an exemplary embodiment of the present disclosure, the template management module is further configured to:

A new tool is registered in response to a user selection operation.

In an exemplary embodiment of the present disclosure, the operation and follow-up module is used to:

in response to triggering an action, test at least one use case;

According to the template attribute of the non-manual use case, call the corresponding tool for testing;

Collect test progress in real-time while recording test results.

In an exemplary embodiment of the present disclosure, the operation and follow-up module is used to:

In response to the user input operation, the test results of the manual use case are recorded.

In an exemplary embodiment of the present disclosure, the report management module is used to:

Statistical analysis is performed on the test results, and results of different test types are displayed and displayed in a unified manner. The test results include but are not limited to: use case running results, logs, and pictures.

According to an aspect of the present disclosure, a templated use case testing method is provided, applied to a first terminal, the method comprising:

Based on the template management module, in response to the setting operation, set the template attribute of the use case;

registering a tool based on the tool registration module, the tool being used to execute the use case;

Obtain the template attribute of the use case based on the running and follow-up module, call the corresponding tool according to the template attribute to test the use case and record the test result;

The report-based management module displays the test results according to preset analysis standards.

In an exemplary embodiment of the present disclosure, a method for testing a templated use case is also provided. After the tool is registered for executing the steps of the use case, the method further includes:

The tool is tested to determine that the tool can be used for use case testing.

In an exemplary embodiment of the present disclosure, a method for testing a templated use case is also provided, wherein the template attribute of the use case is obtained, and a corresponding tool is called according to the template attribute to test the use case and record the test result; Classifying use cases according to template attributes of the use cases in response to the triggering operation;

The use cases are classified to include non-manual use cases and manual use cases.

In an exemplary embodiment of the present disclosure, a templated use case testing method is also provided, and the method further includes:

A new tool is registered in response to a user selection operation.

In an exemplary embodiment of the present disclosure, a method for testing a templated use case is also provided, wherein the operation management and follow-up module is configured to obtain the template attribute of the use case, and call a corresponding tool according to the template attribute to perform the test. Steps to test a use case and record the test results, including:

in response to triggering an action, test at least one use case;

According to the template attribute of the non-manual use case, call the corresponding tool for testing;

Collect test progress in real-time while recording test results.

In an exemplary embodiment of the present disclosure, a templated use case testing method is also provided, and the method further includes:

In response to the user input operation, the test results of the manual use case are recorded.

In an exemplary embodiment of the present disclosure, a method for testing a templated use case is also provided, and the step of displaying the test result by the report management module according to a preset analysis standard includes:

Statistical analysis is performed on the test results, and results of different test types are displayed and displayed in a unified manner. The test results include but are not limited to: use case running results, logs, and pictures.

According to one aspect of the present disclosure, there is provided a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements any one of the methods described above.

According to one aspect of the present disclosure, there is provided a terminal device, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute by executing the executable instructions The method of any of the above.

Exemplary embodiments of the present disclosure may have some or all of the following benefits:

In the templated use case testing system and method provided by the disclosed example embodiments, the template attribute of the use case can be set in response to the setting operation through the template management module; the tool registration module is used to register the tool; through the operation management and follow-up The input module is used to obtain the template attributes of the use case, and the corresponding tools are called according to the template attributes to test the use case and record the test results; the report management module is used to display the test results according to the preset analysis standards. On the one hand, the platform is used to clearly manage the test, which reduces the difficulty of management; on the other hand, the whole process of the test is fully understood through each module, which is convenient for unified evaluation and measurement, and improves the ease of evaluation of the use case test.

It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description serve to explain the principles of the disclosure. Obviously, the drawings in the following description are only some embodiments of the present disclosure, and for those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative effort.

FIG. 1 schematically shows a schematic structural diagram of a templated use case testing system according to an embodiment of the present disclosure;

FIG. 2 schematically shows a schematic diagram of an interface corresponding to a template management module according to an embodiment of the present disclosure;

FIG. 3 schematically shows a schematic diagram of an interface for managing and using elements according to an embodiment of the present disclosure;

FIG. 4 schematically shows a schematic diagram of an interface for registering a tool according to an embodiment of the present disclosure;

FIG. 5 schematically shows a schematic diagram of an interface for displaying test results according to an embodiment of the present disclosure;

6 schematically shows a schematic flowchart of a templated use case testing method according to an embodiment of the present disclosure;

FIG. 7 shows a schematic structural diagram of a computer storage medium in an exemplary embodiment of the present disclosure;

FIG. 8 shows a schematic structural diagram of an electronic device in an exemplary embodiment of the present disclosure.

Detailed ways

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments, however, can be embodied in various forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided in order to give a thorough understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure may be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. may be employed. In other instances, well-known solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repeated descriptions will be omitted. Some of the block diagrams shown in the figures are functional entities that do not necessarily necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations, can be implemented in special purpose hardware-based systems that perform the specified functions or operations, or can be implemented using A combination of dedicated hardware and computer instructions is implemented.

The units involved in the embodiments of the present disclosure may be implemented in software or hardware, and the described units may also be provided in a processor. Among them, the names of these units do not constitute a limitation on the unit itself under certain circumstances.

As another aspect, the present disclosure also provides a computer-readable storage medium. The computer-readable storage medium may be included in the terminal device described in the above embodiments; in the terminal device. The above-mentioned computer-readable storage medium carries one or more programs, and when the above-mentioned one or more programs are executed by a terminal device, the terminal device can implement the methods described in the following embodiments.

In order to fully understand the solution of the present disclosure, FIG. 1 shows a schematic structural diagram of a templated use case testing system in an exemplary embodiment of the present disclosure.

Referring to FIG. 1 , a templated use case testing system 100 according to an embodiment of the present disclosure includes a template management module 110 , a tool registration module 120 , an operation and follow-up module 130 , and a report management module 140 . in:

the template management module 110, configured to set the template attribute of the use case in response to the setting operation;

a tool registration module 120, configured to register a tool for executing the use case;

The running and follow-up module 130 is used to obtain the template attribute of the use case, and according to the template attribute, call a corresponding tool to test the use case and record the test result;

The report management module 140 is configured to display the test result according to the preset analysis standard.

In the templated use case testing system provided by this example embodiment, the template attribute of the use case can be set in response to the setting operation through the template management module; the tool registration module is used to register the tool; the operation management and follow-up module is used to register the tool; It is used to obtain the template attributes of the use case, and according to the template attributes, call the corresponding tool to test the use case and record the test results; the report management module is used to display the test results according to the preset analysis standards. On the one hand, the platform is used to clearly manage the test, which reduces the difficulty of management; on the other hand, the whole process of the test is fully understood through each module, which is convenient for unified evaluation and measurement, and improves the ease of evaluation of the use case test.

The specific execution process of each module in FIG. 1 is described in detail below:

The template management module 110 is configured to set the template attribute of the use case in response to the setting operation.

Test case refers to the overall description of the test task for a specific software product, reflecting the test plan, method, technology and strategy. Test cases include test targets, test environments, input data, test steps, expected results, test scripts, etc., and finally form documents. That is, a test case is a set of test inputs, execution conditions, and expected results prepared for a specific goal to verify whether a specific software requirement is met.

In an exemplary embodiment of the present disclosure, the test case itself has properties such as reliability, consistency, and ease of use, among others. In order to facilitate the management and application of the test case, other template attributes can also be set for the test case to describe the test case. For example, it can be elements such as common text boxes, text fields, single selection, and multiple selection, as well as rich text, YAML (YAML Ain't Markup Language), object notation (JavaScript Object Notation, JSON for short), language codes, etc. For template input and verification, elements can be freely combined and corresponding attributes can be set. At the same time, elements can be expanded into multi-step modes to adapt to the content required by various types of automation tools or to plan use case descriptions for different projects or different departments.

For example, as shown in Figure 2, a template name can be defined, and a template description can be noted. During element management, content such as the identity document (Identity document, ID for short), name, type, size, preset/prompt content, steps and operations of the element can be displayed. As shown in Figure 3, elements three and four can be expanded into multi-step mode, and elements one and two are not adjusted.

The tool registration module 120 is used for registering the tool, and the tool is used for executing the use case.

In an exemplary embodiment of the present disclosure, automated testing means that after running a software program, test cases are automatically executed and test results are generated without any human intervention. When testing cases, use automated testing tools to test cases that cannot be implemented by manual testing, such as common interface operations, repetitive operations, and process testing through fixed inputs and fixed operations; or tests that cannot be covered by manual testing. , for example, including the input of a large amount of data, the basic test of the source code, a large number of step operations, etc. Executing the use case through a tool can improve test efficiency, reduce errors in human testing, and can quickly display potential problems.

Since different test cases may use different automated testing tools, more testing tools need to be used in the actual testing process. For example, you can use LambdaTest that supports Python, Java, Javascript and other languages, and supports recording and playback functions. TestComplete or QMetry Automation Studio and other test tools. When the tool supports the interface call trigger function, the tool registration module can perform docking management with various types of automation tools, and can use the default image and write a data docking script to match. It can be understood that a new automation tool can also be directly registered in the module management module, so as to improve the convenience of tool registration.

In addition, as shown in FIG. 4 , in the case that the automated test tool provides support for running parameters, the global parameters are managed and used through the interface as shown in FIG. 4 .

The running and follow-up module 130 is configured to obtain the template attribute of the use case, call a corresponding tool to test the use case according to the template attribute, and record the test result.

In the exemplary embodiment of the present disclosure, after the template attribute of the test case is selected and defined, each test case may correspond to the template attribute. The operation management and follow-up modules can obtain the template attributes set for the test cases in the template management module, and determine the test cases according to the mapping relationship between the template attributes and the test cases. Further call the corresponding automation tool according to the template and test case, and execute the use case for testing through the automation tool. For example, for test cases that pass through repeated tests, QTP (HP QuickTest Professional software) can be called for testing; according to the attributes of the test cases, it can be used for web function test, web performance test, Java application function test, Java API test, etc. etc., you can call the QEngineAdventNet test tool. When virtual simulation of user operations for testing, it is necessary to automatically record, detect and play back the user's application operations, you can call the WinRunner test tool. During the testing process, the results of the use case testing are recorded in real time.

For example, as shown in the following table:

In addition, before the test case is actually tested by the automation tool, the automation tool can also be tested through the debugging interface provided by the automation tool, so as to ensure that the subsequent use case test can be carried out normally.

The report management module 140 is configured to display the test result according to the preset analysis standard.

In an exemplary embodiment of the present disclosure, the object analyzed by the report management module may be the test results of many test cases. The preset analysis standard can be from multiple perspectives, for example, it can analyze the proportion of various types of test cases, the test time-consuming, the success rate, the efficiency and so on. For example, a test plan may involve functional testing, boundary testing, exception testing, manual use cases and other types of test cases. The content of test results can be use case running results, logs and pictures.

Optionally, the test results can be displayed in various forms, such as pie charts and bar charts. For example, as shown in Figure 5, the pie chart can include three parts, the first part can be interface testing, the second part can be stress testing, and the third part can be manual use case testing.

In an embodiment of the present disclosure, an implementation manner of a templated use case testing system is also provided. The operation and follow-up module is used to:

classifying use cases according to their template attributes after responding to the triggering action;

The use cases are classified to include non-manual use cases and manual use cases.

Non-manual use cases are automated test cases, and all judgment verifications in this type of use case testing need to be scripted. The relationship between the test case steps needs to be related to ensure that the main function of the product is correct and complete; the manual test case can verify whether the function implementation of the current step is correct through artificial logic judgment. It can handle abnormal scenes well, and has a certain jumping ability to locate problems in detail.

In the exemplary embodiment of the present disclosure, after the user completes the start operation, the running and follow-up module can receive the start execution command, and classify the test cases according to their template attributes such as language codes or other elements. The classification results that can be obtained after classifying the use cases include non-manual use cases and manual use cases. The embodiment of the present disclosure does not limit the classification method, and different classification results can be obtained according to different classification methods.

In an embodiment of the present disclosure, an implementation manner of a templated use case testing system is also provided. The operation and follow-up module is used to:

In response to the trigger operation, at least one use case is tested; according to the template attribute of the non-manual use case, a corresponding tool is called for testing; the test progress is collected in real time, and the test result is recorded at the same time.

In an exemplary embodiment of the present disclosure, the corresponding tool is invoked according to the template attribute of the non-manual use case in the use case. The system automatically collects test results of non-manual use cases in real time.

In the testing process of manual use cases, the user is required to manually mark the execution and enter the results according to the steps or the description of the use case. The running and follow-up module may record the test results of the manual use case in response to the user input operation.

Further, in this example implementation, a templated use case testing method is also provided, as shown in FIG. 6 , the method includes:

Step S610, setting the template attribute of the use case in response to the setting operation;

Step S620, registering a tool, where the tool is used to execute the use case;

Step S630, obtaining the template attribute of the use case, and calling a corresponding tool according to the template attribute to test the use case and record the test result;

Step S640, displaying the test result according to the preset analysis standard.

Implementing the method of the embodiment of the present disclosure, the template management module is used to set the template attribute of the use case in response to the setting operation; the tool registration module is used to register the tool; the operation management and follow-up module is used to obtain the template attribute of the use case, According to the template attributes, the corresponding tools are called to test the use cases and record the test results; the report management module is used to display the test results according to the preset analysis standards. On the one hand, the platform is used to clearly manage the test, which reduces the difficulty of management; on the other hand, the whole process of the test is fully understood through each module, which is convenient for unified evaluation and measurement, and improves the ease of evaluation of the use case test.

In an exemplary embodiment of the present disclosure, a method for testing a templated use case is also provided. After the tool is registered for executing the steps of the use case, the method further includes:

The tool is tested to determine that the tool can be used for use case testing.

In an exemplary embodiment of the present disclosure, a method for testing a templated use case is also provided, wherein the template attribute of the use case is obtained, and a corresponding tool is called according to the template attribute to test the use case and record the test result; Classifying use cases according to template attributes of the use cases in response to the triggering operation;

The use cases are classified to include non-manual use cases and manual use cases.

In an exemplary embodiment of the present disclosure, a templated use case testing method is also provided, and the method further includes:

A new tool is registered in response to a user selection operation.

In an exemplary embodiment of the present disclosure, a method for testing a templated use case is also provided, wherein the operation management and follow-up module is configured to obtain the template attribute of the use case, and call a corresponding tool according to the template attribute to perform the test. Steps to test a use case and record the test results, including:

in response to triggering an action, test at least one use case;

According to the template attribute of the non-manual use case, call the corresponding tool for testing;

Collect test progress in real-time while recording test results.

In an exemplary embodiment of the present disclosure, a templated use case testing method is also provided, and the method further includes:

In response to the user input operation, the test results of the manual use case are recorded.

In an exemplary embodiment of the present disclosure, a method for testing a templated use case is also provided, and the step of displaying the test result by the report management module according to a preset analysis standard includes:

Statistical analysis is performed on the test results, and results of different test types are displayed and displayed in a unified manner. The test results include but are not limited to: use case running results, logs, and pictures.

The specific details of each step or unit in the above templated use case testing method have been described in detail in the respective embodiments of the corresponding templated use case testing system, and therefore are not repeated here.

It should be noted that although several modules or units of the apparatus for action performance are mentioned in the above detailed description, this division is not mandatory. Indeed, according to embodiments of the present disclosure, the features and functions of two or more modules or units described above may be embodied in one module or unit. Conversely, the features and functions of one module or unit described above may be further divided into multiple modules or units to be embodied.

Additionally, although the various steps of the methods of the present disclosure are depicted in the figures in a particular order, this does not require or imply that the steps must be performed in the particular order or that all illustrated steps must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step for execution, and/or one step may be decomposed into multiple steps for execution, and the like.

From the description of the above embodiments, those skilled in the art can easily understand that the exemplary embodiments described herein may be implemented by software, or may be implemented by software combined with necessary hardware. Therefore, the technical solutions according to the embodiments of the present disclosure may be embodied in the form of software products, and the software products may be stored in a non-volatile storage medium (which may be CD-ROM, U disk, mobile hard disk, etc.) or on the network , including several instructions to cause a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to an embodiment of the present disclosure.

In an exemplary embodiment of the present disclosure, a computer storage medium capable of implementing the above method is also provided. A program product capable of implementing the method described above in this specification is stored thereon. In some possible embodiments, various aspects of the present disclosure may also be implemented in the form of a program product including program code for causing the program product to run on a terminal device when the program product is run on a terminal device. The terminal device performs the steps according to various exemplary embodiments of the present disclosure described in the above-mentioned "Example Method" section of this specification.

Referring to FIG. 7 , a program product 700 for implementing the above method according to an embodiment of the present disclosure is described, which can adopt a portable compact disk read only memory (CD-ROM) and include program codes, and can be stored in a terminal device, For example running on a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

A computer readable signal medium may include a propagated data signal in baseband or as part of a carrier wave with readable program code embodied thereon. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A readable signal medium can also be any readable medium, other than a readable storage medium, that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any suitable medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages—such as Java, C++, etc., as well as conventional procedural Programming Language - such as the "C" language or similar programming language. The program code may execute entirely on the user computing device, partly on the user device, as a stand-alone software package, partly on the user computing device and partly on a remote computing device, or entirely on the remote computing device or server execute on. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (eg, using an Internet service provider business via an Internet connection).

In addition, in an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.

As will be appreciated by one skilled in the art, various aspects of the present disclosure may be implemented as a system, method or program product. Therefore, various aspects of the present disclosure can be embodied in the following forms: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, which may be collectively referred to herein as implementations "circuit", "module" or "system".

The electronic device 600 according to this embodiment of the present disclosure is described below with reference to FIG. 8 . The electronic device 800 shown in FIG. 8 is only an example, and should not impose any limitation on the function and scope of use of the embodiments of the present disclosure.

As shown in FIG. 8, electronic device 800 takes the form of a general-purpose computing device. Components of the electronic device 800 may include, but are not limited to, the above-mentioned at least one processing unit 810 , the above-mentioned at least one storage unit 820 , a bus 830 connecting different system components (including the storage unit 820 and the processing unit 810 ), and a display unit 840 .

Wherein, the storage unit stores program codes, and the program codes can be executed by the processing unit 810, so that the processing unit 810 executes various exemplary methods according to the present disclosure described in the above-mentioned “Exemplary Methods” section of this specification. Implementation steps. For example, the processing unit 810 may perform as shown in FIG. 6: step S610, setting the template attribute of the use case in response to the setting operation; step S620, registering a tool for executing the use case; Step S630: Obtain the template attribute of the use case, call a corresponding tool to test the use case according to the template attribute, and record the test result; Step S640, display the test result according to the preset analysis standard.

The storage unit 820 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 8201 and/or a cache storage unit 8202 , and may further include a read only storage unit (ROM) 8203 .

The storage unit 820 may also include a program/utility 8204 having a set (at least one) of program modules 8205 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, An implementation of a network environment may be included in each or some combination of these examples.

The bus 830 may be representative of one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local area using any of a variety of bus structures bus.

The electronic device 800 may also communicate with one or more external devices 900 (eg, keyboards, pointing devices, Bluetooth devices, etc.), with one or more devices that enable a user to interact with the electronic device 800, and/or with Any device (eg, router, modem, etc.) that enables the electronic device 800 to communicate with one or more other computing devices. Such communication may take place through input/output (I/O) interface 850 . Also, the electronic device 800 may communicate with one or more networks (eg, a local area network (LAN), a wide area network (WAN), and/or a public network such as the Internet) through a network adapter 860 . As shown, network adapter 860 communicates with other modules of electronic device 800 via bus 830 . It should be understood that, although not shown, other hardware and/or software modules may be used in conjunction with electronic device 800, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives and data backup storage systems.

From the description of the above embodiments, those skilled in the art can easily understand that the exemplary embodiments described herein may be implemented by software, or may be implemented by software combined with necessary hardware. Therefore, the technical solutions according to the embodiments of the present disclosure may be embodied in the form of software products, and the software products may be stored in a non-volatile storage medium (which may be CD-ROM, U disk, mobile hard disk, etc.) or on the network , including several instructions to cause a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to an embodiment of the present disclosure.

In addition, the above-mentioned figures are merely schematic illustrations of the processes included in the methods according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It is easy to understand that the processes shown in the above figures do not indicate or limit the chronological order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously in multiple modules, for example.

Other embodiments of the present disclosure will readily suggest themselves to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or techniques in the technical field not disclosed by the present disclosure . The specification and examples are to be regarded as exemplary only, with the true scope and spirit of the disclosure being indicated by the claims.

Claims (10)

1. A templated use case testing system, comprising: the system comprises a template management module, a tool registration module, an operation and follow-up module and a report management module:

the template management module is used for responding to setting operation and setting the template attribute of the use case;

the tool registration module is used for registering a tool, and the tool is used for executing the use case;

the operation and follow-up module is used for acquiring the template attribute of the use case, calling a corresponding tool according to the template attribute to perform use case test and recording a test result;

and the report management module is used for displaying the test result according to a preset analysis standard.

2. The templated use case testing system of claim 1, wherein the tool registration module is to:

after the tool is registered, the tool is tested to determine that the tool is available for use case testing.

3. The templated use case testing system of claim 1, wherein the run and follow-up module is configured to:

after responding to the trigger operation, classifying the use cases according to the template attributes of the use cases;

and classifying the use cases to obtain non-manual use cases and manual use cases.

4. The templated use case testing system of claim 1, wherein the template management module is further configured to:

and responding to the user selection operation, and registering a new tool.

5. The templated use case testing system of claim 3, wherein the run and follow-up module is to:

responding to the trigger operation, and testing at least one use case;

calling a corresponding tool to test according to the template attribute of the non-manual case;

and collecting the test progress in real time, and recording the test result.

6. The templated use case testing system of claim 3, wherein the run and follow-up module is to:

and responding to the user input operation, and recording the test result of the manual case.

7. The templated use case testing system of claim 1, wherein the report management module is to:

performing statistical analysis on test results, displaying different test type results, and performing unified integrated display, wherein the test results include but are not limited to: use case running results, logs and pictures.

8. A templated use case testing method, the method comprising:

setting the template attribute of the use case based on the response of the template management module to the setting operation;

registering a tool based on a tool registration module, wherein the tool is used for executing the use case;

acquiring template attributes of the use cases based on the operation and follow-up module, calling corresponding tools according to the template attributes to perform use case testing and recording testing results;

and displaying the test result based on a report management module according to a preset analysis standard.

9. A computer-readable medium, on which a computer program is stored which, when being executed by a processor, carries out the templated case testing method according to claim 8.

10. A terminal device, comprising:

one or more processors;

storage means for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement the templated use case testing method recited in claim 8.

Images