CN115080438B - Usability testing method and device, electronic equipment and storage medium - Google Patents
Usability testing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115080438B CN115080438B CN202210753663.5A CN202210753663A CN115080438B CN 115080438 B CN115080438 B CN 115080438B CN 202210753663 A CN202210753663 A CN 202210753663A CN 115080438 B CN115080438 B CN 115080438B
- Authority
- CN
- China
- Prior art keywords
- test
- target
- fault
- test point
- point
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 485
- 238000000034 method Methods 0.000 claims description 25
- 238000012544 monitoring process Methods 0.000 claims description 17
- 238000004590 computer program Methods 0.000 claims description 4
- 238000010998 test method Methods 0.000 abstract description 8
- 230000008569 process Effects 0.000 description 14
- 238000004891 communication Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000011990 functional testing Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 239000000725 suspension Substances 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 238000011056 performance test Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000011076 safety test Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides an availability test method, an availability test device, electronic equipment and a storage medium, which relate to the technical field of nonfunctional test, and are used for selecting a target test point from a plurality of test points to be tested in an acquired tested system; determining at least one system hierarchy associated with the target test point, wherein each system hierarchy includes at least one fault test type; configuring more than one number of fault test contents for each fault test type included in the system hierarchy; and further, based on each fault test content under each fault test type in each system level associated with the configured target test point, the target test point is tested one by one, and the test points to be tested in the tested system are thinned and the test execution steps are unified, so that the deviation of test results caused by different capabilities of execution staff is avoided, the usability problem can be found in time, and the availability of the tested system is ensured.
Description
Technical Field
The present application relates to the field of non-functional testing technologies, and in particular, to an availability testing method, an availability testing device, an electronic device, and a storage medium.
Background
With the development of IT technology, the concentration point of the nonfunctional test is not solely a performance test or a security test, and the importance of the usability test is gradually increased, and the usability refers to the degree to which a system, a product or a component can be operated and accessed when the system, the product or the component needs to be used according to the usability description mentioned in gb_t 25000.10-2016.
In the prior art, when a non-functional test is performed on a tested system, unified execution steps are not available, so that the execution of the usability test is different due to different capabilities of testers, and therefore, a test result is deviated, and a test problem cannot be found in time.
Disclosure of Invention
Accordingly, the present application aims to provide an availability testing method, an availability testing device, an electronic device and a storage medium, which can unify execution steps of an availability test, discover availability problems in time and guarantee availability of a tested system.
In a first aspect, an embodiment of the present application provides a usability testing method, including the steps of:
acquiring a plurality of test points to be tested in a tested system, and selecting a target test point from the plurality of test points;
determining at least one system level associated with the target test point from among a plurality of system levels of the system under test; wherein each system level associated with the target test point includes at least one fault test type;
configuring more than one number of fault test contents for each fault test type included in the system hierarchy;
and testing the target test points one by one based on each fault test content under each fault test type in each system level associated with the configured target test points.
In some embodiments, more than one number of fault test contents are configured for each fault test type included by the system hierarchy by:
for each fault test type included in the system hierarchy, more than one number of fault test contents are configured based on different test objectives for the target test point.
In some embodiments, the target test point is tested one by the following steps:
constructing a test point refinement table based on the selected target test points; the test point refinement table comprises the target test point name, a system level, a fault test type, fault test contents and a test purpose, wherein the system level, the fault test type, the fault test contents and the test purpose are determined based on the target test point;
and testing the target test points one by one according to the constructed fault test contents in the test point refinement table.
In some embodiments, the testing the target test points one by one according to the fault test content in the constructed test point refinement table includes the following steps:
configuring initial parameters of the target test points; wherein, the business of the target test point under the initial parameter is normal;
modifying initial parameters of the target test point, and simulating target fault test contents selected from a plurality of fault test contents of the target test point;
and monitoring whether the service of the target test point under the content of the target fault test is normal or not.
In some embodiments, the monitoring whether the service of the target test point under the target fault test content is normal includes the following steps:
constructing a test execution table based on fault test contents of target test points in the test point refinement table; the test execution table comprises a test step and a monitoring result aiming at each fault test content of the target test point;
and recording the result of whether the business of the target test point under the content of the target fault test is normal into the test point refinement table.
In some embodiments, the system under test partitions a system hierarchy based on a system architecture, the system hierarchy including one or more of an application layer, a platform layer, a data layer, an infrastructure layer.
In a second aspect, an embodiment of the present application provides an usability testing apparatus, including;
the system comprises an acquisition module, a test module and a test module, wherein the acquisition module is used for acquiring a plurality of test points to be tested in a tested system and selecting a target test point from the plurality of test points;
a determining module for determining at least one system level associated with the target test point from among a plurality of system levels of the system under test; wherein each system level associated with the target test point includes at least one fault test type;
a configuration module, configured to configure more than one number of fault test contents for each fault test type included in the system hierarchy;
and the test module is used for testing the target test points one by one based on each fault test content under each fault test type in each system level associated with the configured target test points.
In a third aspect, an embodiment of the present application provides an electronic device including: the system comprises a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, the processor and the memory are communicated through the bus when the electronic device runs, and the machine-readable instructions are executed by the processor to execute the steps of any one of the usability testing methods.
In a fourth aspect, embodiments of the present application provide a computer readable storage medium having a computer program stored thereon, which when executed by a processor performs the steps of any of the usability testing methods described above.
The application provides an availability test method, an availability test device, electronic equipment and a storage medium, wherein a target test point is selected from a plurality of test points to be tested in an acquired tested system; determining at least one system hierarchy associated with the target test point, wherein each system hierarchy includes at least one fault test type; configuring more than one number of fault test contents for each fault test type included in the system hierarchy; and further, based on each fault test content under each fault test type in each system level associated with the configured target test point, the target test point is tested one by one, and the test points to be tested in the tested system are thinned and the test execution steps are unified, so that the deviation of test results caused by different capabilities of execution staff is avoided, the usability problem can be found in time, and the availability of the tested system is ensured.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of an availability testing method according to an embodiment of the application;
FIG. 2 is a schematic flow chart of testing the target test points one by one according to an embodiment of the application;
FIG. 3 is a flow chart of monitoring whether the business of the target test point under the target fault test content is normal or not according to an embodiment of the application;
FIG. 4 is a block diagram illustrating an usability testing system according to an embodiment of the present application;
FIG. 5 is a block diagram of an electronic device according to an embodiment of the application;
FIG. 6 is a diagram illustrating a test point refinement representation constructed for an application cluster in accordance with one embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described with reference to the accompanying drawings in the embodiments of the present application, and it should be understood that the drawings in the present application are for the purpose of illustration and description only and are not intended to limit the scope of the present application. In addition, it should be understood that the schematic drawings are not drawn to scale. A flowchart, as used in this disclosure, illustrates operations implemented according to some embodiments of the present application. It should be understood that the operations of the flow diagrams may be implemented out of order and that steps without logical context may be performed in reverse order or concurrently. Moreover, one or more other operations may be added to or removed from the flow diagrams by those skilled in the art under the direction of the present disclosure.
In addition, the described embodiments are only some, but not all, embodiments of the application. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by a person skilled in the art without making any inventive effort, are intended to be within the scope of the present application.
It should be noted that the term "comprising" will be used in embodiments of the application to indicate the presence of the features stated hereafter, but not to exclude the addition of other features.
Functional testing and nonfunctional testing are often involved in the IT technology field. The functional test is a functional test according to requirements, and the nonfunctional test is a test aiming at wider quality problems, wherein the nonfunctional test comprises a load test, a pressure test, an expansibility test, a capacity test, a safety test, a consistency test, an availability test and the like. The usability is a combination of maturity (controlling the frequency of failures), fault tolerance and easy recovery (controlling the downtime after each failure occurs). Availability testing is therefore primarily aimed at verifying whether those mechanisms that guarantee the availability of the system are valid, and at the same time verifying the impact on the traffic during recovery from a control failure, in order to evaluate the availability of the system. In the prior art, when a tester performs usability tests, the tester performs the tests only according to personal ability, and the tester does not have a uniform test specification, so that deviation occurs in test results. Based on the above, the application provides an availability test method, an availability test device, electronic equipment and a storage medium, which can unify execution steps of an availability test, discover availability problems in time and guarantee availability of a tested system.
Referring to fig. 1 of the specification, in an embodiment, the method for testing usability provided by the present application includes the following steps:
s1, acquiring a plurality of test points to be tested in a tested system, and selecting a target test point from the plurality of test points;
s2, determining at least one system level associated with the target test point from a plurality of system levels of the tested system; wherein each system level associated with the target test point includes at least one fault test type;
s3, configuring more than one number of fault test contents for each fault test type included in the system level;
s4, testing the target test points one by one based on each fault test content under each fault test type in each system level associated with the configured target test points.
Therefore, in the application, through the steps S1-S4, each test point to be tested in the tested system is thinned, the specific fault test content to be carried out on each test point is defined, and then the corresponding test points are tested one by one according to the defined fault test content. Thereby realizing standardized execution of the availability test of the tested system.
Specifically, when the specific fault test content to be performed by the target test point is defined, the system level associated with the target test point, that is, the system level that can be affected by the test point during fault/normal operation, is determined first. In this embodiment, the system under test may be divided into system levels according to the system architecture, such as dividing the system under test into an application layer, a platform layer, a data layer, and an infrastructure layer.
It should be noted that there may be multiple system levels associated with the target test point. As in this embodiment, the target test point is an application cluster and the system level associated with the application cluster has an application layer, a platform layer, and an infrastructure layer.
In addition, in different system levels, since different types of faults exist in the target test point, different effects can be generated on the system level, and therefore, different fault test types need to be configured when the corresponding system level tests the test point. For example, the failure test type of the application layer associated with the application cluster includes a code class, a process class; the fault test types of the platform layer associated with the application cluster comprise container classes, and the fault test types of the infrastructure layer associated with the application cluster comprise server classes, network classes, hardware classes, machine room classes and region classes.
Further, each fault test type may be subdivided into more than one number of fault test contents, such as process class fault test types of an application layer associated with an application cluster, including three specific fault test contents of process suspension, process killing, and process stopping. In this embodiment, for each fault test type included in the system hierarchy, more than one number of fault test contents are configured based on different test objectives for the target test point. If the application cluster is tested for the fault test content of the process suspension under the process fault test type in the application layer, the purpose is to verify whether the application cluster switching is effective or not under the condition that the application process of a certain node is suspended; when testing the fault test content of process killing under the process type fault test type in the application layer aiming at the application cluster, the purpose is to verify whether the application cluster switching is effective or not under the condition that the application process of a certain node is killed; when testing the fault test content of the process stop under the process fault test type in the application layer aiming at the application cluster, the purpose is to verify whether the application cluster switching is effective or not under the condition that the application process of a certain node is stopped.
Meanwhile, in order to better realize standardized execution of the availability test of the tested system, a test point refinement table can be constructed for fault test contents to be carried out on the selected target test points, and then the target test points are tested one by one according to the refined fault test contents according to the constructed test point refinement table. The built test point refinement table comprises a target test point name, a system level determined based on the target test point, a fault test type, fault test contents and a test purpose. In this embodiment, the test point refinement table built for the application clusters is seen in fig. 6 of the specification.
Referring to fig. 2 of the specification, the testing the target test points one by one according to the fault test content in the constructed test point refinement table includes the following steps:
s401, configuring initial parameters of the target test points; wherein, the business of the target test point under the initial parameter is normal;
s402, modifying initial parameters of the target test point, and simulating target fault test contents selected from a plurality of fault test contents of the target test point;
s403, monitoring whether the service of the target test point under the target fault test content is normal or not;
s404, restoring the initial parameters of the target test points, and monitoring whether the service of the target test points under the initial parameters is normal or not after the initial parameters of the target test points are restored.
In this embodiment, taking an example when testing the fault test content of "method return timeout" under the code fault test type in the application layer for the application cluster, firstly checking whether the configuration of the application cluster environment is completed and whether the selected service script is ready to be completed, and after the completion, initiating service pressure by using a press, namely configuring initial parameters of the application cluster, wherein the application cluster distributes the service to each node uniformly, and the service is normal; then modifying the initial parameters of the application cluster, simulating a method returned by the node 1 to be overtime, checking whether the transaction is correctly returned, whether the nodes are distributed in an equalizing mode, whether the fault node is switched, and recovering the normal service time after the switching; and finally, restoring the initial parameters of the application cluster, and checking whether the application cluster distributes the service to each node in an equalizing way and whether the transaction is correct.
Further, referring to fig. 3 of the specification, in this example, monitoring whether the service of the target test point under the target fault test content is normal includes the following steps:
s4031, constructing a test execution table based on fault test contents of target test points in the test point refinement table; the test execution table comprises a test step and a monitoring result aiming at each fault test content of the target test point;
s4032, inputting the result of whether the business of the target test point under the content of the target fault test is normal into the test point refinement table.
Therefore, the corresponding fault test contents are tested according to the constructed test execution table, and the real result of the target test point under the target fault test contents is recorded, so that the standardized execution of the availability test of the tested system can be further realized.
The application provides an availability test method, which is used for determining a system level associated with a target test point to be tested in a tested system, wherein each system level at least comprises a fault test type; configuring more than one number of fault test contents for each fault test type included in the system hierarchy; and then, testing the target test points one by one based on each configured fault test content, so that the test points to be tested in the tested system are thinned, the test execution steps are unified, the phenomenon that test results deviate due to different capabilities of executors is avoided, the usability problem can be found in time, and the availability of the tested system is ensured.
Based on the same inventive concept, the embodiment of the present application further provides an availability test system, and since the principle of solving the problem by the device in the embodiment of the present application is similar to that of the above-mentioned availability test method in the embodiment of the present application, the implementation of the device may refer to the implementation of the method, and the repetition is omitted.
As shown in fig. 4 of the specification, the present application further provides an usability testing apparatus, including:
an obtaining module 401, configured to obtain a plurality of test points to be tested in a tested system, and select a target test point from the plurality of test points;
a determining module 402, configured to determine at least one system hierarchy associated with the target test point from a plurality of system hierarchies of the system under test; wherein each system level associated with the target test point includes at least one fault test type; the tested system divides a system level based on a system architecture, wherein the system level comprises one or more of an application layer, a platform layer, a data layer and an infrastructure layer;
a configuration module 403, configured to configure more than one number of fault test contents for each fault test type included in the system hierarchy;
and the test module 404 is configured to test the target test points one by one based on each fault test content under each fault test type in each system level associated with the configured target test points.
In some embodiments, the configuration module 403 configures more than one number of fault test contents for each fault test type included in the system hierarchy, including:
for each fault test type included in the system hierarchy, more than one number of fault test contents are configured based on different test objectives for the target test point.
In some embodiments, the test module 404 tests the target test points one by one, including:
constructing a test point refinement table based on the selected target test points; the test point refinement table comprises the target test point name, a system level, a fault test type, fault test contents and a test purpose, wherein the system level, the fault test type, the fault test contents and the test purpose are determined based on the target test point;
and testing the target test points one by one according to the constructed fault test contents in the test point refinement table.
In some embodiments, the testing module 404 tests the target test points one by one according to the fault test content in the constructed test point refinement table, including:
configuring initial parameters of the target test points; wherein, the business of the target test point under the initial parameter is normal;
modifying initial parameters of the target test point, and simulating target fault test contents selected from a plurality of fault test contents of the target test point;
monitoring whether the service of the target test point under the content of the target fault test is normal or not;
restoring the initial parameters of the target test points, and monitoring whether the service of the target test points under the initial parameters is normal or not after the initial parameters of the target test points are restored.
In some embodiments, the test module 404 monitors whether the service of the target test point under the target fault test content is normal, including:
constructing a test execution table based on fault test contents of target test points in the test point refinement table; the test execution table comprises a test step and a monitoring result aiming at each fault test content of the target test point;
and recording the result of whether the business of the target test point under the content of the target fault test is normal into the test point refinement table.
The usability testing device provided by the application selects a target testing point from a plurality of testing points required to be tested in an acquired tested system; determining at least one system hierarchy associated with the target test point, wherein each system hierarchy includes at least one fault test type; configuring more than one number of fault test contents for each fault test type included in the system hierarchy; and further, based on each fault test content under each fault test type in each system level associated with the configured target test point, the target test point is tested one by one, and the test points to be tested in the tested system are thinned and the test execution steps are unified, so that the deviation of test results caused by different capabilities of execution staff is avoided, the usability problem can be found in time, and the availability of the tested system is ensured.
Based on the same concept of the present application, fig. 5 of the present disclosure shows a structure of an electronic device 500 according to an embodiment of the present application, where the electronic device 500 includes: at least one processor 501, at least one network interface 504 or other user interface 503, memory 505, at least one communication bus 502. The communication bus 502 is used to enable connected communications between these components. The electronic device 500 optionally includes a user interface 503 including a display (e.g., a touch screen, LCD, CRT, holographic imaging (Holographic) or projection (Projector), etc.), a keyboard or pointing device (e.g., a mouse, trackball, touch pad or touch screen, etc.).
Memory 505 may include read only memory and random access memory and provides instructions and data to processor 501. A portion of the memory 505 may also include non-volatile random access memory (NVRAM).
In some implementations, the memory 505 stores the following elements, executable modules or data structures, or a subset thereof, or an extended set thereof:
an operating system 5051 containing various system programs for implementing various basic services and handling hardware-based tasks;
the application module 5052 includes various application programs such as a desktop (desktop), a Media Player (Media Player), a Browser (Browser), etc., for implementing various application services.
In the embodiment of the present application, the processor 501 is configured to execute steps in an availability test method, for example, by calling a program or an instruction stored in the memory 505, so that the execution steps of the availability test can be unified, the availability problem can be found in time, and the availability of the tested system is ensured.
The application also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor performs steps as in the usability test method.
In particular, the storage medium can be a general-purpose storage medium, such as a removable disk, a hard disk, or the like, on which a computer program can be executed to perform the usability test method described above.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The above-described apparatus embodiments are merely illustrative, for example, the division of units is merely a logical function division, and there may be other manners of division in actual implementation, and for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some communication interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments provided in the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Finally, it should be noted that: the above examples are only specific embodiments of the present application for illustrating the technical solution of the present application, but not for limiting the scope of the present application, and although the present application has been described in detail with reference to the foregoing examples, it will be understood by those skilled in the art that the present application is not limited thereto: any person skilled in the art may modify or easily conceive of the technical solution described in the foregoing embodiments, or perform equivalent substitution of some of the technical features, while remaining within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the corresponding technical solutions. Are intended to be encompassed within the scope of the present application. Therefore, the protection scope of the application is subject to the protection scope of the claims.
Claims (6)
1. A usability testing method, the method comprising the steps of:
acquiring a plurality of test points to be tested in a tested system, and selecting a target test point from the plurality of test points;
determining at least one system level associated with the target test point from among a plurality of system levels of the system under test; wherein the system levels comprise an application layer, a platform layer, a data layer and an infrastructure layer, the associated at least one system level is a system level affected by the failure/normal operation of the target test point, and each system level associated with the target test point comprises at least one failure test type;
configuring more than one number of fault test contents based on different test purposes for the target test point for each fault test type included in the system hierarchy;
based on each fault test content under each fault test type in each system level associated with the configured target test point, testing the target test point one by utilizing a test point refinement table, testing corresponding fault test content according to a constructed test execution table, and recording the real result of the target test point under the target fault test content so as to monitor whether the service of the target test point under the target fault test content is normal or not by utilizing the test execution table;
the method comprises the steps of utilizing a test point refinement table to test target test points one by one, and constructing the test point refinement table based on the selected target test points; the test point refinement table comprises the target test point name, a system level, a fault test type, fault test contents and a test purpose, wherein the system level, the fault test type, the fault test contents and the test purpose are determined based on the target test point; testing the target test points one by one according to the constructed fault test contents in the test point refinement table;
the method comprises the steps that a target test point is tested one by one according to fault test contents in a built test point refinement table, and initial parameters of the target test point are configured; wherein, the business of the target test point under the initial parameter is normal; modifying initial parameters of the target test point, and simulating target fault test contents selected from a plurality of fault test contents of the target test point; and monitoring whether the service of the target test point under the content of the target fault test is normal or not.
2. The usability testing method of claim 1, wherein the monitoring the target test point for normal traffic under the target failure test content further comprises:
restoring the initial parameters of the target test points, and monitoring whether the service of the target test points under the initial parameters is normal or not after the initial parameters of the target test points are restored.
3. The usability testing method according to claim 1 or 2, wherein the monitoring of whether the traffic of the target test point under the target failure test content is normal by using the test execution table comprises the steps of:
constructing a test execution table based on fault test contents of target test points in the test point refinement table; the test execution table comprises a test step and a monitoring result aiming at each fault test content of the target test point;
and recording the result of whether the business of the target test point under the content of the target fault test is normal into the test point refinement table.
4. An usability testing apparatus comprising:
the system comprises an acquisition module, a test module and a test module, wherein the acquisition module is used for acquiring a plurality of test points to be tested in a tested system and selecting a target test point from the plurality of test points;
a determining module for determining at least one system level associated with the target test point from among a plurality of system levels of the system under test; wherein the system hierarchy includes an application layer, a platform layer, a data layer, and an infrastructure layer, each system hierarchy associated with the target test point including at least one fault test type;
a configuration module, configured to configure one or more numbers of fault test contents based on different test purposes for the target test point for each fault test type included in the system hierarchy;
the test module is used for testing the target test points one by utilizing a test point refinement table based on each fault test content under each fault test type in each system level associated with the configured target test points, testing the corresponding fault test content according to the constructed test execution table and recording the real result of the target test points under the target fault test content so as to monitor whether the service of the target test points under the target fault test content is normal or not by utilizing the test execution table;
the method comprises the steps of utilizing a test point refinement table to test target test points one by one, and constructing the test point refinement table based on the selected target test points; the test point refinement table comprises the target test point name, a system level, a fault test type, fault test contents and a test purpose, wherein the system level, the fault test type, the fault test contents and the test purpose are determined based on the target test point; testing the target test points one by one according to the constructed fault test contents in the test point refinement table;
the method comprises the steps that a target test point is tested one by one according to fault test contents in a built test point refinement table, and initial parameters of the target test point are configured; wherein, the business of the target test point under the initial parameter is normal; modifying initial parameters of the target test point, and simulating target fault test contents selected from a plurality of fault test contents of the target test point; and monitoring whether the service of the target test point under the content of the target fault test is normal or not.
5. An electronic device, comprising: a processor, a memory and a bus, said memory storing machine readable instructions executable by said processor, said processor and said memory communicating over the bus when the electronic device is running, said machine readable instructions when executed by said processor performing the steps of the usability testing method of any of claims 1 to 3.
6. A computer-readable storage medium, characterized in that it has stored thereon a computer program which, when executed by a processor, performs the steps of the usability testing method according to any of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210753663.5A CN115080438B (en) | 2022-06-28 | 2022-06-28 | Usability testing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210753663.5A CN115080438B (en) | 2022-06-28 | 2022-06-28 | Usability testing method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115080438A CN115080438A (en) | 2022-09-20 |
| CN115080438B true CN115080438B (en) | 2023-11-28 |
Family
ID=83256638
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210753663.5A Active CN115080438B (en) | 2022-06-28 | 2022-06-28 | Usability testing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115080438B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105930260A (en) * | 2015-12-23 | 2016-09-07 | ***股份有限公司 | Method and apparatus for testing system availability |
| CN111953560A (en) * | 2020-07-17 | 2020-11-17 | 苏州浪潮智能科技有限公司 | Distributed cluster fault testing method and device |
| CN113157577A (en) * | 2021-04-27 | 2021-07-23 | 中国工商银行股份有限公司 | PaaS cloud platform fault testing method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2698680B1 (en) * | 2012-08-13 | 2015-06-10 | Uptime Engineering GmbH | Method for testing the reliability of complex systems |
-
2022
- 2022-06-28 CN CN202210753663.5A patent/CN115080438B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105930260A (en) * | 2015-12-23 | 2016-09-07 | ***股份有限公司 | Method and apparatus for testing system availability |
| CN111953560A (en) * | 2020-07-17 | 2020-11-17 | 苏州浪潮智能科技有限公司 | Distributed cluster fault testing method and device |
| CN113157577A (en) * | 2021-04-27 | 2021-07-23 | 中国工商银行股份有限公司 | PaaS cloud platform fault testing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115080438A (en) | 2022-09-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10956308B2 (en) | Test case reduction for code regression testing | |
| CN111651366B (en) | SDK test method, device, equipment and storage medium | |
| US20080205286A1 (en) | Test system using local loop to establish connection to baseboard management control and method therefor | |
| US20100115496A1 (en) | Filter generation for load testing managed environments | |
| US8225142B2 (en) | Method and system for tracepoint-based fault diagnosis and recovery | |
| CN110765018B (en) | Automatic interface testing method and equipment | |
| CN106357449A (en) | zedis distributed type buffer method | |
| CN110554965A (en) | automated fuzz testing method, related equipment and computer readable storage medium | |
| JP2017201470A (en) | Setting support program, setting support method, and setting support device | |
| CN115328752B (en) | Cluster simulation method and system for Kubernetes control plane test | |
| US7673178B2 (en) | Break and optional hold on failure | |
| CN110007921A (en) | A kind of code dissemination method and device | |
| CN112799953A (en) | Interface testing method and device, computer equipment and storage medium | |
| Schirgi et al. | Quality assurance for microservice architectures | |
| US9501390B1 (en) | Enhancing automated mobile application testing | |
| CN114168471A (en) | Test method, test device, electronic equipment and storage medium | |
| CN115080438B (en) | Usability testing method and device, electronic equipment and storage medium | |
| CN111752601A (en) | Data configuration method, device and system, electronic equipment and storage medium thereof | |
| CN115733741A (en) | Abnormal scene testing method and device for system to be tested | |
| CN114650211A (en) | Fault repairing method, device, electronic equipment and computer readable storage medium | |
| CN114328275A (en) | System testing method, device, computer equipment and storage medium | |
| CN114201413A (en) | Automatic testing method and system and electronic equipment | |
| CN108845932B (en) | Unit testing method and device of network library, storage medium and terminal | |
| CN115437903A (en) | Interface test method, device, apparatus, storage medium, and program | |
| US8918677B1 (en) | Methods and apparatus for performing data validation in a network management application |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |